Lines Matching full:to

10 a POWER and an x86 board can run the same code to emulate a PCI network
12 can run the same code to emulate a SCSI disk while using different
14 disk to their guests, but with three different virtio guest interfaces.
19 anything that is not needed to support a particular target is culled.
21 QEMU uses a simple domain-specific language to describe the dependencies
26   to list the components they need, and the compiled executable will
28   user can add to that board;
33   configurable and it is easy to drop unnecessary (or otherwise unwanted)
34   code to make a leaner binary.
40 Unlike Linux, there is no user interface to edit the configuration, which
69 above, Makefiles will have access to a variable named ``CONFIG_ARM_VIRT``,
77 The ``bool`` data type declaration is optional, but it is suggested to
84   evaluate an expression and force the value of the variable to false
89   While ``depends on`` can force a symbol to false, reverse dependencies can
90   be used to force another symbol to true.  In the following example,
105   Default values are assigned to the config symbol if no other value was
107   ``select`` or ``depends on`` directives do not force the value to true
119   This is similar to ``select`` as it applies a lower limit of ``y``
120   to another symbol.  However, the lower limit is only a default
121   and the "implied" symbol's value may still be set to ``n`` from a
133   The next section explains where to use ``imply`` or ``default y``.
148   Subsystems always default to false (they have no ``default`` directive)
150   up to other symbols to ``select`` whatever subsystems they require.
152   They sometimes have ``select`` directives to bring in other required
179   a video card might specify ``select EDID`` if it needs to build EDID
180   information and publish it to the guest.
189   Device groups provide a convenient mechanism to enable/disable many
190   devices in one go.  This is useful when a set of devices is likely to
200   ``I2C_DEVICES`` is similar to ``PCI_DEVICES``. It contains i2c devices
201   that users might reasonably want to plug in to an i2c bus on any
203   to be wired up in a way that can't be done on the command line).
205   production virtual machines, but provide useful hooks to test QEMU
233   may not be started without it.  Boards default to true, but also
234   have a ``depends on`` clause to limit them to the appropriate targets.
242   for the target they apply to.
260 In addition to the Kconfig files under hw/, each target also includes
262 initialize some Kconfig variables to non-default values and provide the
263 starting point to turn on devices and subsystems.
269     # Uncomment the following lines to disable these optional devices:
285 It is also possible to run QEMU's configure script with the
287 to ``n`` unless it is ``select``\ ed or explicitly switched on in the
290 want to change some lines in the first group, for example like this::
296 further modifications to ``configs/devices/``, a system emulator built
299 command line.  Starting a VM *without* ``--nodefaults`` is allowed to