public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Büsch" <m@bues.ch>
To: "Joshua Peisach" <jpeisach@ubuntu.com>
Cc: "Jonas Gorski" <jonas.gorski@gmail.com>,
	"Johannes Berg" <johannes@sipsolutions.net>,
	<linux-wireless@vger.kernel.org>, <b43-dev@lists.infradead.org>,
	"b43-dev" <b43-dev-bounces@lists.infradead.org>
Subject: Re: Firmware for reverse engineering b43?
Date: Wed, 15 Apr 2026 19:41:50 +0200	[thread overview]
Message-ID: <20260415194150.291dbe2d@barney> (raw)
In-Reply-To: <DHTW44HOVZLS.GFYBZTKJTMP4@ubuntu.com>

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

On Wed, 15 Apr 2026 13:04:40 -0400
"Joshua Peisach" <jpeisach@ubuntu.com> wrote:
> Well, if the regression risk is that high, then I guess I'll let it be.

> Sure. I might just make sure everything is using register definitions
> instead of hardcoded values, but then leave it there.

I mean, I don't want to discourage you from doing anything,
but I just wanted to point out that this is a lot more work than just implement
a TODO here and there.

For most of the code we don't really know what it does exactly.
That may change a bit, if you pull over some code from the newer drivers.
But I don't think the situation will improve fundamentally.

> So I guess this driver just sits here.. not quite pointless to be
> removed from the main tree, but not quite worth the effort to bring it
> up to speed.

Well, it probably still works well on the (few) devices it worked well on,
because it basically hasn't changed.
There are many devices which were never supported at all or were never supported
properly. It's not that just your device is missing to complete
the perfect picture :-)

There might be better uses of your time than working on this legacy stuff.
For example working on the microcode reverse engineering and tools and
get them updated for the current generation of devices is probably
much more useful. And I think much more fun, too.
Or something else altogether.

-- 
Michael Büsch
https://bues.ch/

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-04-15 17:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 12:44 Firmware for reverse engineering b43? Joshua Peisach
2026-04-14  9:14 ` Johannes Berg
2026-04-14 11:30   ` Joshua Peisach
2026-04-14 12:24     ` Jonas Gorski
2026-04-15 11:44       ` Joshua Peisach
2026-04-15 11:54         ` Jonas Gorski
2026-04-15 15:57           ` Michael Büsch
2026-04-15 17:04             ` Joshua Peisach
2026-04-15 17:41               ` Michael Büsch [this message]
2026-04-15 18:58                 ` Joshua Peisach

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=20260415194150.291dbe2d@barney \
    --to=m@bues.ch \
    --cc=b43-dev-bounces@lists.infradead.org \
    --cc=b43-dev@lists.infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=jonas.gorski@gmail.com \
    --cc=jpeisach@ubuntu.com \
    --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