75b0fb2ab9
* While working with a new capacitive touchscreen it was found
that the existing udev rule that creates the
/dev/input/touchscreen0 symlink was too restrictive and did not
match the MODALAIS entry for this touchscreen. which is:
MODALIAS=input:b0018v0000p0000e0000-e0,1,3,k14A,ra0,1,2F,35,36,39,mlsfw
* By looking at the input_print_modalias function in the Linux
kernel drivers/input/input.c file and referencing the meaning
of the evbits and attributes of the input_dev structure it seems
that for identification of a touchscreen the match with ,18
which was matching part of the absbit structure is overkill.
* It seems that the absbit entry is used for devices like
touchscreens and if that the the "a" is followed by 0 and 1 this
is sufficient.
* So the logic has now been changed to check for the "e" 0 and 3
values which correspond to EV_SYN and EV_ABS, then check for
the "a" attribute with 0 and 1.
* More information and history for this can be found at:
http://patchwork.openembedded.org/patch/25093/
http://thread.gmane.org/gmane.comp.handhelds.openembedded.core
* This patch mirrors a patch done by:
Andrea Adami <andrea.adami@gmail.com>
(From OE-Core rev: d95a9b516861594bc89c7ee8079bab2904703ad2)
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a complete prepackaged build system and development environment. It features support for building customised embedded device style images. There are reference demo images featuring a X11/Matchbox/GTK themed UI called Sato. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK with IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of layers which extend the systems capabilities in a modular way.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information e.g. for the hardware support. Poky is in turn a component of the Yocto Project.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at: http://yoctoproject.org/documentation
OpenEmbedded-Core is a layer containing the core metadata for current versions of OpenEmbedded. It is distro-less (can build a functional image with DISTRO = "") and contains only emulated machine support.
For information about OpenEmbedded, see the OpenEmbedded website: http://www.openembedded.org/
Where to Send Patches
As Poky is an integration repository, patches against the various components should be sent to their respective upstreams.
bitbake: bitbake-devel@lists.openembedded.org
meta-yocto: poky@yoctoproject.org
Most everything else should be sent to the OpenEmbedded Core mailing list. If in doubt, check the oe-core git repository for the content you intend to modify. Before sending, be sure the patches apply cleanly to the current oe-core git repository. openembedded-core@lists.openembedded.org
Note: The scripts directory should be treated with extra care as it is a mix of oe-core and poky-specific files.