From: "Randy.Dunlap" <rddunlap@osdl.org>
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:38:59 -0700 [thread overview]
Message-ID: <20040526083859.418e42fa.rddunlap@osdl.org> (raw)
In-Reply-To: <1085573236.2213.77.camel@zen8100a.freedbms.net>
On Wed, 26 May 2004 22:07:17 +1000 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.
I think that most companies do it themselves (or pay to have
it done) for Windows drivers, if their devices don't fit into
some well-known interface.
For Linux drivers, it means finding the right group/project,
if it exists... Could be hard to find at times.
| > 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?
I hear this way too much, for 2 reasons.
(a) You are right, we want to get to that model in Linux.
(b) The thing that bugs me (I guess) and that people seem to
overlook again and again is that Linux developers are not
provided the same access to hardware interface specs that other
driver developers have. That leaves reverse engineering or
trial-and-error (mostly error). That's an awful way to write
a driver IMO. So to me it's just a specs issue, and many
companies won't or cannot provide product specs (often because
they don't own the IP inside the product, sometimes because
they _assume_ that it might aid their competition).
--
~Randy
next prev parent reply other threads:[~2004-05-26 15:49 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
2004-05-26 15:38 ` Randy.Dunlap [this message]
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=20040526083859.418e42fa.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--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®