Skip to contentSkip to conversation

Linux drivers management

DISCUSSION David Chow 12 participants 16 messages Feb 6, 2006 – Feb 7, 2006

lore
Share & tools
lore

David Chow

author
#0 lore raw

Dear maintainers,

Is there any work in Linux undergoing to separate Linux drivers and the the main kernel, and manage drivers using a package management system that only manages kernel drivers and modules? If this can be done, the kernel maintenance can be simple, and will end-up with a more stable (less frequent changed) kernel API for drivers, also make every developers of drivers happy.

Would like to see that happens .

regards,
David Chow

#1 lore raw
Quoted 5 lines · David Chow

Dear maintainers,

Is there any work in Linux undergoing to separate Linux drivers and the the main kernel, and manage drivers using a package management system that only manages kernel drivers and modules? If this can be done, the kernel maintenance can be simple, and will end-up with a more stable (less frequent changed) kernel API for drivers, also make every developers of drivers happy.

Would like to see that happens .

Please read Documentation/stable_api_nonsense.txt in your copy of Linux source.

Michal

#6 lore raw
In reply to David Chow
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"David" == David Chow <[email protected]> writes:

David> Dear maintainers, Is there any work in Linux undergoing to David> separate Linux drivers and the the main kernel, and manage David> drivers using a package management system that only manages David> kernel drivers and modules? If this can be done, the kernel David> maintenance can be simple, and will end-up with a more stable David> (less frequent changed) kernel API for drivers, also make every David> developers of drivers happy.

David> Would like to see that happens .

Simple answer: no

Maybe someone is working on it, but it's highly unlikely to be anything but a waste of that person's time.

This is a classic question, by seperating out the drivers you make it so much harder for all developers to propagate changes into all pieces of the tree.

Cheers,
Jes

author
#2 lore raw
In reply to Michal Schmidt
Quoted 2 lines

Please read Documentation/stable_api_nonsense.txt in your copy of Linux source.

I've read the document, I strongly disagree, because it is not relavant to my question or to my original purpose of this question.

Putting the driver source code in the kernel source tree has nothing to do with talking about a stable kernel API . Even you put the driver sources into the main kernel tree, it will still need a lot of work to port all drivers if the API changes. Driver sources can still host in a different project (e.g. projects in sf.net) and maintain open-source and om by the community, no difference than before

For different compile time options that affect data structures, this is well known a bad idea . These types of techniques no longer allowed in Java and other OO languages . Because I can simply say the code is not portable. If really need a recompile and optimize, the distro vendor should bare this, but according to the document, "As Linux supports a larger number of different devices "out of the box" than any other operating system" , do you think Linux should one day or some day grow to 1TB source tree to include all possible drivers for all hw come from the world? I don't see there is reason why a kernel or OS need to include all the drivers for all the hardware. I don't think there is any OS vendors on the market to capable to distribute all drivers integrity, then the choice is to make a disabled Linux OS because of an OSV who has only limited supporting resources to suppport and certify limited hardware devices.

Please see my other email responded to Jes about the learning curve and documentation issues of a Linux driver developer to pick up Linux skills.

regards,
David Chow

author
#7 lore raw
In reply to Jes Sorensen
Quoted 10 lines

David> separate Linux drivers and the the main kernel, and manage David> drivers using a package management system that only manages David> kernel drivers and modules? If this can be done, the kernel David> maintenance can be simple, and will end-up with a more stable David> (less frequent changed) kernel API for drivers, also make every David> developers of drivers happy.

David> Would like to see that happens .

Quoted 8 lines

Simple answer: no

Maybe someone is working on it, but it's highly unlikely to be anything but a waste of that person's time.

This is a classic question, by seperating out the drivers you make it so much harder for all developers to propagate changes into all pieces of the tree.

I write drivers, never need to change kernel if the kernel API is mature enough to provide the need of a module developer needs. There is no reason to make changes to the kernel source, only needed because the original kernel code is crap or the API designed without proper software/system architectural design work effort. Each Linux kernel version go through a lengthy beta release cycle (e.g. 2.3, 2.5, 2.7), this shouldn't happen and idea collection should be enough through this large Linux community.

If our time is to focus on kernel's kernel, writing good documentation about a stable kernel API, it will benefit many developers to write drivers to Linux . It is too difficult to learn, this is a main reason why Linux is lack of support from manufacturer drivers, not because they don't like Linux and no market, it is because this has created high entry barrier for them.

I've been working on Linux modules for many years, training my engineers, talking to developers, hw manufacturers .. believe it or not, this is the main reason. They all ask for a DDK for Linux that can make drivers easily for their product.

I think I am in a different position like you guys, I've been work with Linux from programmer level to Linux promotion . My goal is not just focus on Linux technical or programming, I would like to promote this operating system to not just for programmers, but also non-technical end-users . Writing C code to me is just bits of task of some process. You are too much focus on programming without considering the market situation.

There is no right or wrong for this question, but my original question is to listen thoughts and to hear the goal of people in the list. And of course, I would really like to see you people look into the way to facilitate more people gets a path with ease to Linux drivers development. User driver installation without the need to know about kernel sources, gcc, make etc.... "Because I am a dummy, I want to plug-in my device, put in the driver disc and hope it works!"

regards,
David Chow

#3 lore raw
In reply to David Chow
Quoted 28 lines · David Chow
Quoted 3 lines

Please read Documentation/stable_api_nonsense.txt in your copy of Linux source.

I've read the document, I strongly disagree, because it is not relavant to my question or to my original purpose of this question.

Putting the driver source code in the kernel source tree has nothing to do with talking about a stable kernel API . Even you put the driver sources into the main kernel tree, it will still need a lot of work to port all drivers if the API changes. Driver sources can still host in a different project (e.g. projects in sf.net) and maintain open-source and om by the community, no difference than before

For different compile time options that affect data structures, this is well known a bad idea . These types of techniques no longer allowed in Java and other OO languages . Because I can simply say the code is not portable. If really need a recompile and optimize, the distro vendor should bare this, but according to the document, "As Linux supports a larger number of different devices "out of the box" than any other operating system" , do you think Linux should one day or some day grow to 1TB source tree to include all possible drivers for all hw come from the world? I don't see there is reason why a kernel or OS need to include all the drivers for all the hardware. I don't think there is any OS vendors on the market to capable to distribute all drivers integrity, then the choice is to make a disabled Linux OS because of an OSV who has only limited supporting resources to suppport and certify limited hardware devices.

Quoted 2 lines

Please see my other email responded to Jes about the learning curve and documentation issues of a Linux driver developer to pick up Linux skills.

Maybe you want something like DKMS from Dell?
http://linux.dell.com/projects.shtml

or maybe some of the distros have something that fits your needs.

Signature · 1 line
~Randy
#8 lore raw
In reply to David Chow

David,

You got my vote..... I make simple hardware to improve availability
of operational systems and i just
can't go to build a native driver because i could not find a kit that works.... now i use a perl script to acomplish this mission... it works greate but is not beaulty as i like it to be.... Time is money.....

Pedro Alves

Quoted 29 lines · David Chow
Quoted 10 lines

David> separate Linux drivers and the the main kernel, and manage David> drivers using a package management system that only manages David> kernel drivers and modules? If this can be done, the kernel David> maintenance can be simple, and will end-up with a more stable David> (less frequent changed) kernel API for drivers, also make every David> developers of drivers happy.

David> Would like to see that happens .

Quoted 8 lines

Simple answer: no

Maybe someone is working on it, but it's highly unlikely to be anything but a waste of that person's time.

This is a classic question, by seperating out the drivers you make it so much harder for all developers to propagate changes into all pieces of the tree.

I write drivers, never need to change kernel if the kernel API is mature enough to provide the need of a module developer needs. There is no reason to make changes to the kernel source, only needed because the original kernel code is crap or the API designed without proper software/system architectural design work effort. Each Linux kernel version go through a lengthy beta release cycle (e.g. 2.3, 2.5, 2.7), this shouldn't happen and idea collection should be enough through this large Linux community.

If our time is to focus on kernel's kernel, writing good documentation about a stable kernel API, it will benefit many developers to write drivers to Linux . It is too difficult to learn, this is a main reason why Linux is lack of support from manufacturer drivers, not because they don't like Linux and no market, it is because this has created high entry barrier for them.

I've been working on Linux modules for many years, training my engineers, talking to developers, hw manufacturers .. believe it or not, this is the main reason. They all ask for a DDK for Linux that can make drivers easily for their product.

I think I am in a different position like you guys, I've been work with Linux from programmer level to Linux promotion . My goal is not just focus on Linux technical or programming, I would like to promote this operating system to not just for programmers, but also non-technical end-users . Writing C code to me is just bits of task of some process. You are too much focus on programming without considering the market situation.

There is no right or wrong for this question, but my original question is to listen thoughts and to hear the goal of people in the list. And of course, I would really like to see you people look into the way to facilitate more people gets a path with ease to Linux drivers development. User driver installation without the need to know about kernel sources, gcc, make etc.... "Because I am a dummy, I want to plug-in my device, put in the driver disc and hope it works!"

Quoted 9 lines

regards,
David Chow
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

begin:vcard
fn:Pedro Alves
n:Alves;Pedro
org:Moebius Tecnologia em Informatica Ltda
adr:;;Rua Jardim Botanico 674 sala 507;Rio de janeiro;RJ;22461000;Brasil email;internet:[email protected]
title:Diretor de Marketing
tel;work:21 2294-3772
tel;fax:21 2294-2794
tel;home:21 8762-1264
tel;cell:21 8762-1264
x-mozilla-html:TRUE
url:http://www.moebius.com.br
version:2.1
end:vcard

#9 lore raw
In reply to David Chow
Quoted 7 lines · David Chow

There is no right or wrong for this question, but my original question is to listen thoughts and to hear the goal of people in the list. And of course, I would really like to see you people look into the way to facilitate more people gets a path with ease to Linux drivers development. User driver installation without the need to know about kernel sources, gcc, make etc.... "Because I am a dummy, I want to plug-in my device, put in the driver disc and hope it works!"

Because I'm not a dummy, I want to plug-in my device, and it will work.

Gr{oetje,eeting}s,

Geert

P.S. Which driver disc? On which format? Anyone still has a floppy drive?
Where's the driver to my memory card reader?
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

#10 lore raw
In reply to David Chow
Quoted 5 lines · David Chow
Quoted 3 lines

This is a classic question, by seperating out the drivers you make it so much harder for all developers to propagate changes into all pieces of the tree.

I write drivers, never need to change kernel if the kernel API is mature enough to provide the need of a module developer needs. There is no reason to make changes to the kernel source, only needed because the original kernel code is crap or the API designed without proper software/system architectural design work effort. Each Linux kernel version go through a lengthy beta release cycle (e.g. 2.3, 2.5, 2.7), this shouldn't happen and idea collection should be enough through this large Linux community.

Silly me, it was a trick question. I should have known better than to fall into that trap. See the responses you got from other people already and go check out the archives.

No even better, here's a link:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/stable_api_nonsense.txt

If you still wish to argue for this, please take me off the CC list. To be honest, I don't think anyone on linux-kernel is interested in yet another round of this one.

Cheers,
Jes

#4 lore raw
In reply to David Chow
Quoted 3 lines · David Chow

do with talking about a stable kernel API . Even you put the driver sources into the main kernel tree, it will still need a lot of work to port all drivers if the API changes.

Convention is that he who breaks an API fixes up the majority of the mess caused or does it by consensus with the other developers.

Of course if your code is out of tree nobody will know so it'll just break.

For example the last time I edited the wdt501 watchdog I submitted according to my logs is about 1998. Since then each person who broke an API it used fixed it up, or the janitors did shortly afterwards.

Quoted 2 lines

For different compile time options that affect data structures, this is well known a bad idea .

Do you have measured performance data, economic models and statistical evidence to back up the claim or is this that well known bad idea called "conventional wisdom" ?

Quoted 3 lines

operating system" , do you think Linux should one day or some day grow to 1TB source tree to include all possible drivers for all hw come from the world?

Why not. By the time it gets that big you'll have over 1TB on your phone let alone a PC. The kernel development structure is optimised for development.

Alan

#5 lore raw
In reply to David Chow
Quoted 6 lines · David Chow
Quoted 3 lines

Please read Documentation/stable_api_nonsense.txt in your copy of Linux source.

I've read the document, I strongly disagree, because it is not relavant to my question or to my original purpose of this question.

It has a lot of relevance.
If you split up drivers and the core kernel into two sepperate projects I can easily imagine the two getting out of sync whenever an API change needs to be made.
Currently whenever someone changes a kernel API that person is required to also update all users of that API. Since all users are in-tree that's resonably easy to do. If the drivers are out-of-tree it's a *lot* harder for several reasons;

a) to fix users of the API I can no longer just 'cd drivers/' I now have to go download & extract a sepperate source tree.

b) if an API change I make gets accepted by the 'core kernel' team but the 'driver-tree' maintainers refuse my updates we get out-of-sync - just as if the 'core kernel' tree rejects the API change but the 'driver-tree' maintainers already merged the update to the drivers to use the new API.

c) presumably the two projects 'driver-tree' and 'core-kernel' would use sepperate mailing lists, making it harder to communicate about API changes.

Maintaining the drivers out of tree would make API changes a lot more painful and thus we'd need to lock down the API a lot harder than we do today. This in turn would mean that some types of bugs will be harder to solve (since a proper fix would involve a painful API change) and advancement of kernel caabilities/features etc will be slower.

Quoted 4 lines

Putting the driver source code in the kernel source tree has nothing to do with talking about a stable kernel API . Even you put the driver sources into the main kernel tree, it will still need a lot of work to port all drivers if the API changes.

You can't dodge the work that needs to be done when API's change, but you /can/ try to make the work as easy to do as possible by keeping the core kernel code and the drivers close together and maintained as a single unit.

Quoted 7 lines

Driver sources can still host in a
different project (e.g. projects in sf.net) and maintain open-source and om by the community, no difference than before

For different compile time options that affect data structures, this is well known a bad idea . These types of techniques no longer allowed in Java and other OO languages .

The kernel is written in C. What other languages do/allow/recommend etc is irrelevant.

Quoted 7 lines

Because I can simply say the code is not
portable. If really need a recompile and optimize, the distro vendor should bare this, but according to the document, "As Linux supports a larger number of different devices "out of the box" than any other operating system" , do you think Linux should one day or some day grow to 1TB source tree to include all possible drivers for all hw come from the world?

First of all, drivers are regularly dropped from the tree; either because they become unmaintained and bitrot or because the hardware becomes extremely obsolete and rare.
Secondly, I predict that available storage sizes and bandwith available to users of the kernel will grow faster than the size of the source tree (and cost of storage & bandwith will likely continue to drop as well).
Thirdly, the day Linux supports "all hw come from the world" I'll be dancing with joy.

Quoted 2 lines

I don't see there is reason why a kernel or OS need to include all the drivers for all the hardware.

This is *extremely* convenient for our users.

Quoted 6 lines

I don't think there is any
OS vendors on the market to capable to distribute all drivers integrity, then the choice is to make a disabled Linux OS because of an OSV who has only limited supporting resources to suppport and certify limited hardware devices.

The user always has the option of building any driver they need themselves. This is easy since the drivers are all in the main kernel source tree, the user doesn't have to go hunt for them online (assuming the user even has an internet connection).

Quoted 3 lines

Please see my other email responded to Jes about the learning curve and documentation issues of a Linux driver developer to pick up Linux skills.

The fact that all documentation (well, at least a lot of it) is kept in a central place (Documentation/) is a very nice thing for someone trying to learn their way around the kernel - I know I've personally bennefitted from that.
Also the fact that core kernel code, drivers and supporting scripts are all kept in a single source tree is very convenient for new developers since there's only one thing to download and then you have a complete tree with the full picture to learn from - again I say this based on personal experience.

But in any case, if you want to maintain one or more drivers out-of-tree, then go ahead, noone's stopping you. But your maintenance work will be a lot lower if you instead submit your drivers for inclusion in mainline since then other people will keep your driver up-to-date and in sync with API changes when they happen. You might even get a few bugs fixed for free and get the code cleaned up for free.

--
Jesper Juhl <[email protected]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html

#14 lore raw
In reply to David Chow
Quoted 6 lines · David Chow

Is there any work in Linux undergoing to separate Linux drivers and the the main kernel, and manage drivers using a package management system that only manages kernel drivers and modules? If this can be done, the kernel maintenance can be simple, and will end-up with a more stable (less frequent changed) kernel API for drivers, also make every developers of drivers happy.

The separation of drivers from the core kernel has nothing to do with the stability of the in-kernel api. To think otherwise is foolish, and does not show an understanding of the current kernel apis. See the archives for all of the times this has come up previously.

Quoted 1 line

Would like to see that happens .

Feel free to submit patches to do so, if it is something you want to do. Otherwise, telling other people to do something will not achieve anything.

good luck,

greg k-h

#15 lore raw
In reply to David Chow
Quoted 9 lines · David Chow

Dear maintainers,

Is there any work in Linux undergoing to separate Linux drivers and the the main kernel, and manage drivers using a package management system that only manages kernel drivers and modules? If this can be done, the kernel maintenance can be simple, and will end-up with a more stable (less frequent changed) kernel API for drivers, also make every developers of drivers happy.

Quoted 6 lines

Would like to see that happens .

regards,
David Chow

Debian includes a tool call module-assistant that allows one to download, compile and install the 3rd party modules that they package pretty painlessly. But it obviously doesn't include the drivers already in the kernel since they're included in the kernel packages.

Jim.

#12 lore raw
In reply to Christoph Hellwig
Quoted 1 line · Christoph Hellwig

could you please shut up as non-contributor and parasite?

I don't like your tone at all. In case you will suggest me to shut up too, I would not.
--
vda

#13 lore raw
Quoted 5 lines · Denis Vlasenko
Quoted 1 line · Christoph Hellwig

could you please shut up as non-contributor and parasite?

I don't like your tone at all. In case you will suggest me to shut up too, I would not.

Not that I'd care too much when, but I wouldn't initially say that to you. You've been doing some useful work, while David has not contributed anything while abusing at least the -fsdevel list with stupid question to help implementing his companies probably illegal filesystem. He's the last one who should speak up on lkml with any questions or suggestions.