From: Greg KH <greg@kroah.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
stathis@ims.tuwien.ac.at, l.schimmer@cgv.tugraz.at
Subject: Re: MMCONFIG broken on Tyan K8WE [was: Fusion MPT driver does not detect controller]
Date: Tue, 21 Feb 2006 11:18:57 -0800 [thread overview]
Message-ID: <20060221191857.GA6610@kroah.com> (raw)
In-Reply-To: <200602211208.38777.bjorn.helgaas@hp.com>
On Tue, Feb 21, 2006 at 12:08:38PM -0700, Bjorn Helgaas wrote:
> This 2.6.15.4 bug is languishing in bugzilla:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=6060
>
> Devices behind a PCI-X bridge are invisible unless the submitter
> uses "pci=nommconf". The devices worked in 2.6.13.5, because we
> always disabled mmconfig for AMD CPUs then. But now it's broken.
It should have been assigned to the pci subsystem, then it would not be
languishing :)
I've fixed that.
We have a patch in the latest -mm that should take care of this issue.
thanks,
greg k-h
prev parent reply other threads:[~2006-02-21 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 19:08 MMCONFIG broken on Tyan K8WE [was: Fusion MPT driver does not detect controller] Bjorn Helgaas
2006-02-21 19:18 ` Greg KH [this message]
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=20060221191857.GA6610@kroah.com \
--to=greg@kroah.com \
--cc=bjorn.helgaas@hp.com \
--cc=l.schimmer@cgv.tugraz.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=stathis@ims.tuwien.ac.at \
/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