public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: BCM5354
Date: Mon, 07 Jun 2010 13:48:22 -0500	[thread overview]
Message-ID: <4C0D3EF6.3040908@lwfinger.net> (raw)
In-Reply-To: <4C0D3B89.7060600@sephix.com>

On 06/07/2010 01:33 PM, Robert Hazbun wrote:
> Hello all,
> 
> I currently work for a company that is using OpenWRT, with linux 2.4, on
> a BCM5354. We really want to move to OpenWRT with linux 2.6 using the
> b43 driver on this chip. Initial test results show that b43 seems to
> work in client / Adhoc mode, but not in AP mode. Unfortunately, I have
> been unable to ascertain the status of the b43 driver with respect to
> this chip.
> 
> Can anyone confirm whether it's fully functional under this platform? If
> not, what's left to be done ?

I believe the BCM5354 has an LP PHY. As such, it should be supported by
any 2.6.32, or later, kernel. AFAIK, no such device has been tested by a
developer. My tests with a BCM4312, which also has an LP PHY, show that
b43/mac80211 will function as an AP using recent versions of hostapd.

Larry

  reply	other threads:[~2010-06-07 18:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07 18:33 BCM5354 Robert Hazbun
2010-06-07 18:48 ` Larry Finger [this message]
2010-06-07 19:00   ` BCM5354 Michael Büsch
     [not found]   ` <4C0D40C2.7050409@sephix.com>
2010-06-07 19:42     ` BCM5354 Larry Finger
2010-06-07 19:55       ` BCM5354 Robert Hazbun
2010-06-07 20:11         ` BCM5354 Gábor Stefanik
2010-06-07 23:38           ` BCM5354 Chris Martin
2010-06-08  1:14             ` BCM5354 Gábor Stefanik
2010-06-08  2:52               ` BCM5354 Chris Martin
2010-06-08  3:29                 ` BCM5354 Gábor Stefanik
2010-06-08  4:41                   ` BCM5354 Chris Martin
2010-06-08  5:00             ` BCM5354 Michael Büsch

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=4C0D3EF6.3040908@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.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