hmm. insmod => single device configuration ?

Paul Barton-Davis (pbd@Op.Net)
Wed, 15 Jul 1998 17:02:15 -0400


It seems to my perhaps naive brain that current module loading scheme
tend to result in the following implication: loading a module is
equivalent to specifying a hardware configuration limited to a single
device.

Although in theory, a module could take multiple similar arguments,
eg.

modprobe foobar io1=0x200 io2=0x305

this can make the control path for init_module() more complex than one
might like. Also, each an every init_module() would have to deal with
this, which is a stupid way to handle what is really common code.

It seems from a user-level simplicity point of view that one should be
able to "insert" a module multiple times if the module options are
different. Obviously, the first load is special, since it actually
gets the module code linked into the kernel, but beyond that,
subsequent insmod()'s should be possible, and in effect say "cook me
another interface configured *this* way ..."

Am I just missing the point ?

--p

-
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.altern.org/andrebalsa/doc/lkml-faq.html