From: davidw@dedasys.com (David N. Welton)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux Incompatibility List
Date: 22 Aug 2004 22:48:58 +0200 [thread overview]
Message-ID: <87vffaq4p1.fsf@dedasys.com> (raw)
In-Reply-To: 1093173291.24341.40.camel@localhost.localdomain
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> On Sad, 2004-08-21 at 20:41, David N. Welton wrote:
> I think the "compatibility list" side is the more important. Trying
> to punish non helpful products/vendors isn't as productive as
> helping stuff that is Linux friendly.
A "compatibility list" is going to be pretty big, and hard to keep up
to date. My thinking is that keeping track of a few notable things
that don't work is easier than running after all the stuff that does.
Of course, if automation can be brought to bear, that might make
either one much easier, but I'm dubious, because "it doesn't work" is
a vague concept, and really ought to be researched some.
A third concept "look, these guys support Linux really well!" (not
just "ok, it works") might also be easy to do.
By the way, the concept is not really about punishing vendors, and I
don't want it to come off looking like that. It's about "this piece
of hardware does not work with Linux". Who knows, maybe the fault is
with the kernel maintainers:-) It might be nice if that gave some
incentive to the manufacturers to help bring the driver up to speed,
though.
> At what level is "Product" - do you need a category. How do you want
> to classify devices. I think this matters because you want
> eventually to be able to deal with things like tools that let users
> rate their setup functionality and submit it automatically.
I'd be worried about people who are just irritated that their system
didn't work out of the box hitting a button to submit this
information.
I suppose some sort of vote system could be put in place so that the 1
guy who didn't get the hardware to work gets outvoted by the 10 who
did, but there is more incentive to hit the button when you are
irritated than when everything 'just worked'.
> > How bad it is (1 to 10, 9 being it almost works and has only minor
> > bugs):
> > Reason (no specs, driver still being worked on, ...):
> > Url for more info:
> > An email address of yours that we may publish (so that we can contact
> > you if someone says "no, that works just fine!"):
> Wikipedia has a discussion page tagged to each article/entry. This
> works extremely well because it provides a public forum for
> discussion of what does/doesn't work, why and when.
It's a wiki, so for now I think placing comments on the bottom of the
page would be sensible. We'll see if and how it grows.
> Could you add "Kernel.org bugzilla #" for not working ones, both to
> help people track them and to encourage submissions ?
Excellent idea.
Thanks for your thoughts,
--
David N. Welton
Personal: http://www.dedasys.com/davidw/
Free Software: http://www.dedasys.com/freesoftware/
Apache Tcl: http://tcl.apache.org/
Photos: http://www.dedasys.com/photos/
next prev parent reply other threads:[~2004-08-22 20:52 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 19:41 Linux Incompatibility List David N. Welton
2004-08-21 20:16 ` Joseph Pingenot
2004-08-21 20:20 ` Wakko Warner
2004-08-21 20:31 ` Lee Revell
2004-08-21 20:51 ` Wakko Warner
2004-08-21 21:06 ` Jan-Benedict Glaw
2004-08-21 21:11 ` Lee Revell
2004-08-21 21:16 ` Lee Revell
2004-08-22 14:30 ` Tonnerre
2004-08-22 14:45 ` Michael Buesch
2004-08-24 15:17 ` Jan-Benedict Glaw
2004-08-24 17:41 ` Michael Buesch
2004-08-21 21:18 ` Francois Romieu
2004-08-21 22:01 ` Wakko Warner
2004-08-21 23:53 ` Andrew Miklas
2004-08-23 3:54 ` Gianni Tedesco
2004-08-25 5:59 ` Andrew Miklas
2004-08-25 7:21 ` Gianni Tedesco
2004-08-29 1:42 ` Andrew Miklas
2004-08-29 3:21 ` Gianni Tedesco
2004-08-29 21:04 ` Andrew Miklas
2004-08-22 5:29 ` Jonathan Bastien-Filiatrault
2004-08-22 1:56 ` James Courtier-Dutton
2004-08-22 6:36 ` Jonathan Bastien-Filiatrault
2004-08-22 4:15 ` Kyle Moffett
2004-08-22 5:58 ` Lee Revell
2004-08-22 8:05 ` Geert Uytterhoeven
2004-08-22 12:07 ` R. J. Wysocki
2004-08-22 12:32 ` Gene Heskett
2004-08-24 21:30 ` Hamie
2004-08-22 15:25 ` Tonnerre
2004-08-22 11:10 ` Alan Cox
2004-08-22 12:42 ` Dave Jones
2004-08-23 6:31 ` Eric W. Biederman
2004-08-21 21:20 ` David N. Welton
2004-08-21 22:03 ` Wakko Warner
2004-08-22 0:18 ` Rutger Nijlunsing
2004-08-21 20:22 ` David N. Welton
2004-08-22 11:14 ` Alan Cox
2004-08-22 15:08 ` Joseph Pingenot
2004-08-22 20:48 ` David N. Welton [this message]
2004-08-22 20:45 ` Alan Cox
2004-08-23 20:45 ` cliff white
[not found] ` <200408221045.29316.mbuesch@freenet.de>
2004-08-22 20:34 ` David N. Welton
2004-08-22 21:24 ` David N. Welton
2004-08-25 7:41 ` Helge Hafting
2004-08-25 7:49 ` David N. Welton
2004-08-31 7:28 ` Helge Hafting
2004-08-31 10:21 ` David N. Welton
-- strict thread matches above, loose matches on Subject: below --
2004-08-22 4:19 linux
2004-08-22 13:05 ` Wakko Warner
2004-08-22 16:43 ` Horst von Brand
2004-08-22 22:42 ` Robin Rosenberg
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=87vffaq4p1.fsf@dedasys.com \
--to=davidw@dedasys.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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