aboutsummaryrefslogtreecommitdiff
path: root/asm/lib.rs
diff options
context:
space:
mode:
authorGravatar bors[bot] <26634292+bors[bot]@users.noreply.github.com> 2020-09-21 23:55:43 +0000
committerGravatar GitHub <noreply@github.com> 2020-09-21 23:55:43 +0000
commit43b9383cbedc5b0fb0b2df51df0e7af742fb7b61 (patch)
tree1bdb110a4d9d2192c8b546c23d7e10dadb27b4b5 /asm/lib.rs
parentaa77c89a5ff0f81f5bbd52799fe8caf12fb493d6 (diff)
parentb7541ddb57b268ebec9591730898c97bd98d36d6 (diff)
downloadcortex-m-43b9383cbedc5b0fb0b2df51df0e7af742fb7b61.tar.gz
cortex-m-43b9383cbedc5b0fb0b2df51df0e7af742fb7b61.tar.zst
cortex-m-43b9383cbedc5b0fb0b2df51df0e7af742fb7b61.zip
Merge #266
266: Implement InterruptNumber for bare_metal::Nr r=therealprof a=adamgreig This PR aims to help backwards compatibility by implementing the new `InterruptNumber` trait (coming in cortex-m 0.7) for the old `bare_metal::Nr` trait. With this included in cortex-m 0.7, existing PACs generated from the current svd2rust (0.17) will work with cortex-m 0.7, and new PACs generated from a to-be-released svd2rust which uses `InterruptNumber directly will also work. We can then remove this implementation in cortex-m 0.8 and upgrade cortex-m to depend on bare-metal 1.0 (or not depend on it at all) at that time. With this PR in place, the upgrade path looks like: * We release cortex-m 0.7, which users can upgrade to without needing a new PAC * We release svd2rust 0.18, which will generate new PACs * PACs update, now requiring cortex-m 0.7 * Users can update their PAC so long as they've already upgraded to cortex-m 0.7 * For cortex-m 0.8, we drop this impl and move off bare-metal 0.2, and a new PAC is required to use 0.8 onwards Co-authored-by: Adam Greig <adam@adamgreig.com>
Diffstat (limited to 'asm/lib.rs')
0 files changed, 0 insertions, 0 deletions