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: Thu, 1 Oct 2026 19:37:14 +0200 [thread overview]
Message-ID: <20261001193714.00005f36@mythread.it> (raw)
In-Reply-To: <BGzX01_Xw0eP0rtUaqPn6IyCeg06zqkSQ8qKQoE38fN4Pzu_QmUjvB-pw5RuEdVn3hXqB3UAMap8WSTwRa8i6Zfg8XUmkhUEBavoBwppNmM=@proton.me>
Il giorno Thu, 01 Oct 2026 12:06:05 +0000
"andreas.wendleder" <andreas.wendleder@proton.me> ha scritto:
> Hi Alessio,
>
> Thanks for the 2.4 GHz trace work. Short status, then the questions.
>
> Status: b43 now runs as the daily connection on my MacBookAir6,1
> (BCM4360, core rev 42, radio 2069 rev 4). The 2.4 GHz station works
> with legacy rates and a TX status fix. Upload is about 18 Mbit/s and
> download about 10.
>
> The open problem: only about 21% of fresh inits can transmit. The
> state is fixed at init. In a bad init the PHY holds CRS|TXF and every
> TX ends in a PHY transmission error, so auth frames are never ACKed.
> A reload wrapper retries until an init connects, which takes 2-5
> tries. I've ruled out temperature, DMA, ASPM, PLL lock, clocks, TX
> core mask, TX power control, the CRS threshold and the MAC setup
> order.
>
> I've updated the clean-room spec (§10 covers this) and can send it if
> it's useful.
>
> Questions:
>
> Do you have a bus-level trace (wl-mmio-trap) of a 2.4 GHz cold init
> and first transmit on a BCM4360 (agcombo or TG789vac), including the
> calibration phase? I'd diff it against mine at register level. Can
> your harness score our driver's register-write sequence against your
> captures? That would show where we diverge without hardware tests.
> Does stock wl ever give you a "bad init" on any of your boards (the
> PHY cannot transmit until the next reset)? That would tell us whether
> the cause is in our init or in the chip.
>
> If your 2.4 GHz support lands, I'll test it on this laptop right away.
>
Oh, i forgot, you have femctrl = 2, all of my boards have femctrl = 6,
so probably the calibration is wrong for your card, but now i try to
fix it. Thank again!
> Thanks,
> Andreas
prev parent reply other threads:[~2026-10-01 17:37 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
2026-10-01 1:31 ` AW: " 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 [this message]
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=20261001193714.00005f36@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