ChanServ changed the topic of #rust-embedded to: Welcome to the Rust Embedded IRC channel! Bridged to #rust-embedded:matrix.org and logged at https://libera.irclog.whitequark.org/rust-embedded, code of conduct at https://www.rust-lang.org/conduct.html
AtleoS has joined #rust-embedded
pbsds3 has quit [Quit: The Lounge - https://thelounge.chat]
_whitelogger has joined #rust-embedded
_whitelogger has joined #rust-embedded
mameluc[m] has quit [Quit: Idle timeout reached: 172800s]
badyjoke[m] has quit [Quit: Idle timeout reached: 172800s]
djdisodo[m] has quit [Quit: Idle timeout reached: 172800s]
crabbedhaloablut has quit []
crabbedhaloablut has joined #rust-embedded
AtleoS has quit [Ping timeout: 240 seconds]
AtleoS has joined #rust-embedded
jotthyr[m] has quit [Quit: Idle timeout reached: 172800s]
aochagavia[m] has joined #rust-embedded
<aochagavia[m]> Newbie question: when using esp_hal_smartled, why do we need to provide an RMT channel? (See [this example](https://docs.rs/esp-hal-smartled/latest/esp_hal_smartled/index.html#example for context). As far as I understand, that uses infrared signals, but I'd expect it to be enough to communicate with the smart led through GPIO. I'm probably missing something, hence my question :0
<aochagavia[m]> * Newbie question: when using esp_hal_smartled, why do we need to provide an RMT channel? (See [this example](https://docs.rs/esp-hal-smartled/latest/esp_hal_smartled/index.html#example for context). As far as I understand, that uses infrared signals, but I'd expect it to be enough to communicate with the smart led through GPIO. I'm probably missing something, hence my question :)
<aochagavia[m]> * Newbie question: when using esp_hal_smartled, why do we need to provide an RMT channel? (See [this example](https://docs.rs/esp-hal-smartled/latest/esp_hal_smartled/index.html#example) for context). As far as I understand, that uses infrared signals, but I'd expect it to be enough to communicate with the smart led through GPIO. I'm probably missing something, hence my question :)
<aochagavia[m]> * Newbie question: when using `esp_hal_smartled`, why do we need to provide an RMT channel? (See [this example](https://docs.rs/esp-hal-smartled/latest/esp_hal_smartled/index.html#example) for context). As far as I understand, that uses infrared signals, but I'd expect it to be enough to communicate with the smart led through GPIO. I'm probably missing something, hence my question :)
<aochagavia[m]> (btw if there's a better place for questions, please let me know)
haobogu[m] has joined #rust-embedded
<haobogu[m]> https://matrix.to/#/#esp-rs:matrix.org could be the place
<haobogu[m]> many esp people in this room and they're all kind
<aochagavia[m]> Thanks, I'll join and ask there ;)
AtleoS has quit [Ping timeout: 256 seconds]
Amit[m] has joined #rust-embedded
<Amit[m]> 👋
kenny has quit [Quit: WeeChat 4.2.2]
kenny has joined #rust-embedded
fuse117[m] has joined #rust-embedded
<fuse117[m]> i am working with an i2c sensor with a relatively complex driver (in C). i need to supply read/write methods to the driver. i would like to do so from rust, but im not sure how to handle some generics. does anyone know of any open source drivers i can look at as an example?
<fuse117[m]> * source drivers that do this that i can
IlPalazzo-ojiisa has joined #rust-embedded
PhilMarkgraf[m] has quit [Quit: Idle timeout reached: 172800s]
diondokter[m] has quit [Quit: Idle timeout reached: 172800s]
richardeoin has quit [Ping timeout: 268 seconds]
richardeoin has joined #rust-embedded
JomerDev[m] has quit [Quit: Idle timeout reached: 172800s]
adamgreig[m] has quit [Quit: Idle timeout reached: 172800s]
inara has quit [Quit: Leaving]
IlPalazzo-ojiisa has quit [Quit: Leaving.]
inara has joined #rust-embedded