Commit e3fac10e authored by Andrew Morton's avatar Andrew Morton Committed by Linus Torvalds

[PATCH] clarify MSI requirements in Kconfig

From: Martine Silbermann <Martine.Silbermann@hp.com>

Having spent a non trivial amount of time trying to pull in the code to
enable MSI, I would suggest that a clear indication in Kconfig that MSI
requires CONFIG_PCI_USE_VECTOR would be very helpful.  Also since the MSI
code was integrated into 2.6.1 I've updated the comment that called for
installing the MSI patch.
parent d79efc1e
......@@ -1094,7 +1094,7 @@ config PCI_DIRECT
default y
config PCI_USE_VECTOR
bool "Vector-based interrupt indexing"
bool "Vector-based interrupt indexing (MSI)"
depends on X86_LOCAL_APIC && X86_IO_APIC
default n
help
......@@ -1104,11 +1104,11 @@ config PCI_USE_VECTOR
1) Support MSI implementation.
2) Support future IOxAPIC hotplug
Note that this enables MSI, Message Signaled Interrupt, on all
MSI capable device functions detected if users also install the
MSI patch. Message Signal Interrupt enables an MSI-capable
hardware device to send an inbound Memory Write on its PCI bus
instead of asserting IRQ signal on device IRQ pin.
Note that this allows the device drivers to enable MSI, Message
Signaled Interrupt, on all MSI capable device functions detected.
Message Signal Interrupt enables an MSI-capable hardware device to
send an inbound Memory Write on its PCI bus instead of asserting
IRQ signal on device IRQ pin.
If you don't know what to do here, say N.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment