[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cd1fd7b4-64a1-4b73-86aa-d3621ed814b4@lunn.ch>
Date: Mon, 19 Jan 2026 15:04:27 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Lorenzo Bianconi <lorenzo@...nel.org>
Cc: Christian Marangi <ansuelsmth@...il.com>,
Krzysztof Kozlowski <krzk@...nel.org>,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH net-next v2 1/2] dt-bindings: net: airoha: npu: Add
EN7581-7996 support
> > So is the firmware name a property of the board?
>
> We need to run different binaries on the NPU based on the MT76 WiFi chip
> available on the board since the MT76 DMA rings layout changes between MT76 SoC
> revisions (e.g. Egle MT7996 vs Kite MT7992). In this sense, I agree, the
> firmware name is a board property.
O.K, lets go with v1 then. List the firmware filename in the board
.dts file.
Andrew
Powered by blists - more mailing lists