what do you think about configuration modules instead of
big-fat configuration interfaces (especially for lowmem-machines).
imagine this:
parts of the kernel (or modules) export the configurable structures
and there are modules which take the params and configure the stuff.
after doing it, they're killed again.
with this concept drivers could be splitted in two parts: (modules)
a resident and a non-resident one.
the resident part is the real driver code. the non resident one
does the initialization, detection, configuration, etc.
after these things are done, the non-resident part is not needed
anylonger and can be kicked away.
bye,
ew.
-------------------------------------------------------------------------------
KAMPF GEGEN ECHOLON - DIE USA SCHNEIDED WELTWEIT DEN EMAIL-VERKEHR
MIT!!!
BITTE ALLE MITMACHEN UND "GEFAEHRLICHE" WOERTER IN DIE SIGNATUR
SCHREIBEN
...
againstNSAletskillthemallaufstanddollarwirtschaftskrieseusakillthepresident
shitfuckingusawewillattacknextweekterrorecholonforkommunismagainstdemocracy.
-
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/
This archive was generated by hypermail 2b29 : Fri Mar 31 2000 - 21:00:20 EST