LinkSys and binary modules [LWN.net]

LinkSys and binary modules

Posted Oct 23, 2003 20:51 UTC (Thu) by mmarq (guest, #2332)
Parent article: LinkSys and binary modules

IMHO Linux need a split driver model

LinkSys is an example of continuous abuse, because they didn't released "that module driver" source, and legally the author(s) of specific "interfaces" involved could sue LinkSys... That could prove to be very bad for both sides.

The flexibility of the C language, as a procedural paradigma, dosent stop there, and there are proves from the GNOME project and others of the possibility of "craving" a real Object Oriented model with "full?" inheritance out of plain C.

So the "full objectivation" of the kernel is the next logic step of "modulation", with hierarchy and classes, like subsystems to kobjects, and char, block, video and sound devices class. But being out of a procedural language, this objectivation, IMO, also speak API allover the place. So the "glue" necessary to make kobjects talk with other kobjects could be completly negligenciable and wrapped inside the kobjects themselfes...

And that could be what is all about a "split driver model":- kobjects talking to other kobjects,... that already have a high natural tendency to be "logically independent functions within the kernel"... only remaining the formality of publishing the APIs... and "hardening" against possible abuses of other functions diferent from the published APIs(important:-saves sueing).

(no bypassing of copyright laws, no special favores to no one)

Being not a expert, and beliving i didn't express to much mistakes, but if so, then please let me know, because in a sense nothing really changes, and a clever configurantion mechanism is plently capable of configure the compiling sources out of diferent paths into a unic binary or into diferent binarys in diferent places(like kernel loadable modules);

Actual:
from /usr/src/Linux to /boot and or /lib/modules/3.0.1(example)

With a split driver model:
from /usr/src/Linux and /usr/src/Drivers to /boot and or /lib/drivers/3.0.1

In the late model, a proprietary binary only driver, that is copyed directly into /lib/drivers/3.0.1(example) would lose the ability to be compiled "in" the specific characteristics of the target machine, and relying on hardware detection mechanism and something like DKMS to be inserted...

In the late model also, all open source drivers could be compiled into a unic kernel image, like is happening today.

And what new world is to have a separated main Linux and Drivers, in terms of time and man/brainpower wasted in fixing bugs or broken things, and accelarating development, at least, well inside the 2 years time frame!!...

(Log in to post comments)