public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@linuxtv.org>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Joshua Kugler <joshua.kugler@uaf.edu>,
	linux-kernel@vger.kernel.org,
	Nicolas Mailhot <nicolas.mailhot@laposte.net>,
	David Chow <davidchow@shaolinmicro.com>
Subject: Re: Linux drivers management
Date: Mon, 06 Feb 2006 14:46:42 -0500	[thread overview]
Message-ID: <43E7A7A2.3060909@linuxtv.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0602061420400.17351@chaos.analogic.com>

linux-os (Dick Johnson) wrote:

>Maybe it would be better for no drivers to be in the tree!
>Something along the lines of an automatic FTP site that
>interacts with a configuration program. You end up downloading
>the drivers that you need. In the case where you don't have
>an Internet connection, a distribution company would put the
>mirror on a CD or DVD.
>  
>
Regardless of whether or not the idea is practical, where would the 
funding come from?  Who is going to donate their time?  What if they get 
bored of it and nobody wants to pick up?

There are enough of us working for free on this stuff, and those that 
get paid already have enough on their plate.  What you're asking for is 
something that just isn't practical.

When I first read this, I thought you were joking... unfortunately, it 
looks like you are being serious.

>Right now, there are really too many drivers in the kernel.
>The kernel should have a stable API for drivers and they
>should be in a separate tree, either on the Web or on a
>distribution disc. There are many drivers that are as old
>as Linux! The 3c501.c and 3c503.c are examples. You can't
>remove them from the kernel without invoking a thousand
>angry responses. These boards and the ne*.c network boards
>just won't go away!
>  
>
Why would we WANT to remove them?  Linux is just about the only 
operating system that will run well on all old machines.  If we were to 
remove these drivers from the kernel, we might as well all throw our old 
hardware into the garbage.

>This means that the amount of drivers will continue to
>increase to, eventually, an unmanagable amount. This is
>why they really need to be seperately managed!
>  
>
That's part of what subsystems and subsystem maintainers are for.  Looks 
like somebody thought ahead. ;-)

FYI, v4l/dvb drivers can be built separately from the kernel as modules, 
directly from our mercurial repository, and we try to keep them all 
backwards compatable with older vanilla kernels.  Surely there are other 
subsystems that do something similar.

>****************************************************************
>The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
>
^^^ I'm sure you've been flamed about this already, so I won't say it....

Cheers,

Michael Krufky



  reply	other threads:[~2006-02-06 19:47 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 18:31 Linux drivers management Nicolas Mailhot
2006-02-06 18:56 ` Yaroslav Rastrigin
2006-02-06 19:02 ` Joshua Kugler
2006-02-06 19:17   ` Yaroslav Rastrigin
2006-02-06 19:39     ` Martin Mares
2006-02-06 19:56       ` Jan-Benedict Glaw
2006-02-06 19:53     ` Jan-Benedict Glaw
2006-02-06 20:04     ` Jesper Juhl
2006-02-06 23:52     ` Bernd Petrovitsch
2006-02-06 19:21   ` linux-os (Dick Johnson)
2006-02-06 19:46     ` Michael Krufky [this message]
2006-02-06 19:58     ` Nicolas Mailhot
2006-02-06 23:16 ` Gene Heskett
  -- strict thread matches above, loose matches on Subject: below --
2006-02-07  4:42 linux
2006-02-07 16:18 ` Eric W. Biederman
2006-02-07 19:45   ` David Chow
2006-02-07 20:03     ` Kyle Moffett
2006-02-07 22:15     ` Theodore Ts'o
2006-02-08  0:52       ` David Chow
2006-02-08  4:02         ` Theodore Ts'o
2006-02-08  9:46         ` Bernd Petrovitsch
2006-02-09  6:09       ` Lee Revell
2006-02-08  1:06     ` Alan Cox
2006-02-08  8:26     ` Denis Vlasenko
2006-02-11 18:47     ` Andrew James Wade
2006-02-06 19:30 Nicolas Mailhot
2006-02-06  9:45 David Chow
2006-02-06 10:05 ` Michal Schmidt
2006-02-06 16:50   ` David Chow
2006-02-06 16:55     ` Randy.Dunlap
2006-02-06 19:45     ` Alan Cox
2006-02-06 19:46     ` Jesper Juhl
2006-02-06 10:08 ` Jes Sorensen
2006-02-06 16:52   ` David Chow
2006-02-06 17:03     ` Pedro Alves
2006-02-06 17:35     ` Geert Uytterhoeven
2006-02-06 17:42     ` Jes Sorensen
2006-02-06 16:56 ` Christoph Hellwig
2006-02-07 11:36   ` Denis Vlasenko
2006-02-07 13:22     ` Christoph Hellwig
2006-02-06 19:51 ` Greg KH
2006-02-06 21:38 ` Jim Crilly

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43E7A7A2.3060909@linuxtv.org \
    --to=mkrufky@linuxtv.org \
    --cc=davidchow@shaolinmicro.com \
    --cc=joshua.kugler@uaf.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=nicolas.mailhot@laposte.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox