Rahix
> whilst also preventing usage of the USART for USART purposes. This part is actually very simple. The `UsartSpi` driver constructor consumes the `USART` peripheral, just like the current UART...
> if you could aid a hand in the direction it needs to go in! Generally, you'll need to add a `usart_spi` module in `avr-hal-generic`, similar in structure to the...
I'd create a completely new module for USART as SPI. `usart_spi` I guess.
From my side, I wouldn't worry too much about the total diff of the PR as long as the commits stay clean and logical. IIRC you're one to take this...
A few more comments: > This could be improved by using the executable versions of svd2rust, svdtools and atdf2svd, but that would greatly reduce reproducibility I am strongly against using...
Custom linker scripts will be a part of tackling #76, I don't think we should separate these two. The linker scripts need to be synchronized with the libc runtime, I'd...
Neat, _prettyplease_ looks perfect for what we are doing here. Would be my favorite, then :)
So this is huge chain of interdependencies that we can't easily resolve right now: 1. We can't upgrade the compiler right now because of some pending regression fixes. See ....
Try `nightly-2024-03-22`, that's the currently recommended compiler. I will get back to you in a few days, to take a closer look at the state of things - feel free...