-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[email protected]
roadmap?
#468
Comments
Initial trait implementations were done by @rursprung in #470! If anyone is interested in picking up the SPI and I2C drivers, please feel free to do so :) |
rursprung
added a commit
to rursprung/avr-hal
that referenced
this issue
Dec 28, 2023
with `embedded-hal` v1 the USART traits have been removed in favour of the new `embedded-io` crate. this adds a (very basic) implementation for `Read` and `Write`. other traits (such as the `*Ready` or `BufRead` traits) have not (yet) been implemented and some (like `Seek`) probably can't be implemented for this HAL. a better implementation might use a buffer in the background to receive more than one byte at once. see also Rahix#249 for a related PR. this is part of Rahix#468
rursprung
added a commit
to rursprung/avr-hal
that referenced
this issue
Dec 28, 2023
with `embedded-hal` v1 the USART traits have been removed in favour of the new `embedded-io` crate. this adds a (very basic) implementation for `Read` and `Write`. other traits (such as the `*Ready` or `BufRead` traits) have not (yet) been implemented and some (like `Seek`) probably can't be implemented for this HAL. a better implementation might use a buffer in the background to receive more than one byte at once. see also Rahix#249 for a related PR. this is part of Rahix#468
rursprung
added a commit
to rursprung/avr-hal
that referenced
this issue
Jan 17, 2024
with `embedded-hal` v1 the USART traits have been removed in favour of the new `embedded-io` crate. this adds a (very basic) implementation for `Read` and `Write`. other traits (such as the `*Ready` or `BufRead` traits) have not (yet) been implemented and some (like `Seek`) probably can't be implemented for this HAL. a better implementation might use a buffer in the background to receive more than one byte at once. see also Rahix#249 for a related PR. this is part of Rahix#468
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey there! I recently went to port one of my driver crates to the new
[email protected]
, with its (honestly much nicer) APIs. However, I also wanted to check if my port worked on real hardware, so I grabbed an Arduino and searched for a matching alpha/rc/etc for this set of crates.To my surprise, there wasn't anything new that I could see, and checking for updates in the various
embedded
channels didn't get me very far. 🥹Is there any plan to begin porting
avr-hal
to[email protected]
? The API is pretty stable now, and it's a good idea to get started before the release on December 28th.If so, could you please link it to me? Otherwise, is this issue a good spot to start sticking down checkboxes? I'd at least like to progress on SPI, I2C, and other higher-level parts of the interface - though some other parts of
avr-hal-generic
are a bit beyond me. (I'm looking at you,delay.rs
!) 😄The text was updated successfully, but these errors were encountered: