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 [email protected]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
