Indan Zupancic
Indan Zupancic
The paragraph above the one you added tried explaining the word ordering already: ``` The bits in the block are laid out in memory in the order they are mentioned...
> @indaz, sorry for that. No need to apologise! > > Let me try to explain by an example: > > ``` > base 64 > block sample { >...
> The diagram specifies the bit numbers in the order they end up in memory -- that is the part that is important. Except the order in memory is reversed:...
Can this be merged or does it need to wait for verification?
I think you are referring to `replyNext` either pointing to a reply object or a SC, which is very weird indeed. We can get rid of the isHead bit too...
I don't understand why you don't just add a cmdline option instead, then you don't need a special Microkit loader for x86. And why not add a dynamic loading bit...
ACK on d4ffd52a210d0fd3f1b7994cb09c0673de7be2ca though, you could create a separate PR for that if you want.
> The drawback with this approach is that since the size of the memory region changes depending on what's in the image, nearly every rebuild means having to update these...
> Hmm I understand the appeal, but this would be quite a departure from the static system image concept of Microkit, wouldn't it? The static image concept applies to what...
Relevant discussion about memory zeroing at #1289.