Hi,
On 12/15/2010 01:20 PM, Frédéric Grelot wrote:
Do you know whenever certain low-level usb ops can work with this?
I expect most usb devices to work with this, I don't know about
really weird ones.
Specifically iphone firmware flashing was mentioned on the list.
I think that should
Hi,
I know of devices that will enumerate twice, first as one device, then
after a certain setup exchange as another. But that seems to be covered
by the suggestion here, it will just be identicle to two completely different
transports.
Or identify devices by physical port instead of bus
Hi,
It could be that the implementation decides to not handle synchroneous
commands synchroneous at all. The main difference I'm trying to make
here is between commands which do things to end points which cannot
be done while other packets are in flight (like setting configuration,
or
Hi,
Thanks for taking the time to read all that!
On 12/13/2010 12:21 PM, Gerd Hoffmann wrote:
Basic packet structure / communication
--
Each packet exchanged between the vm-host and the usb-host starts
with a usb_redir_header, followed by an optional
Do you know whenever certain low-level usb ops can work with this?
I expect most usb devices to work with this, I don't know about
really weird ones.
Specifically iphone firmware flashing was mentioned on the list.
I think that should work, but that is an interesting case about
On Wed, Dec 15, 2010 at 01:15:58PM +0100, Hans de Goede wrote:
Hi,
Thanks for taking the time to read all that!
On 12/13/2010 12:21 PM, Gerd Hoffmann wrote:
Basic packet structure / communication
--
Each packet exchanged between the vm-host and the
Basic packet structure / communication
--
Each packet exchanged between the vm-host and the usb-host starts
with a usb_redir_header, followed by an optional command specific
header follow by optional additional data.
The usb_redir_header each packet starts
