<takkaryx[m]>
<JamesMunns[m]1> "btw, I'm interested if it..." <- ooo, I'll take a look, unfortunately, I'm only updating the embedded side to be rust based, the host side needs to be backwards compatible as I'm forking this project, re-writing both sides at this point isn't quite worth it.
ni has quit [*.net *.split]
crabbedhaloablut has quit [*.net *.split]
Lumpio- has quit [*.net *.split]
Darius has quit [*.net *.split]
dnm has quit [*.net *.split]
limpkin has quit [*.net *.split]
GenTooMan has quit [*.net *.split]
limpkin has joined #rust-embedded
crabbedhaloablut has joined #rust-embedded
Lumpio- has joined #rust-embedded
Darius has joined #rust-embedded
dnm has joined #rust-embedded
ni has joined #rust-embedded
GenTooMan has joined #rust-embedded
pronvis has joined #rust-embedded
IlPalazzo-ojiisa has joined #rust-embedded
pronvis has quit [Ping timeout: 252 seconds]
Ralph[m] has quit [Quit: Idle timeout reached: 172800s]
Makarov has joined #rust-embedded
JamesMunns[m]1 has quit [Quit: Idle timeout reached: 172800s]
<dangroshev[m]>
it's such a joy to use with embassy ❤️
Foxyloxy_ has joined #rust-embedded
AlexandrosLiarok has quit [Quit: Idle timeout reached: 172800s]
Foxyloxy_ has quit [Client Quit]
Foxyloxy has quit [Read error: Connection reset by peer]
Foxyloxy has joined #rust-embedded
henrik_alser[m] has quit [Quit: Idle timeout reached: 172800s]
Makarov25 has joined #rust-embedded
Makarov15 has quit [Ping timeout: 250 seconds]
<firefrommoonligh>
The PIO concept seems very useful
<firefrommoonligh>
Seems like a better way to handle concurrency then sequential operations
<firefrommoonligh>
Handling IO etc, which is I suppose the intent
pronvis has quit [Ping timeout: 260 seconds]
<dangroshev[m]>
<firefrommoonligh> "Handling IO etc, which is I..." <- yes! I linked someone writing a display driver on PIO+DMA, it's quite creative but the result is lovely, a framebuffer is pumped into the display and touch events are grabbed back with no CPU involvement at all
<firefrommoonligh>
I had heard about this MCU and PIO namedropped, but it clicked after the article and some digging. This is great
<firefrommoonligh>
Like multiple cores, but when the extra cores can be baby cores, and you have multiple ones. It sounds as if you could use them like interrupts, but with true concurrency
<firefrommoonligh>
Standard memory sharing concerns OFC that you get with concurrency
<firefrommoonligh>
Never miss IO even if you blocked the CPU for some too long
<firefrommoonligh>
s/some//
henrik_alser[m] has joined #rust-embedded
<henrik_alser[m]>
I switched to it during chipagheddon when it was pretty much the only thing you could get for a while, and because i have a ”policy” of reusing the same mcu as in a prev project unless i have a strong reason to switch it has stuck with me for like at least 30 some different projects/products by now. I really enjoy it, despite its shortcomings (would be cool to have full atomics and an fpu for example), but IRL it hasn’t
<henrik_alser[m]>
yet been a real problem in my use cases for it, compared to what it has to offer with PIO and multicore etc at that price point. The documentation and community support is really good too
Makarov25 has quit [Ping timeout: 250 seconds]
<henrik_alser[m]>
embassy-rp is toooo nice, i agree dangroshev
adamgreig[m] has joined #rust-embedded
<adamgreig[m]>
James Munns: did you make that spreadsheet in the end?
JamesMunns[m] has joined #rust-embedded
<JamesMunns[m]>
shiiiiiiiiiiii
<JamesMunns[m]>
on it now
<adamgreig[m]>
loads of time :D
<adamgreig[m]>
@room happy tuesday, meeting time again! agenda is https://hackmd.io/89W7PykxSCChu1ZY74qoeg, please add anything you'd like to announce; we'll spend this meeting triaging old issues on the wg and embedded-hal repos so please feel free to join in and help spot issues we can close! we'll start in a few minutes
<JamesMunns[m]>
If you're interested in assisting with the triaging, please let me know, and I can start by just dividing up all the issues as a first pass
<JamesMunns[m]>
I'll divide up the first half at 20:05, then if you come late just start claiming them below that :)
Henk[m] has joined #rust-embedded
<Henk[m]>
JamesMunns[m]: I'm interested, but would need some guidance getting started
<JamesMunns[m]>
We're here in chat for guidance!
<JamesMunns[m]>
A big first check is "is this still relevant, and something the WG is likely to do?"
<JamesMunns[m]>
(any other takers? Add the 🙋 emoji to my other message :) )
<adamgreig[m]>
I'll make a new label for "we checked today and it's still a good issue"
<adamgreig[m]>
maybe triage-2024-keep ? open to other ideas though
<Henk[m]>
JamesMunns[m]: I'm just gonna lurk then ;)
<Henk[m]>
* gonna lurk this chat then ;)
bartmassey[m] has joined #rust-embedded
<bartmassey[m]>
Sorry, a little late. Happy to try to help.
<JamesMunns[m]>
Okay, started everyone with 10 issues, newest issues are up for grabs, feel free to chat here :)
<adamgreig[m]>
let's goooooo
<JamesMunns[m]>
Please add comments in the "Triage Status" column
<JamesMunns[m]>
If you aren't sure, feel free to unclaim and ask for help here
<Henk[m]>
💪
dirbaio[m] has joined #rust-embedded
<dirbaio[m]>
a lot of these are "should the WG develop a crate for X", maybe we should think about what the response is for all these together
<dirbaio[m]>
because in 2024 it's clear the WG only develops more "foundational" crates, not random embedded-related libs
<JamesMunns[m]>
Yeah, IMO the best response would be to point people to other places, and mark it as "out of scope" for the WG proper.
<bartmassey[m]>
LOL my first issue is MSRV 😀. Easy start.
<JamesMunns[m]>
If you want to wait, I'm writing up a response we can use for this
<JamesMunns[m]>
therealprof[m]: > Personal Disclosure: I am in the process of starting a consultancy company, focused specifically on Rust for developing systems/embeddded level software, and training on the same topics. I'll update this comment with a bit more detail after we announce this publicly at RustConf (not a big secret, the company just hasn't launched yet 😄)
<JamesMunns[m]>
Phew :)
<therealprof[m]>
I remember thinking back then that it's hard to have a meaningful conflict of interest in the project since we don't have any business decisions to make.
jannic[m] has joined #rust-embedded
<jannic[m]>
Is it useful to keep a ticket that mainly points to a rust-lang RFC? (https://github.com/rust-embedded/wg/issues/366) No activity on either side for years. I can't judge the usefulness of the RFC itself quickly, but the ticket on the wg tracker seems to be a bit redundant anyway.
<therealprof[m]>
@jamesmunns:beeper.com I think we can conclude that time has shown that company sponsorship is a positive thing and will hardly have a conflict of interest potential?
<JamesMunns[m]>
tbh, the largest conflict of interest was when Jorge and I were on the core team, and we privately agreed to recuse ourselves if it was relevant, and leave the discussion to you. After that, I stepped down, making it no longer relevant.
<JamesMunns[m]>
IMO, there is some policy between the council and the foundation regarding "number of people in lead position" from one company, but I don't think we need to immediately apply it
<therealprof[m]>
Oh boy, I seemingly got all the philosophical ones...
<bartmassey[m]>
If someone wanted to take a look at #412 and #418, about stabilizing -rt, that would be great.
<bartmassey[m]>
Sorry, #412 and #383
<bartmassey[m]>
Jeez #418 and #383.
<therealprof[m]>
@jamesmunns:beeper.com Since you can't buy a seat at WG table, I doubt that this will ever become a problem.
<JamesMunns[m]>
Who had the cool parametric driver search from last week again?
<JamesMunns[m]>
therealprof[m]: yeah, IMO we might want to make sure the core team avoids two people from the same company, but beyond that I think we're good
<JamesMunns[m]>
Does anyone have a link to the probe-rs perf thingy?
<bartmassey[m]>
#402 is a good example of an enhancement issue that is inactive since 2019 but is still valid :grinning:. What do we want to do with these?
<adamgreig[m]>
if it's still valid and worth having as an issue we can leave it open, and add the label triage-2024-keep so we know it was checked
<adamgreig[m]>
dirbaio: can't we close 266 as completed? we made a libs team and you're on it :P
diondokter[m] has joined #rust-embedded
<diondokter[m]>
<JamesMunns[m]> "diondokter can you take over..." <- oof, 8 years old! Yeah I can add to it. But what do you mean with 'take over's?
<dirbaio[m]>
lol, true
<diondokter[m]>
s/s//
<JamesMunns[m]>
diondokter[m]: Ah sorry, could you please share the context and any upstream tracking issues for the optimize for size stuff? And go ahead and close the issue, or I can do that after you've added context
<JamesMunns[m]>
btw all, I'm going to mark the doc as not "world writable" to avoid spam, feel free to send me an editor request if you'd like to continue after this meeting. I'll be around for 10m or so more.
<jannic[m]>
Even the reporter sounded like he didn't want to discuss it further, but of course the question itself is still valid so I'm fine with keeping it open.
<dirbaio[m]>
we discussed that in rustnl
<dirbaio[m]>
but the conclusion was a bit ¯\_(ツ)_/¯
<dirbaio[m]>
in that it's too early to "codify" best practices
<jannic[m]>
I think it's fine to keep tickets open as long as someone thinks it is useful. I was only worried about loads of tickets nobody would look into anway.
<JamesMunns[m]>
tbh, I think we should document embassy's best practices first, but I'm waiting for you to propose a time dirbaio so I can help :)
<dirbaio[m]>
haha, sure!
<JamesMunns[m]>
(I know you're busy, just teasing :D)
<dirbaio[m]>
but that'll be "embassy's opinion on best practices", not "THE best practices"
<JamesMunns[m]>
sure, but that's easier to put together, and less contentious. Might be useful to the general discussion
<dirbaio[m]>
other people will have the opinion some of the stuff embassy proposes is bad
<dirbaio[m]>
like, no generics/typestates
<dirbaio[m]>
so idk
<JamesMunns[m]>
IMO setting out what you think is good, might mean finding some subset of that which isn't controversial, or would be useful as a template for someone to propose their own delta.
<dirbaio[m]>
having it documented in an embassy "contributor guide" would still be very useful
<JamesMunns[m]>
yep
<JamesMunns[m]>
do the easy things first, then iterate
<JamesMunns[m]>
(easier, at least maybe)
<JamesMunns[m]>
Okay, flipping the "read only" switch, I'll watch my email for the next few minutes if you want to request edit access, otherwise I can regenerate a new report next time we tackle this again