04:31 <wens> got the gmac200 driver up and running, counters are incrementing but dhcp not getting address

06:38 <dlan> wens: on A527 board?

06:52 <wens> orangepi 4a (t527)

06:52 <wens> it does seem packets are getting in. tcpdump shows other valid incoming packets.

06:55 <wens> my router is probably acting up

07:10 <BroderTuck> wens: sounds similar to what warpme wrote here: https://oftc.catirclogs.org/linux-sunxi/2025-02-16#34009690 I wonder if he found a solution for that

07:14 <warpme> wens: last days i'm working on rk3576 cec ref clk issue; we know how to solve it so i spent less time on a523. lack of any movement with hdmi on a523 simply puts all a523 boards i have into dust collector use-case....

10:15 <eeschalier> An odd development: if I read the BMCR before the BMSR, then the ANEG_ABILITY reads as 0. If I read the BMSR twice in a row, it reads as 1.

14:16 <apritzel> Soupborsh: it looks like the MMC IP in the B288 is the same as in the R40, H5 and A64, and not as in the H3. So the compatible string should be "allwinner,sun50i-a64-emmc", and not "allwinner,sun7i-a20-mmc"

16:21 <wens> I seemed to have gotten it to send packets out, but now it won't :(

18:56 <Noxwell> Resending my original message because I wasn't registered, sorry.

18:56 <Noxwell> Hello! I've been working on a hobby project involving the A133(P) chip and its Cedar VE for about a week or so now, and I was wondering if anyone has been able to figure out how to get the VLD to cooperate with hardware bit reading operations. Every time I try to set up the VLD with userland writes/reads to the appropriate registers, the VLD just either jumps forward to the first start code and locks there, or jumps to bit 31 (