06:20 <AugustoRoman[m]> What's the scoop with memory alignment in rust? If I declare something like let mut buf = [0u8; 8];, is that guaranteed to be aligned to an 8-byte boundary?

06:20 <AugustoRoman[m]> * What's the scoop with memory alignment in rust? If I declare something like let mut buf = \[0u8; 8\];, is that guaranteed to be aligned to an 8-byte boundary?

06:20 <AugustoRoman[m]> * What's the scoop with memory alignment in rust? If I declare something like let mut buf = [0u8; 8]; , is that guaranteed to be aligned to an 8-byte boundary?

06:22 <M9names[m]> nope, that will have the alignment of the element type (1 byte)

06:24 <AugustoRoman[m]> Oh I see: https://github.com/embassy-rs/embassy/blob/3b734a7d0819c1e92f16b358dfc57bacf162f265/embassy-boot/src/lib.rs#L66

06:24 <AugustoRoman[m]> Is there a simpler way to align a specific value or is defining a type the way to go?

06:25 <M9names[m]> defining a type is the way to go. you can use the aligned crate if you're feeling lazy.

06:25 <AugustoRoman[m]> thanks!

11:20 <vivian[m]> Anyone know what the status is for risc-v for the pico 2 in the rpi-hal, I came across this PR that's been open for a while: https://github.com/rp-rs/rp-hal/pull/847 but not much else

14:22 <dngrs[m]> <vivian[m]> "Anyone know what the status is..." <- you can also try asking in the #rp-rs:matrix.org room

17:22 <ac1dg[m]> Hi everyone, I am struggling with LIN mode on STM32MP135F's USART1. According to the reference guide, I have to set the LINEN bit in the USART_CR2 register. I am quite new to Rust and embedded Linux in general. Can someone help me to get LIN mode to work?

18:28 <realroot[m]1> lulf will vibration from https://github.com/lulf/watchful/pull/13 be merged?

18:28 <realroot[m]1> maybe new updated PR with just that?

19:17 <lulf[m]> realroot: yup, happy to accept PRs for that.

19:43 <realroot[m]1> <lulf[m]> "realroot: yup, happy to accept..." <- PR sent ✅

19:46 <realroot[m]1> i wanted to make a separated one for the ticker but github ui merged it when i cliked it on Contribute. it is pretty small anyway

20:17 <thejpster[m]> I don’t know I spend ages patching up Google’s Rust driver for the Arm Generic Interrupt Controller to support Cortex-R52, and then I find Arm have their own Rust driver: https://git.trustedfirmware.org/plugins/gitiles/rust-spmc/arm-gic/

20:18 <thejpster[m]> Can you all just stop writing the same drivers over and over?

20:18 <thejpster[m]> Another PL011 driver too: https://git.trustedfirmware.org/plugins/gitiles/rust-spmc/arm-pl011-uart/

20:32 <dirbaio[m]> No, wheel reinventing will continue until morale improves

20:36 <thejpster[m]> But hey, at least Arm are getting in on it. Albeit under the TF-A umbrella

21:03 <realroot[m]1> lulf to add a timer i am not sure to how handle submenus

22:44 <diondokter[m]> There's a tiny breaking change in it due to a previous oversight that doesn't break any of the public dependents I could find.

22:44 <diondokter[m]> I released device-driver 1.0.3 just now.

22:44 <diondokter[m]> If it actually stops your code from compiling, let me know! I'll yank the release if it's a problem.

23:03 <JamesMunns[m]> Good old "ShoutVer" compatibility 😃

23:04 <diondokter[m]> Yeah, it technically warrants a 2.0 release.

23:04 <diondokter[m]> But you know... Rust would've been a 10.0+ release by know using the same criteria

23:05 <diondokter[m]> s/know/now/