From: Tim Jansen <tim@tjansen.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Automatic download and installation of drivers.
Date: Tue, 16 Oct 2001 18:44:04 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100325962111086@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100319421829170@msgid-missing>
On Tuesday 16 October 2001 18:52, Greg KH wrote:
> 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.
But how does this help for drivers that are not installed yet because they
are not part of the kernel? This is the reason for downloading drivers.
> 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.
I doubt that this will make hardware vendors happy:
- their devices cannot be supported before they are included in a kernel.
Assuming a world where new devices are released with vendor-supported linux
drivers this would mean that a new device cannot be released before their
drivers are in the kernel and distributions picked this kernel up.
- vendors lose control of their device drivers even though their quality is
crucial for the success of their products
This is also a problem for users. Most distributions do update between 1 and
4 times updates per year. This means that users have to wait for their driver
up to one year before they can buy new devices or get an update for their
driver.
bye...
_______________________________________________
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 18:44 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
2001-10-16 18:44 ` Tim Jansen [this message]
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-100325962111086@msgid-missing \
--to=tim@tjansen.de \
--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).