From: Angus Ainslie <angus@akkea.ca>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: Andy Green <andy@warmcat.com>, Shengyu Qu <wiagn233@outlook.com>,
franky.lin@broadcom.com, linux-wireless@vger.kernel.org
Subject: Re: AP6275 / bcm43752 pcie on mainline brcmf
Date: Sat, 03 Dec 2022 05:56:37 -0800 [thread overview]
Message-ID: <852dcabac6bd70a7d55b5ea3f6b0df20@akkea.ca> (raw)
In-Reply-To: <3163e341-bcfc-a2c3-f0e1-5b62c9da2f43@broadcom.com>
On 2022-11-29 11:48, Arend van Spriel wrote:
> On 11/17/2022 7:36 PM, Angus Ainslie wrote:
>> On 2022-11-17 10:12, Arend Van Spriel wrote:
>>> On November 17, 2022 5:06:25 PM Angus Ainslie <angus@akkea.ca> wrote:
>>>
>>>> On 2022-11-17 04:01, Andy Green wrote:
>>>>> On 11/17/22 09:23, Arend van Spriel wrote:
>>>>>> On 11/16/2022 1:25 PM, Shengyu Qu wrote:
>>>>>>> Got a new version of downstream driver and firmware here:
>>>>>>> https://gitlab.com/rk3588_linux/linux/external/rkwifibt/-/tree/linux-5.10-gen-rkr3.4
>>>>>>
>>>>>> Thanks for that. The firmware indeed seems to originate from
>>>>>> Synaptics
>>>>>> and this module can be found on wifi-alliance product finder:
>>>>>>
>>>>>> https://www.wi-fi.org/product-finder-results?sort_by=certified&sort_order=desc&keywords=ap6275
>>>>>>
>>>>>> We have no known contacts there and they do not seem to have much
>>>>>> interest in open-source. In that gitlab repo I see they are
>>>>>> providing
>>>>>> bcmdhd driver and I assume they consider that sufficient.
>>>>>>
>>>>>> Will see what I can do. First have to think on how to approach
>>>>>> this
>>>>>> failure to get most out of a debug effort. I do not have the
>>>>>> module
>>>>>> over here so we would need to go back and forth. The fact that the
>>>>>> issue is seen on both SDIO and PCIe is somewhat encouraging.
>>>>>
>>>>> Yes it seems that at some point with some firmware, SDIO has worked
>>>>> for, eg, Angus. And, it should work well with bchdhd (but that
>>>>> does
>>>>> not seem to work for scan for me on v6.1-rc5 uplevel with the
>>>>> firmware
>>>>> load changed to use kernel apis; but the firmware has no timeout on
>>>>> bcmdhd). So it doesn't feel a million miles away.
>>>>
>>>> This is the firmware we have been using for SDIO. It was sent to us
>>>> directly by SparkLAN so not sure how it compares to other variants.
>>>>
>>>> https://source.puri.sm/Librem5/firmware-brcm43752-nonfree/-/tree/master/firmware/brcm
>>>
>>> It is a tad bit older:
>>>
>>> $ strings brcmfmac43752-sdio.bin | grep FW-TAG
>>> <FW-TAG>4362a2-roml/config_sdio_ampak_release_he
>>> Version=18.35.387.23.7 (b328500@shgit) (wlan=r880297)
>>> Date=2020-07-13T10:34:00Z FWID=01-f50fdff0
>>>
>>
>> Currently it's broken for hotspot mode but I haven't had the chance to
>> see if that is FW or something further up the stack.
>
> Hi Angus,
>
> When you added support for this device in brcmfmac you marked it as a
> Cypress device. Are you sure about that? AFAICT this device is coming
> from Synaptics.
>
Hi Arend,
I assumed Cypress based on the fact that it most closely resembled the
4373 from the driver side.
How would I figure out whether it's Cypress or Synaptics ?
When I search the web for it I only find SparkLAN or "AMPAK technology"
references.
Thanks
Angus
> Regards,
> Arend
>
>> Angus
>>
>>> Thanks,
>>> Arend
>>>
>>>>
>>>> Angus
>>>>
>>>>> I have the hw, and (paid) time to help with debugging this "pair of
>>>>> hands" style. I'm also a little familiar with the kernel code and
>>>>> can
>>>>> try jiggle things autonomously if you can prompt what is
>>>>> interesting.
>>>>>
>>>>> -Andy
>>>>>
>>>>>> Regards,
>>>>>> Arend
next prev parent reply other threads:[~2022-12-03 13:56 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1D540F2B-17E8-4992-BD06-4AA4A66B1964@warmcat.com>
[not found] ` <1845da4b838.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
[not found] ` <b5f564da-d0c1-4617-fef1-771ccdda18e4@warmcat.com>
2022-11-10 7:06 ` AP6275 / bcm43752 pcie on mainline brcmf Andy Green
2022-11-10 7:35 ` Arend Van Spriel
2022-11-13 8:26 ` Shengyu Qu
2022-11-13 9:03 ` Andy Green
2022-11-13 9:10 ` Shengyu Qu
2022-11-13 9:41 ` Andy Green
2022-11-13 10:04 ` Shengyu Qu
2022-11-13 10:56 ` Arend Van Spriel
2022-11-13 15:52 ` Shengyu Qu
2022-11-13 17:35 ` Arend Van Spriel
2022-11-13 18:43 ` Andy Green
2022-11-16 12:25 ` Shengyu Qu
2022-11-16 14:16 ` Andy Green
2022-11-17 9:23 ` Arend van Spriel
2022-11-17 12:01 ` Andy Green
2022-11-17 16:06 ` Angus Ainslie
2022-11-17 18:12 ` Arend Van Spriel
2022-11-17 18:36 ` Angus Ainslie
2022-11-29 19:48 ` Arend van Spriel
2022-12-03 13:56 ` Angus Ainslie [this message]
2022-12-03 15:22 ` Arend Van Spriel
2022-12-03 15:37 ` Angus Ainslie
2022-12-03 17:08 ` Arend Van Spriel
2022-12-04 14:33 ` Angus Ainslie
2022-12-04 15:29 ` Arend Van Spriel
2022-11-17 21:52 ` Arend Van Spriel
2022-11-18 5:41 ` Andy Green
2022-11-24 9:42 ` Arend van Spriel
2022-11-24 10:20 ` Andy Green
2022-11-24 10:49 ` Arend van Spriel
2022-11-24 11:04 ` Andy Green
2022-11-24 11:07 ` Arend van Spriel
2022-11-24 11:11 ` Andy Green
2022-11-24 11:18 ` Arend van Spriel
2022-11-24 11:24 ` Andy Green
2022-11-24 12:14 ` Andy Green
2022-11-24 12:22 ` Arend van Spriel
2022-11-24 12:24 ` Shengyu Qu
2022-11-24 12:26 ` Andy Green
2022-11-24 12:35 ` Shengyu Qu
2022-11-24 12:38 ` Arend van Spriel
2022-11-24 12:44 ` Arend van Spriel
2022-11-24 12:54 ` Andy Green
2022-11-24 13:47 ` Arend van Spriel
2022-11-24 14:16 ` Andy Green
2022-11-24 14:32 ` Andy Green
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=852dcabac6bd70a7d55b5ea3f6b0df20@akkea.ca \
--to=angus@akkea.ca \
--cc=andy@warmcat.com \
--cc=arend.vanspriel@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wiagn233@outlook.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