mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <ahmad@a3f.at>
Cc: barebox@lists.infradead.org, rcz@pengutronix.de
Subject: Re: [PATCH 0/8] drivers: add VirtIO console, block device support
Date: Mon, 22 Feb 2021 10:53:34 +0100	[thread overview]
Message-ID: <20210222095334.GJ10966@pengutronix.de> (raw)
In-Reply-To: <20210222070605.589180-1-ahmad@a3f.at>

On Mon, Feb 22, 2021 at 08:05:56AM +0100, Ahmad Fatoum wrote:
> To make it easier to exchange data with paravirtualized barebox during
> testing, import parts of the VirtIO support in Linux and U-Boot.
> 
> API basically looks like U-Boot's, but driver boilerplate (like having
> a virtio bus) is taken from Linux. Headers are the Linux ones with some
> necessary modifications on top.
> 
> Quite nifty thing is that Qemu will fix up the device tree appropriately,
> so just compile in the drivers and it works. The vexpress_defconfig
> already does this, so this just works:
> 
>   $ qemu-system-arm -m 256M -M virt -nographic                  \
>  	-kernel ./images/barebox-dt-2nd.img                     \
>   	-device virtio-rng-device                               \
>   	-drive if=none,file=/tmp/first.hdimg,format=raw,id=hd0  \
>   	-device virtio-blk-device,drive=hd0		        \
> 
> Ahmad Fatoum (8):
>   kbuild: add include/uapi to path
>   driver: Don't throw an error on probes that didn't find the device
>   drivers: add support for memory-mapped VirtIO paravirtualization
>   hw_random: add VirtIO RNG driver
>   serial: add basic VirtIO console driver
>   block: add VirtIO block device driver
>   ARM: vexpress: config: update for VirtIO support
>   Documentation: add Documentation on VirtIO for barebox

Applied, thanks

Sascha


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2021-02-22  9:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22  7:05 Ahmad Fatoum
2021-02-22  7:05 ` [PATCH 1/8] kbuild: add include/uapi to path Ahmad Fatoum
2021-02-22  7:05 ` [PATCH 2/8] driver: Don't throw an error on probes that didn't find the device Ahmad Fatoum
2021-02-22  7:05 ` [PATCH 3/8] drivers: add support for memory-mapped VirtIO paravirtualization Ahmad Fatoum
2021-02-22  7:06 ` [PATCH 4/8] hw_random: add VirtIO RNG driver Ahmad Fatoum
2021-02-22  7:06 ` [PATCH 5/8] serial: add basic VirtIO console driver Ahmad Fatoum
2021-02-22  7:06 ` [PATCH 6/8] block: add VirtIO block device driver Ahmad Fatoum
2021-02-22  7:06 ` [PATCH 7/8] ARM: vexpress: config: update for VirtIO support Ahmad Fatoum
2021-02-22  7:06 ` [PATCH 8/8] Documentation: add Documentation on VirtIO for barebox Ahmad Fatoum
2021-02-22  7:15   ` [PATCH] fixup! " Ahmad Fatoum
2021-02-22  8:39   ` [PATCH] fixup! " Ahmad Fatoum
2021-02-22  9:53 ` Sascha Hauer [this message]

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=20210222095334.GJ10966@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=ahmad@a3f.at \
    --cc=barebox@lists.infradead.org \
    --cc=rcz@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox