From: Andrew Lunn <andrew@lunn.ch>
To: Aleksei Sviridkin <f@lex.la>
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: Tue, 20 Oct 2026 02:21:39 +0200 [thread overview]
Message-ID: <3078aefc-aad7-4cfb-b7bb-3a1bec5a832b@lunn.ch> (raw)
In-Reply-To: <20261019013304.1612468-1-f@lex.la>
On Mon, Oct 19, 2026 at 04:33:04AM +0300, Aleksei Sviridkin wrote:
> 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.
linux-firmware/airoha$ git log --oneline EthMD32.dm.bin
149f9b8e linux-firmware: update firmware for en8811h 2.5G ethernet phy
d88562a0 linux-firmware: update firmware for en8811h 2.5G ethernet phy
d3480463 linux-firmware: update firmware for en8811h 2.5G ethernet phy
75ac03a8 linux-firmware: update firmware for en8811h 2.5G ethernet phy
73b4429f linux-firmware: update firmware for en8811h 2.5G ethernet phy
ddc99b3d linux-firmware: add firmware for en8811h 2.5G ethernet phy
linux-firmware/airoha$ git log --oneline EthMD32.DSP.bin
149f9b8e linux-firmware: update firmware for en8811h 2.5G ethernet phy
d88562a0 linux-firmware: update firmware for en8811h 2.5G ethernet phy
d3480463 linux-firmware: update firmware for en8811h 2.5G ethernet phy
75ac03a8 linux-firmware: update firmware for en8811h 2.5G ethernet phy
73b4429f linux-firmware: update firmware for en8811h 2.5G ethernet phy
ddc99b3d linux-firmware: add firmware for en8811h 2.5G ethernet phy
Looks like there is 6 of each. Maybe you can look at all these
versions and see if there is a pattern?
But it is just nice to have. Its not required for this patch to be
merged.
Andrew
next prev parent reply other threads:[~2026-10-20 0:21 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
2026-10-20 0:21 ` Andrew Lunn [this message]
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=3078aefc-aad7-4cfb-b7bb-3a1bec5a832b@lunn.ch \
--to=andrew@lunn.ch \
--cc=albert-al.lee@airoha.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=ericwouds@gmail.com \
--cc=f@lex.la \
--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®