qdev: update help on -device

While there, use "property" rather than "option", for consistency with
-global.

Signed-off-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
This commit is contained in:
Markus Armbruster 2010-01-29 19:49:01 +01:00 committed by Anthony Liguori
parent 08350cf06a
commit 40ea285c14

View file

@ -403,20 +403,17 @@ Network adapter that supports CDC ethernet and RNDIS protocols.
ETEXI
DEF("device", HAS_ARG, QEMU_OPTION_device,
"-device driver[,option[=value][,...]]\n"
" add device (based on driver) with default or\n"
" user defined options\n"
"-device driver[,prop[=value][,...]]\n"
" add device (based on driver)\n"
" prop=value,... sets driver properties\n"
" use -device ? to print all possible drivers\n"
" use -device driver,? to print all possible options\n"
" use -device driver,option=? to print a help for value\n")
" use -device driver,? to print all possible properties\n")
STEXI
@item -device @var{driver}[,@var{option}[=@var{value}][,...]]
Add device @var{driver}. Depending on the device type,
@var{option} (with default or given @var{value}) may be useful.
To get a help on possible @var{driver}s, @var{option}s or @var{value}s, use
@code{-device ?},
@code{-device @var{driver},?} or
@code{-device @var{driver},@var{option}=?}.
@item -device @var{driver}[,@var{prop}[=@var{value}][,...]]
Add device @var{driver}. @var{prop}=@var{value} sets driver
properties. Valid properties depend on the driver. To get help on
possible drivers and properties, use @code{-device ?} and
@code{-device @var{driver},?}.
ETEXI
DEF("name", HAS_ARG, QEMU_OPTION_name,