From: Andi Kleen <ak@suse.de>
To: Tim Hockin <thockin@google.com>
Cc: matthew@wil.cx, greg@kroah.com,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@google.com>
Subject: Re: PCI MMCONFIG aperture size
Date: Tue, 22 Aug 2006 09:55:31 +0200 [thread overview]
Message-ID: <200608220955.31620.ak@suse.de> (raw)
In-Reply-To: <20060822024237.GO16573@google.com>
> This says to me that (as long as the MCFG table has an End Bus Number of
> 31) a 32 MB decode area (32 MB aligned, too) is valid.
>
> Would something like the below patch be accepted? It makes my system
> work...
I already got a patch to remove the complete e820 validation code because
it broke far more than it fixed. That should fix your problem too.
> Also, why are we forcing 32 bit base addresses? ACPI defines it to be a
> 64 bit base...
Where do you think we do that?
-Andi
next prev parent reply other threads:[~2006-08-22 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 2:42 PCI MMCONFIG aperture size Tim Hockin
2006-08-22 7:55 ` Andi Kleen [this message]
2006-08-22 14:58 ` Tim Hockin
2006-08-22 15:00 ` Andi Kleen
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=200608220955.31620.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@google.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=thockin@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox