From: "Martin J. Bligh" <mbligh@mbligh.org>
To: Lee Revell <rlrevell@joe-job.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Wireless support
Date: Sun, 07 Aug 2005 22:50:34 -0700 [thread overview]
Message-ID: <392810000.1123480234@[10.10.2.4]> (raw)
In-Reply-To: <1123444566.12766.23.camel@mindpipe>
--Lee Revell <rlrevell@joe-job.com> wrote (on Sunday, August 07, 2005 15:56:06 -0400):
> On Sun, 2005-08-07 at 15:22 -0400, Lee Revell wrote:
>> Is the Linksys WUSB 54GS wireless adapter (FCCID Q87-WUSB54GS)
>> supported?
>>
>
> Wow, Google has really declined in quality. I got zero hits for
> "Linksys WUSB 54G linux". Then I found this page on my own.
>
> (from http://ndiswrapper.sourceforge.net/mediawiki/index.php/List)
>
> Card: Linksys #[WUSB54G], 802.11b/g, USB 2.0 -- [link here|List#WUSB54G]
> * Chipset: Prism54
> * usbid: 5041:2234
> * Driver: Linksys Windows XP driver
> http://www.linksys.com/download/default.asp
> * Other: Works smoothly, of course ;) - this is the device the USB
> extension was originally developed for. WEP is running, WPA is
> supported using wpa_supplicant 0.2.5. No problems with both 1.1
> and 2.0 host controllers. As with many other USB devices, no
> success with 2.4 kernels so far. Try to use 2.6.7 or better.
> There is a native driver for Prism54 that is working on USB
> support. View its status at Prism54.org
>
> Sorry for the WOB. And if anyone from Google is reading, WTF?
It doesn't actually say it works on Linux. Perhaps you wanted
mysticgooglepsychic.com? ;-)
I don't think it is reasonable to expect google to know what ndiswrapper
is ... or perhaps it just has a taste filter installed? ;-)
M.
next prev parent reply other threads:[~2005-08-08 5:50 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 [this message]
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
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='392810000.1123480234@[10.10.2.4]' \
--to=mbligh@mbligh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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®