Conversation

Notices

1. Embed this notice
   ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Monday, 02-Jun-2025 13:04:37 JST ✧✦Catherine✦✧

   networking folks, i've found the terminology around IEEE 802.3 Clause 22 / Clause 45 very confusing; can you take a look over https://github.com/GlasgowEmbedded/glasgow/pull/882/files#diff-bf365b35ccfcabdcaee1fcb6c0351f5aa2c3514fbe4f1711bca787eab1f64e69 and tell me if this API (of ControlMDIOInterface) would make sense to you? Is the overall naming scheme reasonable, or does it look weird or wrong?

   • Embed this notice
     Andrew Zonenberg (azonenberg@ioc.exchange)'s status on Tuesday, 03-Jun-2025 01:45:36 JST Andrew Zonenberg

     in reply to

     @whitequark More generally, do you have any plans to cleanly support nonstandard register banking schemes as used in e.g. the VSC8512?

     (tl;dr MDIO register 31 is used as a bank selector to determine which page of extended registers 16-30 map to, 0-15 are always the IEEE standard ones. it's derpy and I dont know why they didn't juse MMD extended registers)

   • Embed this notice
     ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Tuesday, 03-Jun-2025 01:45:36 JST ✧✦Catherine✦✧

     in reply to

     • Andrew Zonenberg

     @azonenberg hm, yeah why not

   • Embed this notice
     Andrew Zonenberg (azonenberg@ioc.exchange)'s status on Tuesday, 03-Jun-2025 01:45:37 JST Andrew Zonenberg

     in reply to

     @whitequark I use the term MDIO for the bus in all of my usage

   • Embed this notice
     ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Tuesday, 03-Jun-2025 01:46:41 JST ✧✦Catherine✦✧

     in reply to

     • equi

     @equinox thanks, I think I'll switch to that

   • Embed this notice
     equi (equinox@chaos.social)'s status on Tuesday, 03-Jun-2025 01:46:42 JST equi

     in reply to

     @whitequark I have seen "MIIM" maybe once or twice in my lifetime. Most I've seen, people just call it "c45_read" / "c22_read" and the like.

     E.g. this bonanza: https://patchwork.kernel.org/project/netdevbpf/patch/20210331141755.126178-3-danilokrummrich@dk-develop.de/

     Everything is MDIO.

   • Embed this notice
     ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Tuesday, 03-Jun-2025 02:32:01 JST ✧✦Catherine✦✧

     in reply to

     thanks to everyone here and on fedi, i'm going to rename the methods to {c22,c45}_{read,write}

   • Embed this notice
     ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Tuesday, 03-Jun-2025 02:56:30 JST ✧✦Catherine✦✧

     in reply to

     and done!! reviews appreciated

   • Embed this notice
     ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Tuesday, 03-Jun-2025 09:12:43 JST ✧✦Catherine✦✧

     in reply to

     • Andrew Zonenberg

     @azonenberg hey what the fuck

     rtl8211 has that mechanism AND it has standard MMD

   • Embed this notice
     Andrew Zonenberg (azonenberg@ioc.exchange)'s status on Tuesday, 03-Jun-2025 09:12:44 JST Andrew Zonenberg

     in reply to

     @whitequark i'm really curious what the thought process was... MMD extended registers existed alrerady, there was no reason to roll their own indirect accessing scheme.

     except maybe performance, if you bank then accessing any register in the range is faster than making repeated address + data accesses? but what kind of system gets bottlenecked on mdio bandwidth

   • Embed this notice
     ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Tuesday, 03-Jun-2025 10:25:32 JST ✧✦Catherine✦✧

     in reply to

     • Andrew Zonenberg

     @azonenberg RTL8211E has this insane double banking scheme

   • Embed this notice
     Andrew Zonenberg (azonenberg@ioc.exchange)'s status on Tuesday, 03-Jun-2025 10:25:33 JST Andrew Zonenberg

     in reply to

     @whitequark sorry now you can't unsee lol