Linux wireless drivers development
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Andy Green <andy@warmcat.com>, Shengyu Qu <wiagn233@outlook.com>
Cc: franky.lin@broadcom.com, linux-wireless@vger.kernel.org
Subject: Re: AP6275 / bcm43752 pcie on mainline brcmf
Date: Thu, 24 Nov 2022 13:22:09 +0100	[thread overview]
Message-ID: <9fe8caec-453a-28c1-04d3-5966200b8db1@broadcom.com> (raw)
In-Reply-To: <6c3f592e-3e20-edef-ce7a-cde8988eef2d@warmcat.com>

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

On 11/24/2022 1:14 PM, Andy Green wrote:
> 
> 
> On 11/24/22 09:42, Arend van Spriel wrote:
>> On 11/18/2022 6:41 AM, Andy Green wrote:
>>>
>>>
>>> On 11/17/22 21:52, Arend Van Spriel wrote:
>>>
>>>> I see. So could you load bcmdhd and provide log. Preferably with 
>>>> higher debug level. It also has a module parameter for it. I think 
>>>> it is called dhd_msg_level and please set it to 0x817.
>>>
>>> It's here:
>>>
>>> https://warmcat.com/ap6275p-dhd-log1.txt
>>
>> Hi Andy,
>>
>> Thanks for the log. Together with the dhd driver sources I could make 
>> some sense of it. Perhaps you can try the following hack and see if we 
>> make it over the first hurdle.
> 
> OH!  I found that the line below should be count, not sizeof(count).

Good job! I was testing you obviously. You passed. Nah, I just feel stupid.

>> +    addr -= sizeof(count);
>> +    memcpy_toio(devinfo->tcm + addr, seed, count);
>> +}
> 
> With that, you were right on the money, the firmware comes up
> 
> [    3.796062] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43752/2 
> wl0: Jul 12 2022 18:54:54 version 18.35.387.23.146 (g412cc5ec) FWID 
> 01-93c53be6
> 
> along with
> 
> wlP2p33s0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
>          ether d4:9c:dd:f5:bf:7e  txqueuelen 1000  (Ethernet)
>          RX packets 0  bytes 0 (0.0 B)
>          RX errors 0  dropped 0  overruns 0  frame 0
>          TX packets 0  bytes 0 (0.0 B)
>          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> I will try get it to scan...
> 
> ... any way, good job!

Thanks. Will clean it up and formally submit it. I also had a quick look 
at the SDIO variant, but not seeing anything obvious there in terms of 
firmware loading.

Regards,
Arend

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

  reply	other threads:[~2022-11-24 12:22 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
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 [this message]
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=9fe8caec-453a-28c1-04d3-5966200b8db1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox