From: Paolo Bonzini <pbonzini@redhat.com>
To: "Gabriel L. Somlo" <gsomlo@gmail.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: reza.jelveh@tuhh.de, edk2-devel@lists.sourceforge.net,
lersek@redhat.com, qemu-devel@nongnu.org, agraf@suse.de
Subject: Re: [Qemu-devel] OVMF, Q35 and USB keyboard/mouse
Date: Fri, 12 Sep 2014 20:26:01 +0200 [thread overview]
Message-ID: <54133AB9.7080508@redhat.com> (raw)
In-Reply-To: <20140912181806.GI1825@ERROL.INI.CMU.EDU>
Il 12/09/2014 20:18, Gabriel L. Somlo ha scritto:
>> > Now *that* is really strange, especially as UHCI1 is pci function 0,
>> > without probing that successfully you wouldn't see the other pci
>> > functions (1+2+7 for uhci2+uhci3+ehci) in the same slot in the first
>> > place.
> I've only ever skimmed through the PCI spec at high speed, and have no
> real clue about USB, but one thing I noticed is that by default, the
> q35 uhci1-3 and ehci1 devices all share the same pci device (1d).
>
> If I explicitly create "-device ich9-usb-ehci1" and
> "-device ich9-usb-ehci1" via the command line, they each get their own
> distinct PCI device number, and hanging mice and keyboards off of them
> works in that case.
>
> Feel free to ignore me because I'm likely wrong, but any chance there
> might be some bug related to how all these share a pci device number in
> the default setup ?
So it could be an OVMF bug related to multifunction devices.
Well, you could try moving devices around in different functions.
You could try moving ehci1 to 0 and the UHCIs to 1/2/7.
Or drop uhci2/uhci3 and move the two remaining devices around. Once you
have three combinations that work (e.g. 0/4, 0/6, 0/7) you could use it
to add three UHCI controllers (in the above examples, it would be 0/1/2/7).
Remember that one of the two must be xx.0, the other can be anything
from xx.1 to xx.7.
Paolo
next prev parent reply other threads:[~2014-09-12 18:26 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 22:00 [Qemu-devel] OVMF, Q35 and USB keyboard/mouse Gabriel L. Somlo
2014-09-10 0:40 ` Laszlo Ersek
2014-09-10 6:31 ` Gerd Hoffmann
2014-09-10 7:59 ` Laszlo Ersek
2014-09-10 14:06 ` Gabriel L. Somlo
2014-09-10 23:08 ` [Qemu-devel] [edk2] " Paolo Bonzini
2014-09-11 15:42 ` [Qemu-devel] " Gabriel L. Somlo
2014-09-11 15:49 ` Paolo Bonzini
2014-09-11 16:35 ` Gabriel L. Somlo
2014-09-11 16:40 ` Paolo Bonzini
2014-09-11 17:11 ` Gabriel L. Somlo
2014-09-11 17:15 ` [Qemu-devel] [edk2] " Paolo Bonzini
2014-09-11 20:16 ` [Qemu-devel] " Gabriel L. Somlo
2014-09-11 20:46 ` Laszlo Ersek
2014-09-11 21:34 ` Alexander Graf
2014-09-11 23:21 ` Gabriel L. Somlo
2014-09-12 9:17 ` BALATON Zoltan
2014-09-12 17:58 ` Gabriel L. Somlo
2014-09-12 6:46 ` Gerd Hoffmann
2014-09-12 18:18 ` Gabriel L. Somlo
2014-09-12 18:26 ` Paolo Bonzini [this message]
2014-09-12 19:59 ` Gabriel L. Somlo
2014-09-13 5:06 ` Laszlo Ersek
2014-09-15 14:50 ` Gabriel L. Somlo
2014-09-15 15:01 ` Laszlo Ersek
2014-09-15 15:07 ` Gabriel L. Somlo
2014-09-15 18:02 ` Laszlo Ersek
2014-09-15 19:23 ` Gabriel L. Somlo
2014-09-15 19:56 ` BALATON Zoltan
2014-09-16 8:15 ` Gerd Hoffmann
2014-09-21 20:00 ` Gabriel L. Somlo
2014-09-21 22:10 ` Gabriel L. Somlo
2014-09-21 22:43 ` Laszlo Ersek
2014-09-22 16:44 ` [Qemu-devel] [edk2] " Paolo Bonzini
2014-09-22 16:59 ` Gabriel L. Somlo
2014-09-22 20:40 ` Laszlo Ersek
2014-09-24 22:03 ` Gabriel L. Somlo
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=54133AB9.7080508@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=edk2-devel@lists.sourceforge.net \
--cc=gsomlo@gmail.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=reza.jelveh@tuhh.de \
/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.