I don't see how this helps us. All it allows us is to seperate
a piece of memory, so we can scribbe something to it later.
First we don't know what piece of memory is available for
removal, on a 64MB machine you want another part of memory
reserved than on the 2GB one..
Second, how can the driver know what piece of memory it can use?
How can we protect two drivers (sound,grabber?) using the same
piece of memory twice? etc etc
If you revered the guy to the alloc_bootmem() interface I could
seen some light there, but the mem= interface is not the way to
go (for the casual user at least!)
Unfortuantly alloc_bootmem does not work for modules...
I see definitly some light for the bigphysarea patch, working
closely together with alloc_bootmem to get its much needed
memory...
Met vriendelijke groet,
Pauline Middelink
-- PGP Key fingerprint = DE 6B D0 D9 19 AD A7 A0 58 A3 06 9D B6 34 39 E2 For more details look at my website http://www.polyware.nl/~middelin- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/