public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ni, Ray" <ray.ni@intel.com>
To: "rfc@edk2.groups.io" <rfc@edk2.groups.io>,
	"Ni, Ray" <ray.ni@intel.com>,
	"Gao, Zhichao" <zhichao.gao@intel.com>,
	"Gao, Liming" <liming.gao@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Xu, Shiwei" <shiwei.xu@intel.com>
Subject: Re: [edk2-rfc] UEFI terminal console keyboard type extend for Putty
Date: Fri, 6 Sep 2019 20:34:39 +0000	[thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5C2C92C2@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <15C1F1A3FAEC36AF.25153@groups.io>

Another specific question: What's the meaning of "F1 and F2 don't work in UEFI Shell"? That sounds like a bug in Terminal driver.

> -----Original Message-----
> From: rfc@edk2.groups.io <rfc@edk2.groups.io> On Behalf Of Ni, Ray
> Sent: Friday, September 6, 2019 12:57 PM
> To: rfc@edk2.groups.io; Gao, Zhichao <zhichao.gao@intel.com>; Gao, Liming <liming.gao@intel.com>
> Cc: devel@edk2.groups.io; Xu, Shiwei <shiwei.xu@intel.com>
> Subject: Re: [edk2-rfc] UEFI terminal console keyboard type extend for Putty
> 
> Zhichao,
> Can you please summarize what terminal types are supported by EDKII Terminal driver today and what you are going to
> add through this RFC?
> 
> For the newly added terminal types, where is the mapping defined in public space?
> 
> Thanks,
> Ray
> 
> 
> > -----Original Message-----
> > From: rfc@edk2.groups.io <rfc@edk2.groups.io> On Behalf Of Gao, Zhichao
> > Sent: Friday, September 6, 2019 12:56 AM
> > To: Gao, Liming <liming.gao@intel.com>; rfc@edk2.groups.io
> > Cc: devel@edk2.groups.io; Xu, Shiwei <shiwei.xu@intel.com>
> > Subject: Re: [edk2-rfc] UEFI terminal console keyboard type extend for Putty
> >
> > Liming,
> > All the three types will be introduced.
> >
> > By the way, fix one typo 'F4' for VT400 map key should be 'ESC [ 1 4 ~'.
> > Thanks,
> > Zhichao
> >
> > From: Gao, Liming
> > Sent: Friday, September 6, 2019 3:51 PM
> > To: Gao, Zhichao <zhichao.gao@intel.com>; rfc@edk2.groups.io
> > Cc: devel@edk2.groups.io; Xu, Shiwei <shiwei.xu@intel.com>
> > Subject: RE: [edk2-rfc] UEFI terminal console keyboard type extend for Putty
> >
> > Zhichao:
> >   One clarification. What terminal type will be introduced? Xterm, VT400 and Linux?
> >
> > Thanks
> > Liming
> > From: Gao, Zhichao
> > Sent: Friday, September 06, 2019 12:56 PM
> > To: rfc@edk2.groups.io<mailto:rfc@edk2.groups.io>
> > Cc: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Gao, Liming
> > <liming.gao@intel.com<mailto:liming.gao@intel.com>>; Xu, Shiwei <shiwei.xu@intel.com<mailto:shiwei.xu@intel.com>>
> > Subject: [edk2-rfc] UEFI terminal console keyboard type extend for Putty
> >
> > Hi everyone,
> >
> > Putty is a popular terminal console software in windows and it support various types of terminal keyboard type. I would
> > like to add most of the type support. Here is the key map info. Hope to get comments. Here is the type and mapping
> table:
> > Putty function key map:
> >   +=========+======+===========+=============+=============+=============+
> >   |         | EFI  |           |             |             |             |
> >   |         | Scan |           |             |  Normal     |             |
> >   |   KEY   | Code |  VT100+   | Xterm R6    |  VT400      | Linux       |
> >   +=========+======+===========+=============+=============+=============+
> >   | F1      | 0x0B | ESC O P   | NONE        | ESC [ 1 1 ~ | ESC [ [ A   |
> >   | F2      | 0x0C | ESC O Q   | NONE        | ESC [ 1 2 ~ | ESC [ [ B   |
> >   | F3      | 0x0D | ESC O R   | ESC O R     | ESC [ 1 3 ~ | ESC [ [ C   |
> >   | F4      | 0x0E | ESC O S   | ESC O S     | ESC [ 1 3 ~ | ESC [ [ D   |
> >   | F5      | 0x0F | ESC O T   | ESC [ 1 5 ~ | ESC [ 1 5 ~ | ESC [ [ E   |
> >   | F6      | 0x10 | ESC O U   | ESC [ 1 7 ~ | ESC [ 1 7 ~ | ESC [ 1 7 ~ |
> >   | F7      | 0x11 | ESC [ V   | ESC [ 1 8 ~ | ESC [ 1 8 ~ | ESC [ 1 8 ~ |
> >   | F8      | 0x12 | ESC [ W   | ESC [ 1 9 ~ | ESC [ 1 9 ~ | ESC [ 1 9 ~ |
> >   | F9      | 0x13 | ESC [ X   | ESC [ 2 0 ~ | ESC [ 2 0 ~ | ESC [ 2 0 ~ |
> >   | F10     | 0x14 | ESC [ Y   | ESC [ 2 1 ~ | ESC [ 2 1 ~ | ESC [ 2 1 ~ |
> >   | Escape  | 0x17 | ESC       | ESC         | ESC         | ESC         |
> >   | F11     | 0x15 | ESC O Z   | ESC [ 2 3 ~ | ESC [ 2 3 ~ | ESC [ 1 3 ~ |
> >   | F12     | 0x16 | ESC O [   | ESC [ 2 4 ~ | ESC [ 2 4 ~ | ESC [ 1 4 ~ |
> >   +=========+======+===========+=============+=============+=============+
> >
> > For Xterm R6 F1 and F2, it is descripted as ESC+O+P and ESC+O+Q, but it doesn't work on UEFI shell. Same with the SCO
> > mode. So I would ignore the unworkable key map.
> > Info refer to https://www.ssh.com/ssh/putty/putty-manuals/0.68/Chapter4.html#config-funkeys
> >
> > Thanks,
> > Zhichao
> >
> >
> >
> 
> 
> 


  parent reply	other threads:[~2019-09-06 20:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06  4:56 [edk2-rfc] UEFI terminal console keyboard type extend for Putty Gao, Zhichao
2019-09-06  7:51 ` Liming Gao
2019-09-06  7:55   ` Gao, Zhichao
2019-09-06 19:57     ` Ni, Ray
     [not found]     ` <15C1F1A3FAEC36AF.25153@groups.io>
2019-09-06 20:34       ` Ni, Ray [this message]
2019-09-09  0:27         ` Gao, Zhichao
     [not found]         ` <15C29E00BD86BAAF.26261@groups.io>
2019-09-09  0:48           ` Gao, Zhichao

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-list 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=734D49CCEBEEF84792F5B80ED585239D5C2C92C2@SHSMSX104.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /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