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
jxsl has joined #rust-embedded
therealprof[m] has quit [Quit: Idle timeout reached: 172800s]
SbastiendHerbais has quit [Quit: Idle timeout reached: 172800s]
<JamesMunns[m]> Yeah, Sophie in RTICv1, priorities work the way you think, BUT if you share resources between two tasks, the lower task is "escalated" to the priority of the higher task for the length of the lock. The intent is that you keep your locks as short as possible, usually just long enough to read or write some value.
<JamesMunns[m]> It sounds like you have it sorted out now, but if you need the high prio task to not be inhibited, you can look at potentially using something like a channel between low and high to pass information without requiring a lock
<JamesMunns[m]> Misc thought CC adamgreig - I realized that the Rust survey team has the option to run "micro surveys" on behalf of Rust teams: https://github.com/rust-lang/surveys/blob/main/micro-surveys.md... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/HUqqHVXlWZESVkWssRKbUWlt>)
<JamesMunns[m]> I'll go put this in the discussion notes for next week so we don't lose this :D
<JamesMunns[m]> I think a survey could be valuable:... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/tOLYKLSEfEcPoKLJuNydodbR>)
<JamesMunns[m]> (significantly more than Android and iOS, half as much as WASM and macOS!)
thejpster[m] has joined #rust-embedded
<thejpster[m]> I’ve been told by a Big Company that there is no interest in Rust for IoT devices or microcontrollers and so they’re not putting any effort in to it. Some numbers to dispute that would be useful.
therealprof[m] has joined #rust-embedded
<therealprof[m]> Sounds like a great idea! Let's put that into motion.
<JamesMunns[m]> Pinged the survey team about the question number limit, so we can figure out if we need to limit the number of questions
<Sophie[m]> <JamesMunns[m]> "Yeah, Sophie in RTICv1, prioriti..." <- > <@jamesmunns:beeper.com> Yeah, Sophie in RTICv1, priorities work the way you think, BUT if you share resources between two tasks, the lower task is "escalated" to the priority of the higher task for the length of the lock. The intent is that you keep your... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/vpqZPRrCdCWyXKgeJiDjcmTH>)
<Sophie[m]> Ty for clarifying!
ninjasource[m] has quit [Quit: Idle timeout reached: 172800s]
thalesfragoso[m] has quit [Quit: Idle timeout reached: 172800s]
<thejpster[m]> Also, can anyone point me to examples of running a machine learning model on a microcontroller in Rust? Native or via FFI is fine.
<ryan-summers[m]> Maybe https://crates.io/crates/microflow?
t-moe[m] has quit [Quit: Idle timeout reached: 172800s]
GeorgesP[m] has joined #rust-embedded
<GeorgesP[m]> Hi, I am writing a chip driver based on enbedded_io_async because protocol is over UART. I need to set the UART baudrate from within the driver (yes the chip change baudrate during init...), so I defined a Baud trait that the final implantation must provide. I am doing an example using embedded_io_adapter::FromTokio<tokio_serial::SerialStream>. SerialStream impl the crate tokio_serial::SerialPort which have a set_baud_rate()
<GeorgesP[m]> function, but I am not able to go through the FromTokio wrapper. Can you help me plz ?
<dirbaio[m]> I think you'll have to write your own adapter that impls both embedded-io-async and your baudrate trait
<dirbaio[m]> Copy-paste from e-io-adapters and extend
<dirbaio[m]> You could also write a wrapper that forwards embedded-io-async and adds your baudrate trait but I'm not sure if it'd be easier
marmrt[m] has joined #rust-embedded
<marmrt[m]> <thejpster[m]> "Also, can anyone point me to..." <- https://github.com/matteocarnelos/microflow-rs A colleague did his thesis on that
mameluc[m] has quit [Quit: Idle timeout reached: 172800s]
jannic[m] has joined #rust-embedded
<jannic[m]> TIL that `-Cinline-threshold` is ignored by the rust compiler - and has been for a few years. Rust beta just started to print a warning about it.
<dirbaio[m]> wat
<dirbaio[m]> I remember messing with it and it did affect the code size. but maybe that was indeed 2y ago
<dirbaio[m]> how time flies 🥲
<thejpster[m]> I have a question about fugit. When doing rate conversion, it multiplies by NOM and divides by DENOM in https://github.com/korken89/fugit/blob/0ad21f78f7d0b4f691ba9c7445f93299039d9f54/src/rate.rs#L220, should it add half a DENOM to do half-up rounding?
<thejpster[m]> I expect 12_000_000 (Rate<u32, 1, 1>) to convert to 0x0020c49c (Rate<u32, 1000, 65536>) but instead I get 0x0020c49b.
<thejpster[m]>
<thejpster[m]> Converting 0x0020c49b back I get 32767.990 (error 0.01) whereas 0x0020c49c gives 32768.005 (error 0.005).
<thejpster[m]> am I holding it wrong?
<thejpster[m]> Also the new #[warn(clippy::doc_lazy_continuation)] is making clippy very sad
jxsl has quit [Ping timeout: 272 seconds]
jistr has quit [Remote host closed the connection]
jistr has joined #rust-embedded
adamgreig[m] has joined #rust-embedded
<adamgreig[m]> <JamesMunns[m]> "Misc thought CC adamgreig - I..." <- > <@jamesmunns:beeper.com> Misc thought CC adamgreig - I realized that the Rust survey team has the option to run "micro surveys" on behalf of Rust teams: https://github.com/rust-lang/surveys/blob/main/micro-surveys.md... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/BfPaMjKejPNkQNRLLGHopMNb>)