Rahix
Improved documentation in commit 75820c55c2ba ("generic: Improve documentation of clock module"). Still need to document how migration from `arduino-hal` to `atmega-hal` would work.
What is the status with this PR?
Just as an example, this is the trait I've settled on in [`shared-bus`](https://github.com/Rahix/shared-bus): ```rust pub trait BusMutex { type Bus; fn create(v: Self::Bus) -> Self; fn lock R>(&self, f: F)...
There is also [actions-rust-lang/setup-rust-toolchain](https://github.com/actions-rust-lang/setup-rust-toolchain) but I don't know how the two compare.
Hm, so we are running into https://github.com/Rahix/avr-hal/issues/537 here as well now. I'm considering whether going "nuclear" and just pinning `proc-macro2` for `avr-device-macros` directly might be the best solution: ```diff diff...
A downside of pinning in `avr-device-macros` is that downstream users cannot easily override it, I think. This means that when people want to switch to a different toolchain version, they...
Full diff (very large!): [svd2rust-0.33.1-changes.diff.txt.zip](https://github.com/Rahix/avr-device/files/15210998/svd2rust-0.33.1-changes.diff.txt.zip) "Manageable" diff of just ATmega328P: [svd2rust-0.33.1-changes-atmega328p.diff.txt](https://github.com/Rahix/avr-device/files/15210999/svd2rust-0.33.1-changes-atmega328p.diff.txt)
> The most major change seems to be from [0.31.0](https://github.com/rust-embedded/svd2rust/releases/tag/v0.31.0) where registers are now accessed using methods instead of fields. This will require rather large downstream changes. This can be...
The problem is that not all SPI implementations support this. Notably, I think the Linux HAL implementation runs into this problem. The traits here in `embedded-hal` have to be the...
I guess the most straight forward solution to fix this regression would be to add a feature-flag for `AtomicDevice`. We did the same thing back in `shared-bus` to cater for...