Lines Matching refs:device
12 VirtIO is a virtualization standard for network and disk device drivers where
13 just the guest's device driver "knows" it is running in a virtual environment,
24 PCI support might use simple memory mapped device (MMIO) instead of the PCI
25 device. The memory mapped virtio device behaviour is based on the PCI device
26 specification. Therefore most operations including device initialization,
30 The VirtIO spec defines a lots of VirtIO device types, however at present only
31 network and block device, the most two commonly used devices, are supported.
84 -device virtio-net-device,netdev=net0 \
86 -device virtio-blk-device,drive=hd0
94 -device virtio-net-pci,netdev=net0 \
96 -device virtio-blk-pci,drive=hd0
98 Additional net and block devices can be created by appending more '-device'
107 -device virtio-net-pci,netdev=net0 \
109 -device virtio-blk-device,drive=hd0 \
111 -device virtio-blk-pci,drive=hd1
114 (aka modern) devices, pass additional device property/value pairs like below:
120 -device virtio-net-pci,netdev=net0,disable-legacy=true,disable-modern=false \
122 -device virtio-blk-pci,drive=hd0,disable-legacy=true,disable-modern=false
134 virtio device [dev] - show or set current virtio block device
147 Then we can show the connected block device details by:
192 | virtio device drivers |
209 virtio device is discovered in the transport driver's probe() method, and its
210 device ID is saved in the virtio uclass's private data of the transport device.
211 Then in the virtio uclass's post_probe() method, the real virtio device driver
212 (virtio_net.c, virtio_blk.c) is bound if there is a match on the device ID.
215 virtio uclass driver help bring the virtio device driver online. They do things
216 like acknowledging device, feature negotiation, etc, which are really common
220 virtio device driver to call. These ops APIs's parameter is designed to remind
221 the caller to pass the correct 'struct udevice' id of the virtio device, eg:
227 So the parameter 'vdev' indicates the device should be the real virtio device.
236 Here the parameter 'udev' indicates the device should be the transport device.
244 So it's easy to tell which device these functions are operating on.
248 At present only VirtIO network card (device ID 1) and block device (device
252 1. add new device ID in virtio.h
258 2. update VIRTIO_ID_MAX_NUM to be the largest device ID plus 1
282 should be called for driver to negotiate feature support with the device.