<NotHet>
So couple days ago I posted that Zephyr was hanging. I think I found out why. The register definitions in the Zephyr/litex_timer.c are all wrong. If I hack it to have updated addresses Zephr runs
<NotHet>
It seems like the spacing between CSRs AND the location of some of the registers changed, but I am not sure
<NotHet>
Might all of the litex drivers have this? I'm going to try and figure out what all could have been impacted, but I am _totally_ new to this ecosystem and its a bit of a stumble around. What all should I be looking for?
<NotHet>
_florent_ Did the liteeth's change effect Timer's CSRs too? Looking to know if I should keep my PR or cancel it. Not sure how it all fits together, so maybe silly question.
<NotHet>
Seems like the ethlite and the timer are unrelated problems? Like Timer CSRs are using the old style 8 bit CSR bus to access the 32 bit registers. But the LiteX SOC is using 32 bit wide CSR bus now. Which would mean keep the PR open?
NotHet has quit [Ping timeout: 252 seconds]
NotHet has joined #litex
<NotHet>
Actually I think I see a problem in my PR now. The write into TIMER_RELOAD and TIMER_LOAD are using the 8 bit CSR bus....