From 07b2b4d83078d0fd260d5f0812e8d5a34d02b793 Mon Sep 17 00:00:00 2001 From: Jorge Aparicio Date: Wed, 21 Aug 2019 10:17:27 +0200 Subject: doc up --- book/en/src/internals/interrupt-configuration.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'book/en/src/internals/interrupt-configuration.md') diff --git a/book/en/src/internals/interrupt-configuration.md b/book/en/src/internals/interrupt-configuration.md index b34b308..98a98e5 100644 --- a/book/en/src/internals/interrupt-configuration.md +++ b/book/en/src/internals/interrupt-configuration.md @@ -12,7 +12,7 @@ configuration is done before the `init` function runs. This example gives you an idea of the code that the RTFM framework runs: ``` rust -#[rtfm::app(device = ..)] +#[rtfm::app(device = lm3s6965)] const APP: () = { #[init] fn init(c: init::Context) { @@ -39,8 +39,7 @@ The framework generates an entry point that looks like this: unsafe fn main() -> ! { // transforms a logical priority into a hardware / NVIC priority fn logical2hw(priority: u8) -> u8 { - // this value comes from the device crate - const NVIC_PRIO_BITS: u8 = ..; + use lm3s6965::NVIC_PRIO_BITS; // the NVIC encodes priority in the higher bits of a bit // also a bigger numbers means lower priority -- cgit v1.2.3