CONFIG_VME_BUS: VME bridge support

General informations

The Linux kernel configuration item CONFIG_VME_BUS has multiple definitions:

VME bridge support found in drivers/staging/vme_user/Kconfig

The configuration item CONFIG_VME_BUS:

• prompt: VME bridge support
• type: bool
• depends on: CONFIG_PCI
• defined in drivers/staging/vme_user/Kconfig
• found in Linux kernels: 6.0–6.12
• modules built: vme, vme

Help text

Enable support for VME (VersaModular Eurocard bus) bridge modules. The bridge allows connecting VME devices to systems with existing interfaces (like USB or PCI) by means of translating VME protocol operations.

Note that this only enables the bridge framework. You'll also likely want to enable driver for specific bridge device you have to actually use it. If unsure, say N.

VME bridge support found in drivers/vme/Kconfig

The configuration item CONFIG_VME_BUS:

• prompt: VME bridge support
• type: bool
• depends on: CONFIG_PCI
• defined in drivers/vme/Kconfig
• found in Linux kernels: 3.14–3.19, 4.0–4.20, 5.0–5.19, 5.19+HEAD
• modules built: vme, vme

Help text

If you say Y here you get support for the VME bridge Framework.

VME bridge support found in drivers/vme/Kconfig

The configuration item CONFIG_VME_BUS:

• prompt: VME bridge support
• type: tristate
• depends on: CONFIG_PCI
• defined in drivers/vme/Kconfig
• found in Linux kernels: 3.5–3.13
• modules built: vme, vme

Help text

If you say Y here you get support for the VME bridge Framework.

VME bridge support found in drivers/staging/vme/Kconfig

The configuration item CONFIG_VME_BUS:

• prompt: VME bridge support
• type: tristate
• depends on: CONFIG_PCI
• defined in drivers/staging/vme/Kconfig
• found in Linux kernels: 2.6.32–2.6.39, 3.0–3.4
• modules built: vme, vme

Help text

If you say Y here you get support for the VME bridge Framework.

Hardware

PCI

Numeric ID (from LKDDb) and names (from pci.ids) of recognized devices:

• vendor: 10e3 ("Tundra Semiconductor Corp."), device: 0000 ("CA91C042 [Universe]")
• vendor: 10e3 ("Tundra Semiconductor Corp."), device: 0000 ("CA91C042 [Universe]")
• vendor: 10e3 ("Tundra Semiconductor Corp."), device: 0148 ("Tsi148 [Tempe]")
• vendor: 10e3 ("Tundra Semiconductor Corp."), device: 0148 ("Tsi148 [Tempe]")
• vendor: 10e3 ("Tundra Semiconductor Corp."), device: 0148 ("Tsi148 [Tempe]")
• vendor: 114a ("VMIC"), device: 0004
• vendor: 114a ("VMIC"), device: 0004

LKDDb

Raw data from LKDDb:

• lkddb module vme CONFIG_VME_BUS : drivers/staging/vme/Kconfig : "VME bridge support" # in 2.6.32–2.6.39, 3.0–3.4
• lkddb module vme CONFIG_VME_BUS : drivers/vme/Kconfig : "VME bridge support" # in 3.5–3.13
• lkddb pci 10e3 0000 .... .... ...... : CONFIG_STAGING CONFIG_VME_BUS CONFIG_VME_CA91CX42 : drivers/staging/vme/bridges/vme_ca91cx42.c # in 2.6.32–2.6.37
• lkddb pci 10e3 0000 .... .... ...... : CONFIG_VME_BUS CONFIG_VME_CA91CX42 : drivers/vme/bridges/vme_ca91cx42.c # in 3.14–3.19, 4.0–4.20, 5.0–5.19, 5.19+HEAD
• lkddb pci 10e3 0148 .... .... ...... : CONFIG_STAGING CONFIG_VME_BUS CONFIG_VME_TSI148 : drivers/staging/vme/bridges/vme_tsi148.c # in 2.6.32–2.6.37
• lkddb pci 10e3 0148 .... .... ...... : CONFIG_STAGING CONFIG_VME_BUS CONFIG_VME_TSI148 : drivers/staging/vme_user/vme_tsi148.c # in 6.0–6.12
• lkddb pci 10e3 0148 .... .... ...... : CONFIG_VME_BUS CONFIG_VME_TSI148 : drivers/vme/bridges/vme_tsi148.c # in 3.14–3.19, 4.0–4.20, 5.0–5.19, 5.19+HEAD
• lkddb pci 114a 0004 .... .... ...... : CONFIG_STAGING CONFIG_VME_BUS CONFIG_VMIVME_7805 : drivers/staging/vme/boards/vme_vmivme7805.c # in 2.6.34–2.6.39, 3.0
• lkddb pci 114a 0004 .... .... ...... : CONFIG_VME_BUS CONFIG_VMIVME_7805 : drivers/vme/boards/vme_vmivme7805.c # in 3.14–3.19, 4.0–4.20, 5.0–5.19, 5.19+HEAD

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)
• The Linux PCI ID Repository.

Automatic links from Google (and ads)

Custom Search

Popular queries: