public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brice Goglin <brice@myri.com>
To: Greg KH <gregkh@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: AMD 8131 MSI quirk called too late, bus_flags not inherited ?
Date: Mon, 15 May 2006 23:11:33 +0200	[thread overview]
Message-ID: <4468EE85.4000500@myri.com> (raw)

Hi Greg,

While looking at the MSI detection, I noticed that the AMD 8131 quirk
(quirk_amd_8131_ioapic) is defined as FINAL and thus executed after the
PCI hierarchy is scanned. So it looks like the bus_flags won't be
inherited at all. If there's a bridge behind the 8131, then the devices
behind this bridge won't see the bus flags and thus might try to enable
MSI anyway.
I tried to change the AMD 8131 quirk to HEADER so that it is executed
during PCI scanning. But, I don't get its message in dmesg anymore. Any
idea?

Thanks,
Brice


             reply	other threads:[~2006-05-15 21:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-15 21:11 Brice Goglin [this message]
2006-05-18 15:54 ` AMD 8131 MSI quirk called too late, bus_flags not inherited ? Greg KH
2006-05-21 10:16   ` Michael S. Tsirkin
2006-05-21 10:58     ` Brice Goglin
2006-05-21 12:17       ` Michael S. Tsirkin
2006-05-21 12:31         ` Brice Goglin
2006-05-21 13:10           ` Michael S. Tsirkin
2006-05-21 13:24             ` Brice Goglin
2006-05-23  4:19               ` Greg KH
2006-05-23  7:05                 ` Brice Goglin
2006-05-24 16:59                 ` Michael S. Tsirkin
2006-05-24 17:05                   ` Rajesh Shah
2006-05-21 13:29           ` Michael S. Tsirkin
     [not found] <fa.WOQy7TVxeMkzxI+BbQP2Wqi34A0@ifi.uio.no>
     [not found] ` <fa.7RUPmW8q906KfAmuRItEvwbAUvg@ifi.uio.no>
2006-05-21 19:19   ` Dave Olson
     [not found] <fa.qrx8XYAhsFvMnCfipnnEkuNPFSA@ifi.uio.no>
     [not found] ` <fa.hVNDQ4A/sPeiQKqlsb6JDQFEpLE@ifi.uio.no>
2006-05-23  7:32   ` Dave Olson

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=4468EE85.4000500@myri.com \
    --to=brice@myri.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.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