From: Lonnie Mendez <lmendez19@austin.rr.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Bus number and address changes after usb_add?
Date: Wed, 06 Dec 2006 22:25:23 -0600 [thread overview]
Message-ID: <1165465523.19968.10.camel@vaio> (raw)
In-Reply-To: <A3C277AA6499944188602D8A7168B9A701332C62@bjsmsx401>
On Thu, 2006-12-07 at 12:18 +0800, Yu, Xiaoyang wrote:
> After add a USB device by “usb_add”, I can view it by “info usb”. It
> shows the bus number and address.
>
>
>
> As shown in vl.c, it seems that usb_info() is called when issue “info
> usb”, and usb_device_add() is called when issue “usb_add”.
>
>
>
> But if I add call to usb_info() in the end of usb_device_add(), it
> always show the bus number and address as “0.0”, which can be
> different from the output of “usb_add”.
>
> So it seems like the bus number and address of a USB device changed
> some time after “usb_add”. Does anyone know why it changes? Thanks in
> advance!
The address you see with the monitor command "info usb" is the address
all usb devices start out with when connected to the guest. The guest
os will later assign the device an address on bus 0 (the uhci controller
on the i386 system target) after it does things like fetch the device
descriptor, configuration, etc. iirc linux will first assign a device
an address unlike windows which queries for the configuration
information before an address is assigned.
next prev parent reply other threads:[~2006-12-07 4:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 4:18 [Qemu-devel] Bus number and address changes after usb_add? Yu, Xiaoyang
2006-12-07 4:25 ` Lonnie Mendez [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-07 4:20 Yu, Xiaoyang
2006-12-07 6:11 Yu, Xiaoyang
2006-12-07 6:22 ` Lonnie Mendez
2006-12-07 6:43 Yu, Xiaoyang
2006-12-07 7:04 ` Lonnie Mendez
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=1165465523.19968.10.camel@vaio \
--to=lmendez19@austin.rr.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).