From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=192.55.52.43; helo=mga05.intel.com; envelope-from=jaben.carsey@intel.com; receiver=edk2-devel@lists.01.org Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 3BB9A203B992A for ; Mon, 4 Jun 2018 09:21:58 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jun 2018 09:21:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,476,1520924400"; d="scan'208";a="61672745" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by orsmga001.jf.intel.com with ESMTP; 04 Jun 2018 09:21:51 -0700 Received: from fmsmsx154.amr.corp.intel.com (10.18.116.70) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 4 Jun 2018 09:21:51 -0700 Received: from fmsmsx103.amr.corp.intel.com ([169.254.2.125]) by FMSMSX154.amr.corp.intel.com ([169.254.6.26]) with mapi id 14.03.0319.002; Mon, 4 Jun 2018 09:21:50 -0700 From: "Carsey, Jaben" To: "Jim.Dailey@dell.com" CC: "afish@apple.com" , "Ni, Ruiyu" , "edk2-devel@lists.01.org" , "felixp@mail.ru" , "Rothman, Michael A" Thread-Topic: [edk2] How to Interpret ReadKeyStrokeEX Data Thread-Index: AdP51a/hVUcRd8ZXRbW9WoFUsUlqeAB2jMWgABXhBjAAEaRtAAACc8mAAAAWzAD//5AC0Q== Date: Mon, 4 Jun 2018 16:21:50 +0000 Message-ID: References: <3e835c29938d49ea8d285385429870ad@ausx13mps339.AMER.DELL.COM> <734D49CCEBEEF84792F5B80ED585239D5BD232B9@SHSMSX104.ccr.corp.intel.com> <5108c0244ffb45ccb0208dd0a1ed2beb@ausx13mps339.AMER.DELL.COM> <51978119-FF46-425A-A7E9-8C1EBD3C7B1E@apple.com> <0c4414f8ae2742a6af4138e9b34714af@ausx13mps339.AMER.DELL.COM>, In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 Subject: Re: How to Interpret ReadKeyStrokeEX Data X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 16:21:58 -0000 Content-Language: en-US Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Jim, I think I see what you mean. If scan code is 0, then don=92t test the shi= ft state and just use the character raw? Jaben > On Jun 4, 2018, at 9:02 AM, "Jim.Dailey@dell.com" = wrote: >=20 > Please disregard the stupid "Confidential" line that our email tool > adds but hides from me when I send text. :-( >=20 > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of D= ailey, Jim > Sent: Monday, June 4, 2018 11:00 AM > To: afish@apple.com > Cc: ruiyu.ni@intel.com; jaben.carsey@intel.com; edk2-devel@lists.01.org;= felixp@mail.ru > Subject: Re: [edk2] How to Interpret ReadKeyStrokeEX Data >=20 > Dell - Internal Use - Confidential <=3D=3D=3D THIS IS BOGUS !! >=20 >> From: afish@apple.com [mailto:afish@apple.com]=20 >>=20 >> The big picture difference is the original SimpleTextIn was the least c= ommon >> denominator with a serial terminal. The Ex version added more info abou= t >> keyboards, so richer info on modifier keys. >=20 > I get that. But I fail to see how that affects SimpleTextInEx behavior = or > what the UEFI spec has to say about it. >=20 > As I said earlier, the question I am raising is when SimpleTextInEx retu= rns > something like: >=20 > Scan Code =3D 0 > Unicode Char =3D 0x0023 ("#") > Shift Information =3D 0x80000001 (right shift pressed) >=20 > is it correct for the editor to reject this as an invalid key? >=20 > I say, no, it would be wrong to reject this data because the scan code > is 0 and, therefore, the Unicode character is valid and should be used. > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel