3
3
All notable changes to this project will be documented in this file.
4
4
This project adheres to [ Semantic Versioning] ( http://semver.org/ ) .
5
5
6
- For each category, * Added * , * Changed * , * Fixed * add new entries at the top!
6
+ For each category, _ Added _ , _ Changed _ , _ Fixed _ add new entries at the top!
7
7
8
8
## [ Unreleased]
9
9
10
+ ### Fixed
11
+
12
+ - Fixed ` #[cfg] ` tags on hardware and software tasks.
13
+
10
14
## [ v2.1.1] - 2024-03-13
11
15
12
16
### Fixed
@@ -237,6 +241,7 @@ For each category, *Added*, *Changed*, *Fixed* add new entries at the top!
237
241
### Added
238
242
239
243
- Allow annotating resources to activate special resource locking behaviour.
244
+
240
245
- ` #[lock_free] ` , there might be several tasks with the same priority accessing
241
246
the resource without critical section.
242
247
- ` #[task_local] ` , there must be only one task, similar to a task local
@@ -254,7 +259,7 @@ For each category, *Added*, *Changed*, *Fixed* add new entries at the top!
254
259
255
260
[ PR 399 ] : https://github.com/rtic-rs/cortex-m-rtic/pull/399
256
261
257
- - [ breaking-change] [ PR 390] Rework whole spawn/schedule, support ` foo::spawn( ... ) ` ,
262
+ - [ breaking-change] [ PR 390] Rework whole spawn/schedule, support ` foo::spawn( ... ) ` ,
258
263
` foo::schedule( ... ) ` .
259
264
260
265
[ PR 390 ] : https://github.com/rtic-rs/cortex-m-rtic/pull/390
@@ -284,7 +289,7 @@ For each category, *Added*, *Changed*, *Fixed* add new entries at the top!
284
289
285
290
- Added migration guide from ` cortex-m-rtfm ` to ` cortex-m-rtic `
286
291
- No code changes, only a version compatibility release with ` cortex-m-rtfm ` to ease the transition
287
- for users.
292
+ for users.
288
293
289
294
## [ v0.5.2] - 2020-06-11
290
295
@@ -398,7 +403,7 @@ for users.
398
403
399
404
[ RFC 128 ] : https://github.com/rtic-rs/cortex-m-rtic/issues/128
400
405
401
- ``` rust
406
+ ``` rust
402
407
// on v0.4.1 you had to write
403
408
#[interrupt]
404
409
fn USART0 () { .. }
@@ -443,7 +448,7 @@ fn on_new_frame() { .. }
443
448
documentation page
444
449
445
450
- The initialization function can now be written as `fn init() ->
446
- init::LateResources` when late resources are used. This is preferred over the
451
+ init::LateResources` when late resources are used. This is preferred over the
447
452
old ` fn init() ` form. See the section on late resources (resources chapter) in
448
453
the book for more details.
449
454
0 commit comments