ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion
vagrantc has quit [Quit: leaving]
kevery has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 252 seconds]
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
kevery has quit [Read error: Connection reset by peer]
kevery1 is now known as kevery
archetyp` has joined #linux-rockchip
archetyp has quit [Ping timeout: 244 seconds]
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 250 seconds]
unkraut has quit [Quit: leaving]
unkraut has joined #linux-rockchip
archetyp` has quit [Quit: Leaving]
stikonas has joined #linux-rockchip
wwilly has joined #linux-rockchip
chewitt has quit [Quit: Zzz..]
stikonas has quit [Remote host closed the connection]
indy has quit [Remote host closed the connection]
indy has joined #linux-rockchip
alpernebbi has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
mx08 has quit [Quit: WeeChat 2.8]
mx08 has joined #linux-rockchip
<pgwipeout[m]>
So it's not the delays, rgmii-id works on the original working driver but breaks on 5.14. SOC con5 is being set incorrectly. working =0x208 (IIRC) not working =0x8. And this isn't a case of a default value and failing to write, if changed the driver will reset it when the interface is toggled.