search

rust-embedded / bare-metal

Abstractions common to microcontrollers
Apache License 2.0
114 stars 16 forks source link

Ship a 1.0 release #22

Closed thejpster closed 4 years ago

thejpster commented 4 years ago

Part of https://github.com/rust-embedded/wg/issues/383

Blockers:

jonas-schievink commented 4 years ago

Some simple improvements to be made before 1.0:

Other blockers:

Unresolved questions:

rubberduck203 commented 4 years ago

As soon as I find the markdown version of the API checklist, I’m going to create a tracking issue for that work so items can be checked off as they’re reviewed.

rubberduck203 commented 4 years ago

Found it. Will open the tracking issue when time allows. https://github.com/rust-lang/api-guidelines/blob/master/src/checklist.md

therealprof commented 4 years ago

As agreed in the 2020-03-10 meeting we're taking off the Mutex from the 1.0 blocker list. We're aiming to have the new Mutex based on mutex-trait implemented by the arch crates instead.

luojia65 commented 4 years ago

Maybe Nr can be used as a parameter to configure vendor specific interrupt controller. However in this way Nr::nr should not always return a u8 (there could be more than 256 interrupts). It could be necessary to provide as Nr { type Id; fn nr(&self) -> Self::Id } (still working on it to adapt to Bumblebee's ECLIC controller)

jonas-schievink commented 4 years ago

IMO Nr logically belongs in architecture-specific core crates like cortex-m or cortex-m-rt.

We should check what uses it, and whether the users would see any benefit of having a traits that's shared between architectures. Maybe come up with potential use cases.

(EDIT: #32 deleted it)

thejpster commented 4 years ago

Ticked MSRV, as it's in the README.

adamgreig commented 4 years ago

Closed by #35.