Messages in this thread | | | Date | Sat, 17 Apr 2004 08:40:31 -0400 | From | Ross Biro <> | Subject | Re: Kernel writes to RAM it doesn't own on 2.4.24 |
| |
On Sat, 17 Apr 2004 14:40:18 +1000, Ross Dickson <ross@datscreative.com.au> wrote: > This is all most enlightening. If I am understanding correctly then every > device driver that the author specifies to use a "mem=" command to > reserve some memory for said drivers use at the upper part of physical > memory is stuffed by design.
The problem is really that Linux doesn't trust the BARs assigned by the PCI bios because some BIOSes do it incorrectly. So it reprograms them based on the memory map it got from the BIOS. However, before it does that the mem= parameter overrides the memory map from the BIOS.
I believe what I did was to save a copy of the e820 maps for later, and then take then take the first free address as the max of the first free address from the user supplied map and the bios supplied map. I'll send out a patch on Tuesday.
Ross - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |