diff options
| author | Darren Hart <dvhart@linux.intel.com> | 2011-03-15 17:05:51 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-03-16 13:39:09 +0000 |
| commit | 361f7536e75893c51cdcb2c6449e300ee2bbd53a (patch) | |
| tree | cdbe0a4b510b9244d2d4084466cce48be8f91ec6 /meta/recipes-bsp/v86d | |
| parent | 845770e12b6ed51db3179f42de6b8deacdff5093 (diff) | |
| download | openembedded-core-361f7536e75893c51cdcb2c6449e300ee2bbd53a.tar.gz openembedded-core-361f7536e75893c51cdcb2c6449e300ee2bbd53a.tar.bz2 openembedded-core-361f7536e75893c51cdcb2c6449e300ee2bbd53a.tar.xz openembedded-core-361f7536e75893c51cdcb2c6449e300ee2bbd53a.zip | |
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.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Diffstat (limited to 'meta/recipes-bsp/v86d')
0 files changed, 0 insertions, 0 deletions