From: james at jamesanslow.net <james@jamesanslow.net>
To: b43-dev@lists.infradead.org
Subject: 4331 support
Date: Fri, 26 Aug 2011 00:27:31 +0100 [thread overview]
Message-ID: <20110826002731.55067eao70ovewg8@jamesanslow.net> (raw)
In-Reply-To: <4E56D231.5080306@lwfinger.net>
Hi Larry,
Thanks for getting back to me on this. I'm not overly experienced when
it comes to driver development and so I may be best suited to waiting
until this is made live. That is, unless compiling and patching
experimental drivers is an easy thing to do (but from what I
understand it's not?)
Kind regards,
James
Quoting Larry Finger <Larry.Finger@lwfinger.net>:
> On 08/25/2011 05:38 PM, james at jamesanslow.net wrote:
>> Can anyone provide me with an update as to the current status of BCM 4331
>> support? Is support going to be coming eventually? Is anyone working on it?
>
> If you pull the wireless-testing git tree, it is working, perhaps
> with minor changes. See a recent mail message:
>
> ========================================
> Awesome guys,
> thanks for the pointers, it worked! (i m sending this email using
> the b43 driver!)
>
> I used the wireless-next git, and then additionally applied the
> "b43: HT-PHY: allow writing longer tables with a single call" patch.
> (and the ones in Rafal's last mail)
>
> Thanks for the great support and fast answers!
> Congratulations on hacking a driver like this together, I am impressed!
>
> Best regards,
> Maxime
>
> 2011/8/22 Rafa? Mi?ecki <zajec5@gmail.com>
>
> Hi Maxime,
>
> 2011/8/22 Maxime Vincent <maxime.vince@gmail.com>:
> > I'm sorry if this is a noobish question, or asking this kind
> of questions is
> > not done.
> > I'm not really familiar with dev mailing lists.
> > I'm new to kernel development, not new to linux.
> >
> > I was wondering what the status of support for the 4331 wifi
> chipset was?
> > As I can see there's already quite some code for the 4331
> chipset, but I
> > can't really make up from that if it's supposed to work or
> not, or maybe
> > partially?
> >
> > I have compiled latest linux-next kernel including the b43
> driver, extracted
> > firmware, but I can't seem to see an interface registering.
> > Only thing I can see in dmesg:
> > Broadcom 43xx driver loaded [ Features: PMNLS, Firmware-ID: FW13 ]
>
> I'm going to clean HT-PHY (BCM4331) support in about a week, as David
> wrote, it should be quite stable.
>
> Most of the patches are already in wireless-next, I just need to test
> that tree, see if everything was sent&applied correctly and drop
> BROKEN from B43_PHY_HT.
>
> If you're "brave" enough, you can:
> 1) Edit Kconfig and drop BROKEN from B43_PHY_HT
> 2) Edit dma.h and define B43_DMA_RINGMEMSIZE to "2 * PAGE_SIZE"
> (or just wait a week).
> ===============================================
>
>
> Larry
>
next prev parent reply other threads:[~2011-08-25 23:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 22:38 4331 support james at jamesanslow.net
2011-08-25 22:52 ` Larry Finger
2011-08-25 23:27 ` james at jamesanslow.net [this message]
2011-08-25 23:36 ` Larry Finger
2011-08-25 23:39 ` james at jamesanslow.net
2011-08-26 0:33 ` Stuart Longland
2011-08-26 1:14 ` Larry Finger
2011-08-26 15:29 ` James Anslow
2011-08-26 15:35 ` Larry Finger
2011-08-26 15:38 ` James Anslow
2011-08-26 15:57 ` Larry Finger
-- strict thread matches above, loose matches on Subject: below --
2011-08-26 16:13 james at jamesanslow.net
2011-08-26 17:01 ` Larry Finger
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=20110826002731.55067eao70ovewg8@jamesanslow.net \
--to=james@jamesanslow.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