From: Arjan van de Ven <arjan@infradead.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Denis Vlasenko <vda@ilport.com.ua>,
abonilla@linuxwireless.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Wireless support
Date: Mon, 08 Aug 2005 19:51:16 +0200 [thread overview]
Message-ID: <1123523476.3245.51.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1123523298.15269.18.camel@mindpipe>
On Mon, 2005-08-08 at 13:48 -0400, Lee Revell wrote:
> On Mon, 2005-08-08 at 09:31 +0300, Denis Vlasenko wrote:
> > On Monday 08 August 2005 03:39, Alejandro Bonilla Beeche wrote:
> > > On Sun, 2005-08-07 at 15:22 -0400, Lee Revell wrote:
> > > > Is the Linksys WUSB 54GS wireless adapter (FCCID Q87-WUSB54GS)
> > > > supported?
> > >
> > > Normally, linksys doesn't care much about Linux and they won't even
> > > release info for a driver. Yeah, they have some open info for the WRT's
> > > but the adapters are normally usable with ndiswrapper or Linuxant
> > > driver.
> >
> > The more I read this, the more I think about usefulness of blacklisting
> > ndiswrapper.
>
> What's your reasoning? The technical aspect of the argument is obvious
> (incompatible with 4K stacks) but the political side seems insolvable.
> Wouldn't this leave thousands of users with non working hardware?\
arguably it doesn't really work with ndiswrapper either; only most of
the time (due to windows having a 12kb stack)... and it's effectively a
binary only kernel module.
it also provides a discentive for vendors to provide real linux
drivers....
next prev parent reply other threads:[~2005-08-08 17:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 19:22 Lee Revell
2005-08-07 19:56 ` Lee Revell
2005-08-08 5:50 ` Martin J. Bligh
2005-08-08 17:57 ` Lee Revell
2005-08-08 0:39 ` Alejandro Bonilla Beeche
2005-08-08 1:20 ` Lee Revell
2005-08-08 1:29 ` Alejandro Bonilla Beeche
2005-08-08 6:31 ` Denis Vlasenko
2005-08-08 17:48 ` Lee Revell
2005-08-08 17:51 ` Arjan van de Ven [this message]
2005-08-08 18:13 ` Andreas Steinmetz
2005-08-08 18:19 ` Lee Revell
2005-08-08 18:24 ` Andreas Steinmetz
2005-08-08 18:27 ` Lee Revell
2005-08-08 18:56 ` Alejandro Bonilla
2005-08-08 19:06 ` Lee Revell
2005-08-08 19:55 ` alan
2005-08-08 23:29 ` Adrian Bunk
2005-08-08 23:43 ` Alejandro Bonilla Beeche
2005-08-09 9:09 ` Jochen Friedrich
2005-08-09 13:52 ` Kyle Moffett
2005-08-09 14:24 ` Rafael J. Wysocki
2005-08-09 16:09 ` Jochen Friedrich
2005-08-12 2:40 ` Lee Revell
2005-08-12 2:59 ` roucaries bastien
2005-08-12 3:17 ` Lee Revell
2005-08-12 4:18 ` Kyle Moffett
2005-08-08 19:27 ` linux-os (Dick Johnson)
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=1123523476.3245.51.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=abonilla@linuxwireless.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=vda@ilport.com.ua \
/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®