10:19 <xdarklight> narmstrong: ha, thank you for that pointer, that works :)

10:19 <xdarklight> however, that leads to an issue with the PHY reset pin on the X96 Max: GPIOZ_15 is an Open Drain pin (like you've explained to me in the past cannot drive the output HIGH)

10:20 <xdarklight> unfortunately stmmac doesn't handle this yet, so if I change the reset to GPIOZ_15 then the PHY is not detected anymore

10:20 <xdarklight> I'll try to fix that later

14:57 <ukleinek> xdarklight: the shift is ugly, hmm

18:04 <xdarklight> ukleinek: if you agree then I'll keep my non-fancy 0x3 variant. I'll have to re-send the series tomorrow again because I'm informed of a typo in one of the patches (privately) - so please let me know if you want me to change something or if I should keep what I have :)

18:07 <xdarklight> narmstrong: I sent a series which will allow us to *properly* specify the PHY reset GPIOs, it's in your inbox now and (hopefully) contains all the relevant description :)

18:18 <Xogium> did anyone else notice a very impressive latency on odroid c2 when pinging ? Kernel 4.19

18:18 <Xogium> I ping my router, via ethernet, not wifi

18:20 <Xogium> odroid c2: rtt min/avg/max/mdev = 4.713/9.486/18.906/3.392 ms. Laptop, also connected via ethernet: rtt min/avg/max/mdev = 0.289/0.375/0.495/0.046 ms

18:24 <Xogium> not a big deal as of now, but just curious about this

18:24 <Xogium> maybe I just never noticed what a high latency the hardware has

20:20 <xdarklight> Xogium: I don't have any GXBB hardware but these are the results from pinging (from my computer) my Meson8b EC100 (which only has a 10/100 Mbit/s PHY, no Gbit): rtt min/avg/max/mdev = 0.955/1.238/1.984/0.432 ms

20:31 <Xogium> xdarklight: aye. I wonder what is up

20:31 <Xogium> I had a pick at 28 ms