From: Arend van Spriel <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Hante Meuleman <meuleman@broadcom.com>
Subject: Re: [PATCH 2/8] brcmfmac: Add USB device 43566 to supported devices.
Date: Sat, 21 Jun 2014 18:56:59 +0200 [thread overview]
Message-ID: <53A5B95B.2040705@broadcom.com> (raw)
In-Reply-To: <CACna6rz81wbFET4GJH8xQ8aTqGfGccPGmD5vwfmmw9KWsZRPWg@mail.gmail.com>
On 06/21/14 17:55, Rafał Miłecki wrote:
> On 21 June 2014 12:11, Arend van Spriel<arend@broadcom.com> wrote:
>> From: Hante Meuleman<meuleman@broadcom.com>
>>
>> Add the USB 43566 device to the supported devices list. The 43566
>> is a WiFi-only variant of the 43569. It uses the same FW as 43569.
>
> What about USB ID of this device? You didn't add any. Is it shared
> with some different one? A 0a5c:bd27 maybe?
The 43566 has exactly the same USB ID as the 43569. The bootloader in
the device will tell brcmfmac what it is during probe. These devices are
exactly the same for the WiFi part, but 43569 additionally has BT logic
inside being a composite USB device. Patch 4 probably is needed to make
that work. That probably would have been clear when mentioned in the
43569 patch.
Regards,
Arend
next prev parent reply other threads:[~2014-06-21 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-21 10:11 [PATCH 0/8] brcmfmac: new USB devices, vendor command, and cleanup Arend van Spriel
2014-06-21 10:11 ` [PATCH 1/8] brcmfmac: Add 43569 USB support Arend van Spriel
2014-06-21 10:11 ` [PATCH 2/8] brcmfmac: Add USB device 43566 to supported devices Arend van Spriel
2014-06-21 15:55 ` Rafał Miłecki
2014-06-21 16:56 ` Arend van Spriel [this message]
2014-06-21 10:11 ` [PATCH 3/8] brcmfmac: clear ht info during attach phase Arend van Spriel
2014-06-21 10:11 ` [PATCH 4/8] brcmfmac: Change USB probe routine to support Composite USB Arend van Spriel
2014-06-21 10:11 ` [PATCH 5/8] brcmfmac: replace cfg80211 testmode with vendor command Arend van Spriel
2014-06-21 10:11 ` [PATCH 6/8] brcmfmac: correct logging levels in btcoex source Arend van Spriel
2014-06-21 10:11 ` [PATCH 7/8] brcmfmac: Don't control mpc setting during scan operation Arend van Spriel
2014-06-21 10:11 ` [PATCH 8/8] brcmfmac: reduce log level in fwil if firmware returns error Arend van Spriel
2014-06-21 15:58 ` [PATCH 0/8] brcmfmac: new USB devices, vendor command, and cleanup Rafał Miłecki
2014-06-21 16:48 ` Arend van Spriel
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=53A5B95B.2040705@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=meuleman@broadcom.com \
--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).