diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2023-04-11 06:17:00 +0000 |
|---|---|---|
| committer | GitHub <[email protected]> | 2023-04-11 06:17:00 +0000 |
| commit | 636a3d05c2ac129e2fa85cf6e7fb5afff2d8126b (patch) | |
| tree | 91c7bec35c40932932569c889654986a52d30ee7 /rust-toolchain.toml | |
| parent | 1f25d2ba8335300368b32f9ceedf163376dfdb6f (diff) | |
| parent | d3ce64254aecb24feded2408119855daf7380e80 (diff) | |
Merge #1331
1331: Let bootloader partition be u32 r=rmja a=rmja
This is probably controversial but hear me out:)
The idea about changing from usize to u32 is to enable support for 16 bit mcu's with large flash, e.g. MSP430F5529. Its usize is only 16 bit, but its flash is larger than 64k. Hence, to address its entire flash, it needs the flash address space to be u32.
Missing from the PR is `update_len` in the verification methods. There is currently [a different PR](https://github.com/embassy-rs/embassy/pull/1323) that contains changes in those methods, and I will align depending on the merge order of the two.
The general distinction between u32 and usize is:
* If it is a size or address that only ever lives in flash, then it is u32.
* If the offset or size is ever representable in memory, then usize.
Co-authored-by: Rasmus Melchior Jacobsen <[email protected]>
Diffstat (limited to 'rust-toolchain.toml')
0 files changed, 0 insertions, 0 deletions