public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <daahern@cisco.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: erik.rull@rdsoftware.de, kvm@vger.kernel.org
Subject: Re: USB EHCI patch for 0.14.0?
Date: Fri, 11 Mar 2011 09:34:13 -0700	[thread overview]
Message-ID: <4D7A4F05.2020801@cisco.com> (raw)
In-Reply-To: <m3mxl1ljhv.fsf@blackfin.pond.sub.org>



On 03/11/11 09:17, Markus Armbruster wrote:
> David Ahern <daahern@cisco.com> writes:
> 
>> On 03/11/11 08:39, Markus Armbruster wrote:
>>> erik.rull@rdsoftware.de writes:
>>>
>>>> Hi David,
>>>>
>>>> I did a second iteration and it looked way better, maybe my first attempts
>>>> were somehow buggy.
>>>>
>>>> First - please review your DPRINTF in the usb-ehci.c, there is a variable
>>>> "dev" undefined in line 504/505 when enabling the debugging defines at the
>>>> top of the file, the compiler complains there.
>>>>
>>>> I tested again with your hints, here my results:
>>>>
>>>> - using -device usb-host causes windows not to boot completely, using
>>>> -usbdevice host:auto:*.* is fine!
>>>>
>>>> - using -usbdevice tablet is better than using -device usb-tablet
>>>
>>> Better inhowfar?
>>
>> As I recall the USB code is the ignored step-child in qemu; it was never
>> properly/fully integrated into the qdev stuff. The paths appear to
>> differ in how usb devices are handled. I for one have always stuck with
>> the -usbdevice route.
> 
> Please report any deficiencies so we can fix this.

Erik reported a few above.

David

> 
> -usbdevice is around for backward compatibility only.  There are already
> cases where -device provides you more control than -usbdevice.  This
> feature gap will only grow.

  reply	other threads:[~2011-03-11 16:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 15:18 USB EHCI patch for 0.14.0? erik.rull
2011-03-11 15:39 ` Markus Armbruster
2011-03-11 16:01   ` David Ahern
2011-03-11 16:17     ` Markus Armbruster
2011-03-11 16:34       ` David Ahern [this message]
2011-03-11 16:24   ` Erik Rull
2011-03-11 16:46     ` Markus Armbruster
2011-03-11 16:56       ` Erik Rull
2011-03-11 17:11         ` David Ahern
2011-03-11 17:31           ` David Ahern
2011-04-11  9:40             ` ya su
2011-04-11 13:23               ` David Ahern
2011-04-11 16:32                 ` Jan Kiszka
2011-04-11 16:46                 ` Jan Kiszka
2011-04-11 17:53                   ` David Ahern
2011-04-11 20:07                     ` Jan Kiszka
2011-04-11 21:10                       ` Alexander Graf
2011-03-11 15:57 ` David Ahern
2011-03-11 16:32   ` Erik Rull
  -- strict thread matches above, loose matches on Subject: below --
2011-03-14  8:38 erik.rull
2011-03-17 18:05 ` Erik Rull
2011-03-09 15:40 erik.rull
2011-03-09 16:12 ` David Ahern
2011-03-09 21:28   ` Erik Rull
2011-03-09 22:14     ` David Ahern
2011-03-09 22:48       ` Erik Rull
2011-03-08 16:23 Erik Rull
2011-03-08 18:54 ` David Ahern
2011-06-06 11:33   ` André Weidemann
2011-06-06 13:18     ` David Ahern

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=4D7A4F05.2020801@cisco.com \
    --to=daahern@cisco.com \
    --cc=armbru@redhat.com \
    --cc=erik.rull@rdsoftware.de \
    --cc=kvm@vger.kernel.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