public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+hb@blue-labs.org>
To: linux-kernel@vger.kernel.org
Subject: Re: LInksys WMP11 (BCM4301 chip)
Date: Sat, 27 Sep 2003 23:21:14 -0400	[thread overview]
Message-ID: <3F7653AA.2090806@blue-labs.org> (raw)
In-Reply-To: <200309272238.50475.public@mikl.as>

I'm _eagerly_ awaiting more information :)

There's a project on sourceforge, alas it hasn't gone anywhere in the 
several months that it's been there.  I'm relying on my laptop to route 
for me because it has builtin wireless/lan on it and I really need 
network access on my desktop.  I now have two linksys wireless pieces 
of...stuff, and neither are supported or supported well.  I.e the WMP11 
and the WUSB11.

The WUSB11 is slowly moving along, but it's far behind 2.6.0.

I used to by Linksys net Netgear stuff because they were reliable and 
they sometimes stated "Linux" directly on the product box.  These days 
I'm starting to get jaded.  It seems that the 'buzzword hype' of putting 
"Linux" on the box has disappeared.  Pretty fscking annoying when the 
community that can best improve a driver and freely at that, is occluded.

Getting back to the subject.  I have both the WUSB11 and the WMP11 and 
I'm more than willing to provide data for testing.  Even if I gotta 
hardwire the things with baling wire and bubble gum, I gotta get one of 
them working.

David
p.s. To Erik: yes, I know the article was spun :(  I read Andrew's 
original post.  Unfortunately it was spun to say that BC made linux 
people happy.

Andrew Miklas wrote:

>The link mentioned quotes me as saying that the BCM4300 series of wireless 
>chips has excellent support on the MIPS architecture, which indeed it does. 
>Unfortunately, what they don't mention is that the source for that driver was 
>not, and has not been released by Linksys or Broadcom.  Also, the binary 
>driver is only available in the firmware of networking products, like the 
>WRT54G, using Broadcom wireless chips.
>
>Hopefully, I'll have some more information to post here about that in the 
>coming few days.
>  
>


  reply	other threads:[~2003-09-28  3:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-28  2:38 LInksys WMP11 (BCM4301 chip) Andrew Miklas
2003-09-28  3:21 ` David Ford [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-27 22:54 David Ford
2003-09-28  3:05 ` Erik Andersen

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=3F7653AA.2090806@blue-labs.org \
    --to=david+hb@blue-labs.org \
    --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