Embedded WG meeting, February 26

[Disasm]

8-9 PM CET (Berlin time) on #rust-embedded on irc.mozilla.org

Public Google calendar that includes these weekly meetings

Agenda.

• Reminders / announcements

• @vertexclique RTOS team - Embedded WG meeting, February 19 #318 (comment)

• @mathk *-hal deduplication - Embedded WG meeting, February 19 #318 (comment), support for different power modes - Embedded WG meeting, February 19 #318 (comment)

• @Disasm Proper handling of write-only SPI channels (Add non-blocking spi::Send trait embedded-hal#121), semantics of SPI read() function (Document implicit assumption in non-blocking spi trait embedded-hal#120)

• @flip111 svd2rust-like tool for external device specification - Survey: Crates / libraries / tools you need / want #22 (comment)

• Issues nominated for discussion, if any

• [your topic goes here]

This meeting is open for anyone to attend. If you'd like to bring up any issue / topic related to embedded Rust leave a comment in this issue so we can add it to the agenda.

[flip111]

@Disasm can you add this too ? #22 (comment)

[japaric]

@vertexclique

RTOS team

We discussed this during the last meeting and the consensus was that we do not
want to create an RTOS team right now. The reason is that we want to avoid
maintaining crates tied to any particular vendor in the org because that could
snowball into us maintaining crates for all the RTOSes out there -- this is also
the reason why we don't maintain any HAL implementation in the org.

We are open to maintaining things like traits that abstract over different
RTOSes but before those exist different RTOS bindings / implementations must
exist first. Thus we think that developing and maintaining RTOSes / RTOS
bindings should be left up to the community. However, we'd be glad to raise
awareness about on-going community efforts in our newsletters, (not-yet) awesome
lists, etc.

[flip111]

@japaric perhaps it's possible to create some hardware agnostic parts of the RTOS. Maybe a scheduler? Or just having an inventory of which parts would be needed would already be useful. Maybe some people would like to think about this. Not as a team capacity but just investigation.

[Disasm]

This meeting happened! The minutes and logs can be found in PR #325.

The agenda for the next meeting can be found in #326