All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Unable to parse -device drivers containing commas?
Date: Thu, 30 May 2013 11:00:40 +0100	[thread overview]
Message-ID: <51A72348.7040306@ilande.co.uk> (raw)

Hi all,

I found that the QEMU -device command line parser doesn't seem to like 
driver names containing a comma such as "SUNW,tcx" for the video driver 
on qemu-system-sparc:

$ ./qemu-system-sparc -device SUNW,tcx,help
qemu-system-sparc: -device SUNW,tcx,help: Parameter 'driver' expects 
device type
$ ./qemu-system-sparc -device 'SUNW,tcx',help
qemu-system-sparc: -device SUNW,tcx,help: Parameter 'driver' expects 
device type
$ ./qemu-system-sparc -device "SUNW,tcx",help
qemu-system-sparc: -device SUNW,tcx,help: Parameter 'driver' expects 
device type

If I try temporarily removing the comma from the TypeInfo name field in 
hw/display/tcx.c then all is fine:

$ ./qemu-system-sparc -device 'SUNWtcx',help
SUNWtcx.vram_size=hex32
SUNWtcx.width=uint16
SUNWtcx.height=uint16
SUNWtcx.depth=uint16
$ ./qemu-system-sparc -device SUNWtcx,help
SUNWtcx.vram_size=hex32
SUNWtcx.width=uint16
SUNWtcx.height=uint16
SUNWtcx.depth=uint16

Note that there are a couple of other devices in the SPARC32 device tree 
with this problem, since the general device naming convention on SPARC 
is in the form <manufacturer>,<device>. Is there a way of escaping the 
commas on the command line so that it is possible to list properties for 
drivers named in this way?


Many thanks,

Mark.

             reply	other threads:[~2013-05-30 10:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 10:00 Mark Cave-Ayland [this message]
2013-05-30 12:07 ` [Qemu-devel] Unable to parse -device drivers containing commas? Eric Blake
2013-05-31  7:56   ` Mark Cave-Ayland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51A72348.7040306@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.