All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Olivier Galibert <galibert@pobox.com>,
	linux-pci@atrey.karlin.mff.cuni.cz,
	"Hack inc." <linux-kernel@vger.kernel.org>,
	Andi Kleen <ak@suse.de>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] PCI MMConfig: Detect and support the E7520 and the 945G/GZ/P/PL
Date: Thu, 23 Nov 2006 13:40:34 -0700	[thread overview]
Message-ID: <20061123204034.GF6083@parisc-linux.org> (raw)
In-Reply-To: <1164311861.3147.5.camel@laptopd505.fenrus.org>

On Thu, Nov 23, 2006 at 08:57:41PM +0100, Arjan van de Ven wrote:
> On Thu, 2006-11-23 at 20:51 +0100, Olivier Galibert wrote:
> > It seems that the only way to reliably support mmconfig in the
> > presence of funky biosen is to detect the hostbridge and read where
> > the window is mapped from its registers.  Do that for the E7520 and
> > the 945G/GZ/P/PL on x86-64 for a start.
> 
> while I like this approach a lot, I am wondering if this shouldn't be
> done as a PCI quirk instead.... it would make a lot of sense to use that
> shared infrastructure for this...

Except the shared infrastructure kind of relies on having the pci
accesses already working ... unless we want the kernel to print messages
like:

PCI: Using type 1 config access method
...
PCI: Whoops, looks like we're going to use MMCONFIG after all.  Ignore that

  reply	other threads:[~2006-11-23 20:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23 19:51 [PATCH] PCI MMConfig: Detect and support the E7520 and the 945G/GZ/P/PL Olivier Galibert
2006-11-23 19:57 ` Arjan van de Ven
2006-11-23 20:40   ` Matthew Wilcox [this message]
2006-11-23 20:44   ` Olivier Galibert
2006-11-25 19:34 ` Andi Kleen
2006-11-25 20:51   ` Olivier Galibert
2006-11-25 20:59     ` Andi Kleen
2006-11-26 13:15       ` Olivier Galibert
2006-11-26 19:28         ` Andi Kleen
2006-11-27 19:03           ` Olivier Galibert
2006-11-27 19:07             ` Andi Kleen
2006-11-27 20:24               ` Olivier Galibert
2006-12-01  0:19                 ` Olivier Galibert

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=20061123204034.GF6083@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=ak@suse.de \
    --cc=arjan@infradead.org \
    --cc=galibert@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=torvalds@osdl.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 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.