72a9b812c9
Release notes libinput 1.26.1 is now available. A few semi-exciting things, the rest the usual bugfixes you'd expect for a point release. Touchpads now special-case Shift for disable-while-typing, so typing keys with shift down will trigger DWT. Tablets can now be calibrated if libwacom says the tablet is a display tablet. The hid-uclogic kernel driver doesn't set INPUT_PROP_DIRECT so any device handled by that driver didn't have calibration available. Fixed now, provided your tablet is recognised by libwacom. The direction of the first tablet pad relative dial was fixed, it was upside-down. Our debugging tools now support --set-pressure-range for the new tablet tool pressure range configuration added in 1.26 and --set-calibration for the calibration matrix that's been around for a while. The libinput debug-tablet tool now also supports all commandline options that debug-events and debug-gui support. And of course a varied assortment of device specific quirks and fixes. Release notes libinput 1.26.0 is now available. It's been a while since the last release but we have a few notable changes in here: Touchpads can now configure a clickfinger button map, so you can change whether two- or three-finger click means a right or middle click. See libinput_device_config_click_set_clickfinger_button_map Tablet pads now have an API for relative dials. These are typically wheel-like (e.g. Huion Inspiroy 2) or ring-like (e.g. Huion Inspiroy Dial 2) physical devices that send REL_WHEEL and REL_HWHEEL. libinput now provides these via libinput_event_tablet_pad_get_dial_delta_v120() in much the same manner as the v120-based scroll wheel API. A new configuration option for tablet tools allow reducing the available logical range. This is useful for users that want the tool to register only when some physical pressure value is reached, or to reduce the maximum amount of pressure needed to reach the logical maximum pressure. See libinput_tablet_tool_config_pressure_range_set() and friends. Tablet tools can now use BTN_STYLUS3 too and tablet pad strip support should now work for non-Wacom devices, where the kernel driver implements it. Huion tablets (well, and all vendors that use the 256C vendor id) now have a fallback resolution set. This is going to be wrong on most devices but at least it will make those tablets work out of the box, instead of failing with the "missing tablet capabilities: resolution" log message. And of course a varied assortment of device specific quirks and fixes. (From OE-Core rev: 341578e76de1189a2373672e76034e1c99c6783e) Signed-off-by: Markus Volk <f_l_k@t-online.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for 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 BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.