From: Greg KH <greg@kroah.com>
To: Andi Kleen <ak@muc.de>
Cc: Piotr Kaczuba <pepe@attika.ath.cx>,
linux-kernel@vger.kernel.org, tom.l.nguyen@intel.com
Subject: Re: PCI access mode on x86_64
Date: Thu, 17 Feb 2005 15:18:01 -0800 [thread overview]
Message-ID: <20050217231801.GC22195@kroah.com> (raw)
In-Reply-To: <20050214120205.GA33348@muc.de>
On Mon, Feb 14, 2005 at 01:02:05PM +0100, Andi Kleen wrote:
> On Mon, Feb 14, 2005 at 10:47:01AM +0100, Piotr Kaczuba wrote:
> > On Mon, Feb 14, 2005 at 10:18:43AM +0100, Andi Kleen wrote:
> > > Piotr Kaczuba <pepe@attika.ath.cx> writes:
> > > > Is there a reason why "PCI access mode" config option isn't available for
> > > > x86_64? Due to this, PCIE config options aren't available either.
> > >
> > > There is no 64bit PCI BIOS, so access is always direct.
> > >
> > > I assume you mean mmconfig access with "PCIE config options", that is
> > > a separate config option and available.
> >
> > I mean the PCIEPORTBUS option which depends on PCI_GOMMCONFIG or
> > PCI_GOANY. I assume that due to PCI_MMCONFIG / PCI_GOMMCONFIG mismatch
> > it's not available on x86_64.
>
> Ok, that's a bug in PCIEPORTBUS. Best is probably to
> completely remove the dependency, it doesn't make much sense
> (the code has to handle the case of mmconfig not being available at
> runtime anyways)
>
> -Andi
>
> Remove bogus dependency in PCI Express root driver.
Applied, thanks.
greg k-h
prev parent reply other threads:[~2005-02-17 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 21:31 PCI access mode on x86_64 Piotr Kaczuba
2005-02-14 9:18 ` Andi Kleen
2005-02-14 9:47 ` Piotr Kaczuba
2005-02-14 12:02 ` Andi Kleen
2005-02-14 15:46 ` Piotr Kaczuba
2005-02-14 19:15 ` Andi Kleen
2005-02-17 23: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=20050217231801.GC22195@kroah.com \
--to=greg@kroah.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pepe@attika.ath.cx \
--cc=tom.l.nguyen@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.