Thread (13 messages) 13 messages, 5 authors, 2022-07-07

Re: [PATCH net-next RFC 0/3] net: dsa: realtek: drop custom slave MII

From: Luiz Angelo Daros de Luca <hidden>
Date: 2022-06-29 16:50:07

Em qua., 29 de jun. de 2022 às 09:30, Arınç ÜNAL
[off-list ref] escreveu:
On 29.06.2022 06:54, Luiz Angelo Daros de Luca wrote:
quoted
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?
Hello Arinç,

You can backport those patches to mostly any device already using
rtl8365mb. The code it changes is mostly the same since the files
migrated to the realtek directory. However, you do need to backport
fe7324b932 (which is also easily applicable). I believe only the last
patch will conflict as some new functions were added to the
dsa_switch_ops that is being removed.

Regards,

Luiz
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help