Aleš Katona

Resources seems like a good placement, but HAL team should be closely involved because they are the ones that can provide the best "hands on" requirements.

> Hmm I see... the main issue with the volatile-register approach and the Rust ecosystem is that base addresses of peripherals are target-dependent. Therefore we need to deal with const...

> I'm on vacation and I'll be traveling by the time of the meeting. I may have an Internet connection and be able to join, but I'm not 100% sure....

@Disasm I think this should get merged, I just got back and this step actually got me fishing in memory too

I've created [this PR](https://github.com/riscv-rust/riscv-rust-quickstart/pull/25) with new dependencies which should fix this issue. Please try if that works, we should get it merged in soon.

> I'm fine with a mention in the commit message. Thanks. :) Added in the commit msg for alpha.7 support

@Disasm sorry I've been out of the loop for so long. Are these still to be done?

[this PR](https://github.com/riscv-rust/e310x-hal/pull/34) kinda solves this but as mentioned it's low res and anything < `~30us` value will just be a slight `NOOP` slowdown. I think we should keep this open...

> _NOTE_: I don't have hardware to actually test this fix. Sadly currently neither do I since I burned my redv :(

closing in favour of #45