blob: 8e5df6ce36e8f9182627d16cf1e9671aac061524 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
# SPDX-License-Identifier: GPL-2.0
menuconfig VME_BUS
bool "VME bridge support"
depends on PCI
help
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.
if VME_BUS
comment "VME Bridge Drivers"
config VME_TSI148
tristate "Tundra TSI148 VME bridge support"
depends on HAS_DMA
help
If you say Y here you get support for the Tundra TSI148 VME-to-PCI/X
bridge chip (and pin-compatible clones).
TSI148 is a high-performant, 2eSST and VME64-compliant VME-to-PCI/X
interconnect bridge with support for PCI and PCI-X bus interface.
It is primarily used in industrial and embedded systems.
To compile this driver as a module, say M - the module will be
called vme_tsi148. If unsure, say N.
config VME_FAKE
tristate "Fake"
help
If you say Y here you get support for the fake VME bridge. This
provides a virtualised VME Bus for devices with no VME bridge. This
is mainly useful for VME development (in the absence of VME
hardware).
comment "VME Device Drivers"
config VME_USER
tristate "VME user space access driver"
help
If you say Y here you want to be able to access a limited number of
VME windows in a manner at least semi-compatible with the interface
provided with the original driver at <http://www.vmelinux.org/>.
To compile this driver as a module, choose M here. The module will
be called vme_user. If unsure, say N.
endif
|
