path: root/meta/recipes-bsp/formfactor
diff options
authorDarren Hart <>2011-03-16 00:05:51 (GMT)
committerRichard Purdie <>2011-03-16 13:54:29 (GMT)
commit2bbeab25c519c2ae419981de1e313438e6e1af5d (patch)
tree858caaca322d7404ca12a03cc154c2aadf73f9c8 /meta/recipes-bsp/formfactor
parent9a9ebb03b90ea4fdfcda915eca1664b4c678a52c (diff)
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 <> Signed-off-by: Richard Purdie <>
Diffstat (limited to 'meta/recipes-bsp/formfactor')
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/recipes-bsp/formfactor/files/config b/meta/recipes-bsp/formfactor/files/config
index ed15d9e..e936916 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
5fi 5fi
6 6
7if [ -z "$HAVE_TOUCHSCREEN" ]; then 7if [ -z "$HAVE_TOUCHSCREEN" ]; then
9fi 9fi
10 10
11if [ -z "$HAVE_KEYBOARD" ]; then 11if [ -z "$HAVE_KEYBOARD" ]; then