From: Aleksei Sviridkin <f@lex.la>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Lucien Jheng <lucienzx159@gmail.com>,
Albert-AL Lee <albert-al.lee@airoha.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Woudstra <ericwouds@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: phy: air_en8811h: use firmware loaded by the bootloader
Date: Mon, 19 Oct 2026 04:33:04 +0300 [thread overview]
Message-ID: <20261019013304.1612468-1-f@lex.la> (raw)
In-Reply-To: <2d6df47b-2cc3-4003-85db-f72b878427d9@lunn.ch>
On Sun, Oct 18, 2026 at 09:13:46PM +0200, Andrew Lunn wrote:
> Is it possible to figure out from the firmware blob what version it
> is?
Not reliably, as far as I can tell. The version the driver prints is
written into DM by the running MCU; the file holds zeros at that
address. In the DSP blob the halves 0x2506 and 0x2302 sit eight bytes
apart, which looks like the code that builds the word, but that is a
guess at an offset in vendor code.
Lucien, Albert, does Airoha guarantee any field in EthMD32.dm.bin or
EthMD32.DSP.bin as the firmware version, at a fixed place that will not
move in later releases? Without such a guarantee I would rather not
compare versions in the driver.
Aleksei
next prev parent reply other threads:[~2026-10-19 1:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 18:02 Aleksei Sviridkin
2026-10-18 19:13 ` Andrew Lunn
2026-10-19 1:33 ` Aleksei Sviridkin [this message]
2026-10-20 0:21 ` Andrew Lunn
2026-10-21 3:01 ` Jakub Kicinski
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=20261019013304.1612468-1-f@lex.la \
--to=f@lex.la \
--cc=albert-al.lee@airoha.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=ericwouds@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lucienzx159@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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®