Fix wrong perimap link on README
This commit is contained in:
parent
2b87e34c66
commit
3685c36e0a
@ -97,7 +97,7 @@ are only interested in one. It's easier than it looks, and doing all families at
|
|||||||
- Cleanup the register yamls (see below).
|
- Cleanup the register yamls (see below).
|
||||||
- Minimize the diff between each pair of versions. For example between `lpuart_v1.yaml` and `lpuart_v2.yaml`. If one is missing enums or descriptions, copy it from another.
|
- Minimize the diff between each pair of versions. For example between `lpuart_v1.yaml` and `lpuart_v2.yaml`. If one is missing enums or descriptions, copy it from another.
|
||||||
- Make sure the block
|
- Make sure the block
|
||||||
- Add entries to [`perimap`](https://github.com/embassy-rs/stm32-data/blob/main/stm32data/__main__.py#L84), see below.
|
- Add entries to [`perimap`](https://github.com/embassy-rs/stm32-data/blob/main/stm32-data-gen/src/chips.rs#L109), see below.
|
||||||
- Regen, check `data/chips/*.yaml` has the right `block: lpuart_vX/LPUART` fields
|
- Regen, check `data/chips/*.yaml` has the right `block: lpuart_vX/LPUART` fields
|
||||||
|
|
||||||
Please separate manual changes and changes resulting from regen in separate commits. It helps tremendously with review and rebasing/merging.
|
Please separate manual changes and changes resulting from regen in separate commits. It helps tremendously with review and rebasing/merging.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user