Revision 69a319d1 qemu-options.hx
| b/qemu-options.hx | ||
|---|---|---|
| 403 | 403 |
ETEXI |
| 404 | 404 |
|
| 405 | 405 |
DEF("device", HAS_ARG, QEMU_OPTION_device,
|
| 406 |
"-device driver[,options] add device\n") |
|
| 407 |
STEXI |
|
| 408 |
@item -device @var{driver}[,@var{option}[,...]]
|
|
| 406 |
"-device driver[,option[=value][,...]]\n" |
|
| 407 |
" add device (based on driver) with default or\n" |
|
| 408 |
" user defined options\n" |
|
| 409 |
" use -device ? to print all possible drivers\n" |
|
| 410 |
" use -device driver,? to print all possible options\n" |
|
| 411 |
" use -device driver,option=? to print a help for value\n") |
|
| 412 |
STEXI |
|
| 413 |
@item -device @var{driver}[,@var{option}[=@var{value}][,...]]
|
|
| 409 | 414 |
Add device @var{driver}. Depending on the device type,
|
| 410 |
@var{option} (typically @var{key}=@var{value}) may be useful.
|
|
| 415 |
@var{option} (with default or given @var{value}) may be useful.
|
|
| 416 |
To get a help on possible @var{driver}s, @var{option}s or @var{value}s, use
|
|
| 417 |
@code{-device ?},
|
|
| 418 |
@code{-device @var{driver},?} or
|
|
| 419 |
@code{-device @var{driver},@var{option}=?}.
|
|
| 411 | 420 |
ETEXI |
| 412 | 421 |
|
| 413 | 422 |
DEF("name", HAS_ARG, QEMU_OPTION_name,
|
Also available in: Unified diff