Vadim Kaushan

As for the name, I suggest `mutex-trait` or `mutex_trait` (like [`stable_deref_trait`](https://crates.io/crates/stable_deref_trait))

It feels like both HAL and Resources do not match perfectly with the purpose of this mutex crate. Since 1. we do not want to create another Team for this...

From the firmware point of view supporting this hardware is technically possible and should not be very difficult, however, uploading this firmware to the hardware may not be possible. Some...

Starting from version V3J6M2 (~Jan 2020) firmware enables Level2 protection which permanently disables the debug port.

> An open firmware on these devices would really be nice.. oh well... you can't win them all... There is still hope. IIRC new firmware can still be decrypted, so...

I see two cons for using hardware interrupt dispatching: * For each vectored interrupt handler you have to declare register handling code like in [`asm.S/_start_trap`](https://github.com/rust-embedded/riscv-rt/blob/149ef05f54f730189be9e569d642be76c608c559/asm.S#L39-L79), which will cause additional size...

Now we have [template](https://github.com/rust-embedded/template/) repo, where we can introduce and agree upon perfect rustfmt rules.

@japaric, I think these tracking rules still should be made more "socially-comfortable". > First of all, this is only about tracking. You are not expected to do weekly, or biweekly,...

@japaric, > If visibility is an issue we could keep the list private (e.g. https://github.com/orgs/rust-embedded/teams/all) instead of using the "assignee" feature. I personally find the "assignee" feature useful since I...

@stappersg putting aside the opinion that such comments are not appropriate, I'd remind that the question of the ticket is not about "why", it's about "how". There is a demand...