From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=68.232.153.95; helo=esa5.dell-outbound.iphmx.com; envelope-from=jim.dailey@dell.com; receiver=edk2-devel@lists.01.org Received: from esa5.dell-outbound.iphmx.com (esa5.dell-outbound.iphmx.com [68.232.153.95]) (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 62D462096891F for ; Mon, 4 Jun 2018 09:00:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1528127920; x=1559663920; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=XxLck99qHyDgKz3Sb7fPrSlqxVhwKCxkEaqsQY56Sm8=; b=ofDXiy3pKf0PmyagtePIQKx0em0C4SgMoC1cVHZw3drcA1J7aPZowGD9 SCt6z7lH0hbJlmMNXWsrAIGGfCR0yya8AA7IHAbooAIdbuWMqsn52Nki6 Z9FA0RH/fiSg6jcMep6u7sIiKvabQCZbg/5BK0PLufj8ovYtZymELFMKy g=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2FeAAAjYRVbh8mZ6ERcGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYQXgQ0oCotyjG6BeZRLgXgLhGwCghEhNBgBAgEBAQEBAQIBAQI?= =?us-ascii?q?QAQEBCgsJCCgvgjUiglMBAQEDATo/BQsCAQgVIQkHRhECBA4FCIMagXkIqHaIP?= =?us-ascii?q?4Fogi2GFYITg2c1hT+FCAKHLpFABwKOW40ikR+BQYILcIMTgiAOCY4Xb41/gRk?= =?us-ascii?q?BAQ?= X-IPAS-Result: =?us-ascii?q?A2FeAAAjYRVbh8mZ6ERcGQEBAQEBAQEBAQEBAQcBAQEBAYQ?= =?us-ascii?q?XgQ0oCotyjG6BeZRLgXgLhGwCghEhNBgBAgEBAQEBAQIBAQIQAQEBCgsJCCgvg?= =?us-ascii?q?jUiglMBAQEDATo/BQsCAQgVIQkHRhECBA4FCIMagXkIqHaIP4Fogi2GFYITg2c?= =?us-ascii?q?1hT+FCAKHLpFABwKOW40ikR+BQYILcIMTgiAOCY4Xb41/gRkBAQ?= Received: from esa1.dell-outbound2.iphmx.com ([68.232.153.201]) by esa5.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jun 2018 10:58:39 -0500 From: Received: from ausc60pc101.us.dell.com ([143.166.85.206]) by esa1.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jun 2018 21:54:14 +0600 X-LoopCount0: from 10.166.136.215 X-IronPort-AV: E=Sophos;i="5.49,476,1520917200"; d="scan'208";a="1258277663" X-DLP: DLP_GlobalPCIDSS To: CC: , , , Thread-Topic: [edk2] How to Interpret ReadKeyStrokeEX Data Thread-Index: AQHT/BNUB6LohffXK06HpvE6bJIpvKRQP+Cw Date: Mon, 4 Jun 2018 16:00:07 +0000 Message-ID: <0c4414f8ae2742a6af4138e9b34714af@ausx13mps339.AMER.DELL.COM> References: <3e835c29938d49ea8d285385429870ad@ausx13mps339.AMER.DELL.COM> <734D49CCEBEEF84792F5B80ED585239D5BD232B9@SHSMSX104.ccr.corp.intel.com> <5108c0244ffb45ccb0208dd0a1ed2beb@ausx13mps339.AMER.DELL.COM> <51978119-FF46-425A-A7E9-8C1EBD3C7B1E@apple.com> In-Reply-To: <51978119-FF46-425A-A7E9-8C1EBD3C7B1E@apple.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titusconfig: Internal Use 04051212 x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvIiwiaWQiOiIzOTFjMGYwOC00ZjBjLTQ2ZmMtOWU5NC05NGVmZGIyODBiODgiLCJwcm9wcyI6W3sibiI6IkNsYXNzaWZpY2F0aW9uIiwidmFscyI6W3sidmFsdWUiOiJJbnRlcm5hbCBVc2UifV19LHsibiI6IlN1YmxhYmVscyIsInZhbHMiOltdfSx7Im4iOiJFeHRlcm5hbENvcnJlc3BvbmRlbmNlIiwidmFscyI6W3sidmFsdWUiOiJObyJ9XX1dfSwiU3ViamVjdExhYmVscyI6W10sIlRNQ1ZlcnNpb24iOiIxNi4yLjExLjAiLCJUcnVzdGVkTGFiZWxIYXNoIjoibUQ1eTFrK09hcUJMS2NLNHYyZ2Z6ZXA0ZE9uYzdPWUZQbFlsRWduSWxnST0ifQ== x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.143.18.86] 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:00:39 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dell - Internal Use - Confidential =20 > From: afish@apple.com [mailto:afish@apple.com]=20 > > The big picture difference is the original SimpleTextIn was the least com= mon > denominator with a serial terminal. The Ex version added more info about > keyboards, so richer info on modifier keys. I get that. But I fail to see how that affects SimpleTextInEx behavior or what the UEFI spec has to say about it. As I said earlier, the question I am raising is when SimpleTextInEx returns 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? 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.