[SLOF] Keyboard not working when using XHCI as a USB host controller?
Alexey Kardashevskiy
aik at ozlabs.ru
Wed Aug 5 14:06:52 AEST 2015
On 08/04/2015 09:32 PM, Thomas Huth wrote:
>
> Hi!
>
> When I use the following command line to start a guest:
>
> qemu-system-ppc64 -machine pseries,accel=kvm,usb=off \
> -device pci-ohci,id=usb,bus=pci.0,addr=0x2 \
> -device usb-kbd,id=input0 -nographic -vga none
>
> ... SLOF correctly discoveres a keyboard during USB scan:
>
> Scanning USB
> OHCI: initializing
> USB Keyboard
> ...
> 0 > devalias
> keyboard : /pci at 800000020000000/usb at 2/usb-keyboard at 1
> usb0 : /pci at 800000020000000/usb at 2
> ...
>
> However, when I start with an XHCI (or EHCI) controller
> instead:
Sure about EHCI?
./qemu-system-ppc64 -machine pseries,accel=kvm,usb=off -device
usb-ehci,id=usb,bus=pci.0,addr=0x2 -device usb-kbd,id=input0 -nographic
-vga none
...
Populating /pci at 800000020000000
00 1000 (D) : 8086 24cd serial bus [ usb-ehci ]
No NVRAM common partition, re-initializing...
Scanning USB
EHCI: Initializing
USB Keyboard
...
0 > devalias
keyboard : /pci at 800000020000000/usb at 2/usb-keyboard at 1
usb0 : /pci at 800000020000000/usb at 2
...
and "info qtree" is saying there is just a single USB host which is EHCI
and no OHCI around.
>
> qemu-system-ppc64 -machine pseries,accel=kvm,usb=off \
> -device nec-usb-xhci,id=usb,bus=pci.0,addr=0x2 \
> -device usb-kbd,id=input0 -nographic -vga none
>
> ... SLOF does not discover any keyboard:
>
> Scanning USB
> XHCI: Initializing
> ...
> 0 > devalias
> usb0 : /pci at 800000020000000/usb at 2
> ...
>
> Is this supposed to work? Am I doing something wrong?
I'd say it is and we got a bug here.
--
Alexey
More information about the SLOF
mailing list