Scott Mabin

I'd consider the original issue closed via https://github.com/esp-rs/esp-hal/pull/1672, but I'm very keen to discuss the DMA queing API further, so I've opened https://github.com/esp-rs/esp-hal/issues/1785 to do so.

Yep! Thanks!

So it's possible, but what are the complications if we do?

Hmm, this got a bit harder now we have the 802154 driver in tree, I guess I need to figure out what we can do with `c_variadic`

> Maybe we should disable the peripheral on drop (a System::disable would be needed) I am also thinking if we should actually reset the peripheral in enable ... not just...

The `FlashSafeDma` wrapper would help here (but is probably missing some methods/traits for LCD_CAM), but maybe if every driver that uses DMA might need this we should build it into...

I think we should update the example, with a comment referring back to this issue so that when we fix the underlying driver we can remove it.

> Maybe it would be good to have a way to specify which core the interrupt should be handled on. Unfortunately I don't think this is possible, at least on...

Regarding dependencies, this is sadly a general Rust problem which every project with examples will run into. We are pushing people towards using https://github.com/esp-rs/esp-template and picking parts from examples across...

Thank you for the feedback, it's really valuable! Something like `esp-glue` is on our roadmap, but we have some other things, mainly in esp-hal, that we need to work on...