<re_irc>
<@firefrommoonlight:matrix.org> I treat RMs as the source of truth for STM32, eg in how I suggest PAC changes, and how I write and document HAL functions
<re_irc>
<@firefrommoonlight:matrix.org> adamgreig: Yea, like the H7 DMA indexing. It's outstanding!
<re_irc>
<@firefrommoonlight:matrix.org> And re the Stream/Channel thing... This is one case where I deliberately deviated from the RM in API design... I chose consistency with the other STM32s
fabic has joined #rust-embedded
<re_irc>
<@dirbaio:matrix.org> same, embassy calls them all "channels". Why the hell did they change that??? 🤣
<re_irc>
<@firefrommoonlight:matrix.org> It's designed to trigger emotions (like frustration), which increases product engagement
<re_irc>
<@oddstr13:matrix.org> async I can work around with my very ugly unsafe unsound hack, but I don't know to deal with the `self.lower.clone()` stuff (copying around a reference to `ieee802154::Radio`?)
<re_irc>
<@dirbaio:matrix.org> you can probably just put a &Radio
<re_irc>
<@oddstr13:matrix.org> I assume I'm supposed to stash the radio in some other object rather than directly into the struct like this?
<re_irc>
<@dirbaio:matrix.org> on `receive` you can do the receive, then return a RxToken with the received packet and a TxToken with a `&'a mut Radio`so it can later transmit the response
<re_irc>
<@dirbaio:matrix.org> lifetimes on the `Device` trait are a bit confusing, it's kinda a hack to workaround lack of GAT (generic associated types)
<re_irc>
<@dirbaio:matrix.org> essentially it's allowed for RxToken/TxToken to borrow stuff from the Device
<re_irc>
<@dirbaio:matrix.org> ah you're copying from RawSocket?
<re_irc>
<@oddstr13:matrix.org> yep, I grabbed RawSocket
<re_irc>
<@oddstr13:matrix.org> I can push my current mess to github if you wanna look at what I've got
<re_irc>
<@dirbaio:matrix.org> yea these don't have lifetimes in RxToken/TxToken
<re_irc>
<@xiretza:xiretza.xyz> and a simple `[T; 256]` won't cut it?
<re_irc>
<@richarddodd:matrix.org> hmm maybe that's the best solution. Would be 4 * 256 ~ 1K mem. I'm probably not going to beat that with any other method.
<re_irc>
<@richarddodd:matrix.org> Might stick with that for now, then if I run out, then start changing things.
<re_irc>
<@thejpster:matrix.org> I've seen worse. But it does completely break repeatable builds - what do you need the timestamp for?
<re_irc>
<@newam:matrix.org> Just for example code (to make the date-time set a little closer to reality), I wanted to see if I could, I didn't know that proc-macros were not sandboxed.
starblue has quit [Ping timeout: 252 seconds]
DepthDeluxe has quit [Ping timeout: 260 seconds]
DepthDeluxe has joined #rust-embedded
fabic has quit [Ping timeout: 265 seconds]
starblue has joined #rust-embedded
<re_irc>
<@newam:matrix.org> is this safe (or is there a better way do extract non-overlapping sub-slices from an array)?
<re_irc>
<@firefrommoonlight:matrix.org> Has anyone used CMSIS? I'm interested in some of the DSP functions, and am deciding whether to translate, or use FFI. Leaning translate, although FFI has the advantage of being able to import the whole library
<re_irc>
<@firefrommoonlight:matrix.org> The C-compiling and FFI piece seem... nontrivial