Instead, any driver, filesystem or other entity can just register a kernel
command line string and/or a initialization function that will be executed
by using a magic section in the kernel linkage. So there is no need to
touch a common file to add a new driver or a architecture-specific kernel
command line entry.
I've fixed up a few of the old command lines and initialization functions,
but I'm hoping that driver writers can re-instate their own setup
functions rather than me trying to fix up them all by hand. For that
reason there is now a pre-patch-2.3.13-3 on ftp.kernel.org under
"testing".
Go wild.
Linus
-
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/