> Don't be stupid, Lisa. In what respect bigphisarea is "dirtier" than
> using "mem="? Mathias advocates to pull the subtle work of picking at
> mem_start/memory_end inside your driver.
I answered a posting saying you _must_ use bigphysarea just to show
other solutions. I didn't say you _must_ use the mem switch.
Quote:> If you do that, you have to
> deal with any bugs, have intricate understanding how the memory is
> allocated, and support multiply kernel revisions. Certainly a well
> defined interface of bigphisarea, tested by numerous developers,
> provides you a better option.
Fine, thats the drawback of the mem switch and the advantages of
the bigphysarea patch. It isn't really serious. Please remember
you can't (eventually) patch already patched kernels, you need a
patch for your exact kernel version and you depend on the
goodwill of the developers. The mem switch is a well documented feature
of the kernel. That's just the opposite point of view. Please don't tell
someone how to do something. Tell her all possibilities and let her
decide. That's the way. I think we agree on that?