Keith Owens writes:
> It is part of my total Makefile rewrite for 2.5. A clean
> implementation of module parameters mapping to setup code requires the
> mapping of a source file to the module it is linked into. That
> information is difficult to extract with the current Makefile system,
> my rewrite makes it easy.
Hmm, don't we already have all that __setup() stuff laying around? Ok,
it might not be built into the .o for modules, but it could be. Could
we not do something along the lines of:
1. User passes parameters on the kernel command line.
2. modprobe reads the kernel command line and sorts out those that
correspond to the __setup() stuff in the module being loaded.
3. modprobe combines in any extra settings from /etc/modules.conf
IIRC, this would satisfy the original posters intentions, presumably
without too much hastle?
--
Russell King ([EMAIL PROTECTED]) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
