Skip to contentSkip to conversation

Linux drivers management

DISCUSSION [email protected] 10 participants 12 messages Feb 7, 2006 – Feb 11, 2006

lore
Share & tools
lore
#0 lore raw
Quoted 6 lines

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.

Not very seriously. Kernel developers really like the ability to change every user of a kernel programming interface within a single source tree. Breaking it up would make it harder to change the device driver interface when necessary. (It's already hard enough; nobody does it for fun.)

Also, a hardware manufacturer looking for a "stable API" is often really looking for a stable *binary* interface because they want to ship binary-only drivers.

The Linux developers are quite opposed to that, for a variety of excellent reasons I won't bother enumerating. Linus has said he'll (grudgingly) allow it, but won't lift a finger to help. Linux development sailed away from the idea of a stable binary interface years ago, and isn't looking back.

#1 lore raw
Quoted 5 lines · [email protected] writes:

The Linux developers are quite opposed to that, for a variety of excellent reasons I won't bother enumerating. Linus has said he'll (grudgingly) allow it, but won't lift a finger to help. Linux development sailed away from the idea of a stable binary interface years ago, and isn't looking back.

Almost true. There is a stable binary interface to user space, and work is done to maintain that interface.

I just thought I would mention it because too frequently people get the policy on the in-kernel api and the ABI to user space confused.

In general the user space ABI is only appended to.

Eric

#2 lore raw

Dear all,

First of all, thanks for giving me lots of wonderful feedbacks, I read both pros and cons, support and against msgs. And you are right, I am serious person about this matter, not joking. Because I do this for my bread and butter, not just for fun.

Before I continue this discussion, I would really want to clarify who am I before get discriminated by end-users and developers, because I am both.

I am a full-time (M$_less) Linux user (many years...., Sharp Zaurus PDA, Linux on laptop, desktop, server, storage and datacenter) with zero windows experience for the last 5 years (can't remember, my last windows desktop was on NT 4.0/Win98). I am an engineer, I wrote many file systems (cogofs http://www.shaolinmicro.com/product/cogofs/, unionfs, .....more), cluster infrastructure (used in ShaoLin InfiniCluster http://www.shaolinmicro.com/product/icluster/technology.php), data replication (used in Shaolin Volume Replicator), load balancing, iSCSI storage drivers..... . I am also a system architect/engineering manager, architect core Linux system software from scratch, desktop, network computing, servers, network related projects. I am also a R&D team manager, hiring, training, manage engineers .

In fact, this is not to talk about myself, but my full-time Linux experience tells me Linux development is walking away with end-uesrs and commercial developers that try to work with Linux. It sounds too scary by now, with over 40MB tarred gzip kernel source. With personal efforts and company resources, we maintain more than hundreds (probably thousand) of Linux kernel headers and sources in our lab for building off-the-shelf supported binary drivers with multiple hardware archs (x86, ppc...). Because of this, who is going to pay for this? It doesn't make any sense for anyone who want to maintain and write a driver for Linux have to pay this price.

My summary from the responses from lkml collected as follows. Please feel free to make correction if I am wrong, or comment if you want, I will minimize to say about subjective comment to others comment in an open area though.

Community Developers and Maintainers:
- Look at the matter on community development process, programming
- Chase for performance, optimization in source level, even though it is difficult to maintain, who cares?
- Want freedom, change at will (with supported arguments, but who cares?) .
- My feels like it doesn't consider any other forms of development and respect to traditional software engineering or QA process. Because a stable API is first needed for teamwork collaborative development.
- Willing to maintain and develop drivers for free, even though they don't work for the hardware vendor.
- We will follow the convention who make changes to the API will have to patch all the mess in the kernel source, even though there are 3,714,234 hardware peripheral drivers in the kernel in year 2012, I am happy to do that :) . Because I want to make change and following the convention. (how much time to make change or test?)

Technical End-Users:
- Want to compile the drivers from source
- Enjoy building their own kernel, apply patches (patch and make, it works! thats cool....)
- I don't mind to search for drivers and do it myself, because it was fun to make something work with my effort :) .
- I don't mind to upgrade my OS because of a missing driver or needed for new fucntionality. Even my application breaks, down time is not important to my system because it s a sytsem for fun.

Non-technical Users:
- Want the system to have drivers pre-built, so that they don't have to go through a compilation or patching process. Its a waste of time for them (waste of time for me too)
- Why I have to search the drivers? Isn't is suppose to be included in the OS? Or if not included in the OS, it should be included in a driver disk (CD/DVD/floppy or whatever medium or download) .
- Why I have to upgrade the complete OS if only one driver is missing? I want to stay with Redhat-9 , my PHP runs great.
- There is no "Linux support" labels on most the hardware out there, should I risk my money, buy it and try out? Oh, full refund of item is not allowed . Then, don't bother ...

Commercial developers:
- Want a stable API so that drivers can be maintained with ease. Because we don't just work with Linux, we want to focus on our driver development, not chasing the API changes, versions by versions, vendors by vendors. Sometimes there are even vendor specific changes, its a waste of time.
- If I have to make binary drivers, I have to maintain all kernel sources and headers, compilers to make sure my drivers will be built correctly without problem. Of risk to change symbols in the binaries and hope it works!
- Where is the latest up-to-date documentation of the kernel API? /Documentation only partially describe what I need, its version specific, sometimes out-of-date, where the hell is that? Let's google it in amazon.com, "Linux driver books", No good again.... Its crap, all not up-to-date!
- Lets get on to it, read all docs and sample sources... mmm... My driver seems working now.. Lets compile it and distribute it. Users: have you got a driver for Redhat 9 2.4.18 kernel? Answer: No, it doesn't work, because I write my driver on 2.6.15, you may to DIY. User response: I want a refund, because you said your hardware has Linux support, but its a false statement.
- Just leave Linux, who cares, it doens't make sense to us. Because it doesn't make sense to go through all these problems to say "Linux supported hardware", user will get refund the product if we say this on the box on day one.
- Maybe we have another way to do that, submit the driver to the community and hope it to include it in the latest kernel source. Wait.... but what about support for Redhat 9 and SuSe 8.2?
- We are happy to maintain our own drivers, because we know better about our hardware. We are paid to do so, we also have quality assurance process with formal test tools and equipment. Don't think the community can do a better core than us.
- It just doesn't work for us. No more Linux driver Cd's, it will not happen .

My comments:
- Freedom? Someone tell me to shut-up . Some people define freedom using their own way, not even using mailling list for discussion and make suggetions or even define questions as "stupid", I will not say that to anyone. Its rude.
- Wake up! Why would the maintainers bother to maintain the drivers if the driver development work is now back to the hardware vendor, like drivers for other platform did? I think someone mis-understood the whole idea is to "GET RID OF DRIVER MAINTENANCE", belive it or not, it belongs to the vendor, not here. If the driver releases as GPL, you can still make your own changes, but it doesn't have to be in main source tree.
- You plug-in the hardware, it worked! Because many people behind the scene has done a lot of work. My purpose of raising this question is trying to help both users and developers, and try to make more hardware that behaves "plug-n-play" .
- What is the goal of Linux developers? Just for fun? Or you want Linux to get more popular? Users want their system to get supported with latest drivers, not to compile and build to latest kernel. Or not to upgrade their Linux distro every week or month. I don't use 2.6.15 nor happy downloading 40Mb targged gzip kernel source and knowing how to "make" it.
- Linux will not sail to major desktop unless a decent DDK (driver development kit) exists. There is a stable ABI on the user space, but the hardware has to "get worked" before anything in user space happens. I decide to sell my USB wireless-G adapter because I don't have a driver for it, neither Linksys did. I can only choose to get rid of Linux, but can't, so just sell it. For others, why don't they simply choose another supported OS?
- /Documentation/stable_api_nonsense.txt is only a document totally written by a programmer sense, its nothing about people who don't want to compile the drivers, and has assumed drivers should be maintained by the community. But strictly speaking, it shouldn't. Please refer to the process of making a driver from a manufacturers point of view and consider user using old OS'es which don't want to upgrade.

Final comment: There is no right or wrong, stupid or smart, it depends where you stands and where you want Linux to go. I am very clear myself is to get Linux promoted to public sectors (where I belive 99% users are non-technical), easy for developers (I believe everyone wants easy-way-out) and easy for the community (I belive you people like innovation, new ideas, rather thatn spend your time to work/maintain drivers which this work should belongs to the original vendor). If you think I have no contribution and stupid, that's up to you (who cares? Linux has been working like this in day-one that I first compile and run it). But my work has already beyond programming, because making patches for Linux doesn't make any sense to me, especially when porting drivers that I can't even tell what they are. My mood of patching the kernel goes away when today's Linux kernel targged gzip source gets to over 40MB .. I have more important things to do. Its enough for me by now.... Sure its not going to change, maybe but not in a year or two, but freedom of speech exists, right?

regards,
David Chow

#3 lore raw
Quoted 3 lines · David Chow

Before I continue this discussion, I would really want to clarify who am I before get discriminated by end-users and developers, because I am both.

[offtopic babble about credentials]

We do not discriminate based on "end-user" or "developer", we discriminate based on productivity. So far this thread has been extremely counterproductive and wasted a lot of my bandwidth and time. As a result, I am now discriminating against you for wasting my time. Welcome to my killfile. (I still felt the need to point out your grievous logical errors, but don't bother replying because this is the last time I'm going to bother wasting time on this thread)

Quoted 1 line

[junk about commercial development models]

We do not care about your snazzy dev-model ideas, we have one that works for us. We do not care about making things easier for commercial out-of-tree drivers, _end_ _of_ _story_. Any arguments about that issue are just offtopic flames.

Quoted 1 line

Why would the maintainers bother to maintain the drivers if the driver development work is now back to the hardware vendor, like drivers for other platform did? I think someone mis-understood the whole idea is to "GET RID OF DRIVER MAINTENANCE", belive it or not, it belongs to the vendor, not here. If the driver releases as GPL, you can still make your own changes, but it doesn't have to be in main source tree.

WRONG. Driver maintenance is a 2-part effort. The Linux kernel API is *not* stable for a lot of good reasons, and therefore the drivers must be in-tree to make it possible to fix drivers when we change the API. Hardware companies are _expected_ to be good citizens and maintain their own drivers, fix bugs, etc. If your driver sucks, nobody will buy your hardware to use on linux.

Quoted 1 line

Linux will not sail to major desktop unless a decent DDK (driver development kit) exists.

This is wrong. There are a lot of companies that make great server hardware out there whose drivers are in the stock kernel, and by your argument "Linux will not sail to major servers unless a decent DDK exists", which is blatantly false.

Quoted 1 line

/Documentation/stable_api_nonsense.txt is only a document totally written by a programmer sense

Absolutely, and from the programmer point of view, that's all that matters.

Quoted 1 line

its nothing about people who don't want to compile the drivers

This is the job of a distro

Quoted 1 line

and has assumed drivers should be maintained by the community.

Community includes the people making the hardware

Quoted 1 line

But strictly speaking, it shouldn't. Please refer to the process of making a driver from a manufacturers point of view and consider user using old OS'es which don't want to upgrade.

You don't want to upgrade, you don't get new hardware support, simple as that. Upgrading my Debian testing between 2.6 versions has been really painless despite massive internal changes and restructuring, and Debian isn't really even a user-friendly distro.

Quoted 1 line

but freedom of speech exists, right?

As does my freedom to ignore you. Plonk.

Cheers,
Kyle Moffett

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/E/U d- s++: a18 C++++>$ ULBX*++++(+++)>$ P++++(+++)>$ L++++(+++)>$ !E- W+++(++) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+ PGP+ t+(+++) 5 X R? !tv-(--) b++++(++) DI+(++) D+++ G e>++++$ h*(+)>++$ r%(--) !y?-(--) ------END GEEK CODE BLOCK------

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

- What is the goal of Linux developers? Just for fun? Or you want Linux to get more popular? Users want their system to get supported with latest drivers, not to compile and build to latest kernel. Or not to upgrade their Linux distro every week or month. I don't use 2.6.15 nor happy downloading 40Mb targged gzip kernel source and knowing how to "make" it.

Every Linux developer has their own goals, of course, but for most of them it is about making the best possible Linux kernel that is technically possible. If they have working drivers for their system, they may not necessarily care about some company's hardware unless,
(a) it impacts them personally, (b) they are paid or employed to worry about it, or (c) lots of end-users are sending complaining/sending hate-mail about it.

(In some cases, end-users send hate mail to the Linux kernel developers when some idiot company's binary driver modules is buggy and corrupts the kernel in hard-to-debug ways; one particular video driver company is especially guilty here, and is viewed by some as being directly responsible for the tainted kernel flags.)

The assumption by many developers is that if we concetrate on making Linux as good as possible, it will eventually get popular enough that hardware vendors will feel a commercial incentive to cooperate with our way of doing things. Obviously, this in practice things don't always work that way --- the Sony Betamax is story is one where technical excellence doesn't always win out. However, at least in the server space, compromising hasn't obviously been a bad strategy, with many SCSI and FC controller manufacturers deciding on their own to work with the Linux kernel development community. (Sometimes with some help from major system vendors who write in a requirement for a mainline device driver into the sourcing contracts for said controllers, but nevertheless, it shows that this stance is not obviously a bad strategy for Linux kernel developers, at least in the server space.)

David, you may find this frustrating, and at least in the Deskstop space, it's likely that your company hasn't seen sourcing contracts yet where a mainline acceptable device driver is a requirement for some major system vendor, like Dell, Gateway, HP, etc. to decide to use your products. I suspect that if this _was_ the case, your company would in fact dedicate the full-time engineer necessary to make a device driver which could be integrated into the mainstream kernel sources and then could be backported to older distributions. But if you did, I think it is certainly doable.

But at that point it stops being a technical question of "is it possible" and moves to an economic question of "are we willing to fund a full-time engineer to provide support for our hardware under Linux" and "how popular does the Linux desktop have to be before a system vendor will feel obliged to put pressure on their downstream suppliers to provide the necessary driver support"? And as such, LKML will probably not be a very useful place to have that discussion.

Regards,

- Ted

#5 lore raw
Quoted 9 lines

Every Linux developer has their own goals, of course, but for most of them it is about making the best possible Linux kernel that is technically possible. If they have working drivers for their system, they may not necessarily care about some company's hardware unless,
(a) it impacts them personally, (b) they are paid or employed to worry about it, or (c) lots of end-users are sending complaining/sending hate-mail about it.

That's expected. IS there a composition statistics about the LKML? I guess near 100% are technical people here, including me.

Quoted 21 lines

(In some cases, end-users send hate mail to the Linux kernel developers when some idiot company's binary driver modules is buggy and corrupts the kernel in hard-to-debug ways; one particular video driver company is especially guilty here, and is viewed by some as being directly responsible for the tainted kernel flags.)

The assumption by many developers is that if we concetrate on making Linux as good as possible, it will eventually get popular enough that hardware vendors will feel a commercial incentive to cooperate with our way of doing things. Obviously, this in practice things don't always work that way --- the Sony Betamax is story is one where technical excellence doesn't always win out. However, at least in the server space, compromising hasn't obviously been a bad strategy, with many SCSI and FC controller manufacturers deciding on their own to work with the Linux kernel development community. (Sometimes with some help from major system vendors who write in a requirement for a mainline device driver into the sourcing contracts for said controllers, but nevertheless, it shows that this stance is not obviously a bad strategy for Linux kernel developers, at least in the server space.)

Quoted 6 lines

David, you may find this frustrating, and at least in the Deskstop space, it's likely that your company hasn't seen sourcing contracts yet where a mainline acceptable device driver is a requirement for some major system vendor, like Dell, Gateway, HP, etc. to decide to use your products. I suspect that if this _was_ the case, your

No, I never had drivers problems . Because we have our own stable partial_kernel_API to bare this problem and kept all supported kernel sources and headers maintained.

Quoted 5 lines

company would in fact dedicate the full-time engineer necessary to make a device driver which could be integrated into the mainstream kernel sources and then could be backported to older distributions. But if you did, I think it is certainly doable.

Yes it worked for us. But what about others? I don't think everyone that want to support Linux have to do that. We are different, because we only support Linux, so we dare to do that. Other companies have to do Windows, Unix and possibly other OS. This way don't seems feasible for them. Back-port?

Quoted 8 lines

But at that point it stops being a technical question of "is it possible" and moves to an economic question of "are we willing to fund a full-time engineer to provide support for our hardware under Linux" and "how popular does the Linux desktop have to be before a system vendor will feel obliged to put pressure on their downstream suppliers to provide the necessary driver support"? And as such, LKML will probably not be a very useful place to have that discussion.

I have no expectation the LKML will agree to my point . Because 99% of the LKML are likely technical users and community developers. As said, they only care about programming drivers in the kernel source. Freedom of change is cool and fun for them.

regards,
David Chow

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

Community Developers and Maintainers:
- Look at the matter on community development process, programming
- Chase for performance, optimization in source level, even though it is difficult to maintain, who cares?

I've done real studies on this. The majority of the kernel interfaces favour simplicity and independance.

Quoted 2 lines

- Willing to maintain and develop drivers for free, even though they don't work for the hardware vendor.

Most of our drivers are maintained by people with economic incentives to maintain them. Economic incentives are not always cash and employment.

Quoted 5 lines

- We will follow the convention who make changes to the API will have to patch all the mess in the kernel source, even though there are 3,714,234 hardware peripheral drivers in the kernel in year 2012, I am happy to do that :) . Because I want to make change and following the convention. (how much time to make change or test?)

I'd beg to differ. The amount of hardware interfaces in a system that are non standard has been dropping like a stone. Software is *expensive* and it is getting cheaper and cheaper for commodity products to adopt a commodity API, especially in the open source world where pure software pricing scams (eg extra cost for flipping the 'raid enable' bit on a controller) don't work.

The recent directions are pretty clear

	IDE -> Various interfaces -> AHCI
	A billion periphals -> USB (EHCI/OHCI/UHCI) + Class drivers
	SATA -> AHCI
	Sound -> Intel i810 clones/AC97
	USB imaging random drivers -> USB video classes
	Scanners -> USB video/image classes
	A billion camera interfaces -> USB storage
	A load of MP3 player interfaces -> USB storage

Its getting harder and harder to justify non-standard APIs except in a few areas like infinibong and 3D graphics where they can make a product genuinely better. Even RAID cards are drifting inexorably to either extinction or emulating standard interfaces, and no doubt will eventually end up AHCI.

Quoted 3 lines

the community. But strictly speaking, it shouldn't. Please refer to the process of making a driver from a manufacturers point of view and consider user using old OS'es which don't want to upgrade.

But those people have a stable API - usually RHEL3, RHEL4, SuSE Enterprise.

Quoted 2 lines

Sure its not going to change, maybe but not in a year or two, but freedom of speech exists, right?

Time will tell. People said the same when Linux got so big it wouldn't fit on one floppy disk. I can't prove you are wrong but my suspicion is that economic incentives and pressures will mould the development process over time according to the problems it faces.

Alan

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

I have no expectation the LKML will agree to my point . Because 99% of the LKML are likely technical users and community developers. As said, they only care about programming drivers in the kernel source. Freedom of change is cool and fun for them.

Actually, most of the developers work for some a distributions or a system vendor. I for example happen to work for IBM's Linux Technology Center. In that role, I do worry about the device drivers for the hardware devices that we sell to our customers. However, I also am a community developer, and with that hat on I care about Linux being the best OS it can be technically.

I will say that my experience has been that binary kernel modules can easily turn into a disaster for our customers. It's a major issue when a customer needs to install an errata kernel issued by one of our Linux Distribution Partners for stability or security reasons, and they are using a propietary binary kernel module from some third party storage vendor which hasn't yet updated their proprietary binary driver for that errata kernel.

Or there was the time that positively warmed my heart when I spent several very late nights trying to debug a situation for a very high profile, important customer trying to use a Samba file server running on IBM hardware being integrated by IBM Global Services, and the system kept on falling over. It turned out the problem was caused by a memory leak in a propietary, binary-only kernel module from an commercial anti-virus product that shall remain nameless.

So I am firm believer in giving our customers access to source code to all kernel code, not because of any deep desire to "programming drivers in kernel source", or because of any "information wants to be free" religion --- but because it's the best way to keep our customer's systems running reliably and nearly problem-free --- and when there is a problem, I know that we have whatever is necessary to make their problem Go Away.

Yes, I'm aware of the traditional arguments that a stable device driver API would solve all of these problems. Well.... at least the first problem; incompetently written propietary kernel modules filled with memory leaks and wild pointer dereferences and race conditions aren't solved by standardized driver API's; the only solution is source access so we can fix the idiotically written modules. But the reality is the way the Linux kernel is developed, a stable driver API would never work.

- Ted

P.S. Obligatory disclaimer: These are my own opinions, and not necessarily those of my employer.

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

Non-technical Users:
- Want the system to have drivers pre-built, so that they don't have to go through a compilation or patching process. Its a waste of time for them (waste of time for me too)
- Why I have to search the drivers? Isn't is suppose to be included in the OS? Or if not included in the OS, it should be included in a driver disk (CD/DVD/floppy or whatever medium or download) .
- Why I have to upgrade the complete OS if only one driver is missing? I want to stay with Redhat-9 , my PHP runs great.

Then why MS has that auto-update service of theirs?

Quoted 3 lines

- There is no "Linux support" labels on most the hardware out there, should I risk my money, buy it and try out? Oh, full refund of item is not allowed . Then, don't bother ...

Because hardware verdors act stupid and many of them still do not write open-source drivers (or at least provide adequate docs).

Quoted 10 lines

Commercial developers:
- Want a stable API so that drivers can be maintained with ease. Because we don't just work with Linux, we want to focus on our driver development, not chasing the API changes, versions by versions, vendors by vendors. Sometimes there are even vendor specific changes, its a waste of time.
- If I have to make binary drivers, I have to maintain all kernel sources and headers, compilers to make sure my drivers will be built correctly without problem. Of risk to change symbols in the binaries and hope it works!

IOW: "we want to hijack millions of lines of Linux source and won't contribute back our driver(s). Why do you kernel guys make that hard?"

Because we don't like what you're doing.

Quoted 5 lines

- Where is the latest up-to-date documentation of the kernel API? /Documentation only partially describe what I need, its version specific, sometimes out-of-date, where the hell is that? Let's google it in amazon.com, "Linux driver books", No good again.... Its crap, all not up-to-date!

The source is ultimate doc. You never ever will get such a complete doc for any commercial OS. It even documents all bugs! ;)

Quoted 2 lines

- Lets get on to it, read all docs and sample sources... mmm... My driver seems working now.. Lets compile it and distribute it. Users:

Wrong. You should do: "Let's submit it for inclusion in mainline". If you don't want to, it's your problem, not ours.

Quoted 11 lines

have you got a driver for Redhat 9 2.4.18 kernel? Answer: No, it doesn't work, because I write my driver on 2.6.15, you may to DIY. User
response: I want a refund, because you said your hardware has Linux support, but its a false statement.
- Just leave Linux, who cares, it doens't make sense to us. Because it doesn't make sense to go through all these problems to say "Linux supported hardware", user will get refund the product if we say this on the box on day one.
- Maybe we have another way to do that, submit the driver to the community and hope it to include it in the latest kernel source. Wait.... but what about support for Redhat 9 and SuSe 8.2?

You may backport your driver to older kernel(s). Sometimes distro(s) will backport your driver to older kernels if there is demand.

Quoted 4 lines

- We are happy to maintain our own drivers, because we know better about our hardware. We are paid to do so, we also have quality assurance process with formal test tools and equipment. Don't think the community can do a better core than us.

Maintain them "in-tree", not in your own corner.

Quoted 6 lines

- Wake up! Why would the maintainers bother to maintain the drivers if the driver development work is now back to the hardware vendor, like drivers for other platform did? I think someone mis-understood the whole idea is to "GET RID OF DRIVER MAINTENANCE", belive it or not, it belongs to the vendor, not here. If the driver releases as GPL, you can still make your own changes, but it doesn't have to be in main source tree.

Yeah, yeah. I just wrestled with 2 so called "GDI" printers for Windows from 2 different vendors. Both vendors _refused to fix obvious bugs_ in their Windows drivers. Do you want THIS type of driver maintenance to occur in Linux world too?
--
vda

#7 lore raw
In reply to David Chow

On Wed, 2006-02-08 at 08:52 +0800, David Chow wrote:
[...]

Quoted 6 lines
Quoted 6 lines

(In some cases, end-users send hate mail to the Linux kernel developers when some idiot company's binary driver modules is buggy and corrupts the kernel in hard-to-debug ways; one particular video driver company is especially guilty here, and is viewed by some as being directly responsible for the tainted kernel flags.)

Quoted 6 lines
Quoted 6 lines

The assumption by many developers is that if we concetrate on making Linux as good as possible, it will eventually get popular enough that hardware vendors will feel a commercial incentive to cooperate with our way of doing things. Obviously, this in practice things don't always work that way --- the Sony Betamax is story is one where technical excellence doesn't always win out. However, at least in the

But only because the company behind BetaMax (and BetaMax was only second best behind Philips Video2000 AFAIR) had not enough money and/or motivation to stay long enough to make the technical better solution also successful.
IOW you won't get the perspective right if you view from the commercial old-ecenomy world only (as you do up to now!)

Quoted 4 lines
Quoted 4 lines

server space, compromising hasn't obviously been a bad strategy, with many SCSI and FC controller manufacturers deciding on their own to work with the Linux kernel development community. (Sometimes with some help from major system vendors who write in a requirement for a

                  ^^^^^^^^^^^^^^^^^^^^

Do you knwo the contracts, agreements and result of meetings of major of major system vendors with the sales army of big OS corporations in the desktop area?
Probably not.

Quoted 4 lines
Quoted 4 lines

mainline device driver into the sourcing contracts for said controllers, but nevertheless, it shows that this stance is not obviously a bad strategy for Linux kernel developers, at least in the server space.)

Perhaps you should ask them (and I mean "ask the folks to pushed and took the decision and not spokespersons or marketing and sales staff") "why on earth?".

[...]

Quoted 4 lines

Yes it worked for us. But what about others? I don't think everyone that want to support Linux have to do that. We are different, because we only support Linux, so we dare to do that. Other companies have to do Windows, Unix and possibly other OS. This way don't seems feasible for them.

But it is *their* commercial decision if they play the Linux market (as long as it exists) and/or if they play the proprietory market (as long as it exists). As well as it is MSFT decision to play exclusively in the propriatory market, they and you have to live with it.
Of course we all want the best of all worlds - free software, out-of-the-box working toolchains and stable APIs through all of them to minimize my own work. IMHO this is another "choose any 2 of the 3" question.

Quoted 1 line

Back-port?

If you want a commercial answer: Either it pays off or not. It is *their* decision.

Quoted 2 lines
Quoted 2 lines

But at that point it stops being a technical question of "is it possible" and moves to an economic question of "are we willing to fund

Yes, because the free software world generally gives a broad "yes, it is technically possible" (whereas the propriatory world makes of this the key selling point).

Quoted 5 lines
Quoted 5 lines

a full-time engineer to provide support for our hardware under Linux" and "how popular does the Linux desktop have to be before a system vendor will feel obliged to put pressure on their downstream suppliers to provide the necessary driver support"? And as such, LKML will probably not be a very useful place to have that discussion.

Probably wrong. It is completely up to the hardware vendor to decide if -) they just want to sell their hardware and release specs so that
everyone can write (and fix) a (free) driver.
-) also have reasons to maintain the drivers themselves over time. -) just out-source the development and maintenance of a driver. -) just out-source the development of a driver for the current kernel
(to you, me, someone), release the source under GPL, throw it into the kernel and copnsider (and sell!) it as "maintained".
-) divide the driver in one OS-independent lower part and a OS-dependent
upper part (whareas the latter is surely under the GPL and with the former you have to look at each case) to "hide hardware details" for whatever reason.
-) or whatever partial "solutions" (and combinations therof over time)
come to the mind of some deciders.
*The hardware vendor* (and not me and IMHO not LMKL) has to decide which fits most in his business plans. *The hardware vendor* makes the money with after all.

Quoted 2 lines

I have no expectation the LKML will agree to my point . Because 99% of the LKML are likely technical users and community developers. As said,

This is probably correct:^^^^^^^^^^^^^^^
This is plain simply wrong: ^^^^^^^^^^^^^^^^^^^^
There are for sure *far* more then 1% who make living with "Linux" (technically wise).

Quoted 2 lines

they only care about programming drivers in the kernel source. Freedom of change is cool and fun for them.

As long as you want to see (and/or argue) exactly the historically grown propriatory business model, it certainly doesn't work out.

Bernd

Signature · 3 lines
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services
#8 lore raw
In reply to Theodore Ts'o
Quoted 5 lines · Theodore Ts'o

(In some cases, end-users send hate mail to the Linux kernel developers when some idiot company's binary driver modules is buggy and corrupts the kernel in hard-to-debug ways; one particular video driver company is especially guilty here, and is viewed by some as being directly responsible for the tainted kernel flags.)

Wouldn't the tainted kernel flags be necessary even if there had never been a single bug in any binary driver, simply because there's still no reasonable way to debug a kernel with binary drivers loaded?

Lee

#11 lore raw
In reply to David Chow

On Tuesday 07 February 2006 14:45, David Chow wrote:

Speaking as a Linux enthusiast:

Quoted 2 lines

Technical End-Users:
- Want to compile the drivers from source

I want to be able to compile drivers from source. I'm not particularly
interested in actually doing so as I'm not mucking around with driver source. I happen to be compiling drivers because I am interested in mucking around with Linux kernel source, and the drivers are in-tree. But if the fancy takes me to play around with driver source, I want to be able to do so. Or perhaps I want to try out a kernel in which a driver API is being developed, in which case I need to compile drivers as source, and having them in-tree is convenient.

Quoted 2 lines

- Enjoy building their own kernel, apply patches (patch and make, it works! thats cool....)

I enjoy building my own kernel. Applying patches, not so much. I found
applying patches to get the latest -mm drudge work and I'm never able to remember whether 2.6.16-rc2-mm1.bz2 applies to 2.6.16-rc2 or 2.6.16. Fortunately I found a little utility called ketchup that handles the details for me.

Quoted 2 lines

- I don't mind to search for drivers and do it myself, because it was fun to make something work with my effort :) .

And here you go off the mark. It might be fun making that device work,
but if I'm working away at a different puzzle it'll probably be just an annoyance. When it comes to parts of a system I'm not interested in at the moment, I want them to "just work".

Quoted 3 lines

- I don't mind to upgrade my OS because of a missing driver or needed for new fucntionality. Even my application breaks, down time is not important to my system because it s a sytsem for fun.

Some down time is ok for me: I don't need 100% up-time on my system.
I can accept that the cost of running a beta system (-mm kernels) is that it occasionally crashes, and the filesystems occasionally eat data (it's happened to me once), but it's still a nuisance. People like me are volunteers, if it become too inconvenient we'll simply stop volunteering.
The barrier to entry for people like us also needs to be low. And here
the situation for the kernel is fairly good (due to the stable userspace API). When switching to a development kernel the only other thing I had to change was lilo; everything else just worked.

If the Linux development community is to benefit from volunteer
testers, hardware has to work not just for the stable kernels, but also development kernels.

As an aside, there is another good reason to update drivers not just
for stable driver APIs, but also APIs under development: quite apart from testing, implementing APIs is a good way to find problems in the design of the API. Notice the reluctance of the kernel maintainers to merge any API that is not both implemented and used.

Andrew Wade