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:54:29 +0000 |
| commit | 2bbeab25c519c2ae419981de1e313438e6e1af5d (patch) | |
| tree | 858caaca322d7404ca12a03cc154c2aadf73f9c8 /meta/recipes-bsp/zaurusd | |
| parent | 9a9ebb03b90ea4fdfcda915eca1664b4c678a52c (diff) | |
| download | poky-2bbeab25c519c2ae419981de1e313438e6e1af5d.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/zaurusd')
0 files changed, 0 insertions, 0 deletions