We could be at that point in about two weeks if Linus would stop
dropping my "kmalloc" patches without telling me why.
I KNOW I can do the patch (because I've done it before) and I get
tired quickly when I have to spend time redoing the patchfiles for
every kernel that comes out every two days or so.....
The trick is to create a new "kfree" call that can be called with
a pointer and a length field. The indicated area will then be added
to the kmalloc pool without it having been malloced through kmalloc.
A compiled-in-driver that is unable to find its hardware could then
indicate to its caller that it wants to be freed (Data and code space).
In the normal event you would only free the init routine's code....
It is unlikely though that this will create a significant saving.
Roger.
-- ** Q: What's the difference between MicroSoft Windows and a virus? ** ** A: Apart from the fact that virusses install easier, none. ** ** EMail: R.E.Wolff@et.tudelft.nl * Tel +31-15-2783643 or +31-15-2137459 ** *** <a href="http://einstein.et.tudelft.nl/~wolff/">my own homepage</a> ***