mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Zenaan Harkness <zen@freedbms.net>
Cc: debian-devel@lists.debian.org, linux-kernel@vger.kernel.org
Subject: Re: drivers DB and id/ info registration
Date: Wed, 26 May 2004 08:44:49 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0405260835370.858@chaos> (raw)
In-Reply-To: <1085573236.2213.77.camel@zen8100a.freedbms.net>

On Wed, 26 May 2004, Zenaan Harkness wrote:

> On Wed, 2004-05-26 at 21:35, Wouter Verhelst wrote:
> > Op wo 26-05-2004, om 12:07 schreef Zenaan Harkness:
> > > I develop widget X.
> > >
> > > I contact microsoft and have X incorporated into windows.
> >
> > Rotfl.
>
> OK, bad assumption.
>
> The only reason I say that is that so many devices work
> "seamlessly" with MSW*
>
>  - recently I read a review on the X-Arcade retro joystick
> controllers (those heavy "for cabinets and MAME" things).
> The reviewer just plugged it in and Windows literally popped
> up with a dialog telling the "end user recognizable" name of
> the device.
>
>  - a year or so back, my brother bought a "blue eye" USB
> external 2.5" HDD (really nice looking thing) and on his
> XP box it auto added a new drive (E: or whatever). Seamless.
>
> So how come devices tend to just plug and play when
> used with Windows (USB HDDs, audi cards, logitec gear)?
>
> Will a "visible"/ centralized location where manufacturers
> can submit info on their devices (for free software kernels)
> help to get us closer to the "front line" of device support?
>
> thanks
> zen

M$ has a whole division dedicated to plug-and-pray developers.
When their USB disk, camera, or whatever gets "approved", its
name is put into W$ even without installing any "drivers".
That's why W$ is so large. It would be good if somebody
started to do something like that for Linux, perhaps a
database from which configuration stuff could be extracted.
It's not a kernel issue, so some distribution really should
take it up.

Of course, the work needs to be done correctly so you don't
get the M$ problem of; "Everything was working until I installed
my new printer...." Whereupon you install everything from a
newly-formatted hard-disk, all over again, installing the
new printer first!


Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2004-05-26 12:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1085542706.2908.25.camel@zen8100a.freedbms.net>
     [not found] ` <20040526065447.GA32304@dat.etsit.upm.es>
     [not found]   ` <200405260918.51589@fortytwo.ch>
2004-05-26 10:07     ` Zenaan Harkness
2004-05-26 11:35       ` Wouter Verhelst
2004-05-26 12:07         ` Zenaan Harkness
2004-05-26 12:44           ` Richard B. Johnson [this message]
2004-05-26 15:38           ` Randy.Dunlap
2004-05-26 11:53       ` Denis Vlasenko
2004-05-26 13:16         ` Zenaan Harkness
2004-05-26 22:26           ` Horst von Brand
2004-05-27  0:05             ` Zenaan Harkness

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=Pine.LNX.4.53.0405260835370.858@chaos \
    --to=root@chaos.analogic.com \
    --cc=debian-devel@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zen@freedbms.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

all inboxes | Powered by JetHome®