IlPalazzo-ojiisa has quit [Remote host closed the connection]
crabbedhaloablut has quit [Ping timeout: 255 seconds]
crabbedhaloablut has joined #rust-embedded
crabbedhaloablut has quit [Ping timeout: 255 seconds]
crabbedhaloablut has joined #rust-embedded
starblue has joined #rust-embedded
IlPalazzo-ojiisa has joined #rust-embedded
neceve has joined #rust-embedded
neceve has quit [Ping timeout: 268 seconds]
<re_irc>
< (@firefrommoonlight:matrix.org)> Depends if you like Async syntax or not
<re_irc>
< (@firefrommoonlight:matrix.org)> (I like RTIC)
<re_irc>
< (@firefrommoonlight:matrix.org)> RTIC is a thin wrapper around interrupt handlers and the resources they share
IlPalazzo-ojiisa has quit [Quit: Leaving.]
IlPalazzo-ojiisa has joined #rust-embedded
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #rust-embedded
<re_irc>
<thejpster> Do you want to do Wi-Fi on the same chip as your application, or do you want a separate Wi-Fi / Bluetooth modem with a low-level interface (like the Raspberry Pi Pico-W uses) or a separate Wi-Fi / Bluetooth modem with a high-level interface (one that uses AT commands over UART and runs the IP stack internally)?
<re_irc>
<thejpster> I guess this depends on your target bill-of-materials budget and your power / energy budget. Using a modem with a high-level interface probably involves less software work on the applications processor, but it'll use more energy to do the same work, and it'll cost a few $ more.
eigenform has left #rust-embedded [#rust-embedded]