[yocto] Release Candidate Build for yocto-2.1_M2.rc3_M2.rc3 now available.

-e A release candidate build for yocto-2.1_M2.rc3 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M2.rc3 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 5640cd6bc13a520ba4bf73c94fe9b739ac23c7e6 meta-fsl-arm :

[linux-yocto] USB mouse is not working in Yocto image

Dear, I have created the qt4e-demo-image using poky. It was successfully created. But USB mouse is not working. What could be the problem? How do I enable USB host & X11 features in my distro ? Host system : Ubuntu 14.04 Target machine : AM437x-evm If you need any more details, please let

[linux-yocto] [PATCH 3/7] pca9685: PCA9685 PWM and GPIO multi-function device.

From: Josef Ahmad There is also a driver for the same chip in drivers/pwm. This version has support for setting the output in GPIO mode in addition to the PWM mode. Upstream-status: Forward-ported from Intel IOT Develper Kit Quark BSP Signed-off-by: Ismo Puustinen

[linux-yocto] [PATCH 1/7] acpi: added a custom DSDT file.

From: Ismo Puustinen The file has fixed GPIO IRQ assignment and moved SPI devices to be under the SPI bus in the ACPI definitions as assumed by ACPI version 5. Upstream-status: Inappropriate, custom firmware Signed-off-by: Ismo Puustinen ---

[linux-yocto] [PATCH 5/7] staging:iio: add support for ADC1x8s102.

From: Todor Minchev Original author is Bogdan Pricop . Upstream-status: Forward-ported from Intel IOT Develper Kit Quark BSP Signed-off-by: Ismo Puustinen --- drivers/staging/iio/adc/Kconfig | 13 ++

[linux-yocto] [PATCH 7/7] gpio-pca953x: add "drive" property.

From: Ismo Puustinen Galileo gen 2 has support for setting GPIO modes. Expose these properties through the GPIO sysfs interface. This approach is bit hacky, since it changes the interface semantics. The original patch was by Josef Ahmad

[linux-yocto] [PATCH 2/7] gpio: pca953x: provide GPIO base based on _UID

From: Andy Shevchenko Custom kernel for Intel Galileo Gen2 provides and moreover libmraa relies on the continuous GPIO space. To do such we have to configure GPIO base per each GPIO expander. The only value we can use is the ACPI _UID. Signed-off-by: Andy

[linux-yocto] [PATCH 4/7] spi-pxa2xx: fixed ACPI-based enumeration of SPI devices.

From: Ismo Puustinen Slave devices were not enumerated by ACPI data because the ACPI handle for the spi-pxa2xx controller was NULL if it was itself enumerated by PCI. Upstream-status: Inappropriate, real fix forthcoming Signed-off-by: Ismo Puustinen

[linux-yocto] [PATCH 0/7] Galileo Patches - non-upstreamed

Bruce, This is this is a set of patches for 4.1, there is another similar that I will be sending shortly for 4.4. The only difference between the 4.1 and 4.4 patch set is 07/07 gpio-pca953x does not apply to 4.4, the other 6 do These patches are mostly targeted to Galileo Gen2 and deal with

[yocto] [meta-security][PATCH] nmap: update to version 7.0.1

fixed WARNING: QA Issue: /usr/bin/ndiff_nmap contained in package nmap requires /usr/bin/python2.7, but no providers found in its RDEPENDS [file-rdeps] Signed-off-by: Armin Kuster --- recipes-security/nmap/{nmap_7.00.bb => nmap_7.01.bb} | 8 ++-- 1 file changed, 6

Re: [linux-yocto] [PATCH v2 00/12] intel-common: add intel-developer-drivers.scc to preempt-rt BSPS

On 02/12/2016 07:48 PM, Paul Gortmaker wrote: > [[PATCH v2 00/12] intel-common: add intel-developer-drivers.scc to preempt-rt > BSPS] On 12/02/2016 (Fri 17:42) California Sullivan wrote: > >> Since we include the developer ktype we should include developer drivers. >> >> Signed-off-by: California

[yocto] Release Candidate Build for yocto-2.1_M2.rc2_M2.rc2 now available.

A release candidate build for yocto-2.1_M2.rc2 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M2.rc2 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 5640cd6bc13a520ba4bf73c94fe9b739ac23c7e6 meta-fsl-arm :

Re: [linux-yocto] [PATCH 0/3] Backport Capabilities Patches to 4.1

On Tue, 2016-02-16 at 09:38 -0500, Bruce Ashfield wrote: > On 16-02-11 11:16 AM, Saul Wold wrote: > > > > Add the Capabilities support that some projects would like to use > > in the linux-yocto-4.1 kernel. > > > > These 3 are all upstream in 4.3 or later > > I've staged the patches, and pushed

[yocto] [meta-security][PATCH 1/2] suricata: update to 3.0

removed patch no longer needded. LIC_FILES_CHKSUM changed do to copyright date updates. Signed-off-by: Armin Kuster --- .../suricata/files/no_pcap_pkgconf_check.patch | 26 -- recipes-security/suricata/libhtp_0.5.18.bb | 2 +-

Re: [linux-yocto] [PATCH 0/3] Backport Capabilities Patches to 4.1

On 16-02-11 11:16 AM, Saul Wold wrote: Add the Capabilities support that some projects would like to use in the linux-yocto-4.1 kernel. These 3 are all upstream in 4.3 or later I've staged the patches, and pushed them out. SRCREV updates to follow shortly (preferably after the 4.4 issues

Re: [yocto] jethro 2.0.1/ubi-utils not installed on target

On 16 February 2016 at 09:03, wrote: > It seems to be insufficient to add mtd-utils to a packagegroup[1] and add > this to the image for it to be installed in the image. > The package is being built and I can install it afterwards e.g. opkg > install

[yocto] jethro 2.0.1/ubi-utils not installed on target

Hi, I would like to have ubi-utils, which is part of mtd-utils, installed on my target. It seems to be insufficient to add mtd-utils to a packagegroup[1] and add this to the image for it to be installed in the image. The package is being built and I can install it afterwards e.g. opkg

Re: [yocto] Dropping Debian 7 as supported?

On Thursday 11 Feb 2016 14:32:50 Burton, Ross wrote: > On 11 February 2016 at 14:21, Nick Leverton wrote: > > Possibly a little early - Debian 7 will be going onto LTS security support > > for > > two years, starting some time this month. Quoting from > >