_florent_ changed the topic of #litex to: LiteX FPGA SoC builder and Cores / Github : https://github.com/enjoy-digital, https://github.com/litex-hub / Logs: https://libera.irclog.whitequark.org/litex
tpb has quit [Remote host closed the connection]
tpb has joined #litex
Degi_ has joined #litex
Degi has quit [Ping timeout: 268 seconds]
Degi_ is now known as Degi
<MoeIcenowy> _florent_: btw I am thinking how does LiteX keep the register layout of mainline-Linux-supported cores?
FabM has joined #litex
FabM has quit [Changing host]
FabM has joined #litex
Brinx has joined #litex
Brinx has quit [Ping timeout: 260 seconds]
Brinx has joined #litex
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
Brinx has quit [Remote host closed the connection]
Brinx has joined #litex
Brinx has quit [Remote host closed the connection]
Brinx has joined #litex
FabM has quit [Ping timeout: 268 seconds]
Guest7521 has joined #litex
indy has quit [Ping timeout: 248 seconds]
indy has joined #litex
Brinx has quit [Remote host closed the connection]
Guest7521 has quit [Quit: Client closed]
Brinx has joined #litex
minute has quit [Ping timeout: 246 seconds]
minute has joined #litex
<MoeIcenowy> _florent_: I suddenly realized openc906 is not in test/test_cpu.py, however maybe if I add it it will fall into "untested" like rocket?
FabM has joined #litex
FabM has joined #litex
FabM has quit [Quit: Leaving]
Brinx has quit [Remote host closed the connection]
Brinx has joined #litex
Brinx has quit [Ping timeout: 260 seconds]
nelgau_ has joined #litex
nelgau has quit [Ping timeout: 260 seconds]
nelgau has joined #litex
nelgau_ has quit [Ping timeout: 248 seconds]
<_florent_> MoeIcenowy: For the linux supported cores, we are avoiding register interface changes for now but indeed discuss about putting something in place. This could be an API version register that would always be read at the location.
<_florent_> MoeIcenowy: For OpenC906, if it's passing test_cpu in CI, we could test it. For rocket, IIRC the issue was related to Github CI, maybe limiting the number of jobs as shenki_ just did for Microwatt would work
<cr1901> Do device trees allow register layouts to change (in addition to dynamically defining "where's all the peripherals"?
nelgau_ has joined #litex
nelgau has quit [Ping timeout: 260 seconds]
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
<zyp> I think they only define the base address for the whole register block, not the order of individual registers
<tnt> Well, technically you "could" have DT bindings where every sub-reg address is configurable, but it'd be a major pain.