|
| 1 | +# Embedded Working Group Meeting 2023-10-03 |
| 2 | + |
| 3 | +* [Coordination Repository] |
| 4 | +* Meetings: Tuesday 8pm Europe/Berlin time |
| 5 | +* [Join the Chat] |
| 6 | +* Today's date: 2023-10-03 |
| 7 | +* [Nominated issues](https://github.com/search?q=org%3Arust-embedded+label%3Anominated+is%3Aopen&type=Issues) |
| 8 | +* [IRC logs] |
| 9 | + |
| 10 | +[Coordination Repository]: https://github.com/rust-embedded/wg |
| 11 | +[Join the Chat]: https://matrix.to/#/#rust-embedded:matrix.org |
| 12 | +[IRC logs]: https://libera.irclog.whitequark.org/rust-embedded/2023-10-03 |
| 13 | + |
| 14 | +## Attendance |
| 15 | + |
| 16 | +Write your GH username or Matrix handle here! |
| 17 | + |
| 18 | +* adamgreig |
| 19 | +* newAM |
| 20 | +* mabez |
| 21 | +* cr1901 |
| 22 | +* therealprof |
| 23 | +* dirbaio |
| 24 | +* jamesmunns |
| 25 | +* thejpster |
| 26 | +* posborne |
| 27 | + |
| 28 | +## Agenda |
| 29 | + |
| 30 | +* Announcements |
| 31 | + * @MabezDev joins the risc-v and HAL teams :tada: |
| 32 | + * embedded-io{,-async,-adaptors} 0.6 released with change to write_all |
| 33 | + * svdtools 0.3.3 released |
| 34 | + * svd2rust 0.30.1 released |
| 35 | + * rust 1.73 out Thurs |
| 36 | + * Ferrocene announcement/launch party tomorrow ([link](https://www.eventbrite.de/e/a-decade-of-rust-with-ferrous-systems-tickets-680492891557?aff=oddtdtcreator)) |
| 37 | +* Anti-spam bot still being tested, any issues? |
| 38 | +* Should mutex-trait be archived/deprecated? |
| 39 | + * https://github.com/rust-embedded/mutex-trait/issues/13 |
| 40 | + * Lots of discussion on this point. It's not clear if the current trait is serving a useful purpose and it's definitely not been widely adopted, but should we aim to fix it or just deprecate it? |
| 41 | + * Original RFC was https://github.com/rust-embedded/wg/blob/master/rfcs/0377-mutex-trait.md |
| 42 | + * The intended users are application, driver, HAL developers who want to abstract over a generic mutex to share state with interrupts/threads/etc |
| 43 | + * In practise, such an ecosystem hasn't developed, probably because the mutex interface (especially whether it requires &mut self or not) depends on the executor and what tradeoffs are desired |
| 44 | + * Additionally, the newer critical_section::Mutex is a concrete type which can have multiple backing providers per platform, so may be good enough for many use cases |
| 45 | + * We'll finish discussions on the issue |
| 46 | +* book: tooling page still needs updating |
| 47 | +* bors: ops documentation still needs updating |
| 48 | +* rustc target maintainers: |
| 49 | + * @adamgreig to open wg issue to discuss WG teams being target maintainers |
| 50 | +* volatile_register potentially unsound https://github.com/rust-embedded/cortex-m/issues/485 |
| 51 | + * No update on volatile-register PR |
| 52 | + |
| 53 | +## Last Week's Minutes |
| 54 | + |
| 55 | +* Announcements |
| 56 | + * svdtools 0.3.1 released |
| 57 | + * aarch64-cpu 9.4.0 released |
| 58 | +* We are trying out the Mjolnir bot to pre-ban spammers, please report any feedback |
| 59 | +* book: tooling page still needs updating |
| 60 | +* bors: ops documentation still needs updating |
| 61 | +* rustc target maintainers: https://github.com/rust-lang/rust/pull/116004 |
| 62 | + * AG to open wg issue to discuss WG teams being target maintainers |
| 63 | +* volatile_register potentially unsound https://github.com/rust-embedded/cortex-m/issues/485 |
0 commit comments