From: Rajesh Shah <rajesh.shah@intel.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Rajesh Shah <rajesh.shah@intel.com>, Andi Kleen <ak@suse.de>,
Brice Goglin <brice@myri.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] PCI extended conf space when MMCONFIG disabled because of e820
Date: Fri, 23 Jun 2006 00:41:42 -0700 [thread overview]
Message-ID: <20060623004141.A27049@unix-os.sc.intel.com> (raw)
In-Reply-To: <449A629F.9000401@linux.intel.com>; from arjan@linux.intel.com on Thu, Jun 22, 2006 at 11:27:59AM +0200
On Thu, Jun 22, 2006 at 11:27:59AM +0200, Arjan van de Ven wrote:
> Rajesh Shah wrote:
> > Oh I agree with you that booting is more important. My point with
> > the spec statement was that most BIOS developers may not even know
> > they are doing something "wrong" by not listing these resources in
> > the int15 E820 table, since the document they normally refer to
> > doesn't say so. I suspect there are many more systems out there
> > which do the same thing and will fail the check, but we never notice
> > since most users don't try to ever access the extended space today.
>
> well... it's sort of common sense though.. if you want non-ACPI OSes to
> work properly (like the older 2.4 based distros...)
>
In this case we already have an ACPI dependence, since the MCFG
table is listed in ACPI. In any case, I have a patch that got me
my extended config space back on the one machine I've tested so
far. I'll test it out on the remaining 2 where I saw this problem
and send it out.
Rajesh
next prev parent reply other threads:[~2006-06-23 7:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 21:07 Brice Goglin
2006-06-14 21:09 ` Arjan van de Ven
2006-06-15 1:45 ` Andi Kleen
2006-06-15 1:57 ` Brice Goglin
2006-06-15 6:47 ` Arjan van de Ven
2006-06-21 22:19 ` Rajesh Shah
2006-06-21 22:32 ` Andi Kleen
2006-06-22 0:15 ` Rajesh Shah
2006-06-22 9:27 ` Arjan van de Ven
2006-06-23 7:41 ` Rajesh Shah [this message]
2006-06-15 8:41 Chuck Ebbert
2006-06-15 13:18 ` Arjan van de Ven
2006-06-15 14:32 ` Barry Scott
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=20060623004141.A27049@unix-os.sc.intel.com \
--to=rajesh.shah@intel.com \
--cc=ak@suse.de \
--cc=arjan@linux.intel.com \
--cc=brice@myri.com \
--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
Powered by JetHome