From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Automatic download and installation of drivers.
Date: Tue, 16 Oct 2001 16:52:33 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100325179712967@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100319421829170@msgid-missing>
On Tue, Oct 16, 2001 at 09:58:38AM +0200, Tim Jansen wrote:
> > But the main question I have is:
> > What is the real problem that you are trying to solve?
> > and
> > Why does the current kernel/driver situation not work for you?
>
> 1. It makes it much easier for a user to find a driver that's not included in
> his distribution. Linux drivers are usually named after the chipset's name or
> the first device that was supported. How can a user know that his Logitech
> Quickcam Pro 3000 needs the pwc (philips webcam) driver? And where can he
> find the driver?
The current linux-hotplug interface solves this problem. The driver
itself lets the kernel/world know for what devices it supports. Coming
from the other direction (what driver supports this device) is just as
easy. Look at modules.usbmap and modules.pcimap for examples.
> 2. (source driver packages only) right now the situation for drivers authors
> who want to distribute their drivers to end-users is really bad. Either they
> make it complicated for their users and distribute the drivers in source
> form. Even now I would guess the majority of Linux users is not able to
> compile their own drivers, and hopefully the percentage will be much lower in
> a couple of years. Or the driver author provides binary packages for each
> version of each distribution. It is a lot of work and still won't help all
> users. This is probably one of the reasons that so few hardware
> manufacturers provide Linux drivers.
The solution to this is to either live with the nightmare of supporting
binary packages for _every_ distro kernel release (1 kernel release from
RedHat is 11 kernels, multiply that by different versions of that distro
and the number of different distros, you have a huge mess) or simply put
the driver in the kernel source tree.
By putting the driver into the tree, all the problems go away, users
don't have to compile their own drivers, the drivers are all distributed
by the different Linux vendors, vendors don't have to update their
driver for every kernel api change, and everyone is happy. Well, the
people who don't like open source drivers aren't happy, but we aren't
here to make their lives easier :)
thanks,
greg k-h
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-10-16 16:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 0:02 Automatic download and installation of drivers Stamatis Mitrofanis
2001-10-16 5:29 ` Greg KH
2001-10-16 7:35 ` David Brownell
2001-10-16 7:58 ` Tim Jansen
2001-10-16 11:38 ` Keith Owens
2001-10-16 16:52 ` Greg KH [this message]
2001-10-16 18:44 ` Tim Jansen
2001-10-16 18:58 ` Tim Jansen
2001-10-16 19:19 ` Greg KH
2001-10-17 2:01 ` David Brownell
2001-10-17 2:03 ` David Brownell
2001-10-17 18:47 ` Tim Jansen
2001-10-17 19:24 ` David Brownell
2001-10-17 23:31 ` Tim Jansen
2001-10-17 23:32 ` Greg KH
2001-10-18 0:07 ` Dmitri
2001-10-18 0:19 ` Stamatis Mitrofanis
2001-10-18 0:47 ` Tim Jansen
2001-10-18 2:17 ` Keith Owens
2001-10-18 2:35 ` Dmitri
2001-10-29 21:53 ` Greg KH
2001-10-30 8:26 ` Tim Jansen
2001-10-30 17:21 ` Greg KH
2001-10-30 21:24 ` Tim Jansen
2001-10-30 21:51 ` Dmitri
2001-10-31 12:36 ` Keith Owens
2001-10-31 20:49 ` Greg KH
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=marc-linux-hotplug-100325179712967@msgid-missing \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).