From: Jonathan Bastien-Filiatrault <joe@dastyle.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Wakko Warner <wakko@animx.eu.org>,
"David N. Welton" <davidw@dedasys.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux Incompatibility List
Date: Sun, 22 Aug 2004 01:29:48 -0400 [thread overview]
Message-ID: <41282F4C.9060305@dastyle.net> (raw)
In-Reply-To: <1093120274.854.145.camel@krustophenia.net>
Lee Revell wrote:
>On Sat, 2004-08-21 at 16:20, Wakko Warner wrote:
>
>
>>>>Ideas/comments/suggestions are welcome at this stage.
>>>>
>>>>
>>>Sounds interesting; is there a vendor blacklist (i.e. vendors that are
>>> either hostile toward or simply don't care about Linux and their products
>>> just won't ever work with Linux?)
>>>
>>>
>>Broadcom's wireless chips come to mind...
>>
>>
>
>Nvidia. AFAIK all nvidia Linux drivers are either binary-only or
>reverse-engineered.
>
>To add insult to injury they have a stupid 20+page 'Nvidia Linux
>Advantage' whitepaper on their site that conveniently fails to mention
>the above. They probably spent more money for some marketroid to put
>that together than they ever spent on actually supporting Linux.
>
>
Vendors should understand that ACTUALLY supporting linux means adopting
the free software philosophy. In many cases, vendors think that they
should be the only one to be able to write drivers, since 99% of desktop
users dont care about their software freedom. Vendors should not try to
obscure the workings of their devices, they should show the world how
they are innovating in hardware design by releasing specs on a
freely-redistributable basis. This would greatly improve competiveness
and innovation in the domain of hardware design. Give me a binary driver
and i will buy from you once, give me the specs and i'll appreciate the
effort you put in designing the device.
next prev parent reply other threads:[~2004-08-22 1:30 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 [this message]
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
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=41282F4C.9060305@dastyle.net \
--to=joe@dastyle.net \
--cc=davidw@dedasys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=wakko@animx.eu.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