Messages in this thread |  | | From | Keith Owens <> | | Subject | Re: PATCH: "Pass module parameters" to built-in drivers | | Date | Tue, 23 Jan 2001 17:37:02 +1100 |
| |
On Mon, 22 Jan 2001 21:55:23 +0000 (GMT), Russell King <rmk@arm.linux.org.uk> wrote: >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?
Apart from the fact that it is completely backwards from the original intent. The problem is objects that have MODULE_PARM but no __setup.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |