01:39 <sneakernet[m]> is it possible to create a single embedded-rust project that can build for multiple hardware (and if so can you link to an example)?

06:25 <paulyoung[m]> <sneakernet[m]> "is it possible to create a..." <- There's a video on YouTube about this by diondokter: https://youtu.be/8ydYtuUKOsI?si=VWCAeB5D7d4bgLjV

07:35 <Kaspar[m]> <sneakernet[m]> "is it possible to create a..." <- We're trying to get there with [RIOT-rs](https://github.com/future-proof-iot/RIOT-rs). Early stages though ...

14:07 <dirbaio[m]> hehe the static mut lint is going to get stronger https://github.com/rust-lang/rust/issues/123060

14:08 <JamesMunns[m]> good.gif

14:16 <thejpster[m]> This was an interesting comment:

14:16 <thejpster[m]> > The general rule for -mcpu options is that they should (roughly) enable the maximum set of features available

14:16 <thejpster[m]> https://github.com/llvm/llvm-project/pull/88287

14:17 <thejpster[m]> My read of that is that -C target-cpu=cortex-m85, say, should turn on M-Profile Vector Extensions and double precision floating point, and you should use -C target-features=-fp64,-mve or something similar to turn them off again.

15:36 <Ecco> embassy question: how am I supposed to create drivers from embassy_stm32::Peripherals?

15:36 <Ecco> Let's suppose I have a "display" driver and a RTC driver

15:37 <Ecco> I have a function build_display(p: embassy_stm32::Peripherals) -> MyDisplay

15:37 <Ecco> and another build_rtc(p: embassy_stm32::Peripherals) -> Rtc

15:37 <dirbaio[m]> Pass individual peripherals, not the entire Peripherals struct 

15:38 <Ecco> so individual peripherals/pins

15:38 <dirbaio[m]> Yes 

15:38 <Ecco> how about passing a reference to embassy_stm32::Peripherals?

15:38 <dirbaio[m]> This might be helpful to reduce boilerplate https://github.com/adamgreig/assign-resources 

15:38 <Ecco> oh cool

15:38 <Ecco> exactly my problem

15:38 <Ecco> thanks!

15:39 <dirbaio[m]> Ecco: Won't work, because these functions need to take ownership of the peripherals they need

15:39 <dirbaio[m]> A borrow is not enough 

15:39 <Ecco> indeed

15:39 <Ecco> makes sense

15:39 <Ecco> they most likely want some level of exclusive access to the device

15:40 <Ecco> assign-resources is exactly what I was trying to conceptualize

15:40 <Ecco> excellent!

15:40 <Ecco> Question: I assume assign-resources is zero-cost. is it?

15:40 <dirbaio[m]> Yes 

15:41 <Ecco> yeah, it's really just doing the partial moves in a nice way

15:41 <Ecco> the code is really short

15:41 <Ecco> cool

15:41 <Ecco> Honestly, I think this should be part of embassy itself

15:42 <Ecco> or at least used in an embassy example

15:42 <Ecco> b/c that's most likely a problem most users are going to run into

15:42 <Ecco> anyway, thanks a lot for the pointer - super helpfup, as always!

15:42 <Ecco> *helpful

18:38 <JomerDev[m]> Has anybody here played with overclocking the rp2040/pico with rust and has an example?

19:19 <ithinuel[m]> <JomerDev[m]> "Has anybody here played with..." <- I think some people in #rp-rs:matrix.org did play with overclocking. Whether they have an example or not, I don’t know.

20:05 <thejpster[m]> <ithinuel[m]> "I think some people in #rp-rs:..." <- How much do you want to overclock?

20:09 <JomerDev[m]> thejpster[m]: In theory to at least 200Mhz. I have by now found a project on github which shows how to do it with embassy