From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] usb: kbd: implement special keys
Date: Sat, 24 Feb 2018 12:46:15 +0100 [thread overview]
Message-ID: <239dbfd9-c01e-b04a-35ff-88e752be5ef4@gmx.de> (raw)
In-Reply-To: <CAPnjgZ0=WQiWoB=gk1ncgcmk+cVFnbvGJe=aoz5z+_q=AZicJg@mail.gmail.com>
On 02/23/2018 09:59 PM, Simon Glass wrote:
> Hi Heinrich,
>
> On 22 February 2018 at 05:04, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
>> Correct support for arrow keys: use the standard xterm escape sequences.
>>
>> Provide support for F1-F12, Insert, Delete, Home, End, Page Up, Page Down.
>>
>> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
>> ---
>> common/usb_kbd.c | 121 +++++++++++++++++++++++++++++++++++++++++--------------
>> 1 file changed, 90 insertions(+), 31 deletions(-)
>>
>
> Is there any way this code could be shared with input.c? It has
> translation tables.
Hello Simon,
input.c seems to be another incomplete implementation of a keyboard
driver. Yes it would make sense to avoid duplicating code. But
unfortunately input.c lacks any documentation.
As maintainer I hope you can answer the following:
When configuring a German keyboard and typing Right-Alt + M the output
is 0xE6. This is mju (µ) in code page 437. Wouldn't we always use UTF-8
in U-Boot?
The scan codes for PS/2 serial keyboards and USB keyboards differ (cf.
"USB HID to PS/2 Scan Code Translation Table"
http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/translate.pdf).
Is input.c meant to handle PS/2 scan codes or USB scan codes?
Regards
Heinrich
next prev parent reply other threads:[~2018-02-24 11:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 12:04 [U-Boot] [PATCH 0/2] usb: kbd: implement special keys Heinrich Schuchardt
2018-02-22 12:04 ` [U-Boot] [PATCH 1/2] usb: kbd: allow multibyte sequences to be put into ring buffer Heinrich Schuchardt
2018-02-22 14:20 ` Marek Vasut
2018-02-22 18:06 ` Heinrich Schuchardt
2018-02-22 19:55 ` Marek Vasut
2018-02-22 20:53 ` Heinrich Schuchardt
2018-02-22 23:02 ` Marek Vasut
2018-02-23 5:50 ` Heinrich Schuchardt
2018-02-23 6:04 ` Marek Vasut
2018-02-23 7:09 ` Heinrich Schuchardt
2018-02-22 12:04 ` [U-Boot] [PATCH 2/2] usb: kbd: implement special keys Heinrich Schuchardt
2018-02-23 20:59 ` Simon Glass
2018-02-24 11:46 ` Heinrich Schuchardt [this message]
2018-03-08 22:04 ` Heinrich Schuchardt
2018-03-19 17:59 ` Simon Glass
2018-03-20 0:12 ` Tom Rini
2019-06-16 21:43 [U-Boot] [PATCH 0/2] " Heinrich Schuchardt
2019-06-16 21:43 ` [U-Boot] [PATCH 2/2] " Heinrich Schuchardt
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=239dbfd9-c01e-b04a-35ff-88e752be5ef4@gmx.de \
--to=xypron.glpk@gmx.de \
--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 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.