All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Shengyu Qu <wiagn233@outlook.com>, Andy Green <andy@warmcat.com>
Cc: franky.lin@broadcom.com, linux-wireless@vger.kernel.org
Subject: Re: AP6275 / bcm43752 pcie on mainline brcmf
Date: Thu, 17 Nov 2022 10:23:16 +0100	[thread overview]
Message-ID: <625f1d5d-e137-7ad7-96b9-92035e87df8b@broadcom.com> (raw)
In-Reply-To: <TY3P286MB26118BD94839F752CADCCF5298079@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 2164 bytes --]

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.

Regards,
Arend

> 于 2022年11月14日 GMT+08:00 上午1:35:49, Arend Van Spriel <arend.vanspriel@broadcom.com> 写到:
>> On November 13, 2022 4:52:45 PM Shengyu Qu <wiagn233@outlook.com> wrote:
>>
>>> 在 2022/11/13 18:56, Arend Van Spriel 写道:
>>
>> [snip]
>>
>>>
>>>
>>>>>
>>>>>> Besides who I should ask to make proper firmware for it into
>>>>>> linux-firmware repo?
>>>>>
>>>>> It would also be great to hear if the PCIe firmware from Rockchip aimed
>>>>> at the OOT driver was definitively incompatible with the mainline driver
>>>>> and we have to find a solution for that from Broadcom, or it is expected
>>>>> to basically work.  I realize it might not be easy to get an answer
>>>>> internally but this chipset is likely to appear in more RK3588 SBCs soon
>>>>> since it's the one on the evb.
>>>>
>>>> Right now I don't have enough information to comment on this.
>>> Besides, could you upload the firmware that works with mainline driver
>>> to linux-firmware repo?
>>
>> I honestly don't know what entity provides the ampak wifi module. I guess it is coming from Synaptics, but I am not sure. I rather fix the mainline driver to make it work with the firmware (if possible) instead of releasing a specific firmware for mainline.
>>
>> Regards,
>> Arend
>>
>>
>>

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]

  parent reply	other threads:[~2022-11-17  9:24 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 [this message]
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
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=625f1d5d-e137-7ad7-96b9-92035e87df8b@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=andy@warmcat.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 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.