mirror of
https://github.com/rtic-rs/rtic.git
synced 2024-11-23 20:22:51 +01:00
Fixes for repo rename to rtic
This commit is contained in:
parent
4a3f7ea123
commit
f03aede2f5
4 changed files with 6 additions and 6 deletions
6
.github/workflows/matrix-bot.yml
vendored
6
.github/workflows/matrix-bot.yml
vendored
|
@ -5,7 +5,7 @@ on:
|
||||||
|
|
||||||
jobs:
|
jobs:
|
||||||
new-pr:
|
new-pr:
|
||||||
if: github.event.action == 'opened' && github.repository == 'rtic-rs/cortex-m-rtic'
|
if: github.event.action == 'opened' && github.repository == 'rtic-rs/rtic'
|
||||||
runs-on: ubuntu-latest
|
runs-on: ubuntu-latest
|
||||||
continue-on-error: true
|
continue-on-error: true
|
||||||
steps:
|
steps:
|
||||||
|
@ -18,7 +18,7 @@ jobs:
|
||||||
server: "matrix.org"
|
server: "matrix.org"
|
||||||
|
|
||||||
merged-pr:
|
merged-pr:
|
||||||
if: github.event.action == 'closed' && github.event.pull_request.merged == true && github.repository == 'rtic-rs/cortex-m-rtic'
|
if: github.event.action == 'closed' && github.event.pull_request.merged == true && github.repository == 'rtic-rs/rtic'
|
||||||
runs-on: ubuntu-latest
|
runs-on: ubuntu-latest
|
||||||
continue-on-error: true
|
continue-on-error: true
|
||||||
steps:
|
steps:
|
||||||
|
@ -31,7 +31,7 @@ jobs:
|
||||||
server: "matrix.org"
|
server: "matrix.org"
|
||||||
|
|
||||||
abandoned-pr:
|
abandoned-pr:
|
||||||
if: github.event.action == 'closed' && github.event.pull_request.merged == false && github.repository == 'rtic-rs/cortex-m-rtic'
|
if: github.event.action == 'closed' && github.event.pull_request.merged == false && github.repository == 'rtic-rs/rtic'
|
||||||
runs-on: ubuntu-latest
|
runs-on: ubuntu-latest
|
||||||
continue-on-error: true
|
continue-on-error: true
|
||||||
steps:
|
steps:
|
||||||
|
|
|
@ -17,6 +17,6 @@ create-missing = false
|
||||||
command = "mdbook-mermaid"
|
command = "mdbook-mermaid"
|
||||||
|
|
||||||
[output.html]
|
[output.html]
|
||||||
git-repository-url = "https://github.com/rtic-rs/cortex-m-rtic"
|
git-repository-url = "https://github.com/rtic-rs/rtic"
|
||||||
git-repository-icon = "fa-github"
|
git-repository-icon = "fa-github"
|
||||||
additional-js = ["mermaid.min.js", "mermaid-init.js"]
|
additional-js = ["mermaid.min.js", "mermaid-init.js"]
|
||||||
|
|
|
@ -10,7 +10,7 @@ All tasks bound to an explicit interrupt are called *hardware tasks* since they
|
||||||
|
|
||||||
Specifying a non-existing interrupt name will cause a compilation error. The interrupt names are commonly defined by [PAC or HAL][pacorhal] crates.
|
Specifying a non-existing interrupt name will cause a compilation error. The interrupt names are commonly defined by [PAC or HAL][pacorhal] crates.
|
||||||
|
|
||||||
Any available interrupt vector should work. Specific devices may bind specific interrupt priorities to specific interrupt vectors outside user code control. See for example the [nRF “softdevice”](https://github.com/rtic-rs/cortex-m-rtic/issues/434).
|
Any available interrupt vector should work. Specific devices may bind specific interrupt priorities to specific interrupt vectors outside user code control. See for example the [nRF “softdevice”](https://github.com/rtic-rs/rtic/issues/434).
|
||||||
|
|
||||||
Beware of using interrupt vectors that are used internally by hardware features; RTIC is unaware of such hardware specific details.
|
Beware of using interrupt vectors that are used internally by hardware features; RTIC is unaware of such hardware specific details.
|
||||||
|
|
||||||
|
|
|
@ -7,7 +7,7 @@ ARMv8-M-base architectures, which forces RTIC to use source masking instead. For
|
||||||
of lock and a detailed commentary of pros and cons, see the implementation of
|
of lock and a detailed commentary of pros and cons, see the implementation of
|
||||||
[lock in src/export.rs][src_export].
|
[lock in src/export.rs][src_export].
|
||||||
|
|
||||||
[src_export]: https://github.com/rtic-rs/cortex-m-rtic/blob/master/src/export.rs
|
[src_export]: https://github.com/rtic-rs/rtic/blob/master/src/export.rs
|
||||||
|
|
||||||
These differences influence how critical sections are realized, but functionality should be the same
|
These differences influence how critical sections are realized, but functionality should be the same
|
||||||
except that ARMv6-M/ARMv8-M-base cannot have tasks with shared resources bound to exception
|
except that ARMv6-M/ARMv8-M-base cannot have tasks with shared resources bound to exception
|
||||||
|
|
Loading…
Reference in a new issue