comment "VME Bridge Drivers" config VME_CA91CX42 tristate "Universe II" depends on VIRT_TO_BUS help If you say Y here you get support for the Tundra CA91C142 (Universe II) VME bridge chip. config VME_TSI148 tristate "Tempe" depends on HAS_DMA 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). tory'/>
summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorJan Beulich <JBeulich@suse.com>2017-01-23 08:12:19 -0700
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2017-01-23 13:27:41 -0500
commitb32728ffef7f233dbdabb3f11814bdf692aaf501 (patch)
tree5bf0326545d0c4525a43f3c50cfcdef09f0baa88 /drivers
parentd61b7f972dab2a7d187c38254845546dfc8eed85 (diff)
xen-blkfront: feature flags handling adjustments
Don't truncate the "feature-persistent" value read from xenstore: Any non-zero value is supposed to enable the feature, just like is already being done for feature_secdiscard. Just like the other feature_* fields, feature_flush and feature_fua are boolean flags, and hence fit well into a single bit. Keep all bit fields together to limit gaps. Signed-off-by: Jan Beulich <jbeulich@suse.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'drivers')