vme: Adding Fake VME driver
This patch introduces a fake VME bridge driver. This driver currently emulates a subset of the VME bridge functionality. This allows some VME subsystem development and even some VME device driver development to be carried out in the absence of a proper VME bus. Signed-off-by: Martyn Welch <martyn@welchs.me.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
050c3d52cc
commit
658bcdae9c
|
@ -13,3 +13,11 @@ config VME_TSI148
|
|||
help
|
||||
If you say Y here you get support for the Tundra TSI148 VME bridge
|
||||
chip.
|
||||
|
||||
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).
|
||||
|
|
|
@ -1,2 +1,3 @@
|
|||
obj-$(CONFIG_VME_CA91CX42) += vme_ca91cx42.o
|
||||
obj-$(CONFIG_VME_TSI148) += vme_tsi148.o
|
||||
obj-$(CONFIG_VME_FAKE) += vme_fake.o
|
||||
|
|
File diff suppressed because it is too large
Load Diff
Loading…
Reference in New Issue