[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6f4e00d6-6b7d-e4c7-8108-67c009f7a6d8@arinc9.com>
Date: Wed, 29 Jun 2022 15:30:03 +0300
From: Arınç ÜNAL <arinc.unal@...nc9.com>
To: Luiz Angelo Daros de Luca <luizluca@...il.com>,
netdev@...r.kernel.org
Cc: linus.walleij@...aro.org, alsi@...g-olufsen.dk, andrew@...n.ch,
vivien.didelot@...il.com, f.fainelli@...il.com, olteanv@...il.com,
davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
robh+dt@...nel.org, krzk+dt@...nel.org
Subject: Re: [PATCH net-next RFC 0/3] net: dsa: realtek: drop custom slave MII
On 29.06.2022 06:54, Luiz Angelo Daros de Luca wrote:
> The last patch cleans all the deprecated code while keeping the kernel
> messages. However, if there is no "mdio" node but there is a node with
> the old compatible stings "realtek,smi-mdio", it will show an error. It
> should still work but it will use polling instead of interruptions.
>
> My idea, if accepted, is to submit patches 1 and 2 now. After a
> reasonable period, submit patch 3.
>
> I don't have an SMI-connected device and I'm asking for testers. It
> would be nice to test the first 2 patches with:
I'd love to test this on an Asus RT-AC88U which has got the
smi-connected RTL8365MB switch but modifying the OpenWrt SDK to build
for latest kernels is a really painful process. I know it's not related
to this patch series but, does anyone know a more efficient way of
building the kernel with rootfs with sufficent userspace tools? Like, am
I supposed to use Buildroot, Yocto?
Arınç
Powered by blists - more mailing lists