All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Krasnyansky <maxk@kernel.org>
To: Mark Burkley <qemu@emutex.com>
Cc: Pantelis Koukousoulas <pktoss@gmail.com>,
	Mark Burkley <mark.burkley@emutex.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: Qemu/KVM ehci support
Date: Thu, 11 Dec 2008 14:35:25 -0800	[thread overview]
Message-ID: <494195AD.1020901@kernel.org> (raw)
In-Reply-To: <a9t2k4t89f6dpf7i04e8mb4bhur789df6g@4ax.com>

Mark Burkley wrote:
> On Thu, 11 Dec 2008 10:52:10 -0800, you wrote:
> 
>> Hi Mark,
>>
>> Mark Burkley wrote:
>>> On Mon, 24 Nov 2008 17:21:35 -0800, MaxK wrote:
>>>> Mark, I'm planning on playing with it some more later today. If you have 
>>>> an updated version please send me a patch or a GIT tree to pull from.
>>>> My first attempt as you remember was not very successful (ie XP was just 
>>>> crashing).
>>> I never did find out why that was happening but I will update the
>>> patch against trunk and retest today to see if I can duplicate the
>>> problem.
>> Do you have an updated patch ?
> 
> I got tangled up trying to install git and get a hole poked in the
> firewall then had to go firefighting.  Apologies again, I'll try to
> follow up on the status tomorrow.  git port should be open on our
> server but I will have to check.
Sounds good.

>> btw I noticed a FIXME in the code that said that host device handoff is 
>> not supported yet (or something along those lines). Does that mean that 
>> we cannot yet use Linux host devices with EHCI ?
>> Also how did you test EHCI in general ? 'info ehci' monitor command is 
>> commented out and if I try to un-comment/call it qemu dies.
> 
> That's probably why it is commented out - I didn't get around to
> merging the info command.
> 
> I tested primarily using mass storage devices.  It used to work with
> mice and printers too but I haven't tested those lately.  Basically
> any device that uses bulk and/or interrupt but not isochronous should
> work.
 >
> The handoff refers to the handoff from EHCI to UHCI if a device is
> USB1.1.  At the moment EHCI handles all devices whether they are 1.1
> or 2.0 though this isn't actually an issue due to backward
> compatibility.
Got it. As soon as you send an update I'll give it a shoot again with 
the devices I have.

Thanx
Max

      reply	other threads:[~2008-12-11 22:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1295ed070811220528m3fb93b5evb19de8a855aad62c@mail.gmail.com>
     [not found] ` <492B531F.3030200@qualcomm.com>
     [not found]   ` <sknsi4149t1j371uod18rnfn9evab5rjtf@4ax.com>
2008-12-11 18:52     ` [Qemu-devel] Re: Qemu/KVM ehci support Max Krasnyansky
2008-12-11 20:22       ` Mark Burkley
2008-12-11 22:35         ` Max Krasnyansky [this message]

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=494195AD.1020901@kernel.org \
    --to=maxk@kernel.org \
    --cc=mark.burkley@emutex.com \
    --cc=pktoss@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu@emutex.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.