[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c78e2725-0be7-caa8-40db-2f355cc2cdec@gmail.com>
Date: Tue, 31 Jan 2023 12:55:14 +0100
From: Matthias Brugger <matthias.bgg@...il.com>
To: Arınç ÜNAL <arinc.unal@...nc9.com>,
frank-w@...lic-files.de, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
erkin.bozoglu@...ont.com, Sean Wang <sean.wang@...iatek.com>,
DENG Qingfang <dqfext@...il.com>
Subject: Re: [PATCH 4/5] arm: dts: mt7623: mux phy0 on Bananapi BPI-R2
On 25/01/2023 17:54, Arınç ÜNAL wrote:
> On 25.01.2023 19:41, Frank Wunderlich wrote:
>> Am 20. Januar 2023 21:53:17 MEZ schrieb "Arınç ÜNAL" <arinc.unal@...nc9.com>:
>>
>>> switch@1f {
>>> compatible = "mediatek,mt7530";
>>> reg = <0x1f>;
>>> @@ -199,11 +208,6 @@ ports {
>>> #address-cells = <1>;
>>> #size-cells = <0>;
>>>
>>> - port@0 {
>>> - reg = <0>;
>>> - label = "wan";
>>> - };
>>> -
>>
>> This will break existing userspace setups using wan as interface name.
>
> Yup. The OS being used will have to either rename the interface or adapt to the
> new name, eth1.
>
In that case please explain in the commit message why this is needed. We are
trying really hard to not break userspace by a device-tree update.
Regards,
Matthias
Powered by blists - more mailing lists