Brad Campbell
Brad Campbell
This looks really good to me. For me, I'm not keen on exposing both a synchronous version and an async version. Converting a sync to async is pretty straightforward using...
Need more investigation on the frame pointers, since removing them seems to break cortex-m4 support.
> @bradjc How would you feel about enabling this just for the RISC-V boards? After all, the frame pointer win is miniscule on ARM but big on RISC-V, which seems...
I can see that components allow for one author to add the call to initialize and it would be less likely to be forgotten, but I'm not sure what else...
I think `configure(arg1, arg2, ...)` is important, but I'm still not sure how `hil.initialize()` (no arguments) is useful. Why should a board initialize a peripheral (in components or otherwise) if...
Handling ReturnCodes is hard, but if there is no mechanism to report errors that writing reliable long-running applications is hard too, so in general I think we do need a...
But then we lose access to the rest of that buffer forever, right?
The other problem, is what happens if the hardware _does_ receive too much? For example, serial over USB isn't a real UART bus, and we might get longer packets from...
That's not the only thing, the driver can also just pass up more bytes than were asked for (of course until the buffer runs out of space). That is what...
> Well that's slightly terrifying. I don't think it's a good behavior for the kernel to modify parts of the buffer that the app didn't ask it to. We should.....