From: Greg KH <gregkh@suse.de>
To: Andi Kleen <ak@suse.de>
Cc: Greg KH <gregkh@suse.de>,
len.brown@intel.com, acpi-devel@lists.sourceforge.net,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 02/04] PCI: use the MCFG table to properly access pci devices (i386)
Date: Wed, 15 Jun 2005 13:21:58 -0700 [thread overview]
Message-ID: <20050615202158.GC31022@kroah.com> (raw)
In-Reply-To: <20050615190338.GT11898@wotan.suse.de>
On Wed, Jun 15, 2005 at 09:03:38PM +0200, Andi Kleen wrote:
> > > For those you would have bus->ops pointing to the old port code,
> > > for the others to the mmconfig code.
> >
> > Well, for that, I'll have to set the bus ops when they are discovered.
> > So the same callback I mentioned can be used for that (due to the need
> > to check the ranges in the MCFG table). I'll work on that too.
> >
> > Does the K8 box just not have MCFG entries for the northbridge busses?
>
> I believe so.
Ok, that give us a fighting chance to get this to work...
thanks,
greg k-h
prev parent reply other threads:[~2005-06-15 20:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 5:29 [PATCH 00/04] PCI: add proper MCFG support to let AMD boxes support MMCONFIG Greg KH
2005-06-15 5:30 ` [PATCH 01/04] PCI: add proper MCFG table parsing to ACPI core Greg KH
2005-06-15 5:31 ` [PATCH 02/04] PCI: use the MCFG table to properly access pci devices (i386) Greg KH
2005-06-15 5:32 ` [PATCH 03/04] PCI: use the MCFG table to properly access pci devices (x86-64) Greg KH
2005-06-15 5:33 ` [PATCH 04/04] PCI: let AMD boxes use MMCONFIG Greg KH
2005-06-16 22:34 ` [PATCH 03/04] PCI: use the MCFG table to properly access pci devices (x86-64) Rajesh Shah
2005-06-16 22:42 ` Greg KH
2005-06-16 23:00 ` Andi Kleen
2005-06-16 23:49 ` Brian Gerst
2005-06-17 1:15 ` Rajesh Shah
2005-06-15 9:48 ` [PATCH 02/04] PCI: use the MCFG table to properly access pci devices (i386) Andi Kleen
2005-06-15 17:31 ` Jeff Garzik
2005-06-15 17:54 ` Greg KH
2005-06-15 18:23 ` Andi Kleen
2005-06-15 18:35 ` Greg KH
2005-06-15 19:03 ` Andi Kleen
2005-06-15 20:21 ` 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=20050615202158.GC31022@kroah.com \
--to=gregkh@suse.de \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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