Re: Question about BCM43228 and outdated description in MAINTAINERS

[Larry Finger <Larry.Finger@lwfinger.net>]

On 06/27/2012 03:37 AM, Arend van Spriel wrote:
> On 06/25/2012 05:41 PM, Larry Finger wrote:
>
> I noticed your email on the lockdep_init_map() function. Maybe the
> hybrid driver will be modified, but I leave that to Brett.

Obviously, the kernel will not be changed to make that routine available.

> My personal experience with ndiswrapper on 64-bit kernels is different,
> but I tend to consider ndiswrapper as a last resort. Most issues I had
> were between ndiswrapper and wpa_supplicant (when using dbus ipc).
>
>> Reverse engineering this device to be able to drive it with b43 would
>> involve a lot of effort. If your group is planning on adding it to
>> brcmsmac, then I would not undertake this project. To the fullest extent
>> that you can, please advise me regarding this matter.
>
> Our focus is currently on extending brcmfmac. We had requests for 43228
> support before, but did not start that task. Will inform internally what
> the plan is here and let you know to the fullest extent ;-)

Any help you can give will be appreciated.

>
> Under the folder drivers/net/wireless/brcm80211/ are both brcmfmac and
> brcmsmac (and shared module brcmutil). So maybe patch it like this:
>
> - BROADCOM BRCM80211 IEEE802.11n WIRELESS DRIVER
> + BROADCOM BRCM80211 IEEE802.11n WIRELESS DRIVERS

That will help, but perhaps you might make it

+ BROADCOM BRCM80211 IEEE802.11n WIRELESS DRIVERS (brcmsmac, brcmfmac)

This way, a search for brcmsmac or brcmfmac will succeed.

Larry