00:11 <zmatt> frostsnow: I see there's definitely been some DT changes between 5.10 and 6.1 related to ethernet

00:33 <zmatt> frostsnow: actually, I see only one major difference: the ethernet0/ethernet1 properties in /aliases point to different nodes

00:33 <zmatt> they used to reference &cpsw_emac0 and 1

00:33 <zmatt> in 6.1 they reference &cpsw_port1 and 2

01:00 <frostsnow> zmatt: Is there some command I need to run in order to alert userspace of a change? I'm not familiar with the working of device trees; I did update the device tree that gets booted with the kernel update.

01:02 <frostsnow> The only method I'm aware of is using 'ifconfig -a' to list inactive interfaces and then issuing commands to bring them up, but I don't see any interfaces besides loopback.

01:27 <zmatt> oh since you were using a custom kernel I kinda assumed you'd also have a custom dt.. if you're not then ignore what I said, then I have no idea why they're not showing up for you

01:29 <zmatt> you checked the kernel log for any lines containing "cpsw" or "eth" ?

01:51 <zmatt> check that you have CONFIG_TI_CPSW_SWITCHDEV=y and CONFIG_TI_CPSW_PHY_SEL=y

01:54 <zmatt> on 6.1 the ethernet device now lists cpsw-switch as its driver rather than cpsw

01:58 <zmatt> frostsnow: https://pastebin.com/Vu6ukrZn

02:03 <frostsnow> I checked the kernel logs for both 'cpsw' and 'eth' and got nothing. I had 'CONFIG_TI_CPSW_PHY_SEL=y' but tried switching it off to no avail. 'CONFIG_TI_CPSW_SWITCHDEV' is set to 'n'; I don't think it was selectable last I looked. I'll see about enabling both.

04:27 <frostsnow> zmatt: Yesss that did it! Thank you! I had to set 'NET_SWITCHDEV=y' before 'TI_CPSW_SWITCHDEV' would even appear. 'lshw' now shows the driver as 'cpsw-switch' instead of just 'cpsw'.

04:28 <frostsnow> I'm curious why the "switch" stuff, though. Shouldn't that be reserved for a link-layer switch or is this an overload of the word "switch"?

04:35 <zmatt> the AM335x has an integrated 3-port ethernet switch (two external (R)(G)MII ports, one internal port to the OS)

04:36 <zmatt> so even though the beaglebone only uses one of the two external ports, the driver still needs to configure the switch

04:40 <frostsnow> Makes sense, thanks!

04:46 <ds2> zmatt: do you happen to know if that switch will handle dot1q in HW?

05:06 <zmatt> ds2: it's a vlan switch yeah

05:06 <zmatt> also has some queueing features for AVB