@pmaydell: Thanks for the quick response! For whatever it's worth, I think
that there's definitely a bunch of interest in the M-profile work: in the
embedded Rust space (for example) Cortex-M is very much the reference
platform. Viz. the Embedded Rust Book:
Having a QEMU that had first-class support for a widely-available development
platform (e.g., the STM32F Discovery) would be of great interest to this
community -- and I'm sure many others!
To prevent filing of issues that are already known: is there a list of
known issues with the M-profile with QEMU?
@pmaydell: Thanks for the quick response! For whatever it's worth, I think
that there's definitely a bunch of interest in the M-profile work: in the
embedded Rust space (for example) Cortex-M is very much the reference
platform. Viz. the Embedded Rust Book:
https:/ /rust-embedded. github. io/book/
For this, we have been using an xPack QEMU fork:
https:/ /github. com/xpack- dev-tools/ qemu-arm- xpack
Having a QEMU that had first-class support for a widely-available development
platform (e.g., the STM32F Discovery) would be of great interest to this
community -- and I'm sure many others!
To prevent filing of issues that are already known: is there a list of
known issues with the M-profile with QEMU?