diff options
author | Darren Hart <dvhart@linux.intel.com> | 2011-03-15 17:05:51 -0700 |
---|---|---|
committer | Saul Wold <sgw@linux.intel.com> | 2011-03-16 08:08:17 -0700 |
commit | 6d990c8ca179275b19322214d9a1088b7e54cc98 (patch) | |
tree | a829a14f43c336144e9d27f1ae1bfda16226bc0c /meta/recipes-bsp | |
parent | d065ae731193e242cd1326e37af802202d0ae1de (diff) | |
download | poky-6d990c8ca179275b19322214d9a1088b7e54cc98.tar.gz |
formfactor: Assume HAVE_TOUCHSCREEN=0
If no machine specific formfactor is found, the formfactor config defaults
to HAVE_TOUCHSCREEN=1. The result is for the matchbox session to disable
the cursor. This can lead to a lot of churn sorting out why the cursor doesn't
appear: xorg bug, xorg driver bug, kernel drm driver bug, kms bug, many
of which appear when searching for invisible cursor on the web.
On the other hand, if a cursor appears on a touchscreen device, one is much
more likely to reach a correct conclusion: "I need to set HAVE_TOUCHSCREEN=1
in my custom machine formfactor config". Which likely exists or is needed for
other formfactor specific things such as dpi, screen size, rotation, etc.
(From OE-Core rev: 361f7536e75893c51cdcb2c6449e300ee2bbd53a)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-bsp')
-rwxr-xr-x | meta/recipes-bsp/formfactor/files/config | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/recipes-bsp/formfactor/files/config b/meta/recipes-bsp/formfactor/files/config index ed15d9e031..e936916b43 100755 --- a/meta/recipes-bsp/formfactor/files/config +++ b/meta/recipes-bsp/formfactor/files/config | |||
@@ -5,7 +5,7 @@ if [ -e /etc/formfactor/machconfig ]; then | |||
5 | fi | 5 | fi |
6 | 6 | ||
7 | if [ -z "$HAVE_TOUCHSCREEN" ]; then | 7 | if [ -z "$HAVE_TOUCHSCREEN" ]; then |
8 | HAVE_TOUCHSCREEN=1 | 8 | HAVE_TOUCHSCREEN=0 |
9 | fi | 9 | fi |
10 | 10 | ||
11 | if [ -z "$HAVE_KEYBOARD" ]; then | 11 | if [ -z "$HAVE_KEYBOARD" ]; then |