All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>
Subject: brcmsmac on BCM47XX SoCs
Date: Tue, 10 Apr 2012 16:18:48 +0200	[thread overview]
Message-ID: <4F844148.2010701@broadcom.com> (raw)
In-Reply-To: <4F82CE7B.8010803@hauke-m.de>

On 04/09/2012 01:56 PM, Hauke Mehrtens wrote:
> On 04/08/2012 09:54 PM, Rafa? Mi?ecki wrote:
>> 2012/4/8 Arend van Spriel<arend@broadcom.com>:
>>> On 04/06/2012 11:43 PM, Hauke Mehrtens wrote:
>>>> What are your plans to support phy_ht in brcmsmac, for now it is just
>>>> supported by b43?
>>>
>>>
>>> I have not been paying good attention to community feedback on b43 phy_ht
>>> support. As b43 support bcm4331 with that phy we decided to stay clear from
>>> that device. We are to add new phy code for new devices. Not sure if that
>>> includes the phy_ht.
>>
>> Whoops, that's extremely too bad. HT support is really wanted for a
>> lot of routers. What we have in b43 is support coming from watching
>> mmio ops only, there is no way for it to be complete. I believe you
>> really should think and releasing HT PHY code, a lot of ppl will be
>> interested in that.
>>
> The TODO list for brcmsmac in the wireless wiki [0] says "Add support
> for more chips, including (near term) BCM43227, BCM43228, and BCM4331."
> The BCM4331 uses a HT-Phy, but b43 does not support 802.11n speed (the
> chip supports up to 450MBit/s) and 5GHz wifi and I do not think b43 will
> support these features in the near future, if it will ever support these
> features.

Yes. bcm4331 was/is on our TODO list, but when b43 added support for it 
we were unsure how to move forward.

> I do not think it is a big problem if brcmsmac supports some chips b43
> also supports as b43 misses some important features, for now some
> devices IDs for devices supported by brcmsmac and b43 they are
> deactivated in b43 by default so brcmsmac is used every time. I would
> like to see brcmsmac supporting all wifi chips using bcma (ai bus).

I am 100% with you and counting the votes I think we should add bcm4331 
as well ;-)

Gr. AvS

WARNING: multiple messages have this Message-ID (diff)
From: "Arend van Spriel" <arend@broadcom.com>
To: "Hauke Mehrtens" <hauke@hauke-m.de>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>
Subject: Re: brcmsmac on BCM47XX SoCs
Date: Tue, 10 Apr 2012 16:18:48 +0200	[thread overview]
Message-ID: <4F844148.2010701@broadcom.com> (raw)
In-Reply-To: <4F82CE7B.8010803@hauke-m.de>

On 04/09/2012 01:56 PM, Hauke Mehrtens wrote:
> On 04/08/2012 09:54 PM, Rafał Miłecki wrote:
>> 2012/4/8 Arend van Spriel<arend@broadcom.com>:
>>> On 04/06/2012 11:43 PM, Hauke Mehrtens wrote:
>>>> What are your plans to support phy_ht in brcmsmac, for now it is just
>>>> supported by b43?
>>>
>>>
>>> I have not been paying good attention to community feedback on b43 phy_ht
>>> support. As b43 support bcm4331 with that phy we decided to stay clear from
>>> that device. We are to add new phy code for new devices. Not sure if that
>>> includes the phy_ht.
>>
>> Whoops, that's extremely too bad. HT support is really wanted for a
>> lot of routers. What we have in b43 is support coming from watching
>> mmio ops only, there is no way for it to be complete. I believe you
>> really should think and releasing HT PHY code, a lot of ppl will be
>> interested in that.
>>
> The TODO list for brcmsmac in the wireless wiki [0] says "Add support
> for more chips, including (near term) BCM43227, BCM43228, and BCM4331."
> The BCM4331 uses a HT-Phy, but b43 does not support 802.11n speed (the
> chip supports up to 450MBit/s) and 5GHz wifi and I do not think b43 will
> support these features in the near future, if it will ever support these
> features.

Yes. bcm4331 was/is on our TODO list, but when b43 added support for it 
we were unsure how to move forward.

> I do not think it is a big problem if brcmsmac supports some chips b43
> also supports as b43 misses some important features, for now some
> devices IDs for devices supported by brcmsmac and b43 they are
> deactivated in b43 by default so brcmsmac is used every time. I would
> like to see brcmsmac supporting all wifi chips using bcma (ai bus).

I am 100% with you and counting the votes I think we should add bcm4331 
as well ;-)

Gr. AvS


  reply	other threads:[~2012-04-10 14:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 22:43 brcmsmac on BCM47XX SoCs Hauke Mehrtens
2012-04-08  8:51 ` Arend van Spriel
2012-04-08  8:51   ` Arend van Spriel
2012-04-08 19:54   ` Rafał Miłecki
2012-04-08 19:54     ` Rafał Miłecki
2012-04-09 11:56     ` Hauke Mehrtens
2012-04-09 11:56       ` Hauke Mehrtens
2012-04-10 14:18       ` Arend van Spriel [this message]
2012-04-10 14:18         ` Arend van Spriel
2012-04-09 13:32     ` Seth Forshee
2012-04-09 13:32       ` Seth Forshee
2012-04-09 13:06   ` Hauke Mehrtens
2012-04-09 13:06     ` Hauke Mehrtens
2012-04-14 20:20   ` Hauke Mehrtens
2012-04-14 20:20     ` Hauke Mehrtens

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=4F844148.2010701@broadcom.com \
    --to=arend@broadcom.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=hauke@hauke-m.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.