Brad Campbell

The basic idea is you are creating a version of the Tock kernel that runs the bootloader code. You would want to combine the main esp-c3 [board](https://github.com/tock/tock/tree/master/boards/esp32-c3-devkitM-1) with a version...

I think we should drop the XOR and use a 4 byte length. Applications really need to initialize this correctly. Maybe not on the first allow, but applications need to...

`WriteableProcessSliceAppendable`? `WriteableProcessSliceBuffered`?

Ok bear with me for a second: What if we make this functionality the _default_, and make applications/drivers opt-out (I'm not exactly sure how they opt out, but let's ignore...

After reading through #4024, I think the main question is: do we make any changes to the kernel to support this? I lean towards no, with potentially one exception. The...

Also after reading through https://github.com/tock/tock/pull/4024, it might be easiest to specify only a minimum header: say a 4 byte length. Anything extra (overflow bit, version, type of overflow, number of...

> > The exception I'm thinking about is: it would be convenient to have the kernel reset the header metadata when a new buffer is allowed. > > I thought...

I think you make a good point, I just think userspace is better off not having to manage this complexity. It adds another step in the learning curve as some...

I agree. I would like to see documentation that says that userspace must reset the header by zeroing it. That gives us more flexibility going forward.

> Given that this infrastructure does not require either `unsafe`, nor any changes to the core process buffer infrastructure (pretty cool!), I'd rather we move it to some other file...