linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Jansen <tim@tjansen.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Automatic download and installation of drivers.
Date: Wed, 17 Oct 2001 23:31:17 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-100336151817589@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100319421829170@msgid-missing>

On Wednesday 17 October 2001 21:24, David Brownell wrote:
> > With a patch, "knowledgeable" users can get going right away.  All
> > others are going to need to wait for a new release in any case, or
> > will ask their "knowledgeable user" friends for help.
> It's well known that even in the Windows world, most support
> comes from friendly local experts ("power users").  Those are
> the folk that get called in when a vendor's driver disk doesn't
> install correctly (the ones I get usually don't).

But this is one of the problems with Linux and newbies - even with today's 
distributions there are far too many things you need "knowledgable" users 
for. This is definitely not the way it should be, and Windows shows that it 
is not neccessary. While it is true that it the driver installation fails 
sometimes you can be sure that this will improve over the next years. 
Actually the frequent failures of driver installations are probably the main 
reasons that Microsoft started their driver certification program.


> So far as I know, there isn't even an authoritative list of all
> the USB and CardBus devices supported by, say, the 2.4.12
> kernel. 

You wouldn't need this in the kernel for automatic downloads. Actually the 
idea of automatic downloadable drivers is to provide drivers that are NOT in 
the kernel. If the user connects a new device and the system doesn't find a 
driver for it it would request one from some server. This server could either 
provide a driver itself, based the device's vendor and model id, or forward 
the system to the vendor's server which would then try to find one for the 
model.

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

  parent reply	other threads:[~2001-10-17 23:31 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
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 [this message]
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-100336151817589@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).