Conrad Meyer dfca0a8b3d virtio(4): Expose PNP metadata through newbus ... Expose the same fields and widths from both vtio buses, even though they don't quite line up; several virtio drivers can attach to both buses, and sharing a PNP info table for both seems more convenient. In practice, I doubt any virtio driver really needs to match on anything other than bus and device_type (eliminating the unused entries for vtmmio), and also in practice device_type is << 2^16 (so far, values range from 1 to 20). So it might be fine to only expose a 16-bit device_type for PNP purposes. On the other hand, I don't see much harm in overkill here. Reviewed by: bryanv, markj (earlier version) Differential Revision: https://reviews.freebsd.org/D20406		2019-06-04 02:34:59 +00:00
..
balloon
block
console
mmio	virtio(4): Expose PNP metadata through newbus	2019-06-04 02:34:59 +00:00
network	Remove non-functional SCTP checksum offload support for virtio.	2019-05-07 20:28:12 +00:00
pci	virtio(4): Expose PNP metadata through newbus	2019-06-04 02:34:59 +00:00
random	virtio_random(4): Fix random(4) integration	2019-06-04 00:01:37 +00:00
scsi	Fix SCSI sense data pass through.	2019-04-12 18:54:09 +00:00
virtio_bus_if.m
virtio_config.h	Update VirtIO definitions from Linux virtio_config.h and virtio_ring.h headers	2018-06-17 20:45:48 +00:00
virtio_ids.h
virtio_if.m
virtio_ring.h	Update VirtIO definitions from Linux virtio_config.h and virtio_ring.h headers	2018-06-17 20:45:48 +00:00
virtio.c	virtio(4): Expose PNP metadata through newbus	2019-06-04 02:34:59 +00:00
virtio.h	virtio(4): Expose PNP metadata through newbus	2019-06-04 02:34:59 +00:00
virtqueue.c
virtqueue.h