Román Cárdenas Rodríguez

I think that this pull request should be accepted. I've checked the tests and it crashes for Python 3.6+.

Yes, it is possible, though is a little bit "difficult". If you check the `setup.py` file, you will find that it defines different entry points that specify the available plugins....

`portable-atomic` 1.5.0 is out with this feature: https://github.com/taiki-e/portable-atomic/releases/tag/v1.5.0 Should I set up a PR?

I will try with other sensor as soon as possible and report here the results

I have tried the code with another three different DHT11, and the same issue happened: around 80% of the measures reported a checksum error.

Hi! I need to think more about this, but currently, I think that `riscv` should support common cases. For very specific scenarios, developers could always use inline assembly.

For the `riscv` environment, would it make sense to move the `Exception` and `Interrupt` enums to this crate? Or do you think it is better to have them duplicate in...

Yep, my plan is to create a new `riscv-interrupt-number` crate (or perhaps a more generic name, as I also plan to move priority numbers or HART ID numbers) that follows...

I propose a modification to this crate to ease vector-like handling of the external interrupts. Right now, `svd2rust` will generate a `__EXTERNAL_INTERRUPTS` table with all the handlers for the external...

It turns out that my proposed approach wasn't that easy to implement. I developed a macro for doing the same. You can check it in rust-embedded/riscv-rt#113