d255f4f72a
Updating the 4.1 branches with backported mainline support for the galileo. a5327464dad9 iio: light: add support for ROHM BH1710/BH1715/BH1721/BH1750/BH1751 ambient light sensors 7a868ce12675 pwm-pca9685: enable ACPI device found on Galileo Gen2 9f169f0f6493 at24: enable ACPI device found on Galileo Gen2 8b662e6343a1 gpio: pca953x: support ACPI devices found on Galileo Gen2 a9939d26a6a0 gpio: pca953x: store driver_data for future use 52355b7a7fee mfd: intel_quark_i2c_gpio: support devices behind i2c bus ba850c2a9965 mfd: intel_quark_i2c_gpio: load gpio driver first 8b322e7df2bf mfd: core: redo ACPI matching of the children devices 23c1fb4bc37d i2c / ACPI: Rework I2C device scanning f7eea071b03c gpio / ACPI: Return -EPROBE_DEFER if the gpiochip was not found bdc90004c8d5 GPIO / ACPI: export acpi_gpiochip_request(free)_interrupts for module use 447db37b6df9 gpio / ACPI: Add support for retrieving GpioInt resources from a device edce965b0881 i2c: fix leaked device refcount on of_find_i2c_* error path f9b93689fdf5 i2c: core: only use set_scl for bus recovery after calling prepare_recovery a10a703575bd i2c: core: Reduce stack size of acpi_i2c_space_handler() ad91512127cd i2c: core: fix typo in comment b16ba95782f1 i2c: check for proper length of the reg property 028a8d9209b7 i2c: slave: add error messages to slave core 58551fe2320d i2c / ACPI: Assign IRQ for devices that have GpioInt automatically 85153945ad9e i2c / ACPI: Use 0 to indicate that device does not have interrupt assigned (From OE-Core rev: 2ff6c2ca2e22eaef37ccb4025bc0b78c42695eed) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.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 = "nodistro") 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 (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
bitbake: Git repository: http://git.openembedded.org/bitbake/ Mailing list: bitbake-devel@lists.openembedded.org
documentation: Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/ Mailing list: yocto@yoctoproject.org
meta-yocto(-bsp): Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto(-bsp) Mailing list: poky@yoctoproject.org
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.
Git repository: http://git.openembedded.org/openembedded-core/
Mailing list: 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.