Skip to content

Conversation

@stephanosio
Copy link
Member

At some point, the QEMU recipe was changed from using the Zephyr QEMU fork (GitHub zephyrproject-rtos/qemu) to the upstream tarball with local patches, which made it quite difficult and error-prone to submit, review and manage patches.

This commit reverts the QEMU recipe to use the Zephyr QEMU fork, tracking the zephyr-qemu-v10.0.2 branch with all the existing patches applied.

All future patches to QEMU must be submitted to the zephyr-qemu-v10.0.2 branch of the Zephyr QEMU fork.

At some point, the QEMU recipe was changed from using the Zephyr QEMU
fork (GitHub zephyrproject-rtos/qemu) to the upstream tarball with local
patches, which made it quite difficult and error-prone to submit, review
and manage patches.

This commit reverts the QEMU recipe to use the Zephyr QEMU fork,
tracking the `zephyr-qemu-v10.0.2` branch with all the existing patches
applied.

All future patches to QEMU must be submitted to the
`zephyr-qemu-v10.0.2` branch of the Zephyr QEMU fork.

Signed-off-by: Stephanos Ioannidis <[email protected]>
@keith-packard
Copy link
Contributor

I like this plan; so much easier than adding yet-another-patch.

Enable network access during the `do_configure` step because QEMU build
system may fetch additional submodules, such as `keycodemapdb`, in it.

Signed-off-by: Stephanos Ioannidis <[email protected]>
@stephanosio stephanosio marked this pull request as ready for review July 7, 2025 11:46
@stephanosio stephanosio added area: QEMU Issues related to QEMU area: Host Tools Issues related to Host Tools labels Jul 7, 2025
@stephanosio stephanosio requested a review from nashif July 7, 2025 11:46
@stephanosio stephanosio merged commit 451e4e2 into zephyrproject-rtos:main Jul 8, 2025
45 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: Host Tools Issues related to Host Tools area: QEMU Issues related to QEMU

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants