[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
QEMU commit 0a923be2f642 broke my or1k image.
From: |
Rob Landley |
Subject: |
QEMU commit 0a923be2f642 broke my or1k image. |
Date: |
Wed, 11 Sep 2024 00:42:58 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 |
Grab this tarball, extract it, and ./run-qemu.sh. It's a simple
linux+initramfs image that boots to a shell prompt.
https://landley.net/bin/mkroot/latest/or1k.tgz
QEMU 7.0.0 ran that linux-or1k image, but newer qemu does not. I besected the
issue to qemu commit 0a923be2f642, and it's still broken in current tip of tree.
Rebuilding the image with current linux-git doesn't seem to make a difference?
Either way I get serial output with old qemu and don't with current qemu.
Rob
P.S. Reproduction sequence for the tarball available upon request, kernel config
is in the docs/ directory, userspace is just a toybox mkroot build but "not
getting kernel boot messages" happens way before userspace gets a vote.
- QEMU commit 0a923be2f642 broke my or1k image.,
Rob Landley <=