From: Arend van Spriel <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 00/16] brcmfmac: new device support and P2P fixes
Date: Mon, 11 Jan 2016 09:33:20 +0100 [thread overview]
Message-ID: <569368D0.8080906@broadcom.com> (raw)
In-Reply-To: <CACna6rxWJNo5vB+XH4nmL5bwqp5cmLO1O=V3XpB-NfFLeQVYDw@mail.gmail.com>
On 01/10/2016 10:12 PM, Rafał Miłecki wrote:
> On 10 January 2016 at 21:59, Arend van Spriel <arend@broadcom.com> wrote:
>> On 01/10/2016 12:48 AM, Rafał Miłecki wrote:
>>>
>>> On 18 September 2015 at 22:08, Arend van Spriel <arend@broadcom.com>
>>> wrote:
>>>>
>>>> This series is intended for v4.4 containing the following highlights:
>>>>
>>>> * support for BCM4350, BCM4365, and BCM4366 PCIE devices.
>>>> * fixed for legacy P2P and P2P device handling.
>>>> * correct set and get tx-power.
>>>
>>>
>>> Hi Arend, can you provide us some update on progress of releasing
>>> brcmfmac4366b-pcie.bin, please?
>>
>>
>> Sure. No progress. You also want to know about brcmfmac4365b-pcie.bin? Both
>> devices are still in development or just taped-out if I am not mistaken
>> (maybe missed a memo or two). I will ask for expected eta.
>
> I'm not really interested in BCM4365 as I can't find any market device
> using this chipset.
>
> BCM4366 can be found in following devices:
> ASUS RT-AC3100
> ASUS RT-AC5300
> ASUS RT-AC88U
> D-Link DIR-885L rev A1
> D-Link DIR-895L rev A1
> Netgear R8500
>
> You can already buy most of them in US, ASUS RT-AC5300 is also
> available in Europe.
So I missed the memo. Thanks.
Gr. AvS
prev parent reply other threads:[~2016-01-11 8:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 20:08 [PATCH 00/16] brcmfmac: new device support and P2P fixes Arend van Spriel
2015-09-18 20:08 ` [PATCH 01/16] brcmfmac: Fix exception handling Arend van Spriel
2015-09-19 9:43 ` Arend van Spriel
2015-09-29 7:57 ` [01/16] " Kalle Valo
2015-09-18 20:08 ` [PATCH 02/16] brcmfmac: Add support for the BCM4350 PCIE device Arend van Spriel
2015-09-18 20:08 ` [PATCH 03/16] brcmfmac: Fix set and get tx-power functions Arend van Spriel
2015-09-18 20:08 ` [PATCH 04/16] brcmfmac: Only assign primary netdev to if2bss array Arend van Spriel
2015-09-18 20:08 ` [PATCH 05/16] brcmfmac: Inform p2p module about p2pon through API Arend van Spriel
2015-09-18 20:08 ` [PATCH 06/16] brcmfmac: Fix bug in flowring management Arend van Spriel
2015-09-18 20:08 ` [PATCH 07/16] brcmfmac: Make p2pon module param always available Arend van Spriel
2015-09-18 20:08 ` [PATCH 08/16] brcmfmac: Workaround in change vif for wpa_supplicant support Arend van Spriel
2015-09-18 20:08 ` [PATCH 09/16] brcmfmac: Deleting of p2p device is leaking memory Arend van Spriel
2015-09-18 20:08 ` [PATCH 10/16] brcmfmac: Only handle p2p_stop_device if vif is valid Arend van Spriel
2015-09-18 20:08 ` [PATCH 11/16] brcmfmac: Fix p2p bug for older firmwares Arend van Spriel
2015-09-18 20:08 ` [PATCH 12/16] brcmfmac: Add module parameter to disable features Arend van Spriel
2015-09-18 20:08 ` [PATCH 13/16] brcmfmac: Fix race condition bug when deleting p2p interface Arend van Spriel
2015-09-18 20:08 ` [PATCH 14/16] brcmfmac: Add support for the BCM4365 and BCM4366 PCIE devices Arend van Spriel
2015-09-18 20:08 ` [PATCH 15/16] brcmfmac: Fix TDLS setup by properly handling p2p noif Arend van Spriel
2015-09-18 20:08 ` [PATCH 16/16] brcmfmac: Accept events when TDLS is used in combination with p2p Arend van Spriel
2015-09-19 9:43 ` Arend van Spriel
2015-09-18 21:29 ` [PATCH 00/16] brcmfmac: new device support and P2P fixes Rafał Miłecki
2015-09-19 9:40 ` Arend van Spriel
2015-09-19 14:24 ` Arend van Spriel
2015-09-19 15:05 ` Rafał Miłecki
2015-09-19 16:32 ` Arend van Spriel
2015-09-21 12:17 ` Kalle Valo
2015-09-28 17:48 ` Arend van Spriel
2015-09-28 18:14 ` Pending patches in patchwork and their states Kalle Valo
2016-01-09 23:48 ` [PATCH 00/16] brcmfmac: new device support and P2P fixes Rafał Miłecki
2016-01-10 20:59 ` Arend van Spriel
2016-01-10 21:12 ` Rafał Miłecki
2016-01-11 8:33 ` Arend van Spriel [this message]
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=569368D0.8080906@broadcom.com \
--to=arend@broadcom.com \
--cc=kvalo@codeaurora.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).