Lines Matching full:devices
16 Each QEMU target enables a subset of the boards, devices and buses that
27 include all the required dependencies and all the devices that the
31 of boards or devices. For example, by default most targets will include
32 all emulated PCI devices that QEMU supports, but the build process is
156 **devices**
166 Devices are the most complex of the five. They can have a variety
168 all the devices that can be accessed from QEMU.
170 Devices *depend on* the bus that they lie on, for example a PCI
172 have no ``depends on`` directive. Devices also *select* the buses
174 ``select SCSI``. Finally, devices are usually ``default y`` if and
178 Devices also select any optional subsystem that they use; for example
190 devices in one go. This is useful when a set of devices is likely to
196 and ``TEST_DEVICES``. PCI devices usually have a ``default y if
198 some boards (notably s390) easily support a subset of PCI devices,
199 for example only VFIO (passthrough) and virtio-pci devices.
200 ``I2C_DEVICES`` is similar to ``PCI_DEVICES``. It contains i2c devices
204 ``TEST_DEVICES`` instead is used for devices that are rarely used on
229 Boards specify their constituent devices using ``imply`` and ``select``
253 devices. They are usually enabled with ``select`` and in turn select
263 starting point to turn on devices and subsystems.
269 # Uncomment the following lines to disable these optional devices:
279 the user which devices or device groups are implied by the boards.
286 ``--without-default-devices`` option. When this is done, everything defaults
295 and/or pick a subset of the devices in those device groups. Without
296 further modifications to ``configs/devices/``, a system emulator built
297 without default devices might not do much more than start an empty
301 ``--without-default-devices`` are considered bugs in the test code:
306 Right now there is no single place that lists all the optional devices
316 example some devices depend on the availability of KVM or on the presence