Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1279464 > unrolled thread
| Started by | Peter Crosthwaite <crosthwaitepeter@gmail.com> |
|---|---|
| First post | 2015-11-29 23:20 +0100 |
| Last post | 2015-11-30 00:20 +0100 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.kernel
Adding VIRTIO to the multi_v7_defconfig Peter Crosthwaite <crosthwaitepeter@gmail.com> - 2015-11-29 23:20 +0100
Re: Adding VIRTIO to the multi_v7_defconfig Arnd Bergmann <arnd@arndb.de> - 2015-11-29 23:40 +0100
Re: Adding VIRTIO to the multi_v7_defconfig Peter Crosthwaite <crosthwaitepeter@gmail.com> - 2015-11-30 00:00 +0100
Re: Adding VIRTIO to the multi_v7_defconfig Arnd Bergmann <arnd@arndb.de> - 2015-11-30 00:20 +0100
| From | Peter Crosthwaite <crosthwaitepeter@gmail.com> |
|---|---|
| Date | 2015-11-29 23:20 +0100 |
| Subject | Adding VIRTIO to the multi_v7_defconfig |
| Message-ID | <qAiu5-3rA-3@gated-at.bofh.it> |
Hi, 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? Regards, Peter -- 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/
[toc] | [next] | [standalone]
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Date | 2015-11-29 23:40 +0100 |
| Message-ID | <qAiNr-3xK-3@gated-at.bofh.it> |
| In reply to | #1279464 |
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/
[toc] | [prev] | [next] | [standalone]
| From | Peter Crosthwaite <crosthwaitepeter@gmail.com> |
|---|---|
| Date | 2015-11-30 00:00 +0100 |
| Message-ID | <qAj6N-3DZ-7@gated-at.bofh.it> |
| In reply to | #1279472 |
On Sun, Nov 29, 2015 at 2:31 PM, Arnd Bergmann <arnd@arndb.de> wrote: > 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. > So minimally I am looking for: CONFIG_VIRTIO_PCI=y" CONFIG_VIRTIO_BLK=y" CONFIG_VIRTIO_NET=y" As that gets you booted with network without needing initrd. I guess the rest of VIRTIO makes more sense as modules as follow up work? Regards, Peter > 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/
[toc] | [prev] | [next] | [standalone]
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Date | 2015-11-30 00:20 +0100 |
| Message-ID | <qAjqa-3ZG-5@gated-at.bofh.it> |
| In reply to | #1279474 |
On Sunday 29 November 2015 14:56:53 Peter Crosthwaite wrote: > > So minimally I am looking for: > > CONFIG_VIRTIO_PCI=y" > CONFIG_VIRTIO_BLK=y" > CONFIG_VIRTIO_NET=y" > > As that gets you booted with network without needing initrd. I guess > the rest of VIRTIO makes more sense as modules as follow up work? Sounds reasonable to me, though we could debate about VIRTIO_NET. If nobody else objects, just make it built-in. 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/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web