qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Yang Jin <andysycrane@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] CAN device
Date: Fri, 28 Jun 2013 14:51:25 +0200	[thread overview]
Message-ID: <51CD86CD.9060809@suse.de> (raw)
In-Reply-To: <CAPmXEmn4E1KMxJjv54uZ8YMrLQ7cbbSDAQ4cuVJ93-fjDh7FJw@mail.gmail.com>

Hi,

Am 28.06.2013 14:19, schrieb Yang Jin:
> I try to develop a CAN device on QEMU. And I found pci-serial is similar
> to CAN. 
> 
> Untill now, I have some questions about how to use pci-serial on QEMU.
> Actually, QEMU use isa-serial as a default serial device. So I try to
> use isa-serial firstly.
> 
> Some useful information we can get from docs/qdev-device-use.txt. I know
> that we should use "-chardev" argument to create a host part, and then
> use "-device isa-serial,iobase=IOADDR,irq=IRQ,index=IDX" to start a
> isa-serial. I get those arguments from the source file, the following
> can work.
>    "-device isa-serial,chardev=isa0,iobase=0x3f8,irq=4,index=0"
> However, when I try to create a host through "-chardev
> serial,id=isa0,path=./", error "chardev: opening backend "serial"
> failed" occurs. When change it to "-chardev
> serial,id=isa0,path=/dev/ttyS0", it works. Now, I donot know what "path"
> means? Does it have some relation to the host device? Or it's just a
> symbol means nothing.

Searching man qemu for "chardev serial" should answer that question. :)
There you will also find alternative chardev backends you can use.

> And some questions about pci bus. On docs/qdev-device-use.txt, we get
> Example: device i440FX-pcihost is on the root bus, and provides a PCI
> bus named pci.0.  To put a FOO device into its slot 4, use -device
> FOO,bus=/i440FX-pcihost/pci.0,addr=4.  The abbreviated form bus=pci.0
> also works as long as the bus name is unique.
> So, how can we get the name of the root device which we use now?

You can browse the QOM hierarchy using the ./QMP/qom-list script and an
appropriate -qmp option (e.g. unix:./qmp-sock,server,nowait).

But leaving out the bus= option should work fine just as well.

Regards,
Andreas

> I searched that for some days, but doesnot get some usefull information.
> 
> Thanks,
> Jin yang.

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-06-28 12:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 12:19 [Qemu-devel] CAN device Yang Jin
2013-06-28 12:51 ` Andreas Färber [this message]
2013-06-30 12:25   ` Yang Jin
2013-06-30 12:37     ` Andreas Färber

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=51CD86CD.9060809@suse.de \
    --to=afaerber@suse.de \
    --cc=andysycrane@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).