From: Gerd Hoffmann <kraxel@redhat.com>
To: M P <buserror@gmail.com>
Cc: qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ehci and low/full speed peripherals
Date: Thu, 13 Dec 2012 15:25:15 +0100 [thread overview]
Message-ID: <50C9E54B.3040206@redhat.com> (raw)
In-Reply-To: <CAMMfpEze5DFRK7V2z0bmd1PxxBFMtrzzz1D-tHBjtZqavyj1JQ@mail.gmail.com>
Hi,
> I added the properties (see patch lower down) and I Use the following to
> create a companion ohci, however qemu starts, seems to let me attach lower
> speed devices, but linux reports:
> "hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad" I have to
> say I'm not sure where that comes from -- so I need some sort of kernel
> support for companion ports perhaps?
Hmm, no idea offhand, patch looks ok.
Which controller is usb1? ohci or ehci?
cheers,
Gerd
prev parent reply other threads:[~2012-12-13 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 10:38 [Qemu-devel] ehci and low/full speed peripherals M P
2012-12-13 12:25 ` Gerd Hoffmann
2012-12-13 13:56 ` M P
2012-12-13 14:25 ` Gerd Hoffmann [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=50C9E54B.3040206@redhat.com \
--to=kraxel@redhat.com \
--cc=buserror@gmail.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).