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

Book: Section 3B: Portability #119

Closed
jamesmunns opened this issue Jul 10, 2018 · 2 comments
Closed

Book: Section 3B: Portability #119

jamesmunns opened this issue Jul 10, 2018 · 2 comments
Assignees
Milestone

Comments

@jamesmunns
Copy link
Member

How can use of Rust improve portability between Projects, Targets, or even Operating Systems?

@TotalKrill
Copy link

I would really like to see some more graphical representation on how the different crates are thought to interact with the software, also some recommended guidelines for naming the crates so they are more easily found on crates.io. Example:
device crates should end with *-device, and board crates should end with *-board, driver crates should end with *-driver.

A graphical representation that basically says:

  • Device crate = MCU registers, peripherals, settings, timers etc
  • Board crate = Where SPI, UART etc are hooked up, what oscillators are running. ( are drivers a part of the board crate?)

Similar to this picture:
image

@japaric
Copy link
Member

japaric commented Aug 10, 2018

This issue was moved to rust-embedded/book#6

@japaric japaric closed this as completed Aug 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants