aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-bsp/formfactor/files/config
AgeCommit message (Collapse)Author
2016-03-06formfactor: assume a keyboard is plugged inRoss Burton
A sensible assumption is that BSPs have a USB keyboard and mouse connected unless told otherwise, so flip the logic in the formfactor config script that previously assumed that a keyboard was not connected by default. [ YOCTO #9174 ] Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-08-21formfactor: Clean up errors on machines without framebuffersRichard Purdie
If fbset can't find a framebuffer we end up with a mess on the console. We might as well avoid doing this on machines without a framebuffer. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-08formfactor: use full path to fbsetPaul Eggleton
When using rootless X, /usr/sbin is not in PATH and thus running "fbset" will fail; so specify /usr/sbin/fbset instead. Fixes [YOCTO #1986] Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-03-16formfactor: Assume HAVE_TOUCHSCREEN=0Darren Hart
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>
2010-08-27Major layout change to the packages directoryRichard Purdie
Having one monolithic packages directory makes it hard to find things and is generally overwhelming. This commit splits it into several logical sections roughly based on function, recipes.txt gives more information about the classifications used. The opportunity is also used to switch from "packages" to "recipes" as used in OpenEmbedded as the term "packages" can be confusing to people and has many different meanings. Not all recipes have been classified yet, this is just a first pass at separating things out. Some packages are moved to meta-extras as they're no longer actively used or maintained. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>