Cortex-R Team: Decide on 2019 objectives

[adamgreig]

As part of our 2019 planning, we want to figure out what each team wants to work on this year, including new ideas, items from the 2019 wishlist (#256), and any leftover items from this year.

Let's use this issue to come up with a list of possible items and then prioritise them.

[japaric]

cc @rust-embedded/cortex-r @kenkeiter

From the wishlist:

• Add support for Cortex-R52

Backlog:

• cortex-r, cortex-r-rt and other crates to bring Cortex-R development up to par with Cortex-M development. There's https://github.com/paoloteti/cortex-r-rt and https://github.com/paoloteti/ti-hercules-bsp; I also have my own (currently not public) Cortex-R stack. We should sit down and put the common pieces under the rust-embedded org. (The R5 device I'm using has a totally different memory layout and interrupt handling than TI's Cortex-R devices; also I use it in split mode rather than in lockstep mode so I think this will be interesting).

Other ideas:

• We should piggy back on the effort for stabilizing Cortex-M intrinsics in core::arch::arm to also stabilize the Cortex-R intrinsics we need.

[paoloteti]

At the moment (except I'm missing something) you cannot buy Cortex-R52 devices easly. Are usually available for selected partners or "approved customers" and under an NDA. (see NXP GreenBox for example).

So I prefer to wait for obvious reasons.

PS: Cortex-R52 support also the DCLS mode up to 8 cores, rather then Split/Lock mode

[japaric]

We discussed in yesterday's meeting (#290) that teams should start deciding on
how to prioritize their work items for this year. We'll let each team decide how
to do the item prioritization but we recommend having a real-time / synchronous
meeting (IRC or video meeting) to discuss all the potential goals.

If appropriate, you can reserve a time slot during the weekly meetings to have
this synchronous discussion. Just let us know in advance in one of the meeting
issues (e.g. #291).

Finally, if any of your goals for this year requires changes in any of the
rust-lang/* repositories and you haven't mentioned them in #256 or #269 then
please report them in #269 ASAP. We'll discuss prioritization of rust-lang
request during the next meeting (2019-01-15).

cc @rust-embedded/cortex-r

[eldruin]

2019 finished. Maybe we can create a follow up issue for 2020. Nominating for next week's meeting.

[adamgreig]

Closing as we're now well into 2020; if anything outstanding from this list is still relevant please add it to the not-yet-awesome embedded rust list, or create a new issue to track it.