07:07 <xobs> Hey florent, what happens when you add a Memory to the CSR bus?

07:08 <xobs> I'm looking mostly at `ident` right now, which is just a `Memory`. If I say `ident="string"`, then is e.g. `0xe0002800=='s'`, `0xe0002804=='t'`, `0xe0002808=='r'`, ...? Or is it 8-byte aligned? Or do I keep reading from `0xe0002800`?

08:54 <_florent_> Hi xobs, that's the first assumption, if that can help, here is how it's read from software: https://github.com/enjoy-digital/litex/blob/master/litex/soc/software/libbase/id.c

08:55 <tpb> Title: litex/id.c at master · enjoy-digital/litex · GitHub (at github.com)

08:55 <xobs> Thanks! I'll note that.

08:56 <xobs> Is there anything else that can live on the CSR bus? Or is it just Memory and _CSRBase?

09:12 <_florent_> IIRC that's all yes

12:24 <keesj> Hi

12:25 <keesj> it's been a while.. I hope to restart doing my research soon

13:56 <_florent_> Hi keesj, nice, i hope you'll be able to get things working

14:25 <keesj> there is also a orconf soon right?

14:29 <daveshah> Yes, starting on Friday

14:58 <john_k[m]> hey _florent_ I'm back from vacation - have you had a chance to look at the PanoLogic G2 yet?

14:59 <_florent_> john_k[m]: sorry i've been busy with others things...

14:59 <john_k[m]> no problem, was just curious

14:59 <john_k[m]> will probably start poking at it again later today

15:01 <_florent_> ok, i'll try to install the ISE version needed to be able to help

16:05 <_florent_> xobs: regarding a we signal for CSRStatus (you asked a few days ago), i just added it. It's generally not recommended to do actions on register read, but that can still be very useful in some cases.

16:06 <_florent_> xobs: a usecase: i was trying to improve LiteScope upload speed, with this easy change i get > 10x speed-up: https://github.com/enjoy-digital/litescope/commit/7a9fa9d3b18362bf707dff25a78661395ef9ee7a

16:06 <tpb> Title: core: use new CSRStatus.we signal to speed-up Storage upload (>10x sp… · enjoy-digital/litescope@7a9fa9d · GitHub (at github.com)

16:56 <davidc__> _florent_: out of curiosity, why is it generally not recommended to do actions on register read? Clear-on-read + FIFO-pop-on-read seem fantastic

17:06 <_florent_> davidc__: it's only useful for specific usecases as you mention, heavily used it's just that it can becomes difficult to understand how the system is behaving and complicate debugging (you can to check the status of your system but things are then evolving, etc...)

17:09 <davidc__> _florent_: yeah, good point on debugging. I usually like two copies of the register: One doesn't pop/clear (just 'status'), the other does

17:10 <davidc__> but otherwise bit-identical