From: Ilia Mirkin <imirkin@alum.mit.edu>
To: linux-pci@vger.kernel.org
Cc: "nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
brian.johnathan.b@gmail.com
Subject: How to check for proper MSI support?
Date: Wed, 2 Jul 2014 23:20:52 -0400 [thread overview]
Message-ID: <CAKb7UviGCtebGwyHbXRLZhDOiDAez+eKkxPe9jz5kc-3R1kUvQ@mail.gmail.com> (raw)
Hello,
A user (cc'd) reported that nouveau's enabling of MSI causes the card
to not work on his setup [1]. I think the situation is that MSI is
just not supported by the underlying motherboard, even though the
card, and probably bridge, support it just fine. It's a very old
board. The nouveau code does:
pmc->use_msi = pci_enable_msi(device->pdev) == 0;
Does it need to do more checking than that before trying to enable MSI
on the device? Could it be that the linux pci subsystem is missing on
inheriting MSI capabilities somewhere?
Thanks,
-ilia
[1]
00:00.0 Host bridge [0600]: Intel Corporation 430FX - 82437FX TSC
[Triton I] [8086:122d] (rev 01)
Flags: bus master, medium devsel, latency 64
00:0e.0 PCI bridge [0604]: PLX Technology, Inc. PEX8112 x1 Lane PCI
Express-to-PCI Bridge [10b5:8112] (rev aa) (prog-if 00 [Normal
decode])
Flags: bus master, 66MHz, medium devsel, latency 66
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000f000-0000ffff
Memory behind bridge: f5e00000-fbffffff
Prefetchable memory behind bridge: d5d00000-f5dfffff
Capabilities: [40] Power Management version 2
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [60] Express PCI/PCI-X to PCI-Express Bridge, MSI 00
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96
[GeForce 9400 GT] [10de:0641] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Jaton Corp Device [1b13:0641]
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at f8000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at fc80 [size=128]
[virtual] Expansion ROM at d5d00000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [b4] Vendor Specific Information: Len=14 <?>
Kernel driver in use: nouveau
next reply other threads:[~2014-07-03 3:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 3:20 Ilia Mirkin [this message]
2014-07-03 5:58 ` How to check for proper MSI support? Yijing Wang
2014-07-04 0:40 ` Brian Becker
[not found] ` <CALhae2jRz8hL0bwySAbP7r+vJGOG5aif4GA_Yjp0inGAwz5JEA@mail.gmail.com>
2014-07-04 2:35 ` Yijing Wang
2014-07-04 2:43 ` Ilia Mirkin
2014-07-04 3:09 ` Yijing Wang
2014-07-04 3:30 ` Ilia Mirkin
2014-07-04 3:56 ` Yijing Wang
2014-07-04 4:32 ` Ilia Mirkin
2014-07-04 5:59 ` Yijing Wang
2014-07-04 6:26 ` Brian Becker
2014-07-04 7:01 ` Yijing Wang
2014-07-05 22:21 ` Bjorn Helgaas
2014-07-05 23:04 ` Brian Becker
2014-07-04 2:45 ` Brian Becker
2014-07-04 3:13 ` Yijing Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKb7UviGCtebGwyHbXRLZhDOiDAez+eKkxPe9jz5kc-3R1kUvQ@mail.gmail.com \
--to=imirkin@alum.mit.edu \
--cc=brian.johnathan.b@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).