From: Nikita Kiryanov <nikita@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] usbkbd input double echoed
Date: Mon, 24 Nov 2014 16:41:06 +0200 [thread overview]
Message-ID: <54734382.9070703@compulab.co.il> (raw)
In-Reply-To: <5471FABD.6090507@redhat.com>
Hi Hans,
On 11/23/2014 05:18 PM, Hans de Goede wrote:
> Hi,
>
> On 11/23/2014 04:07 PM, Nikita Kiryanov wrote:
>> Hi all,
>>
>> I've enabled USB keyboard for cm_fx6 using these three defines:
>>
>> #define CONFIG_USB_KEYBOARD
>> #define CONFIG_SYS_USB_EVENT_POLL
>> #define CONFIG_SYS_STDIO_DEREGISTER
>>
>> I am able to probe it with `usb start`, and set it as input using
>> `setenv stdin usbkbd`.
>>
>> It works, save for one problem: all key presses are echoed twice.
>> The double echo happens both on serial and vga stdout.
>> It is not dependant on the keyboard (tried different ones).
>> Output from commands looks normal.
>> Switching to CONFIG_SYS_USB_EVENT_POLL_VIA_CONTROL_EP did not help.
>> Shell still understands each key press as one key press, so
>> even though "pprriinntteennvv" is displayed, the shell still sees
>> "printenv".
>>
>> Any idea what the cause may be?
>
> In my experience both polling methods are sub-optimal, if your board
> has an ehci controller, try using CONFIG_SYS_USB_EVENT_POLL_VIA_INT_QUEUE
>
> Also I use CONFIG_CONSOLE_MUX, then you can do:
>
> setenv stdin serial,usbkbd
>
> And get both, using this usb-kbd support works fine for me, without the
> double echo, both on the serial console and on the sunxi-cfb console over
> hdmi.
>
> Regards,
>
> Hans
>
I think I must have encountered some toolchain bug. After switching to
another branch to work on something else I came back to my dev branch
and the compiled images no longer have this bug.
Thanks for the help though..
--
Regards,
Nikita Kiryanov
prev parent reply other threads:[~2014-11-24 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 15:07 [U-Boot] usbkbd input double echoed Nikita Kiryanov
2014-11-23 15:18 ` Hans de Goede
2014-11-24 14:41 ` Nikita Kiryanov [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=54734382.9070703@compulab.co.il \
--to=nikita@compulab.co.il \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox