[PATCH RFC] aquantia-firmware: package MediaTek's Aquantia AQR113C firmware

Christian Marangi ansuelsmth at gmail.com
Mon Feb 5 11:51:22 PST 2024

On Mon, Feb 05, 2024 at 08:21:43PM +0100, Rafał Miłecki wrote:
> On 5.02.2024 15:21, Daniel Golle wrote:
> > On Mon, Feb 05, 2024 at 02:23:08PM +0100, Rafał Miłecki wrote:
> > > From: Rafał Miłecki <rafal at milecki.pl>
> > > 
> > > Aquantia AQR113C is PHY that needs loading a firmware. Some devices may
> > > have it stored on flash and some need filesystem to provide it.
> > 
> > Are you aware of any MediaTek boards which do come with AQR113C but
> > don't bring their own dedicated firmware flash/EEPROM IC connected
> > directly to first PHY?
> > UniFi 6 LR v1/v2 (Aquantia AQR112C) and MT7988RFB (Aquantia AQR113C)
> > both come with a dedidated flash/EEPROM IC for the PHY firmware.
> > However, that firmware (esp. on the UniFi 6 LR) may of course be
> > outdated by now and we may want to load newer firmware from within
> > Linux anyway.
> I'm not sure if I can verify using Linux if there is EEPROM attached to
> any of two PHYs on my board. I don't believe Linux's PHY driver exposes
> possibly-attached EEPROM as any Linux device.
> I think however that with EEPROM present I wouldn't need Linux driver
> to load PHY firmware. In my board case I need to do that which makes me
> believe there is no EEPROM chip with firmware present.

Just to be clear, the EEPROM (actually it's a spi) is attached directly
to the PHY internally, you don't have a way to expose it in linux...

Also in that configuration, the FW is loaded automatically and with the
current driver, fw loading is skipped as a correct FW version is read
from the PHY. (FW loading from attached EEPROM is setup by hw strapping)

There is no need to verify if an EEPROM is attached, the check we do
is either a FW is present and loaded or a FW is not loaded and the PHY
FW version reg answer with 0.0.0 (or 0xff if held in reset state)


More information about the openwrt-devel mailing list