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>
937 B
Executable File
#!/bin/sh
if [ -e /etc/formfactor/machconfig ]; then . /etc/formfactor/machconfig fi
if [ -z "$HAVE_TOUCHSCREEN" ]; then HAVE_TOUCHSCREEN=0 fi
if [ -z "$HAVE_KEYBOARD" ]; then HAVE_KEYBOARD=0 fi
if [ -z "$HAVE_KEYBOARD_PORTRAIT" ]; then HAVE_KEYBOARD_PORTRAIT=0 fi
if [ -z "$HAVE_KEYBOARD_LANDSCAPE" ]; then HAVE_KEYBOARD_LANDSCAPE=0 fi
if [ -z "$DISPLAY_CAN_ROTATE" ]; then DISPLAY_CAN_ROTATE=0 fi
if [ -z "$DISPLAY_ORIENTATION" ]; then DISPLAY_ORIENTATION=0 fi
if [ -z "$DISPLAY_WIDTH_PIXELS" ]; then
DISPLAY_WIDTH_PIXELS=fbset | grep geometry | awk '{ print $2 }'
fi
if [ -z "$DISPLAY_HEIGHT_PIXELS" ]; then
DISPLAY_HEIGHT_PIXELS=fbset | grep geometry | awk '{ print $3 }'
fi
if [ -z "$DISPLAY_BPP" ]; then
DISPLAY_BPP=fbset | grep geometry | awk '{ print $6 }'
fi
No way to guess these or have any defaults
#DISPLAY_WIDTH_MM #DISPLAY_HEIGHT_MM #DISPLAY_SUBPIXEL_ORDER=