Linux wireless drivers development
 help / color / mirror / Atom feed
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,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/7] b43: complete N-PHY rev 8 + radio 2057 rev 8 support
Date: Mon, 25 May 2026 14:04:38 +0200	[thread overview]
Message-ID: <20260525140438.265975e7@fedora> (raw)
In-Reply-To: <20260525100752.16cdb59e@barney>

Il giorno Mon, 25 May 2026 10:07:52 +0200
Michael Büsch <m@bues.ch> ha scritto:

> On Sun, 24 May 2026 23:56:17 +0200
> Alessio Ferri <alessio.ferri@mythread.it> wrote:
> 
> > Alessio Ferri (7):
> >       b43: add firmware mappings and remove comments wondering
> > about rev22 initvals 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
> > 
> >  drivers/net/wireless/broadcom/b43/main.c        |  22 ++-
> >  drivers/net/wireless/broadcom/b43/radio_2057.c  | 230
> > ++++++++++++++++++++++--
> > drivers/net/wireless/broadcom/b43/tables_nphy.c |  58 ++++++ 3
> > files changed, 290 insertions(+), 20 deletions(-)  
> 
> 
> Looks good and in general low risk because it doesn't change any code
> paths of supported hw revisions.
> I'd still prefer if somebody could test this change on another
> supported 2057 radio. I don't have such a device unfortunately.
> 
> Does the D-Link DSL-3580L work with full expected wireless throughput
> after this change or are there any remaining known issues?
> 
> Acked-by: Michael Büsch <m@bues.ch>
> 

Please clarify "full expected wireless throughput", HT is
not supported by b43, so it runs only with NOHT in g-like speed:

wireless.radio0=wifi-device
wireless.radio0.type='mac80211'
wireless.radio0.path='platform/ubus/10007000.wlan/10004000.axi/bcma0:1'
wireless.radio0.band='2g'
wireless.radio0.channel='36'
wireless.radio0.htmode='NOHT'
wireless.radio0.country='IT'
wireless.default_radio0=wifi-iface
wireless.default_radio0.device='radio0'
wireless.default_radio0.network='lan'
wireless.default_radio0.mode='ap'
wireless.default_radio0.ssid='DSL3580L'
wireless.default_radio0.encryption='psk2'
wireless.default_radio0.disabled='0'

Enabling HT for N chips is out of scope, also there nothing to
gain and a lot to risk, so i won't do it.

Once this lands, i would move to fix AC support for the only two chips
that require b43 to work (4352 & 4360). I own them both, in multiple
routers, so i can safely develop for them. It is also low risk as there
are no existings users.


  reply	other threads:[~2026-05-25 12:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-24 21:56 [PATCH v3 0/7] b43: complete N-PHY rev 8 + radio 2057 rev 8 support Alessio Ferri
2026-05-24 21:56 ` [PATCH v3 1/7] b43: add firmware mappings and remove comments wondering about rev22 initvals Alessio Ferri
2026-05-24 21:56 ` [PATCH v3 2/7] b43: add d11 core revision 0x16 to id table Alessio Ferri
2026-05-24 21:56 ` [PATCH v3 3/7] b43: route d11 corerev 22 to 24-bit indirect radio access Alessio Ferri
2026-05-24 21:56 ` [PATCH v3 4/7] b43: support radio 2057 rev 8 Alessio Ferri
2026-05-24 21:56 ` [PATCH v3 5/7] b43: add IPA TX gain table for N-PHY r8 + radio 2057 r8 Alessio Ferri
2026-05-24 21:56 ` [PATCH v3 6/7] b43: add channel info " Alessio Ferri
2026-05-24 21:56 ` [PATCH v3 7/7] b43: add RF power offset " Alessio Ferri
2026-05-25  8:07 ` [PATCH v3 0/7] b43: complete N-PHY rev 8 + radio 2057 rev 8 support Michael Büsch
2026-05-25 12:04   ` Alessio Ferri [this message]
2026-05-25 18:14     ` Michael Büsch
2026-05-25 19:28       ` 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=20260525140438.265975e7@fedora \
    --to=alessio.ferri@mythread.it \
    --cc=b43-dev@lists.infradead.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