Re: [edk2] How to Interpret ReadKeyStrokeEX Data

2018-06-06 Thread Andrew Fish
माइकल रोथ्मेन् / Михаил Ротман / משה רוטמן) > רועה עיקרי של חתולים > > -Original Message- > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of > Rothman, Michael A > Sent: Monday, June 4, 2018 10:31 AM > To: jim.dai...@dell.com; Ni, Ruiyu > Cc: Carsey, Jab

Re: [edk2] How to Interpret ReadKeyStrokeEX Data

2018-06-06 Thread Jim.Dailey
, 2018 10:31 AM To: jim.dai...@dell.com; Ni, Ruiyu Cc: Carsey, Jaben ; edk2-devel@lists.01.org; fel...@mail.ru Subject: Re: [edk2] How to Interpret ReadKeyStrokeEX Data Since I'm largely the person who might be to blame for the language and intent here and I’ll focus on the spec-related item. See

Re: [edk2] How to Interpret ReadKeyStrokeEX Data

2018-06-05 Thread Rothman, Michael A
: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Rothman, Michael A Sent: Monday, June 4, 2018 10:31 AM To: jim.dai...@dell.com; Ni, Ruiyu Cc: Carsey, Jaben ; edk2-devel@lists.01.org; fel...@mail.ru Subject: Re: [edk2] How to Interpret ReadKeyStrokeEX Data Since I'm largely

Re: [edk2] How to Interpret ReadKeyStrokeEX Data

2018-06-04 Thread Rothman, Michael A
-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of jim.dai...@dell.com Sent: Friday, June 1, 2018 11:27 AM To: Ni, Ruiyu Cc: Carsey, Jaben ; edk2-devel@lists.01.org; fel...@mail.ru Subject: [edk2] How to Interpret ReadKeyStrokeEX Data (Subject changed) I guess this is a question

Re: [edk2] How to Interpret ReadKeyStrokeEX Data

2018-06-04 Thread Jim.Dailey
.com; jaben.car...@intel.com; edk2-devel@lists.01.org; > fel...@mail.ru > Subject: Re: [edk2] How to Interpret ReadKeyStrokeEX Data > > Dell - Internal Use - Confidential <=== THIS IS BOGUS !! > >> From: af...@apple.com [mailto:af...@apple.com] >> >> Th

Re: [edk2] How to Interpret ReadKeyStrokeEX Data

2018-06-04 Thread Carsey, Jaben
ben.car...@intel.com; edk2-devel@lists.01.org; > fel...@mail.ru > Subject: Re: [edk2] How to Interpret ReadKeyStrokeEX Data > > Dell - Internal Use - Confidential <=== THIS IS BOGUS !! > >> From: af...@apple.com [mailto:af...@apple.com] >> >> The big picture

Re: [edk2] How to Interpret ReadKeyStrokeEX Data

2018-06-04 Thread Jim.Dailey
Cc: ruiyu...@intel.com; jaben.car...@intel.com; edk2-devel@lists.01.org; fel...@mail.ru Subject: Re: [edk2] How to Interpret ReadKeyStrokeEX Data Dell - Internal Use - Confidential <=== THIS IS BOGUS !! > From: af...@apple.com [mailto:af...@apple.com] > > The big picture difference is the

Re: [edk2] How to Interpret ReadKeyStrokeEX Data

2018-06-04 Thread Jim.Dailey
Dell - Internal Use - Confidential > From: af...@apple.com [mailto:af...@apple.com] > > The big picture difference is the original SimpleTextIn was the least common > denominator with a serial terminal. The Ex version added more info about > keyboards, so richer info on modifier keys. I get

Re: [edk2] How to Interpret ReadKeyStrokeEX Data

2018-06-04 Thread Andrew Fish
Jim, The big picture difference is the original SimpleTextIn was the least common denominator with a serial terminal. The Ex version added more info about keyboards, so richer info on modifier keys. Thanks, Andrew Fish > On Jun 4, 2018, at 7:46 AM, jim.dai...@dell.com wrote: > > >>

Re: [edk2] How to Interpret ReadKeyStrokeEX Data

2018-06-04 Thread Jim.Dailey
>Thanks/Ray > >> From: jim.dai...@dell.com >> >> I guess this is a question of UEFI spec interpretation. In the Console >> I/O Protocol description of Version 2.5 of the spec (page 456), it says: >> >> If the Scan Code is set to 0x00 then the Unicode character is >> valid and should

Re: [edk2] How to Interpret ReadKeyStrokeEX Data

2018-06-03 Thread Ni, Ruiyu
Thanks/Ray > -Original Message- > From: jim.dai...@dell.com > Sent: Saturday, June 2, 2018 2:27 AM > To: Ni, Ruiyu > Cc: Carsey, Jaben ; fel...@mail.ru; edk2- > de...@lists.01.org > Subject: How to Interpret ReadKeyStrokeEX Data > > (Subject changed) > > I guess this is a question

[edk2] How to Interpret ReadKeyStrokeEX Data

2018-06-01 Thread Jim.Dailey
(Subject changed) I guess this is a question of UEFI spec interpretation. In the Console I/O Protocol description of Version 2.5 of the spec (page 456), it says: If the Scan Code is set to 0x00 then the Unicode character is valid and should be used. To me that clearly says it all. The