From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: yocto@yoctoproject.org
Subject: Re: USB keyboard not working on PC-Engines host
Date: Thu, 27 Jan 2011 09:36:07 -0500 [thread overview]
Message-ID: <4D4182D7.1050605@windriver.com> (raw)
In-Reply-To: <953D6EA3-E3D9-4998-8147-2FF0E325AA56@keylevel.com>
On 11-01-27 09:22 AM, Chris Tapp wrote:
> I've built poky-image-minimal for a machine that's based on
> qemux86.conf. I've create a modified copy to target x86 hardware and
> made sure usbhost and usbgadget are in the MACHINE_FEATURES.
>
> If I boot on an Intel Atom board then everything is fine. However, if I
> boot on a PC-Engines ALIX 3D3 the usb keyboard doesn't work and I can't
> login.
>
> I have had to disable USB 2 support in the ALIX BIOS to prevent "unable
> to enumerate USB device on port ..." messages, but USB 1.1 is still
> enabled. The OHCI device code is 1d6b:0001 and works ok with an EO build
> that I have.
What's the kernel version on the working build ?
Do you have the dmesg output from the working/non working
boots handy ? Also the .config from your non-working
boot would also be handy.
>
> Can anyone point me to where I should be looking to find out how to get
> this working?
This smells like a configuration issue, or something different
between kernel versions. The information above will help us
narrow it down.
Cheers,
Bruce
>
> Chris Tapp
>
> opensource@keylevel.com
> www.keylevel.com
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
prev parent reply other threads:[~2011-01-27 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 14:22 USB keyboard not working on PC-Engines host Chris Tapp
2011-01-27 14:36 ` Bruce Ashfield [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=4D4182D7.1050605@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=opensource@keylevel.com \
--cc=yocto@yoctoproject.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 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.