[Fw_Os_Forum] How to detect devices that support touch
Aaron.Pop at congatec.com
Aaron.Pop at congatec.com
Thu Mar 3 13:08:38 EST 2016
EDK implements a console splitter for input device. This console splitter
creates a absolute pointer protocol instance that does not contain a
device path.
You can locate a handle buffer of all the handles that contain an absolute
pointer protocol, and then you can go through the handles and make sure
that there is a handle that contains a device path. If there are no
absolute pointer instances that contain a device path.
From: Venkat Gorla <venkatagorla at gmail.com>
To: fw_os_forum at mailman.uefi.org,
Date: 03/03/2016 01:06 AM
Subject: [Fw_Os_Forum] How to detect devices that support touch
Sent by: fw_os_forum-bounces at mailman.uefi.org
Hello,
We are making some product changes that are specific to touch devices
(such as a tablet) in the Windows pre-boot UEFI environment. I am
referring the following document for the UEFI specification:
http://www.uefi.org/sites/default/files/resources/UEFI_Spec_2_3_1.pdf
However I haven't been able to definitively check for touch devices vs
non-touch devices using the specification.
For example, querying for the absolute pointer protocol interface succeeds
even on a non-touch device such as a laptop or a desktop. Additionally,
the absolute max X and max Y values are also being reported as non-zero
when I query the "Mode" of the protocol interface.
So my question is how do I filter out the negative scenarios (devices that
don't support touch) using the UEFI specification?
Any pointers or help will is much appreciated.
Thanks,
Venkat _______________________________________________
Fw_os_forum mailing list
Fw_os_forum at mailman.uefi.org
http://lists.mailman.uefi.org/mailman/listinfo/fw_os_forum
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mailman.uefi.org/pipermail/fw_os_forum/attachments/20160303/d661db1f/attachment.html>
More information about the Fw_os_forum
mailing list