Conversation
closes #183
Closed
korken89
approved these changes
Sep 1, 2018
korken89
left a comment
Contributor
There was a problem hiding this comment.
Looks good! I'm looking forward to see what happens here!
Emilgardis
approved these changes
Sep 1, 2018
hannobraun
approved these changes
Sep 3, 2018
adamgreig
approved these changes
Sep 3, 2018
nastevens
approved these changes
Sep 3, 2018
ryankurte
approved these changes
Sep 4, 2018
posborne
approved these changes
Sep 4, 2018
thejpster
approved these changes
Sep 4, 2018
andre-richter
approved these changes
Sep 4, 2018
Member
Author
|
🔔 This has been approved. bors r+ Welcome to the WG, @paoloteti! |
Contributor
|
👎 Rejected by label |
Member
Author
|
sudo |
bors Bot
added a commit
that referenced
this pull request
Sep 6, 2018
199: [RFC] initial Cortex-R team r=japaric a=japaric This is a proposal for creating a Cortex-R team. @paoloteti and I will be the initial members. I know pretty much nothing about the Cortex-R but will be working with them starting November; @paoloteti is the real expert here. The following work has been planed for this team (some of it has been done already) - [x] Add more built-in targets to cover existing devices. In rust-lang/rust#53679 we went from 1 target to 4. We now have good coverage of Cortex R4(F) and R5(F) cores. - [x] Move to LLD to remove the dependency on a external linker. Done in rust-lang/rust#53679. - [x] Produce `rust-std` components to not depend on tools like Xargo, which require nightly. Also done in rust-lang/rust#53679. - [ ] Create a `cortex-r` crate (\*) akin to the `cortex-m` crate that provides a safe API to emit arch-specific instructions and to manipulate system registers. - [ ] Create a `cortex-r-rt` crate (\*) akin to the `cortex-m-rt` crate that helps building a minimal `no_std` binary. - [ ] See if we can generate register APIs from the XML files that vendors like TI ship with their IDEs. (\*) Initial work in this area: https://github.com/paoloteti/ti-hercules-bsp @rust-embedded/all please vote on this proposal using [GitHub reviews][approve]. This proposal needs at least 11 approvals to land (/all has 21 members atm). [approve]: https://help.github.com/articles/approving-a-pull-request-with-required-reviews/ Co-authored-by: Jorge Aparicio <jorge@japaric.io>
Contributor
Build succeeded |
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a proposal for creating a Cortex-R team.
@paoloteti and I will be the initial members. I know pretty much nothing about
the Cortex-R but will be working with them starting November; @paoloteti is the
real expert here.
The following work has been planed for this team (some of it has been done
already)
Add more built-in targets to cover existing devices. In
add more Cortex-R targets rust-lang/rust#53679 we went from 1 target to 4. We now have good coverage of
Cortex R4(F) and R5(F) cores.
Move to LLD to remove the dependency on a external linker. Done in
add more Cortex-R targets rust-lang/rust#53679.
Produce
rust-stdcomponents to not depend on tools like Xargo, whichrequire nightly. Also done in add more Cortex-R targets rust-lang/rust#53679.
Create a
cortex-rcrate (*) akin to thecortex-mcrate that providesa safe API to emit arch-specific instructions and to manipulate system
registers.
Create a
cortex-r-rtcrate (*) akin to thecortex-m-rtcrate thathelps building a minimal
no_stdbinary.See if we can generate register APIs from the XML files that vendors like
TI ship with their IDEs.
(*) Initial work in this area: https://github.com/paoloteti/ti-hercules-bsp
@rust-embedded/all please vote on this proposal using GitHub reviews.
This proposal needs at least 11 approvals to land (/all has 21 members atm).