<JamesMunns[m]>
Just wanted to share some pretty RGB :D
Rodney[m] has joined #rust-embedded
<Rodney[m]>
<JamesMunns[m]> "bafkreidmwikpwcgmk7qukvm4clb66g2..." <- You can never have too many LEDs 😃 What's this project?
<JamesMunns[m]>
Rodney[m]: I'm giving a training at RustNL, this is the hardware I'm going to have the people use. The board has two rp2040s, one acting as a debug probe and the other acting as the target, goal will be to write some tools for getting the PC and the MCU talking
<Rodney[m]>
<JamesMunns[m]> "https://2024.rustnl.org/..."; <- Ah nice, I was guessing it was a game with the two thumb controls near the bottom and all the LEDs, but I'm sure your trainings are more fun than any game!
IlPalazzo-ojiisa has joined #rust-embedded
Socke has quit [Ping timeout: 268 seconds]
djdisodo[m] has quit [Quit: Idle timeout reached: 172800s]
vollbrecht[m] has quit [Quit: Idle timeout reached: 172800s]
M9names[m] has quit [Quit: Idle timeout reached: 172800s]
dirbaio[m] has quit [Quit: Idle timeout reached: 172800s]
crabbedhaloablut has quit []
crabbedhaloablut has joined #rust-embedded
barafael[m] has joined #rust-embedded
<barafael[m]>
I have ported one of my drivers to e-hal 1.0. It's of course still blocking. Is there anything I need to/should/can do to make this driver easier to use for people using async environments? Like implement e-hal-async traits?
burrbull[m] has joined #rust-embedded
<burrbull[m]>
yes. You should add "async" feature to your crate and add async variant of your driver there
Lister has joined #rust-embedded
starblue has quit [Ping timeout: 268 seconds]
<barafael[m]>
burrbull: should the async and blocking features be mutually exclusive? I know features are supposed to be additive only. Do I have to post-fix all async methods `..._async`?
<burrbull[m]>
if your structure will support both blocking and async at one time, yes. But I would better create other structure, or add Async/Blocking mode type parameter for this structure and methods to switch between them
Lister has joined #rust-embedded
<barafael[m]>
a different other structure sounds feasible. Thanks a lot burrbull !
mali[m] has quit [Quit: Idle timeout reached: 172800s]
GrantM11235[m] has quit [Quit: Idle timeout reached: 172800s]
crabbedhaloablut has quit []
crabbedhaloablut has joined #rust-embedded
Lister has joined #rust-embedded
Lister has quit [Ping timeout: 256 seconds]
Lister has joined #rust-embedded
Lister has quit [Ping timeout: 264 seconds]
Lister has joined #rust-embedded
Lister has quit [Ping timeout: 268 seconds]
starblue has quit [Ping timeout: 260 seconds]
<burrbull[m]>
you could add it to awesome-embedded-rust page on gh
starblue has joined #rust-embedded
Lister has joined #rust-embedded
Lister has quit [Ping timeout: 268 seconds]
Lister has joined #rust-embedded
Lister has quit [Ping timeout: 252 seconds]
M9names[m] has joined #rust-embedded
<M9names[m]>
<barafael[m]> "I did the async impl now..." <- i would have not bothered having an async feature. since your blocking and async impls don't collide there's no good reason to make async optional.