Christian Herber

ok that is reasonable. had a look at it, but it doesnt seem to clear the cloned git repository under core-v-cores, so it doesn't go back to distribution state

I cannot at this point, as the contribution to this repo is still a pending topic. Such a cleaning would also me much easier, if the repos where cloned into...

> Not in my view. This would place restrictions on how members use CORE-V-VERIF and due to the wide variety of users in the OpenHW community it would be difficult...

ok, that sounds great. If you are asking my opinion, anything the `make` clones should really be in a subdirectory of the core in some build directory and should be...

One question I have around the indirect CSRs is related to the user registers. The indirect CSR access is only defined for M and S mode. CLIC is sort of...

This is a proposal for a potential CSR map for CLIC using S*csrind. - I would expect the CSRs which are currently directly accesible to stay unchanged. - xcliccfg is...

Giving some background to the proposal above: Addressing: The address layout is optimized to accesses that are multiples of 6, as there are 6 xiregs. E.g. a xiselect value of...

@kasanovic I believe a CSR-only version of CLIC should work. The memory-mapped register in IMSIC really comes from the need for MSIs. In CLIC, I would expect that some of...

Implementations done before ratification cannot prohibit further spec development. Otherwise we also would not have the vector 1.0 spec as it is today. SW like Zephyr will be able to...

> This is the preemptible example so it does need to enable mstatus.mie to allow higher level interrupts to preempt. I think the beqz is then really just error checking...