Adam Greig

I haven't actually tried. We'd just need to set ``` [package.metadata.docs.rs] all-features = true ``` in the Cargo.toml of one crate and see what happens. I'm planning on a 0.2.1...

I added that to stm321, stm32f2, stm32f3 crates before releasing 0.2.1. However, the cortex-m dependency fails to build docs at the moment, so that might trip up docs.rs irregardless.

Mixed results: [stm32f1](https://docs.rs/stm32f1/0.2.1/stm32f1/) worked, [stm32f2](https://docs.rs/stm32f2/0.2.1/stm32f2/) did too, but stm32f3 [got this error log](https://docs.rs/crate/stm32f3/0.2.1/builds/107432) indicating the process was SIGKILL'd. I'm guessing the first two just about fit but the f3 didn't,...

That's not a bad idea... perhaps pick one or two representative devices per family which are likely to be popular or similar to everything else.

I've updated crates to all build at least one or two devices. We'll see if it works and if any fail I might need to reduce the number of devices...

We still don't build _all_ devices in the docs -- each family crate has a list of which devices to include which is meant to be a vaguely representative subset,...

They have different binary names (`svd` for Python, `svdtools` for Rust), the `SVDTOOLS` environment variable tells Make which one to use but defaults to Rust now. Are you able to...

Ah, that explains it! For correct input they should both generate the same output, but the Rust version is stricter about validity checking (or rather: has new validity checks that...

The size of the field in the register doesn't change the access width, but instead it depends on the size of the register itself. I'm not sure which PAC you're...

Yea, it looks like at the moment the register is set to 32 bits wide in the SVD. It should be updated to 16 bits wide, and additionally you could...