All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 1/1] riscv: allow building w/o DHCP, SCSI, VIRTIO
Date: Sun, 3 Jul 2022 14:09:41 +0200	[thread overview]
Message-ID: <5df27902-9009-afb9-68d3-186fdb4e4067@canonical.com> (raw)
In-Reply-To: <20220703112837.98207-1-heinrich.schuchardt@canonical.com>



On 7/3/22 13:28, Heinrich Schuchardt wrote:
> Consider which boot devices are enabled in the definition of the
> BOOT_TARGET_DEVICES() macro.
> 
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>

Hello Bin,

With the patch I can run U-Boot

qemu-riscv_smode_defconfig
CONFIG_MTD_NOR_FLASH=n
CONFIG_CMD_NET=n

with QEMU 7.0 using KVM using command

qemu-system-riscv64
         -M virt -accel kvm -m 2G -smp 2
         -nographic
         -kernel u-boot
         -device virtio-net-device,netdev=eth0
         -netdev user,id=eth0,hostfwd=tcp::8022-:22
         -drive file=riscv64.img,format=raw,if=none,id=NVME1
         -device nvme,drive=NVME1,serial=nvme-1

and boot Linux from it.

But whenever virtio is accessed by U-Boot QEMU crashes without output.

E.g. after 'virtio scan' even CTRL+A,C is ignored.

Did you have more success? Any clue how to debug this?

Best regards

Heinrich

  reply	other threads:[~2022-07-03 12:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-03 11:28 [PATCH 1/1] riscv: allow building w/o DHCP, SCSI, VIRTIO Heinrich Schuchardt
2022-07-03 12:09 ` Heinrich Schuchardt [this message]
2022-07-04  9:55   ` Bin Meng
2022-07-04 11:02     ` Heinrich Schuchardt
2022-07-04  9:50 ` Bin Meng
2022-07-04 10:07   ` Heinrich Schuchardt
2022-07-04 10:16     ` Bin Meng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5df27902-9009-afb9-68d3-186fdb4e4067@canonical.com \
    --to=heinrich.schuchardt@canonical.com \
    --cc=bmeng.cn@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.