[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1196145] [NEW] usb-host: hostaddr=0XX is parsed as oct
From: |
Sascha Krissler |
Subject: |
[Qemu-devel] [Bug 1196145] [NEW] usb-host: hostaddr=0XX is parsed as octal number |
Date: |
Sat, 29 Jun 2013 22:12:52 -0000 |
Public bug reported:
when doing
device_add usb-host,hostaddr=010
taking 010 in the format of both lsusb or udev, qemu parses an octal number and
assumes hostaddr=8.
(i used a 2.0 device on the ehci.0 bus)
at least to me that is confusing.
also:
when adding a non-existent usb device (bogus hostaddr), the following is
created according to 'usb info':
Device 1.0, Port 1, Speed 1.5 Mb/s, Product USB Host Device
in usb_qdev_init():
usb_claim_port is called but usb_device_init does not report an error and thus
usb_release_port is not called.
** Affects: qemu
Importance: Undecided
Status: New
** Tags: usb
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1196145
Title:
usb-host: hostaddr=0XX is parsed as octal number
Status in QEMU:
New
Bug description:
when doing
device_add usb-host,hostaddr=010
taking 010 in the format of both lsusb or udev, qemu parses an octal number
and assumes hostaddr=8.
(i used a 2.0 device on the ehci.0 bus)
at least to me that is confusing.
also:
when adding a non-existent usb device (bogus hostaddr), the following
is created according to 'usb info':
Device 1.0, Port 1, Speed 1.5 Mb/s, Product USB Host Device
in usb_qdev_init():
usb_claim_port is called but usb_device_init does not report an error and
thus usb_release_port is not called.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1196145/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |