From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Peter Crosthwaite <crosthwaitepeter@gmail.com>,
        Guenter Roeck <linux@roeck-us.net>, linux-kernel@vger.kernel.org,
        Peter Maydell <peter.maydell@linaro.org>
Subject: Re: Adding VIRTIO to the multi_v7_defconfig
Date: Sun, 29 Nov 2015 23:31:47 +0100
Message-ID: <2788112.C4O6ljO5dG@wuerfel>
User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <CAPokK=rMi0OuqwePNkWMEi+5f_GZzw-j8fkN__2docvzwGV5+A@mail.gmail.com>
References: <CAPokK=rMi0OuqwePNkWMEi+5f_GZzw-j8fkN__2docvzwGV5+A@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1017
Lines: 23

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/