From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from IMSVA.IN.MEGATRENDS.COM (Webmail.amiindia.co.in [203.199.198.232]) (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 5220E21E49BBB for ; Mon, 21 Aug 2017 23:32:58 -0700 (PDT) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 89E2E82055; Tue, 22 Aug 2017 12:07:56 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7DC058204A; Tue, 22 Aug 2017 12:07:56 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS; Tue, 22 Aug 2017 12:07:56 +0530 (IST) Received: from VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5]) by Venus2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b%14]) with mapi id 14.03.0248.002; Tue, 22 Aug 2017 12:05:24 +0530 From: Ramesh R. To: Michael Zimmermann , edk2-devel-01 Thread-Topic: [edk2] meaning of EFI_ABSOLUTE_POINTER_PROTOCOL axis values Thread-Index: AQHTGpxlhjzs02QqOEiTFfFmbC+ssKKP62sw Date: Tue, 22 Aug 2017 06:35:23 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.84.17] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1600-8.1.0.1062-23274.005 X-TM-AS-Result: No--3.900-5.0-31-10 X-imss-scan-details: No--3.900-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.1.1062-23274.005 X-TMASE-Result: 10--3.900300-10.000000 X-TMASE-MatchedRID: cgbqQT5W8hf1LtJ9LFjjYxWCVBr+Ay98guwtqyXlE6FnerzbhugqstEv k7xjlIKi9DbUuStLCBVRmAGdyGr3VgTI9DBbkEFq4EprSlQmFqAZskwWqoib3AbYcy9YQl6e7lE HFdtaZK1IQM6HKCx3HR1wtJbe4ntI8Rof46HMoPl8qY334HYDD5JOcXMQc4jBaOWLD7G8i106W3 3UwHDV5uLzNWBegCW2OubYLCVnBVFYF3qW3Je6+69TGfqMIqrtOEiZT/q7O4YM0+NjR4OYq34+N UOxPOzMUj1DRYYE6MAz5e6RzMD72mpd/KxTjXtrj7gIwnVKh1zdoAFkkpXgFlyQCnflp4PmEr8E AKxXM1y1rnR+ZHUF+XRIPNHXw7ge4hgG5y/uHEJ+3BndfXUhXQ== X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0,39:0-0 Subject: Re: meaning of EFI_ABSOLUTE_POINTER_PROTOCOL axis values X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Aug 2017 06:32:58 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Michael, The values are related to the display device resolution. Each Protocol h= as the EFI_ABSOLUTE_POINTER_MODE defined and it has the value of the actual= screen hardware resolution ( not the current display resolution).=20 The touched values are based screen hardware resolution.=20 Thanks, Ramesh -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Mich= ael Zimmermann Sent: 21 August 2017 22:12 To: edk2-devel-01 Subject: [edk2] meaning of EFI_ABSOLUTE_POINTER_PROTOCOL axis values Do the axis-values returned by this protocol need to have any relation to t= he device's screen so I can reliably calculate which pixel was touched?(at = least with the rule of three). If not every application using the touchscreen would have to provide it's o= wn calibration tool and store the results in a config. Thanks Michael _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel