From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Adding VIRTIO to the multi_v7_defconfig
Date: Sun, 29 Nov 2015 23:31:47 +0100 [thread overview]
Message-ID: <2788112.C4O6ljO5dG@wuerfel> (raw)
In-Reply-To: <CAPokK=rMi0OuqwePNkWMEi+5f_GZzw-j8fkN__2docvzwGV5+A@mail.gmail.com>
On Sunday 29 November 2015 14:18:24 Peter Crosthwaite wrote:
>
> I started a small project to test as many QEMU emulated ARM boards
> using the multi_v7 defconfig:
>
> https://lists.gnu.org/archive/html/qemu-devel/2015-10/msg00755.html
>
> One thing that came up was we cannot use the virt board as it relies
> on virtio hotplug and drivers to get block and network support. The
> defconfig is missing the drivers. Should we add the VIRTIO drivers to
> the defconfig to bring this into play?
Yes, please send a patch, this is definitely useful. We normally ask
everyone to use loadable modules for newly enabled device drivers
in multi_v7_defconfig, but we might actually use built-in drivers
here if that would otherwise be the only module needed for booting.
Arnd
next prev parent reply other threads:[~2015-11-29 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 22:18 Adding VIRTIO to the multi_v7_defconfig Peter Crosthwaite
2015-11-29 22:31 ` Arnd Bergmann [this message]
2015-11-29 22:56 ` Peter Crosthwaite
2015-11-29 23:15 ` Arnd Bergmann
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=2788112.C4O6ljO5dG@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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