futarisIRCcloud has quit [Ping timeout: 244 seconds]
flammit has quit [Ping timeout: 240 seconds]
tcal has quit [Ping timeout: 244 seconds]
y2kbugger has quit [Ping timeout: 244 seconds]
esden has quit [Ping timeout: 260 seconds]
mithro has quit [Ping timeout: 260 seconds]
carlomaragno has quit [Ping timeout: 240 seconds]
bubble_buster has quit [Ping timeout: 244 seconds]
tannewt has joined #litex
key2 has quit [Ping timeout: 260 seconds]
sorear has quit [Ping timeout: 260 seconds]
daveshah has quit [Ping timeout: 260 seconds]
flammit has joined #litex
tcal has joined #litex
y2kbugger has joined #litex
daveshah has joined #litex
futarisIRCcloud has joined #litex
sorear has joined #litex
mithro has joined #litex
bubble_buster has joined #litex
key2 has joined #litex
esden has joined #litex
carlomaragno has joined #litex
civec has joined #litex
<leons>
zyp: yeah, that's what I was doing. Unfortunately it's not as detailed as I'd hoped and I don't feel like I understand enough yet to be actually contributing documentation. :)
<leons>
On another note: Can I rely on the fact that the LiteX CSR positions (at the base offset) of a core remain constant between generating different SoCs?
<zyp>
depends
<leons>
Of course, if there are changes made to a core, the CSRs of that core could potentially change (although hopefully only extended for backwards compatibility).
<tpb>
Title: Add optional location to CSRs within a Module · Issue #548 · enjoy-digital/litex · GitHub (at github.com)
<leons>
zyp: I see, thanks. That's exactly what I was looking for.
<leons>
I'm probably in the same situation with the OS I'm porting to. It's easy to instantiate drivers at different offsets, but hard to define a register mapping depending on dynamically generated CSV/JSON files
<zyp>
exactly
<zyp>
if I may ask, which OS are you porting?
<leons>
I'm in the progress of porting TockOS.
<leons>
Only in the early stages, although the basic kernel, LEDs and UART works.
<zyp>
ah, haven't heard of that before
<leons>
But with the "assurance" that it's "okay" to for now develop drivers with the assumption of relative CSR-locations not changing, I'm very certain that the port will be upstreamable. :)
<zyp>
assumption holds as long as the core doesn't change and doesn't have optional CSRs that gets turned on or off
<leons>
zyp: Yes, but I guess that's good enough for me - for now. Upon a LiteX version bump I'll probably need to check the diff of the respective cores and run a test suite.
civec has quit [Remote host closed the connection]
xobs has quit [Quit: killed]
leons has quit [Quit: killed]
sajattack[m] has quit [Quit: killed]
DerFetzer[m] has quit [Quit: killed]
david-sawatzke[m has quit [Quit: killed]
CarlFK[m] has quit [Quit: killed]
disasm[m]1 has quit [Quit: killed]
nrossi has quit [Quit: killed]
sajattack[m] has joined #litex
sajattack[m] has quit [Remote host closed the connection]