Closed nevapadonak closed 3 years ago
The last port in the switch is the host port that connects to the MAC. The DSA driver uses tail tagging which means only the last port will work. The device tree defines the first port as the CPU port.
The last port in the switch is the host port that connects to the MAC. The DSA driver uses tail tagging which means only the last port will work. The device tree defines the first port as the CPU port.
Thank you! Is it possible to fix driver to support first port as CPU and not last?
The problem is solved! CPU port should only be wired to KSZ8895 switch as 5 (last) port. It is hardware requierment, not the driver restriction.
Hello!
I use EVB-KSZ9477/KSZ/kernels/linux-4.9.143/drivers/net/dsa/microchip/ksz8863_spi.c driver.
The problem is the packets don't go through Ethernet interfaces. I have development board with KSZ8895 switch and PC. The PC is connected to lan2@eth0 virtual interface of KSZ8895 switch.
I did ping from CPU port eth0 on development board to PC. The PC sees incoming ARP packet, sends ARP response back, but then the board sends a new ARP request, so it didn't receive any packets.
This is part of my DTS:
The ip link output:
We see the driver created virtual lan1-lan3 interfaces. The KSZ driver loading debug:
Can you help me or give me some advice?
The pings go successfully before ksz8895 driver is loaded. So the driver breaks the network. I think uninitialized status of virtual lan1-lan3 ports may means somewhat? How to fix them to be initialized?
Thanks. Artem Korotchenko.