public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "Joshua Peisach" <jpeisach@ubuntu.com>
To: "Michael Büsch" <m@bues.ch>, "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 14:58:42 -0400	[thread overview]
Message-ID: <DHTYJFGLKPQ0.RYJIDH2VLV3W@ubuntu.com> (raw)
In-Reply-To: <20260415194150.291dbe2d@barney>

On Wed Apr 15, 2026 at 1:41 PM EDT, Michael Büsch wrote:
>
> 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 :-)
>

Of course - but I don't currently feel like bending over backwards for
this one chip. Keep the working stuff working.

> 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.

I can gladly say that using Ghidra on the firmware, v4, v5, and v6 is
amazing. Export symbols help a lot, and it gives you a good idea of what
is going on; with the exception of the decompiler giving goto statements
that jump all over the place and make things confusing :/

But again, it's legacy.

As for newer gens - I thought they are already provided by Broadcom
devs in the kernel? I may be wrong, I can look later.

Thanks :)
-Josh

      reply	other threads:[~2026-04-15 18:58 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
2026-04-15 18:58                 ` Joshua Peisach [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=DHTYJFGLKPQ0.RYJIDH2VLV3W@ubuntu.com \
    --to=jpeisach@ubuntu.com \
    --cc=b43-dev-bounces@lists.infradead.org \
    --cc=b43-dev@lists.infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=jonas.gorski@gmail.com \
    --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