Brad Campbell

I think that adding a dynamic RAM slice approach needs to be its own PR. There is a lot going on in that change and it really needs independent scrutiny....

I made a start on this here: https://github.com/tock/tock/compare/master...rp2040-fixed-clocks following the SAM4L example.

> a basis for discussion of whether/which features _should_ move where to enable no-unsafe or minimize unsafe in certain chip crates. This would be very helpful. This PR only changes...

> Moreover, merging a design pattern change like this whole cloth for just one chip, rather than more targeted parts of the design pattern across all chips, seems worse to...

> As a sidenote, I'm glad to see the Nrf5x aes implementation updated to use a `TakeCell`. The existing implementation is unsound with regards to DMA. Unfortunately I'm pretty sure...

I agree that you can see why something like a device tree is attractive, and I'm inclined to believe that having something like a device tree would be an improvement...

> Why was it abandoned? The tool required a fair bit of customization to support each chip and capsule in Tock, and it wasn't immediately obvious how to make it...

Right, something like https://github.com/zephyrproject-rtos/zephyr/blob/main/dts/arm/nordic/nrf52840.dtsi describes the hardware, but doesn't include something like userspace should have access to the Screen driver which uses the ScreenSplit virtualizer which provides a 128x32 pixel...

I would like to see the default MPU (if we still have one) align to a multiple of 4, which allows apps to at least run. ------- As for a...

I updated this with the changes to debug.rs.