Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Agenda for 2019-12-10 meeting #403

Closed
japaric opened this issue Dec 3, 2019 · 11 comments · Fixed by #407
Closed

Agenda for 2019-12-10 meeting #403

japaric opened this issue Dec 3, 2019 · 11 comments · Fixed by #407
Labels

Comments

@japaric
Copy link
Member

japaric commented Dec 3, 2019

8-9 PM CET (Berlin time) on #rust-embedded:matrix.org

Public Google calendar that includes these weekly meetings

Agenda

  • The big picture of embedded-hal / re-organizing embedded-hal. cc @thejpster

  • Motivation for book monorepo proposal -- @ghost (who proposed this?)

  • Digital v3 (voting? idk) -- @Disasm (?)

  • [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.

@jamesmunns
Copy link
Member

Current CI testing is a No-Op: rust-lang/rust#67018

@thejpster
Copy link
Contributor

Some guidance on rust-embedded/cortex-m-quickstart#78 would be useful. How do we feel about IDE specific additions to quickstart? Would we take an Intelli-J IDEA project, or a Sublime Text project?

@rubberduck203
Copy link

Some context for that conversion @thejpster

Screen Shot 2019-12-06 at 6 07 54 AM

https://www.jetbrains.com/lp/devecosystem-2019/rust/

@jonas-schievink
Copy link
Contributor

That PR adds configuration for very specific MCUs, for use with a specific VSCode plugin, not all VSCode users will benefit from that.

Another agenda item: rust-embedded/cortex-m-rt#223 (regression in the cortex-m-rt release).

@rubberduck203
Copy link

@jonas-schievink I didn’t intend to imply that it would. Only providing some editor usage data to frame the conversation.

@IGBC
Copy link

IGBC commented Dec 6, 2019

Can we chuck Generic Radio Traits on the agenda?
We have a few driver crates for various radio standards, but when building a protocal ontop of those and making them driver agnostic it would be nice to have a trait for each radio standard (LoRa, Zigbee, Bluetooth, WiFi, whatever) to bind to instead.

@therealprof
Copy link
Contributor

Can we chuck Generic Radio Traits on the agenda?

You can put pretty much anything on the agenda but unless you have a proposal it's not very likely that this will result in fruitful discussion since these topics require a high level of domain specific knowledge. It would probably be better to form a group exploring the options and the way forward leading to an RFC proposing those traits and then put it on the agenda for discussion.

@IGBC
Copy link

IGBC commented Dec 6, 2019

welp. I will not claim to be experienced in the area.

@ryankurte
Copy link
Contributor

ryankurte commented Dec 10, 2019

Can we chuck Generic Radio Traits on the agenda?

@IGBC i've been working on this for a while now for ISM / LoRa stuff, not sure about how it'd work with WiFi which (afaik) it'd be unusual to interact with as a radio (rather than via some kind of socket API).

You might be interested in previous discussion in embedded-hal, some discussion on rubble, and my WIP implementation (which links out to a set of implementers). I haven't looked at extracting commonality for configuration yet, but the operation of all of em is the same.

If you'd like to talk about it more we could re-open the HAL issue as a place to chat.

@Disasm
Copy link
Member

Disasm commented Dec 10, 2019

Sorry, I will not be able to attend the meeting. As for the digital::v3, I'd rather postponed the voting until we agree on the future structure of the embedded-hal crate.

@thejpster
Copy link
Contributor

I'm afraid I've been off sick most of the last week, so I haven't written up the RFC yet.

@jamesmunns jamesmunns mentioned this issue Dec 10, 2019
@bors bors bot closed this as completed in b4731ff Dec 10, 2019
@bors bors bot closed this as completed in #407 Dec 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants