public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: James Anslow <james@jamesanslow.net>
To: b43-dev@lists.infradead.org
Subject: [wireless-next][PATCH 0/3][ANNOUNCE] b43 the first Linux driver supporting HT-PHY (BCM4331)!
Date: Sat, 27 Aug 2011 13:59:50 +0100	[thread overview]
Message-ID: <4E58EA46.40202@jamesanslow.net> (raw)
In-Reply-To: <CACna6rzFhf=U9gXwo1k0j5G5=OHCHEuqCoxRF1kpVaqiSf9dwQ@mail.gmail.com>

On 27/08/11 11:22, Rafa? Mi?ecki wrote:
> 2011/8/27 James Anslow <james@jamesanslow.net>:
>> On 26/08/11 19:41, Rafa? Mi?ecki wrote:
>>> After improving DMA (the important patch for BCM4331 is my one) we can finally
>>> enable support for HT-PHY. The whole code has been written from MMIO dumps
>>> grabbed from ndiswrapper+windows driver, but seems to be stable and was tested
>>> by 3 people. Unfortunately there are still some missing conditions that can't
>>> be fixed without RE the closed driver or having Broadcom co-operating. However
>>> it seems we live with that well enough for basic usage :)
>>>
>>> BCM4331 doesn't have any Linux driver yet, both: wl and brcm80211 don't support
>>> it. So we can be really proud of it ;) Ah, and I should mention that ndiswrapper
>>> was frequently reported to lock up machines when working with this card (see
>>> Ubuntu's forum about MacBook 8.1).
>>>
>>> To use b43 with BCM4331 you will need to grab the newest b43-fwcutter and
>>> extract firmware from some recent closed source driver. See our wiki page in
>>> few hours for nice howto.
>>>
>>> Big thanks go to David Woodhouse for providing me access to his MacBook, letting
>>> grab the dumps, test patches and debugging a lot of hard cases with me (and
>>> sometime without ;) ).
>>>
>>> Larry Finger (1):
>>>   b43: Relax requirement for descriptors to be in the DMA zone
>>>
>>> Rafa? Mi?ecki (2):
>>>   b43: use 8K buffers for 64-bit DMA to workaround hardware bug
>>>   b43: make HT-PHY support experimental
>>>
>>>  drivers/net/wireless/b43/Kconfig |    6 +++---
>>>  drivers/net/wireless/b43/dma.c   |   31 ++++++++++++++++---------------
>>>  drivers/net/wireless/b43/dma.h   |    3 ++-
>>>  3 files changed, 21 insertions(+), 19 deletions(-)
>>>
>> I've checked the wiki page and downloads area but the latest version of
>> fwcutter that I could find was from several days ago.
>>
>> Can anyone direct me towards the latest b43-fwcutter download as
>> mentioned above?
>>
>> Can't wait to get 4331 support!
> Just use the howto for kernel 3.2 (I know it's a little tricky for now
> to use 3.2, wireless-next is also OK for that howto):
> http://wireless.kernel.org/en/users/Drivers/b43#Other_distributions_not_mentioned_above
>
> You have to:
> 1) Clone git repository wireless-next
> 2) Apply 3 patches from this patchset
> 3) Compile kernel with B43_PHY_HT
> 4) Install firmware (I think you already started that part)
>
> b43-fwcutter in 015 version is alright for extracting 666.2 firmware.
>
Thanks for your support on this.

I'm not too knowledgeable when it comes to kernel development. However,
I am eager to learn.

I've cloned the repo and have wireless-next.

Can you tell me where I will find these 3 patches to apply them to
wireless-next?

Many thanks

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20110827/b8264c1c/attachment-0001.sig>

  reply	other threads:[~2011-08-27 12:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-26 18:41 [wireless-next][PATCH 0/3][ANNOUNCE] b43 the first Linux driver supporting HT-PHY (BCM4331)! Rafał Miłecki
2011-08-26 19:56 ` James Anslow
2011-08-26 21:27 ` Michael Büsch
2011-08-26 21:34   ` Larry Finger
2011-08-27 10:16 ` James Anslow
2011-08-27 10:22   ` Rafał Miłecki
2011-08-27 12:59     ` James Anslow [this message]
2011-08-27 13:22       ` Rafał Miłecki
2011-08-27 13:38         ` James Anslow
2011-08-27 13:47           ` Rafał Miłecki

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=4E58EA46.40202@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