From: Lee Revell <rlrevell@joe-job.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Wakko Warner <wakko@animx.eu.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux Incompatibility List
Date: Sat, 21 Aug 2004 17:16:52 -0400 [thread overview]
Message-ID: <1093123011.854.173.camel@krustophenia.net> (raw)
In-Reply-To: <20040821210606.GA18334@lug-owl.de>
On Sat, 2004-08-21 at 17:06, Jan-Benedict Glaw wrote:
> On Sat, 2004-08-21 16:51:57 -0400, Wakko Warner <wakko@animx.eu.org>
> wrote in message <20040821205157.GA9300@animx.eu.org>:
> > > Nvidia. AFAIK all nvidia Linux drivers are either binary-only or
> > > reverse-engineered.
> >
> > True, however, their video cards *DO* work on linux (even though it is
> > binary-only). I have a laptop that has the chip. Does any broadcom
> > wireless chip work on linux (ndis wrapper or that piece of junk from
> > linuxant doesn't count)
>
> Right, binary-only drivers and/or GPLed/OSS drivers should be counted
> separately. Think about AVM's ISDN cards (very popular over here in
> Germany, but the newer products require a CAPI-only binary-only
> driver:-(
>
Also, it's probably best to focus on new products. Many vendors, VIA
for example, are now very Linux friendly, but were not always so in the
past, and may not be able to release OSS drivers for older products due
to IP issues.
Lee
next prev parent reply other threads:[~2004-08-21 21:19 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 [this message]
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
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=1093123011.854.173.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
--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