From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=68.232.149.229; helo=esa6.dell-outbound.iphmx.com; envelope-from=jim.dailey@dell.com; receiver=edk2-devel@lists.01.org Received: from esa6.dell-outbound.iphmx.com (esa6.dell-outbound.iphmx.com [68.232.149.229]) (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 C351320971732 for ; Mon, 4 Jun 2018 09:28:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1528129717; x=1559665717; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=04t/R0JYBjKCeYiAf9hoCpoQu0O9xA3JlaCqrSMCecE=; b=ZAjmXyC55cAKc/XXNBJWnRMw/0W7tL9i+CZ5NSkGG+biGiZJ/sZFchem 2B3Iymu3Ij2eqTBnEJcxv38XRcEJ0zONFMgAXhoWxFAWgojMj0YMzzf/D mGXiD/cEDk4LKYSkcRkEANpgEB06O0fTSmerCCPnhoFRcyBGMH+65S/c+ A=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2H6AAC3ZxVbmGOa6ERcGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYQXDn8oCphggXmUSxSBZAsYCwuEPgKCESE1FwECAQEBAQEBAgE?= =?us-ascii?q?BAhABAQEBAQgLCwYoIwyCNSIRegEBAQEBAQEBAU0CDWMBAQEDAQEBODQLBQcEA?= =?us-ascii?q?gEIEQQBAQEeCQcnAR4JCAIEDgUIgxoCgWcDDQgPqQqHBhWBJIFjBYIthhWCE4N?= =?us-ascii?q?nNYMRAQSBKgERAgElMRSFCAKHLpFABwKFbIUXg1iBRIN4h2aJeIcngUIBgRhxc?= =?us-ascii?q?FCCQ4IgDgmILiuFPm+Nf4EZAQE?= X-IPAS-Result: =?us-ascii?q?A2H6AAC3ZxVbmGOa6ERcGQEBAQEBAQEBAQEBAQcBAQEBAYQ?= =?us-ascii?q?XDn8oCphggXmUSxSBZAsYCwuEPgKCESE1FwECAQEBAQEBAgEBAhABAQEBAQgLC?= =?us-ascii?q?wYoIwyCNSIRegEBAQEBAQEBAU0CDWMBAQEDAQEBODQLBQcEAgEIEQQBAQEeCQc?= =?us-ascii?q?nAR4JCAIEDgUIgxoCgWcDDQgPqQqHBhWBJIFjBYIthhWCE4NnNYMRAQSBKgERA?= =?us-ascii?q?gElMRSFCAKHLpFABwKFbIUXg1iBRIN4h2aJeIcngUIBgRhxcFCCQ4IgDgmILiu?= =?us-ascii?q?FPm+Nf4EZAQE?= Received: from esa6.dell-outbound2.iphmx.com ([68.232.154.99]) by esa6.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jun 2018 11:28:36 -0500 From: Received: from ausc60pc101.us.dell.com ([143.166.85.206]) by esa6.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jun 2018 22:28:35 +0600 X-LoopCount0: from 10.166.136.212 X-IronPort-AV: E=Sophos;i="5.49,476,1520917200"; d="scan'208";a="1258285277" X-DLP: DLP_GlobalPCIDSS To: CC: , , , , Thread-Topic: [edk2] How to Interpret ReadKeyStrokeEX Data Thread-Index: AdP51a/hVUcRd8ZXRbW9WoFUsUlqeAB2jMWgABXhBjAAEaRtAAACc8mAAAAWzAD//5AC0f///kwQ Date: Mon, 4 Jun 2018 16:28:34 +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: msip_labels: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.143.242.75] 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:28:38 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Yes! Sorry if I was unclear. -----Original Message----- From: Carsey, Jaben [mailto:jaben.carsey@intel.com]=20 Sent: Monday, June 4, 2018 11:22 AM To: Dailey, Jim Cc: afish@apple.com; Ni, Ruiyu; edk2-devel@lists.01.org; felixp@mail.ru; R= othman, Michael A Subject: Re: [edk2] How to Interpret ReadKeyStrokeEX Data Jim, I think I see what you mean. If scan code is 0, then don't test the shift= 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