diff options
| author |  Henrik Tjäder <henrik@tjaders.com>
| 2023-11-01 20:27:29 +0100 |
|---|---|---|
| committer |  Emil Fresk <emil.fresk@gmail.com>
| 2023-11-01 20:20:30 +0000 |
| commit | 9f0ab21a340e3ab6719634aa0461957fbacdbd8e (patch) | |
| tree | da92437b308be35ad13ec05b7c57e80008a5e8aa | |
| parent | 3c9a8f290d0615dd88c4f9a6e7660bdc7ce6fc9f (diff) | |
| download | rtic-9f0ab21a340e3ab6719634aa0461957fbacdbd8e.tar.gz rtic-9f0ab21a340e3ab6719634aa0461957fbacdbd8e.tar.zst rtic-9f0ab21a340e3ab6719634aa0461957fbacdbd8e.zip | |
Book: timber-lang from the dead
Link to RTFM and RTIC publication search.
| -rw-r--r-- | book/en/src/preface.md | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/book/en/src/preface.md b/book/en/src/preface.md index 1061b2dc..7c015ee1 100644 --- a/book/en/src/preface.md +++ b/book/en/src/preface.md @@ -31,12 +31,14 @@ is no software kernel and that it relies on external HALs. This section gives a background to the RTIC model. Feel free to skip to section [RTIC the model](preface.md#rtic-the-model) for a TL;DR. -The RTIC framework takes the outset from real-time systems research at Luleå University of Technology (LTU) Sweden. RTIC is inspired by the concurrency model of the [Timber] language, the [RTFM-SRP] based scheduler, the [RTFM-core] language and [Abstract Timer] implementation. For a full list of related research see [TODO]. +The RTIC framework takes the outset from real-time systems research at Luleå University of Technology (LTU) Sweden. RTIC is inspired by the concurrency model of the [Timber] language, the [RTFM-SRP] based scheduler, the [RTFM-core] language and [Abstract Timer] implementation. For a full list of related research see [RTFM][rtfm_publications] and [RTIC][rtic_publications] publications. -[Timber]: https://timber-lang.org/ +[Timber]: https://web.archive.org/web/20230325133224/http://timber-lang.org/ [RTFM-SRP]: https://www.diva-portal.org/smash/get/diva2:1005680/FULLTEXT01.pdf [RTFM-core]: https://ltu.diva-portal.org/smash/get/diva2:1013248/FULLTEXT01.pdf [Abstract Timer]: https://ltu.diva-portal.org/smash/get/diva2:1013030/FULLTEXT01.pdf +[rtfm_publications]: http://ltu.diva-portal.org/smash/resultList.jsf?query=RTFM&language=en&searchType=SIMPLE&noOfRows=50&sortOrder=author_sort_asc&sortOrder2=title_sort_asc&onlyFullText=false&sf=all&aq=%5B%5B%5D%5D&aqe=%5B%5D&aq2=%5B%5B%5D%5D&af=%5B%5D +[rtic_publications]: http://ltu.diva-portal.org/smash/resultList.jsf?query=RTIC&language=en&searchType=SIMPLE&noOfRows=50&sortOrder=author_sort_asc&sortOrder2=title_sort_asc&onlyFullText=false&sf=all&aq=%5B%5B%5D%5D&aqe=%5B%5D&aq2=%5B%5B%5D%5D&af=%5B%5D ## Stack Resource Policy based Scheduling @@ -149,7 +151,7 @@ The answer is - improved ergonomics! A recurring use case is to have task perfor Rust `async`/`await` support is still incomplete and/or under development (e.g., there are no stable way to express `async` closures, precluding use in iterator patterns). Nevertheless, Rust `async`/`await` is production ready and covers most common use cases. -An important property is that futures are composable, thus you can await either, all, or any combination of possible futures (allowing e.g., timeouts and/or asynchronous errors to be promptly handled). For more details and examples see Section [todo]. +An important property is that futures are composable, thus you can await either, all, or any combination of possible futures (allowing e.g., timeouts and/or asynchronous errors to be promptly handled). ## RTIC the model |