From: Robert Hancock <hancockr@shaw.ca>
To: Jesse Barnes <jesse.barnes@intel.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] support PCI MCFG space on Intel i915 bridges
Date: Tue, 01 May 2007 17:59:18 -0600 [thread overview]
Message-ID: <4637D456.3040303@shaw.ca> (raw)
In-Reply-To: <200705011627.14948.jesse.barnes@intel.com>
Jesse Barnes wrote:
> On Monday, April 30, 2007 4:20 pm Robert Hancock wrote:
>>> Right, but you patch should obsolete this stuff anyway. I'll test
>>> it out in the next few days.
>> We likely still want this chipset-specific support, it will catch the
>> case where the MCFG table lists a location which is reserved in ACPI
>> but the chipset was actually programmed to a different location
>> entirely, which I seem to remember someone mentioning was actually
>> the case on some boards..
>
> Yeah, I suppose that's true. So maybe your new checking code should
> leverage the stuff in mmconfig-shared.c to check against the register
> values like Olivier mentioned?
The patch I sent takes the MCFG address from the chipset registers for
known chipsets, or the ACPI MCFG table otherwise. Either way, it will
verify that the memory range is reserved in ACPI.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next prev parent reply other threads:[~2007-05-02 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.aWIs6SNmpl2IhGAAoSWJu6oKjPo@ifi.uio.no>
2007-04-30 2:10 ` [PATCH] support PCI MCFG space on Intel i915 bridges Robert Hancock
2007-04-30 19:25 ` Jesse Barnes
2007-04-30 23:20 ` Robert Hancock
2007-05-01 23:27 ` Jesse Barnes
2007-05-01 23:59 ` Robert Hancock [this message]
2007-04-26 19:27 Jesse Barnes
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=4637D456.3040303@shaw.ca \
--to=hancockr@shaw.ca \
--cc=akpm@linux-foundation.org \
--cc=jesse.barnes@intel.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