Re: or1k -M virt -hda and net.

[Rob Landley <rob@landley.net>]

On 11/24/24 00:50, Stafford Horne wrote:
>> Speaking of which, is there a way to get or1k to exit the emulator? I told
>> the kernel to reboot but it says "reboot failed, system halted" and hangs
>> instead of exiting qemu. (My testroot runs qemu under "timeout -i 10" to
>> kill it after 10 seconds of inactivity, I.E. nothing written to stdout, but
>> it still counts as a failure on one of the criteria.)
> 
> With the or1k-sim board it is not possible.  Traditionally on or1k we use
> special NOP instructions to reboot simulators i.e. 'l.nop 1'.  The QEMU team was
> not happy to support this mechanism.
> 
>    https://lore.kernel.org/openrisc/fb69c137317a365dcb549dfef1ecd2fbff48e92c.1492384862.git.shorne@gmail.com/T/#mef76d30d294aed84548b1e0d3e23aae499deaeec
> 
> As an alertnative we can use the 'virt' board which supports shutdown and
> restart via the generic syscon drivers.
> 
>      $ grep -C1 SYSCON arch/openrisc/configs/virt_defconfig
>      CONFIG_POWER_RESET=y
>      CONFIG_POWER_RESET_SYSCON=y
>      CONFIG_POWER_RESET_SYSCON_POWEROFF=y
>      CONFIG_SYSCON_REBOOT_MODE=y
>      # CONFIG_HWMON is not set

I built the 6.12 ARCH=openrisc virt_defconfig and got it to boot my 
initramfs, but while it does shut down, it hasn't got network or block 
device support.

The kernel config looks like it should have virt block device support, 
but nether -hda README nor "-drive file=README,format=raw,id=hd0 -device 
virtio-blk-device,drive=hd0" seem to be wiring it up in qemu where the 
kernel can find it?

Haven't tried to get fancy with the network yet. The buildroot config is 
still or1ksim...

Rob