Johnathan Van Why
Johnathan Van Why
[Rendered](https://github.com/tock/tock/blob/appid/doc/reference/trd-appid.md)
As far as I am aware, any mechanism for deriving non-colliding short IDs for every process on a Tock system requires access to writeable nonvolatile storage. Therefore any design has...
@cfrantz, @kupiakos, @lschuermann: I think you all would be interested in this RFC.
Sorry about the title change: I composed the PR description in a second document, and forgot to move the title over from that document when I opened this PR.
I've identified a soundness issue with this design. In my proposed struct design (`pub` added where necessary): ```rust #[repr(C)] struct Registers { pub rw_single: rw_single, pub rw_array: rw_array, // access...
> Can you point us to the exact crate that you are using and the crate (library) that it depends on from this repository? I checked `cortex-a`'s `Cargo.toml`, and it...
I edited the issue title to mention `tock-registers`, so that Tock developers understand at a glance which library this issue refers to. The overarching issue for making Tock build on...
PR opened: https://github.com/tock/tock/pull/2983 The specific unstable feature in use is likely to be stabilized soon, and the PR I opened has some drawbacks, so it's possible that we will not...
Making `tock-registers` work on stable Rust will not solve your issue on its own, because `cortex-a` depends on unstable Rust as well: https://github.com/rust-embedded/cortex-a/blob/fd6688419ac9884abd1d79a18b3ff64b4776e1f4/src/lib.rs#L82. It'll just move the compilation error from...
The consensus at #2983 was to wait for `feature(const_fn_trait_bound)` to be stabilized before moving `tock-registers` over to stable Rust. It sounds like moving to a nightly toolchain is a reasonable...