From: Alessio Ferri <alessio.ferri@mythread.it>
To: "Michael Büsch" <m@bues.ch>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org,
kvalo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] b43: complete N-PHY rev 8 + radio 2057 rev 8 support
Date: Tue, 19 May 2026 23:02:41 +0200 [thread overview]
Message-ID: <20260519230241.49489a8f@DELL-MOBILE03.ad.smart.it> (raw)
In-Reply-To: <20260519175812.7ce97ba1@barney>
On Tue, 19 May 2026 17:58:12 +0200
Michael Büsch <m@bues.ch> wrote:
> On Mon, 18 May 2026 03:49:33 +0200
> Alessio Ferri <alessio.ferri@mythread.it> wrote:
>
> > This series completes b43 support for the Broadcom N-PHY revision 8
> > paired with radio 2057 revision 8. b43 already supports the
> > surrounding PHY family - N-PHY rev 8 with radio 2057 rev 5 and rev
> > 7 are handled, and rev 16 with radio 2057 rev 9 is handled - but
> > the rev 8 + rev 8 combination falls through four dispatcher gaps:
>
> > Alessio Ferri (6):
> > b43: add d11 core revision 0x16 to id table
> > b43: route d11 corerev 22 to 24-bit indirect radio access
> > b43: support radio 2057 rev 8
> > b43: add IPA TX gain table for N-PHY r8 + radio 2057 r8
> > b43: add channel info table for N-PHY r8 + radio 2057 r8
> > b43: add RF power offset for N-PHY r8 + radio 2057 r8
>
>
> In general this looks Ok.
> From the style I assume that this is AI generated, right?
> If so, can you tell us a bit more about the inputs used for the AI?
> What information is this implementation based on?
>
The patchset is tested on my own DLink DSL 3580L router and generated by
claude from our shared notes, i then reviewed it for sanity and
verified it by navigating from the router with modified b43 driver with
my phone.
The shared notes were: logs and dumps taken from the proprietary binary
driver while running the stock firmware in the router, files from
brcmsmac that had some details for rev 22, GPL released broadcom code
in the GPL dump of the vendor, .rodata pieces from the binary driver and
finally logs and dumps from the live b43 running in the router flashed
with openwrt. Gathering all of this was a week long task, and writing
code was only a small part of it, like in the 5% range.
next prev parent reply other threads:[~2026-05-19 21:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 1:49 Alessio Ferri
2026-05-18 1:50 ` [PATCH 1/6] b43: add d11 core revision 0x16 to id table Alessio Ferri
2026-05-18 1:51 ` [PATCH 2/6] b43: route d11 corerev 22 to 24-bit indirect radio access Alessio Ferri
2026-05-18 1:51 ` [PATCH 3/6] b43: support radio 2057 rev 8 Alessio Ferri
2026-05-18 1:53 ` [PATCH 4/6] b43: add IPA TX gain table for N-PHY r8 + radio 2057 r8 Alessio Ferri
2026-05-18 1:54 ` [PATCH 5/6] b43: add channel info " Alessio Ferri
2026-05-18 1:54 ` [PATCH 6/6] b43: add RF power offset " Alessio Ferri
2026-05-19 15:58 ` [PATCH 0/6] b43: complete N-PHY rev 8 + radio 2057 rev 8 support Michael Büsch
2026-05-19 19:32 ` Joshua Peisach
2026-05-19 19:52 ` Michael Büsch
2026-05-19 23:13 ` Joshua Peisach
2026-05-19 21:02 ` Alessio Ferri [this message]
2026-05-20 11:06 ` Johannes Berg
2026-05-20 21:25 ` Alessio Ferri
2026-05-20 23:16 ` 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=20260519230241.49489a8f@DELL-MOBILE03.ad.smart.it \
--to=alessio.ferri@mythread.it \
--cc=b43-dev@lists.infradead.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
/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
all inboxes | Powered by JetHome®