Linux wireless drivers development
 help / color / mirror / Atom feed
From: Alessio Ferri <alessio.ferri@mythread.it>
To: "andreas.wendleder" <andreas.wendleder@proton.me>
Cc: "b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: BCM4360 AC-PHY support for b43 — reverse-engineered, seeking guidance on a clean path upstream
Date: Tue, 29 Sep 2026 22:13:21 +0200	[thread overview]
Message-ID: <20260929221321.000023a7@mythread.it> (raw)
In-Reply-To: <OG0AU4A6pMu865qvxpXQjF7NvEP6p2bwR_IZRaLxONsn_3Gdxm00PiOOaGuWbYy-AmxhLGRyz29ZPtUKzDwsKJk_UjTLAU1bctgCzdWlNlE=@proton.me>

Il giorno Tue, 29 Sep 2026 14:45:41 +0000
"andreas.wendleder" <andreas.wendleder@proton.me> ha scritto:

> > If you are using an older ucode, probably my driver don't work on
> > your device because it interact with newer ucode, can you look for
> > mac behaviour diff from yours? Maybe we can merge the handling with
> > some ifs, repo here: https://github.com/aleferri/b43-ac-wip  
> 
>  I'm on ucode42.fw (D11 core rev 42), firmware 832.127 (2014-09-19);
> my driver checks SHM UCODEREV against ≤0x128. I don't have a captured
> rev number to compare against yours off-hand — what ucode rev/date
> does your driver target? I've mapped a decent chunk of the real MAC
> event loop (dispatcher + wait points) and the watchdog tick (SHM
> 0x158, ~1.024s) by decompiling wl, so a diff is doable if I know what
> to diff against. Game for merging with #ifdefs if the divergence is
> small.


i have firmware 938.1502, October 2017, as the "target", but i ran a
similarity scan between 938.1502 ucode and 938.10005 and there are no
changes except for the version. The 938.1201 likewise is also very
similar, as far as the similarity tool is concerned. While they are all
very different from the 784.2 from my D Link dsl 3580L router.
So at this point there are 3 version of ucode for AC:
- 784.2 is the original one, dated 2012
- 832.127 is the broadcom sta for linux one
- 938.1xxx is the most recent one

You seems to have decoded fairly well the rx/tx path, i have instead
understood quite a lot of the phy/radio level, you could try to
incorporate my work for the phy and test if you it can improve your own
results. I will take your decoding of the mac handling to test 784.2
and 938.1xxx ucodes. 

If you send me your raw bits of srom and opt with a full trace from wl
unloaded to wl loaded, bss up and running, i can tell you if there are
still blindspots in my phy code or if you should be good to go.

  reply	other threads:[~2026-09-29 20:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <rOzY3WnW4q5L1osv7iagU81dLGldzZEsu3EqHxmH4d7Z4vxubBYvRNT0vsrbr8n-CUSEYyXxGFE3h9PHLHgePjm3_rMK_B_0m5loTpyxX-M=@proton.me>
2026-09-28 13:42 ` AW: BCM4360 AC-PHY support for b43 — reverse-engineered, seeking guidance on a clean path upstream andreas.wendleder
2026-09-28 18:03   ` Michael Büsch
2026-09-28 21:49     ` AW: " andreas.wendleder
2026-09-29  6:14       ` Michael Büsch
2026-09-29  6:32         ` AW: " andreas.wendleder
2026-09-29  7:34         ` Alessio Ferri
2026-09-29  7:49           ` AW: " andreas.wendleder
2026-09-29  8:05             ` Alessio Ferri
2026-09-29  8:27               ` AW: " andreas.wendleder
2026-09-29  8:58                 ` Alessio Ferri
     [not found]                   ` <oYmDL00YinKfSdWHxkjmqPRGHWmeA_0SCR6tpafsgCvGyqYAEKuCt0kg7w_C47be5hm7IwFsxRnulMhvPFJEXQNDaDPgZNzMIQ0vfRKnOLw=@proton.me>
     [not found]                     ` <20260929113109.2c561844@DELL-MOBILE03.ad.smart.it>
2026-09-29 14:45                       ` AW: " andreas.wendleder
2026-09-29 20:13                         ` Alessio Ferri [this message]
2026-10-01  1:31                           ` andreas.wendleder
2026-10-01  6:02                             ` Alessio Ferri
2026-10-01 12:06                               ` AW: " andreas.wendleder
2026-10-01 17:12                                 ` Alessio Ferri
2026-10-01 17:37                                 ` Alessio Ferri

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=20260929221321.000023a7@mythread.it \
    --to=alessio.ferri@mythread.it \
    --cc=andreas.wendleder@proton.me \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    /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