date:20161031

Re: [yocto] Package relation between package.manifest and license.manifest

2016-10-31 Thread Hugo Heutinck

I am using the Jethro branch, which one are you using ?

For me this provides quite a list of delta's, some seem to be related (e.g.
the dbus, dbus-glib, dbus-lib vs. dbus-1),
but others are not (e.g. expat).

Was something on license file generation improved between Jethro and more
recent branches  ?

--- /tmp/a.manifest
+++ /tmp/package.manifest
@@ -24,9 +24,7 @@
 cracklib
 cronie
 curl
-dbus
-dbus-glib
-dbus-lib
+dbus-1
 debianutils
 debianutils-run-parts
 diffutils
@@ -39,26 +37,16 @@
 ed
 elfutils
 ethtool
-expat
 factory-tools
 file
 findutils
 firmware-update
 flex
-freetype
 fuser
 gawk
-gdbm
-gdbm-compat
-glib-2.0
-glib-2.0-locale-en-gb
-glibc
 glibc-binary-localedata-en-gb
 glibc-binary-localedata-en-us
 glibc-locale-en-gb
-gmp
-gnutls
-gnutls-openssl
 grep
 gzip
 i2c-tools
@@ -75,46 +63,70 @@
 iputils-tracepath
 iputils-tracepath6
 iputils-traceroute6
-json-c
 kernel-crc-env
 killall
 kmod
 led-control
 less
-libacl
-libattr
-libbz2
-libcap
-libcomerr
-libcrypto
-libcurl
-libdw
-libe2p
-libelf
-libestr
+libacl1
+libattr1
+libblkid1
+libbz2-0
+libc6
+libcap2
+libcom-err2
+libcrypto1.0.0
+libcurl4
+libdbus-1-3
+libdbus-glib-1-2
+libdw1
+libe2p2
+libelf1
+libestr0
 libevent
-libext2fs
-libffi
-libgcc
+libexpat1
+libext2fs2
+libfdisk1
+libffi6
+libfreetype6
+libgcc1
 libgcrypt
-libgpg-error
-libkmod
+libgdbm-compat4
+libgdbm4
+libglib-2.0-0
+libglib-2.0-locale-en-gb
+libgmp10
+libgnutls-openssl27
+libgnutls28
+libgpg-error0
+libjson-c2
+libkmod2
 liblogging
-liblzma
-libpci
-libpcre
-libpython2
-libss
-libssl
-libstdc++
-libsysfs
-libsystemd
-libudev
-libwrap
-libx11
-libxau
-libxcb
-libxdmcp
+liblzma5
+libmount1
+libncurses5
+libncursesw5
+libpci3
+libpcre1
+libperl5
+libpopt0
+libpython2.7-1.0
+libreadline6
+libsmartcols1
+libss2
+libssl1.0.0
+libstdc++6
+libsysfs2
+libsystemd0
+libtinfo5
+libudev1
+libuuid1
+libwrap0
+libx11-6
+libxau6
+libxcb1
+libxdmcp6
+libz1
 locale-base-en-gb
 locale-base-en-us
 logrotate
@@ -130,9 +142,6 @@
 mktemp
 modutils-initscripts
 ncurses
-ncurses-libncurses
-ncurses-libncursesw
-ncurses-libtinfo
 ncurses-terminfo
 ncurses-terminfo-base
 net-tools
@@ -167,8 +176,6 @@
 pciutils
 pciutils-ids
 perl
-perl-lib
-popt
 procps
 psmisc
 psplash
@@ -208,7 +215,6 @@
 python-unittest
 python-xml
 python-xmlrpc
-readline
 rsyslog
 run-postinsts
 sed
@@ -232,11 +238,6 @@
 util-linux
 util-linux-cfdisk
 util-linux-fdisk
-util-linux-libblkid
-util-linux-libfdisk
-util-linux-libmount
-util-linux-libsmartcols
-util-linux-libuuid
 util-linux-losetup
 util-linux-mkfs
 util-linux-mount


2016-10-28 4:25 GMT+02:00 Khem Raj :

>
> On Oct 26, 2016, at 5:45 AM, Hugo Heutinck  wrote:
>
> Question: What is the relation between the package.manifest and
> license.manifest ?
>
> After a yocto poky based image has been built there are 2 files in the
> licenses directory "tmp/deploy/licenses/*image_name-datestamp*"
>
> One is the package.manifest, which if understood correctly is a list of
> all packages included in the image.
>
> The second file is the license.manifest, but this one contains besides the
> package name also the version, recipe name and license of the package.
>
> However if I compare the package names in both lists, there seem to be a
> number of packages in the license.manifest that are not part of the
> package.manifest. E.g. "readline, popt, expat, freetype".
>
> Is the license.manifest a list of all items in the package.manifest +
> ?build dependencies? or something ?
>
>
> They should be same.
>
> try something like this
> cat license.manifest | grep "PACKAGE NAME: " | sed "s/PACKAGE NAME: //“ >
> a.manifest
> diff a.manifest package.manifest
>
> For me both files comes out same.
>
>
>
> Regards,
>
> H.Heutinck
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How do I "remove" my application from ROOTFS and add it to INITRD ?

2016-10-31 Thread Lars Larsen



I have a recipie that builds and work fine.

It producue a rootfs.img and an initrd, all nicely wrapped in bootable 
ISO and hdd images



It all ends in rootfs.img , but I would like it to end in initrd.
(this would makes my update procedure towards costumers simpler, since 
we only have handle distribution of the initrd file)


My main recipe uses IMAGE__INSTALL to add my application - that contains 
a bunch of recipes for compiled modules, and a directory structure with 
a number of scripts.


So after analyzing bootimg.bbclass I can see, that I need to add a 
cpio.gz image of my application to get the INITRD variable, and remove 
it from ROOTFS


But how do I achieve this, in a compatible manor ?

-Lars

--

Best Regards
Lars Larsen

F.Poulsen Engineering Aps
Tjørnager 16
4330 Hvalsø
Denmark
+45 29802784
www.visionweeding.com

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] esdk without using Poky?

2016-10-31 Thread Gary Thomas


I'm trying to build an extensible SDK (eSDK) for my target and running into
a few problems.

  gthomas@zeus:~$ /work/tmp/mlb-glibc-x86_64-arm-toolchain-ext-2.2+snapshot.sh
  MLB @SDK_TITLE@ Associates Embedded (Poky/Yocto Powered) Extensible SDK 
installer version 2.2+snapshot
  
==
  Enter target directory for SDK (default: ~/mlb_sdk):
  You are about to install the SDK to "/home/gthomas/mlb_sdk". Proceed[Y/n]? y
  Extracting SDK.done
  Setting it up...
  Extracting buildtools...
  Preparing build system...
  Error: 'meta-poky/conf' must be a directory containing local.conf & 
bblayers.conf

The first thing I notice is the banner which should read:
  MLB & Associates Embedded (Poky/Yocto Powered) Extensible SDK installer 
version 2.2+snapshot
  


The second is that I use my own distribution (not poky).  How can I
build an eSDK using my distribution?

Once I ran into this error, I tried rebuilding using the [old] SDK.
I noticed that it seemed to rebuild [most] everything all over again.
Is there no shared state / reusable components between the eSDK and SDK?

Finally, since I had to install SDK and not eSDK, I'm missing some tools
I was hoping to have.  I want to build PRU programs for the BeagleBoneBlack
and I'm using meta-ti to import those tools and programs.  I was expecting
the PRU tools which come from ti-cgt-pru-native to be included with my
eSDK/SDK, but they don't seem to be, at least not in the SDK.  How can I
get these tools available so I can use the SDK to develop PRU code for the BBB?

Thanks

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-selinux][PATCH RESEND] libpcre_%.bbappend: add missing symlink libpcre.so.1

2016-10-31 Thread Ioan-Adrian Ratiu

This bbappend moves sysroot lib libpcre.so.x.x.x from /usr/lib to /lib
and symlinks /usr/lib/libpcre.so to ../../lib/libpcre.so.x.x.x, but this
causes certain recipes dependent on libpcre (like pango) to fail because
they also expect libpcre.so.1 to exist which this recipe omits to create.

(the reason why the lib is moved in the first place is to avoid a QA issue
because there's a risk for /usr to be on another partition)

Signed-off-by: Ioan-Adrian Ratiu 
---
 recipes-support/libpcre/libpcre_%.bbappend | 1 +
 1 file changed, 1 insertion(+)

diff --git a/recipes-support/libpcre/libpcre_%.bbappend 
b/recipes-support/libpcre/libpcre_%.bbappend
index 9131f8d..ad18d61 100644
--- a/recipes-support/libpcre/libpcre_%.bbappend
+++ b/recipes-support/libpcre/libpcre_%.bbappend
@@ -7,6 +7,7 @@ do_install_append () {
mv -f ${D}${libdir}/libpcre.so.* ${D}${base_libdir}/
relpath=${@os.path.relpath("${base_libdir}", "${libdir}")}
ln -sf ${relpath}/${realsofile} ${D}${libdir}/libpcre.so
+   ln -sf ${relpath}/${realsofile} ${D}${libdir}/libpcre.so.1
fi
 }
 
-- 
2.10.2

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 6/6] rpi-base.inc: build vc4-fkms-v3d.dtbo

2016-10-31 Thread Andrei Gherzan

On Thu, Sep 22, 2016 at 07:47:54AM +0200, Andreas Müller wrote:
> For those who want to run closed source driver with mesa. See further details
> at [1]
>
> [1] http://anholt.livejournal.com/47717.html
>
> Signed-off-by: Andreas Müller 
> ---
>  conf/machine/include/rpi-base.inc | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/conf/machine/include/rpi-base.inc 
> b/conf/machine/include/rpi-base.inc
> index 69774f4..737e842 100644
> --- a/conf/machine/include/rpi-base.inc
> +++ b/conf/machine/include/rpi-base.inc
> @@ -38,6 +38,7 @@ KERNEL_DEVICETREE ?= " \
>  overlays/w1-gpio-pullup.dtbo \
>  overlays/pi3-miniuart-bt.dtbo \
>  overlays/vc4-kms-v3d.dtbo \
> +overlays/vc4-fkms-v3d.dtbo

There is a problem with this change. It seems like this dtb overlay is
not availble in kernel version above 4.4. Don't know exactly why.

>  "
>  KERNEL_IMAGETYPE ?= "Image"
>
> --
> 2.5.5
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 4/6] linux-raspberrypi: update to 4.4.21

2016-10-31 Thread Andrei Gherzan

On Thu, Sep 22, 2016 at 07:47:52AM +0200, Andreas Müller wrote:
> This version contains vc4_firmware_kms [1]
>
> https://github.com/raspberrypi/linux/commit/598f79fb5a7ea1a6fbd37b9849e097dd0bea70fc
>
> Signed-off-by: Andreas Müller 
> ---
>  .../0002-vc4-ioctl-rendering-allow.patch   | 29 
> --
>  recipes-kernel/linux/linux-raspberrypi_4.4.bb  |  5 ++--
>  2 files changed, 2 insertions(+), 32 deletions(-)
>  delete mode 100644 
> recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch
>
> diff --git 
> a/recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch
>  
> b/recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch
> deleted file mode 100644
> index 59d0ed7..000
> --- 
> a/recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch
> +++ /dev/null
> @@ -1,29 +0,0 @@
> -This patch has been accepted upstream in kernel 4.7-rc3
> -But it has not yet been backported to 4.4...
> -Upstream-Status: Accepted 
> [http://www.gossamer-threads.com/lists/linux/kernel/2459302]
> -Signed-off-by: Herve Jourdain 
> 
> -
> -diff --git a/drivers/gpu/drm/vc4/vc4_drv.c b/drivers/gpu/drm/vc4/vc4_drv.c
> -index a5b68c1..14b5ec1 100644
>  a/drivers/gpu/drm/vc4/vc4_drv.c
> -+++ b/drivers/gpu/drm/vc4/vc4_drv.c
> -@@ -75,12 +75,12 @@ static const struct file_operations vc4_drm_fops = {
> - };
> -
> - static const struct drm_ioctl_desc vc4_drm_ioctls[] = {
> --DRM_IOCTL_DEF_DRV(VC4_SUBMIT_CL, vc4_submit_cl_ioctl, 0),
> --DRM_IOCTL_DEF_DRV(VC4_WAIT_SEQNO, vc4_wait_seqno_ioctl, 0),
> --DRM_IOCTL_DEF_DRV(VC4_WAIT_BO, vc4_wait_bo_ioctl, 0),
> --DRM_IOCTL_DEF_DRV(VC4_CREATE_BO, vc4_create_bo_ioctl, 0),
> --DRM_IOCTL_DEF_DRV(VC4_MMAP_BO, vc4_mmap_bo_ioctl, 0),
> --DRM_IOCTL_DEF_DRV(VC4_CREATE_SHADER_BO, vc4_create_shader_bo_ioctl, 0),
> -+DRM_IOCTL_DEF_DRV(VC4_SUBMIT_CL, vc4_submit_cl_ioctl, 
> 0|DRM_RENDER_ALLOW),
> -+DRM_IOCTL_DEF_DRV(VC4_WAIT_SEQNO, vc4_wait_seqno_ioctl, 
> 0|DRM_RENDER_ALLOW),
> -+DRM_IOCTL_DEF_DRV(VC4_WAIT_BO, vc4_wait_bo_ioctl, 0|DRM_RENDER_ALLOW),
> -+DRM_IOCTL_DEF_DRV(VC4_CREATE_BO, vc4_create_bo_ioctl, 
> 0|DRM_RENDER_ALLOW),
> -+DRM_IOCTL_DEF_DRV(VC4_MMAP_BO, vc4_mmap_bo_ioctl, 0|DRM_RENDER_ALLOW),
> -+DRM_IOCTL_DEF_DRV(VC4_CREATE_SHADER_BO, vc4_create_shader_bo_ioctl, 
> 0|DRM_RENDER_ALLOW),
> - DRM_IOCTL_DEF_DRV(VC4_GET_HANG_STATE, vc4_get_hang_state_ioctl,
> -   DRM_ROOT_ONLY),
> - };
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> index 9a49dc1..81e32c0 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> @@ -1,10 +1,9 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
> -LINUX_VERSION ?= "4.4.16"
> +LINUX_VERSION ?= "4.4.21"

Current master already has 4.4.23.

>
> -SRCREV = "cff67c7e03f4333149f2a8f6eafd3bc44475114a"
> +SRCREV = "9669a50a3a8e4f33b4fe138277bc4407e1eab9b2"
>  SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
> file://0001-fix-dtbo-rules.patch \
> -   file://0002-vc4-ioctl-rendering-allow.patch \
>  "
>  require linux-raspberrypi.inc
> --
> 2.5.5
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 0/6] Kernel update + VC4-enhancements

2016-10-31 Thread Andrei Gherzan

On Thu, Sep 22, 2016 at 07:47:48AM +0200, Andreas Müller wrote:
> Patches I am using for a while. If my images don't break for other
> issues I am able to run X11 and weston accelerated in one image. Had
> never a machine before able to do that.
>
> Andreas Müller (6):
>   mesa: align for vc4
>   xorg align for vc4
>   vc4: why no framebuffer device?
>   linux-raspberrypi: update to 4.4.21
>   eglinfo-x11: align to VC4
>   rpi-base.inc: build vc4-fkms-v3d.dtbo
>
>  conf/machine/include/rpi-base.inc  |  1 +
>  recipes-graphics/eglinfo/eglinfo-x11_%.bbappend|  2 +-
>  recipes-graphics/mesa/mesa_%.bbappend  |  1 +
>  .../xorg-xserver/xserver-xorg_%.bbappend   |  9 +++
>  .../0002-vc4-ioctl-rendering-allow.patch   | 29 
> --
>  recipes-kernel/linux/linux-raspberrypi_4.4.bb  |  5 ++--
>  recipes-kernel/linux/linux-rpi.inc |  2 +-
>  7 files changed, 15 insertions(+), 34 deletions(-)
>  create mode 100644 recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend
>  delete mode 100644 
> recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch
>
> --
> 2.5.5
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Patch 1,2,3 and 5 from this series were merge to master. Thank you.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] JFFS2 doesn't use OOB on CCIMX53

2016-10-31 Thread Mariano Dominguez

Hi,
I'm using Connect Core IMX53 board with Kernel version 2.6.35.14 and Yocto
1.4 OS.
I have a random problem when writing operations are done over the Nand
Flash: for instance when I insert rows into the database (the file grows)
or when I copy new files to the jffs2 partition. Sometimes I got an
input/output error and after that I won't be able to recovery the file
neither if I try to remove or if a try to copy a new file which override
the one who has problem.

Below you can see the logs:
When I insert "ls" command, the terminal throw:
'./res' input/output error   ("res" is the folders name)
And if I check the Kernel log:
jffs2_scan_inode_node(): CRC failed on node at 0x0df497c0: Read 0x,
calculated 0x33b7fc9f
JFFS2 error: (1) jffs2_build_inode_pass1: child dir "res" (ino #9334) of
dir ino #9333 appears to be a hard link
JFFS2 warning: (973) jffs2_get_inode_nodes: Eep. No valid nodes for ino
#9334.
JFFS2 warning: (973) jffs2_do_read_inode_internal: no data nodes found for
ino #9334
iget() failed for ino #9334
JFFS2 notice: (746) check_node_data: wrong data CRC in data node at
0x0df47474: read 0xfbf9abb7, calculated 0xbf64ad10.
JFFS2 warning: (1016) jffs2_get_inode_nodes: Eep. No valid nodes for ino
#9334.
JFFS2 warning: (1016) jffs2_do_read_inode_internal: no data nodes found for
ino #9334

Also I checked in U-boot if exist any bad blocks and it doesn't.
I was researching how a Nand flash works and I found that it has an
Out-of-Band (OOB) area that contains an Error-Correcting-Code (ECC)
algorithm. This ECC is used to check and fix any possible writing error.
So, when I was checking if that feature is enabled in my board I found in
the kernel log the message:

user.warn kernel: Memory policy: ECC disabled, Data cache writeback
user.info kernel: JFFS2 doesn't use OOB.


I want to know if my hypothesis is correct and how can i enable and use the
ECC and OOB?

Thanks

-- 




Mariano Dominguez

Software Engineer

Taller Technologies Argentina

San Lorenzo 47, 3rd Floor, Office 5

Córdoba, Argentina

Mobile: +5435157157848
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: Fix path for mkknlimg in bundle_initramfs task

2016-10-31 Thread Piotr Lewicki

Task do_bundle_initramfs() was failing because of "mkknlimg: not found"
The path to "mkknlimg" is now updated.
---
 recipes-kernel/linux/linux-raspberrypi.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
b/recipes-kernel/linux/linux-raspberrypi.inc
index 6184402..9d6ef5f 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -61,7 +61,7 @@ do_bundle_initramfs_append() {
 if test -n "${KERNEL_DEVICETREE}"; then
 # Add RPi bootloader trailer to kernel image to enable 
DeviceTree support
 for type in ${KERNEL_IMAGETYPES} ; do
-${STAGING_BINDIR_NATIVE}/mkknlimg --dtok 
${KERNEL_OUTPUT_DIR}/$type.initramfs ${KERNEL_OUTPUT_DIR}/$type.initramfs
+${STAGING_KERNEL_DIR}/scripts/mkknlimg --dtok 
${KERNEL_OUTPUT_DIR}/$type.initramfs ${KERNEL_OUTPUT_DIR}/$type.initramfs
 done
 fi
 fi
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto 2.2 minimum kernel requirement

2016-10-31 Thread Vuille, Martin (Martin)

We are looking at upgrading from Yocto 1.8 to 2.2.

Yocto 2.2 has a minimum kernel requirement of 3.2.0.

This isn't an issue for our target (ARMv5, Linux 4.4) but may be
an issue for our automated build machines (x86, Linux 2.6.32-CentOS 6.)

However, there is a note that says
"For x86 and x86_64, you can reset 
OLDEST_KERNEL
 to anything down to 2.6.32 if desired."

Is it possible to configure things such that we can keep supporting the old
kernel for the SDK while we support a more up-to-date kernel for the target?

MV
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto 2.2 minimum kernel requirement

2016-10-31 Thread Vuille, Martin (Martin)

I should clarify that these build machines are not for Yocto builds,
but for building an application that uses the Yocto SDK.

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Vuille, Martin (Martin)
Sent: October 31, 2016 10:38
To: yocto@yoctoproject.org
Subject: [yocto] Yocto 2.2 minimum kernel requirement

We are looking at upgrading from Yocto 1.8 to 2.2.

Yocto 2.2 has a minimum kernel requirement of 3.2.0.

This isn't an issue for our target (ARMv5, Linux 4.4) but may be
an issue for our automated build machines (x86, Linux 2.6.32-CentOS 6.)

However, there is a note that says
"For x86 and x86_64, you can reset 
OLDEST_KERNEL
 to anything down to 2.6.32 if desired."

Is it possible to configure things such that we can keep supporting the old
kernel for the SDK while we support a more up-to-date kernel for the target?

MV
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: Fix path for mkknlimg in bundle_initramfs task

2016-10-31 Thread Andrei Gherzan

On Mon, Oct 31, 2016 at 02:42:35PM +0100, Piotr Lewicki wrote:
> Task do_bundle_initramfs() was failing because of "mkknlimg: not found"
> The path to "mkknlimg" is now updated.
> ---
>  recipes-kernel/linux/linux-raspberrypi.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
> b/recipes-kernel/linux/linux-raspberrypi.inc
> index 6184402..9d6ef5f 100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++ b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -61,7 +61,7 @@ do_bundle_initramfs_append() {

The entire append here can be removed as mkknlimg tool was removed
completely. See fe92cc7e1428ba7f982c371101150851c621532a.

>  if test -n "${KERNEL_DEVICETREE}"; then
>  # Add RPi bootloader trailer to kernel image to enable 
> DeviceTree support
>  for type in ${KERNEL_IMAGETYPES} ; do
> -${STAGING_BINDIR_NATIVE}/mkknlimg --dtok 
> ${KERNEL_OUTPUT_DIR}/$type.initramfs ${KERNEL_OUTPUT_DIR}/$type.initramfs
> +${STAGING_KERNEL_DIR}/scripts/mkknlimg --dtok 
> ${KERNEL_OUTPUT_DIR}/$type.initramfs ${KERNEL_OUTPUT_DIR}/$type.initramfs
>  done
>  fi
>  fi
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH V2 0/4] U-boot/kernel improvements

2016-10-31 Thread Andrei Gherzan

On Sat, Oct 22, 2016 at 08:49:53PM +0100, Paul Barker wrote:
> These changes allow u-boot to successfully boot Linux without a manual 
> sequence
> of commands being entered at boot time. This has been tested on an old 
> Raspberry
> Pi B+ as well as a Raspberrypi 3. It should work for other models as well.
>
> Also, the kernel image is removed from the main rootfs /boot directory as it 
> is
> not needed outside the FAT32 boot partition.
>
> Changes in V2 (a bit late sorry!):
> * Rebased onto latest master
> * Address review comments from V1
> * Set COMPATIBLE_MACHINE in rpi-u-boot-scr
>
> Paul Barker (4):
>   rpi-base.inc: Don't install kernel image into rootfs
>   rpi-u-boot-scr: Add recipe to create u-boot boot script
>   u-boot: Add RDEPENDS on rpi-u-boot-scr
>   sdcard_image-rpi.bbclass: Include boot script when using u-boot
>
>  classes/sdcard_image-rpi.bbclass|  1 +
>  conf/machine/include/rpi-base.inc   |  4 
>  .../rpi-u-boot-scr/files/raspberrypi/boot.cmd   |  6 ++
>  .../rpi-u-boot-scr/files/raspberrypi0/boot.cmd  |  6 ++
>  .../rpi-u-boot-scr/files/raspberrypi2/boot.cmd  |  6 ++
>  .../rpi-u-boot-scr/files/raspberrypi3/boot.cmd  |  6 ++
>  recipes-bsp/rpi-u-boot-scr/rpi-u-boot-scr.bb| 21 
> +
>  recipes-bsp/u-boot/u-boot_2016.03.bbappend  |  1 +
>  8 files changed, 51 insertions(+)
>  create mode 100644 recipes-bsp/rpi-u-boot-scr/files/raspberrypi/boot.cmd
>  create mode 100644 recipes-bsp/rpi-u-boot-scr/files/raspberrypi0/boot.cmd
>  create mode 100644 recipes-bsp/rpi-u-boot-scr/files/raspberrypi2/boot.cmd
>  create mode 100644 recipes-bsp/rpi-u-boot-scr/files/raspberrypi3/boot.cmd
>  create mode 100644 recipes-bsp/rpi-u-boot-scr/rpi-u-boot-scr.bb
>  create mode 100644 recipes-bsp/u-boot/u-boot_2016.03.bbappend
>
> --
> 2.1.4
>

Thanks Paul for this. I merged these in master.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Package relation between package.manifest and license.manifest

2016-10-31 Thread Khem Raj


> On Oct 31, 2016, at 12:54 AM, Hugo Heutinck  wrote:
> 
> I am using the Jethro branch, which one are you using ?

morty/master

> 
> For me this provides quite a list of delta's, some seem to be related (e.g. 
> the dbus, dbus-glib, dbus-lib vs. dbus-1),
> but others are not (e.g. expat).
> 
> Was something on license file generation improved between Jethro and more 
> recent branches  ?
> 
> --- /tmp/a.manifest
> +++ /tmp/package.manifest
> @@ -24,9 +24,7 @@
>  cracklib
>  cronie
>  curl
> -dbus
> -dbus-glib
> -dbus-lib
> +dbus-1
>  debianutils
>  debianutils-run-parts
>  diffutils
> @@ -39,26 +37,16 @@
>  ed
>  elfutils
>  ethtool
> -expat
>  factory-tools
>  file
>  findutils
>  firmware-update
>  flex
> -freetype
>  fuser
>  gawk
> -gdbm
> -gdbm-compat
> -glib-2.0
> -glib-2.0-locale-en-gb
> -glibc
>  glibc-binary-localedata-en-gb
>  glibc-binary-localedata-en-us
>  glibc-locale-en-gb
> -gmp
> -gnutls
> -gnutls-openssl
>  grep
>  gzip
>  i2c-tools
> @@ -75,46 +63,70 @@
>  iputils-tracepath
>  iputils-tracepath6
>  iputils-traceroute6
> -json-c
>  kernel-crc-env
>  killall
>  kmod
>  led-control
>  less
> -libacl
> -libattr
> -libbz2
> -libcap
> -libcomerr
> -libcrypto
> -libcurl
> -libdw
> -libe2p
> -libelf
> -libestr
> +libacl1
> +libattr1
> +libblkid1
> +libbz2-0
> +libc6
> +libcap2
> +libcom-err2
> +libcrypto1.0.0
> +libcurl4
> +libdbus-1-3
> +libdbus-glib-1-2
> +libdw1
> +libe2p2
> +libelf1
> +libestr0
>  libevent
> -libext2fs
> -libffi
> -libgcc
> +libexpat1
> +libext2fs2
> +libfdisk1
> +libffi6
> +libfreetype6
> +libgcc1
>  libgcrypt
> -libgpg-error
> -libkmod
> +libgdbm-compat4
> +libgdbm4
> +libglib-2.0-0
> +libglib-2.0-locale-en-gb
> +libgmp10
> +libgnutls-openssl27
> +libgnutls28
> +libgpg-error0
> +libjson-c2
> +libkmod2
>  liblogging
> -liblzma
> -libpci
> -libpcre
> -libpython2
> -libss
> -libssl
> -libstdc++
> -libsysfs
> -libsystemd
> -libudev
> -libwrap
> -libx11
> -libxau
> -libxcb
> -libxdmcp
> +liblzma5
> +libmount1
> +libncurses5
> +libncursesw5
> +libpci3
> +libpcre1
> +libperl5
> +libpopt0
> +libpython2.7-1.0
> +libreadline6
> +libsmartcols1
> +libss2
> +libssl1.0.0
> +libstdc++6
> +libsysfs2
> +libsystemd0
> +libtinfo5
> +libudev1
> +libuuid1
> +libwrap0
> +libx11-6
> +libxau6
> +libxcb1
> +libxdmcp6
> +libz1
>  locale-base-en-gb
>  locale-base-en-us
>  logrotate
> @@ -130,9 +142,6 @@
>  mktemp
>  modutils-initscripts
>  ncurses
> -ncurses-libncurses
> -ncurses-libncursesw
> -ncurses-libtinfo
>  ncurses-terminfo
>  ncurses-terminfo-base
>  net-tools
> @@ -167,8 +176,6 @@
>  pciutils
>  pciutils-ids
>  perl
> -perl-lib
> -popt
>  procps
>  psmisc
>  psplash
> @@ -208,7 +215,6 @@
>  python-unittest
>  python-xml
>  python-xmlrpc
> -readline
>  rsyslog
>  run-postinsts
>  sed
> @@ -232,11 +238,6 @@
>  util-linux
>  util-linux-cfdisk
>  util-linux-fdisk
> -util-linux-libblkid
> -util-linux-libfdisk
> -util-linux-libmount
> -util-linux-libsmartcols
> -util-linux-libuuid
>  util-linux-losetup
>  util-linux-mkfs
>  util-linux-mount
> 
> 
> 2016-10-28 4:25 GMT+02:00 Khem Raj  >:
> 
>> On Oct 26, 2016, at 5:45 AM, Hugo Heutinck > > wrote:
>> 
>> Question: What is the relation between the package.manifest and 
>> license.manifest ?
>> 
>> After a yocto poky based image has been built there are 2 files in the 
>> licenses directory "tmp/deploy/licenses/image_name-datestamp"
>> 
>> One is the package.manifest, which if understood correctly is a list of all 
>> packages included in the image.
>> 
>> The second file is the license.manifest, but this one contains besides the 
>> package name also the version, recipe name and license of the package.
>> 
>> However if I compare the package names in both lists, there seem to be a  
>> number of packages in the license.manifest that are not part of the 
>> package.manifest. E.g. "readline, popt, expat, freetype".
>> 
>> Is the license.manifest a list of all items in the package.manifest + ?build 
>> dependencies? or something ?
> 
> They should be same.
> 
> try something like this
> cat license.manifest | grep "PACKAGE NAME: " | sed "s/PACKAGE NAME: //“ > 
> a.manifest
> diff a.manifest package.manifest
> 
> For me both files comes out same.
> 
> 
>> 
>> Regards,
>> 
>> H.Heutinck
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org 
>> https://lists.yoctoproject.org/listinfo/yocto 
>> 
> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] recipe for cmocka

2016-10-31 Thread Dinh Nguyen (dinhn)


https://github.com/clibs/cmocka

Dear Yocto Gurus,

Want to bring it into our SDK Yocto workspace. Is there any existing recipe for 
cmocka ?

Thanks,
  —Dinh
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] linux-firmware: Correct the LICENSE for brcm43430-license

2016-10-31 Thread Andrei Gherzan

On Mon, Oct 17, 2016 at 09:08:57AM +1100, Jonathan Liu wrote:
> The license for brcm43430-license should be the license it contains
> instead of all the licenses of the linux-firmware packages.
>
> [YOCTO #10251]
>
> Signed-off-by: Jonathan Liu 
> ---
>  recipes-kernel/linux-firmware/linux-firmware_git.bbappend | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/recipes-kernel/linux-firmware/linux-firmware_git.bbappend 
> b/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
> index b4408cb..bcfadde 100644
> --- a/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
> +++ b/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
> @@ -20,6 +20,7 @@ do_install_append() {
>  PACKAGES =+ "${PN}-brcm43430 ${PN}-brcm43430-license"
>
>  LICENSE_${PN}-brcm43430 = "Firmware-broadcom_brcm80211"
> +LICENSE_${PN}-brcm43430-license = "Firmware-broadcom_brcm80211"
>  FILES_${PN}-brcm43430-license = "/lib/firmware/LICENSE.broadcom_brcm80211"
>  FILES_${PN}-brcm43430 = " \
>  /lib/firmware/brcm/brcmfmac43430-sdio.bin \
> --
> 2.10.0
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

This was merged to master. Thank you.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto 2.2 minimum kernel requirement

2016-10-31 Thread Khem Raj


> On Oct 31, 2016, at 7:37 AM, Vuille, Martin (Martin)  
> wrote:
> 
> We are looking at upgrading from Yocto 1.8 to 2.2.
> 
> Yocto 2.2 has a minimum kernel requirement of 3.2.0.
> 
> This isn’t an issue for our target (ARMv5, Linux 4.4) but may be
> an issue for our automated build machines (x86, Linux 2.6.32—CentOS 6.)
> 
> However, there is a note that says
> “For x86 and x86_64, you can reset OLDEST_KERNEL 
> 
>  to anything down to 2.6.32 if desired.”
> 
> Is it possible to configure things such that we can keep supporting the old
> kernel for the SDK while we support a more up-to-date kernel for the target?

I think that should be the default. We do not set it for x86/nativesdk case. 
File a ticket if thats not
the case.

> 
> MV
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org 
> https://lists.yoctoproject.org/listinfo/yocto 
> 


signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 1/1] linux-raspberrypi: Update to 4.8.4

2016-10-31 Thread Andrei Gherzan

Signed-off-by: Andrei Gherzan 
---
 recipes-kernel/linux/linux-raspberrypi_4.8.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi_4.8.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.8.bb
index 7934747..528cfef 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.8.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.8.bb
@@ -1,8 +1,8 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
 
-LINUX_VERSION ?= "4.8.2"
+LINUX_VERSION ?= "4.8.4"
 
-SRCREV = "0105b0ea92b1614ac00329a530da940053e64a4a"
+SRCREV = "d8f7c2da3d33ea4fb4f67411badad374b1160b44"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.8.y \
 "
 require linux-raspberrypi.inc
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 6/6] rpi-base.inc: build vc4-fkms-v3d.dtbo

2016-10-31 Thread Khem Raj


> On Oct 31, 2016, at 7:10 AM, Andrei Gherzan  wrote:
> 
> On Thu, Sep 22, 2016 at 07:47:54AM +0200, Andreas Müller wrote:
>> For those who want to run closed source driver with mesa. See further details
>> at [1]
>> 
>> [1] http://anholt.livejournal.com/47717.html
>> 
>> Signed-off-by: Andreas Müller 
>> ---
>> conf/machine/include/rpi-base.inc | 1 +
>> 1 file changed, 1 insertion(+)
>> 
>> diff --git a/conf/machine/include/rpi-base.inc 
>> b/conf/machine/include/rpi-base.inc
>> index 69774f4..737e842 100644
>> --- a/conf/machine/include/rpi-base.inc
>> +++ b/conf/machine/include/rpi-base.inc
>> @@ -38,6 +38,7 @@ KERNEL_DEVICETREE ?= " \
>> overlays/w1-gpio-pullup.dtbo \
>> overlays/pi3-miniuart-bt.dtbo \
>> overlays/vc4-kms-v3d.dtbo \
>> +overlays/vc4-fkms-v3d.dtbo
> 
> There is a problem with this change. It seems like this dtb overlay is
> not availble in kernel version above 4.4. Don't know exactly why.
> 

Interesting, did you apply latest firmware patch ?

>> "
>> KERNEL_IMAGETYPE ?= "Image"
>> 
>> --
>> 2.5.5
>> 
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> 
> --
> Andrei Gherzan
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 6/6] rpi-base.inc: build vc4-fkms-v3d.dtbo

2016-10-31 Thread Andrei Gherzan

On Mon, Oct 31, 2016 at 09:41:18AM -0700, Khem Raj wrote:
>
> > On Oct 31, 2016, at 7:10 AM, Andrei Gherzan  wrote:
> >
> > On Thu, Sep 22, 2016 at 07:47:54AM +0200, Andreas Müller wrote:
> >> For those who want to run closed source driver with mesa. See further 
> >> details
> >> at [1]
> >>
> >> [1] http://anholt.livejournal.com/47717.html
> >>
> >> Signed-off-by: Andreas Müller 
> >> ---
> >> conf/machine/include/rpi-base.inc | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> diff --git a/conf/machine/include/rpi-base.inc 
> >> b/conf/machine/include/rpi-base.inc
> >> index 69774f4..737e842 100644
> >> --- a/conf/machine/include/rpi-base.inc
> >> +++ b/conf/machine/include/rpi-base.inc
> >> @@ -38,6 +38,7 @@ KERNEL_DEVICETREE ?= " \
> >> overlays/w1-gpio-pullup.dtbo \
> >> overlays/pi3-miniuart-bt.dtbo \
> >> overlays/vc4-kms-v3d.dtbo \
> >> +overlays/vc4-fkms-v3d.dtbo
> >
> > There is a problem with this change. It seems like this dtb overlay is
> > not availble in kernel version above 4.4. Don't know exactly why.
> >
>
> Interesting, did you apply latest firmware patch ?

You mean kernel update patch, right? No I haven't but the sources seem
to not deploy this dtbo:
https://github.com/raspberrypi/linux/tree/rpi-4.8.y/arch/arm/boot/dts/overlays

>
> >> "
> >> KERNEL_IMAGETYPE ?= "Image"
> >>
> >> --
> >> 2.5.5
> >>
> >> --
> >> ___
> >> yocto mailing list
> >> yocto@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/yocto
> >
> > --
> > Andrei Gherzan
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>



--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 1/6] firmware: Update to latest

2016-10-31 Thread Khem Raj

Fixes issues with display not starting with weston

Signed-off-by: Khem Raj 
---
 recipes-bsp/common/firmware.inc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
index 29f9c01..6ce89a5 100644
--- a/recipes-bsp/common/firmware.inc
+++ b/recipes-bsp/common/firmware.inc
@@ -1,5 +1,5 @@
-RPIFW_SRCREV ?= "ec63df146f454e8cab7080380f9138246d877013"
-RPIFW_DATE ?= "20161005"
+RPIFW_SRCREV ?= "ec5a517ed6051974a5a09f7b7811d21c443a7c74"
+RPIFW_DATE ?= "20161020"
 RPIFW_SRC_URI ?= 
"git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
 RPIFW_S ?= "${WORKDIR}/git"
 
-- 
2.10.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 4/6] userland: Update to latest master tip

2016-10-31 Thread Khem Raj

Signed-off-by: Khem Raj 
---
 recipes-graphics/userland/userland_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-graphics/userland/userland_git.bb 
b/recipes-graphics/userland/userland_git.bb
index 3c63f94..7558851 100644
--- a/recipes-graphics/userland/userland_git.bb
+++ b/recipes-graphics/userland/userland_git.bb
@@ -16,7 +16,7 @@ COMPATIBLE_MACHINE = "raspberrypi"
 
 SRCBRANCH = "master"
 SRCFORK = "raspberrypi"
-SRCREV = "2350bf2511fa49e177fb35c9613eef1b657a7506"
+SRCREV = "2852d9ff5a9038021f1c22d95e8a9e3aad09893f"
 
 SRC_URI = "\
 git://github.com/${SRCFORK}/userland.git;protocol=git;branch=${SRCBRANCH} \
-- 
2.10.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 2/6] linux-raspberrypi_4.8.bb: Update to 4.8.4

2016-10-31 Thread Khem Raj

Signed-off-by: Khem Raj 
---
 recipes-kernel/linux/linux-raspberrypi_4.8.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi_4.8.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.8.bb
index 02623f4..528cfef 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.8.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.8.bb
@@ -1,8 +1,8 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
 
-LINUX_VERSION ?= "4.8.1"
+LINUX_VERSION ?= "4.8.4"
 
-SRCREV = "5b7970b19bbb2ea1620591bfb6517848696ed0b9"
+SRCREV = "d8f7c2da3d33ea4fb4f67411badad374b1160b44"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.8.y \
 "
 require linux-raspberrypi.inc
-- 
2.10.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 5/6] firmware: Update to 20161030

2016-10-31 Thread Khem Raj

Signed-off-by: Khem Raj 
---
 recipes-bsp/common/firmware.inc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
index 6ce89a5..ed0782f 100644
--- a/recipes-bsp/common/firmware.inc
+++ b/recipes-bsp/common/firmware.inc
@@ -1,5 +1,5 @@
-RPIFW_SRCREV ?= "ec5a517ed6051974a5a09f7b7811d21c443a7c74"
-RPIFW_DATE ?= "20161020"
+RPIFW_SRCREV ?= "413fc664838e81caeabdc4118dc51e138d5d6c71"
+RPIFW_DATE ?= "20161030"
 RPIFW_SRC_URI ?= 
"git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
 RPIFW_S ?= "${WORKDIR}/git"
 
-- 
2.10.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 3/6] weston: Unify bbappends for weston into single file

2016-10-31 Thread Khem Raj

Signed-off-by: Khem Raj 
---
 recipes-graphics/wayland/weston_%.bbappend | 10 ++
 recipes-graphics/weston/weston_%.bbappend  |  8 
 2 files changed, 10 insertions(+), 8 deletions(-)
 delete mode 100644 recipes-graphics/weston/weston_%.bbappend

diff --git a/recipes-graphics/wayland/weston_%.bbappend 
b/recipes-graphics/wayland/weston_%.bbappend
index 57b8079..f2cb7aa 100644
--- a/recipes-graphics/wayland/weston_%.bbappend
+++ b/recipes-graphics/wayland/weston_%.bbappend
@@ -1,2 +1,12 @@
 EXTRA_OECONF_append_rpi = "${@bb.utils.contains('MACHINE_FEATURES', 
'vc4graphics', '', ' --enable-rpi-compositor 
WESTON_NATIVE_BACKEND=rpi-backend.so', d)}"
 
+PACKAGECONFIG_remove_rpi = "${@bb.utils.contains('MACHINE_FEATURES', 
'vc4graphics', 'fbdev', '', d)}"
+
+EXTRA_OECONF += "--disable-xwayland-test \
+ --disable-simple-egl-clients \
+"
+
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--enable-rpi-compositor', d)}"
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--disable-resize-optimization', d)}"
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--disable-setuid-install', d)}"
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'WESTON_NATIVE_BACKEND=rpi-backend.so', d)}"
diff --git a/recipes-graphics/weston/weston_%.bbappend 
b/recipes-graphics/weston/weston_%.bbappend
deleted file mode 100644
index b964542..000
--- a/recipes-graphics/weston/weston_%.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-PACKAGECONFIG_remove_rpi = "${@bb.utils.contains('MACHINE_FEATURES', 
'vc4graphics', ' fbdev', '', d)}"
-EXTRA_OECONF += "--disable-xwayland-test \
- --disable-simple-egl-clients \
-"
-EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--enable-rpi-compositor', d)}"
-EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--disable-resize-optimization', d)}"
-EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--disable-setuid-install', d)}"
-EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'WESTON_NATIVE_BACKEND=rpi-backend.so', d)}"
-- 
2.10.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 6/6] linux-raspberrypi-4.4: Update to 4.4.28

2016-10-31 Thread Khem Raj

Signed-off-by: Khem Raj 
---
 recipes-kernel/linux/linux-raspberrypi_4.4.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
index 4b15f88..19e8552 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
@@ -1,8 +1,8 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
 
-LINUX_VERSION ?= "4.4.23"
+LINUX_VERSION ?= "4.4.28"
 
-SRCREV = "c2a1d975537fcac01da80ce34f10bc491620a64e"
+SRCREV = "5afda48c3408e15742d4569459a4ff668e2857f7"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
file://0001-fix-dtbo-rules.patch \
 "
-- 
2.10.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 6/6] rpi-base.inc: build vc4-fkms-v3d.dtbo

2016-10-31 Thread Khem Raj


> On Oct 31, 2016, at 9:44 AM, Andrei Gherzan  wrote:
> 
> On Mon, Oct 31, 2016 at 09:41:18AM -0700, Khem Raj wrote:
>> 
>>> On Oct 31, 2016, at 7:10 AM, Andrei Gherzan  wrote:
>>> 
>>> On Thu, Sep 22, 2016 at 07:47:54AM +0200, Andreas Müller wrote:
 For those who want to run closed source driver with mesa. See further 
 details
 at [1]
 
 [1] http://anholt.livejournal.com/47717.html
 
 Signed-off-by: Andreas Müller 
 ---
 conf/machine/include/rpi-base.inc | 1 +
 1 file changed, 1 insertion(+)
 
 diff --git a/conf/machine/include/rpi-base.inc 
 b/conf/machine/include/rpi-base.inc
 index 69774f4..737e842 100644
 --- a/conf/machine/include/rpi-base.inc
 +++ b/conf/machine/include/rpi-base.inc
 @@ -38,6 +38,7 @@ KERNEL_DEVICETREE ?= " \
overlays/w1-gpio-pullup.dtbo \
overlays/pi3-miniuart-bt.dtbo \
overlays/vc4-kms-v3d.dtbo \
 +overlays/vc4-fkms-v3d.dtbo
>>> 
>>> There is a problem with this change. It seems like this dtb overlay is
>>> not availble in kernel version above 4.4. Don't know exactly why.
>>> 
>> 
>> Interesting, did you apply latest firmware patch ?
> 
> You mean kernel update patch, right? No I haven't but the sources seem
> to not deploy this dtbo:
> https://github.com/raspberrypi/linux/tree/rpi-4.8.y/arch/arm/boot/dts/overlays

I see. I think it could be an oversight in 4.8

> 
>> 
"
 KERNEL_IMAGETYPE ?= "Image"
 
 --
 2.5.5
 
 --
 ___
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto
>>> 
>>> --
>>> Andrei Gherzan
>>> --
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>> 
> 
> 
> 
> --
> Andrei Gherzan



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 1/1] linux-raspberrypi: Update to 4.8.4

2016-10-31 Thread Khem Raj

Hi Andrei

Sent a series which includes upgrade for 4.8

> On Oct 31, 2016, at 9:39 AM, Andrei Gherzan  wrote:
> 
> Signed-off-by: Andrei Gherzan 
> ---
> recipes-kernel/linux/linux-raspberrypi_4.8.bb | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.8.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.8.bb
> index 7934747..528cfef 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.8.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.8.bb
> @@ -1,8 +1,8 @@
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
> 
> -LINUX_VERSION ?= "4.8.2"
> +LINUX_VERSION ?= "4.8.4"
> 
> -SRCREV = "0105b0ea92b1614ac00329a530da940053e64a4a"
> +SRCREV = "d8f7c2da3d33ea4fb4f67411badad374b1160b44"
> SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.8.y \
> "
> require linux-raspberrypi.inc
> --
> 2.7.4
> 
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 1/1] linux-raspberrypi: Update to 4.8.4

2016-10-31 Thread Andrei Gherzan

On Mon, Oct 31, 2016 at 05:39:53PM +0100, Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan 
> ---
>  recipes-kernel/linux/linux-raspberrypi_4.8.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.8.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.8.bb
> index 7934747..528cfef 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.8.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.8.bb
> @@ -1,8 +1,8 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
> -LINUX_VERSION ?= "4.8.2"
> +LINUX_VERSION ?= "4.8.4"
>
> -SRCREV = "0105b0ea92b1614ac00329a530da940053e64a4a"
> +SRCREV = "d8f7c2da3d33ea4fb4f67411badad374b1160b44"
>  SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.8.y \
>  "
>  require linux-raspberrypi.inc
> --
> 2.7.4
>

Merged to master.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/2] firmware: Update to latest

2016-10-31 Thread Andrei Gherzan

On Thu, Oct 20, 2016 at 10:09:56PM -0700, Khem Raj wrote:
> Fixes issues with display not starting with weston
>
> Signed-off-by: Khem Raj 
> ---
>  recipes-bsp/common/firmware.inc | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
> index 29f9c01..6ce89a5 100644
> --- a/recipes-bsp/common/firmware.inc
> +++ b/recipes-bsp/common/firmware.inc
> @@ -1,5 +1,5 @@
> -RPIFW_SRCREV ?= "ec63df146f454e8cab7080380f9138246d877013"
> -RPIFW_DATE ?= "20161005"
> +RPIFW_SRCREV ?= "ec5a517ed6051974a5a09f7b7811d21c443a7c74"
> +RPIFW_DATE ?= "20161020"
>  RPIFW_SRC_URI ?= 
> "git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
>  RPIFW_S ?= "${WORKDIR}/git"
>
> --
> 2.10.0
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged both to master. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] linux-firmware: Fix "No generic license file exists" warning

2016-10-31 Thread Andrei Gherzan

On Sun, Oct 16, 2016 at 01:27:39PM +1100, Jonathan Liu wrote:
> The NO_GENERIC_LICENSE map value for Firmware-broadcom_brcm80211 needs
> to have the full path to LICENSE.broadcom_brcm80211 from the URL
> instead of just the filename.
>
> Fixes the following warning building the linux-firmware recipe:
> WARNING: linux-firmware-1_0.0+gitAUTOINC+42ad5367dd-r0 do_populate_lic: 
> linux-firmware: No generic license file exists for: 
> Firmware-broadcom_brcm80211 in any provider
>
> Signed-off-by: Jonathan Liu 
> ---
>  recipes-kernel/linux-firmware/linux-firmware_git.bbappend | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-kernel/linux-firmware/linux-firmware_git.bbappend 
> b/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
> index 20ef05f..b4408cb 100644
> --- a/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
> +++ b/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
> @@ -4,7 +4,7 @@ LICENSE_append = " & Firmware-broadcom_brcm80211"
>
>  LIC_FILES_CHKSUM_append = " 
> file://${WORKDIR}/LICENSE.broadcom_brcm80211;md5=8cba1397cda6386db37210439a0da3eb"
>
> -NO_GENERIC_LICENSE[Firmware-broadcom_brcm80211] = 
> "LICENSE.broadcom_brcm80211"
> +NO_GENERIC_LICENSE[Firmware-broadcom_brcm80211] = 
> "${WORKDIR}/LICENSE.broadcom_brcm80211"
>
>  SRC_URI_append = " \
>  file://brcmfmac43430-sdio.bin \
> --
> 2.10.0
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Merged to master. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 6/6] rpi-base.inc: build vc4-fkms-v3d.dtbo

2016-10-31 Thread Andrei Gherzan

On Mon, Oct 31, 2016 at 09:52:59AM -0700, Khem Raj wrote:
>
> > On Oct 31, 2016, at 9:44 AM, Andrei Gherzan  wrote:
> >
> > On Mon, Oct 31, 2016 at 09:41:18AM -0700, Khem Raj wrote:
> >>
> >>> On Oct 31, 2016, at 7:10 AM, Andrei Gherzan  wrote:
> >>>
> >>> On Thu, Sep 22, 2016 at 07:47:54AM +0200, Andreas Müller wrote:
>  For those who want to run closed source driver with mesa. See further 
>  details
>  at [1]
> 
>  [1] http://anholt.livejournal.com/47717.html
> 
>  Signed-off-by: Andreas Müller 
>  ---
>  conf/machine/include/rpi-base.inc | 1 +
>  1 file changed, 1 insertion(+)
> 
>  diff --git a/conf/machine/include/rpi-base.inc 
>  b/conf/machine/include/rpi-base.inc
>  index 69774f4..737e842 100644
>  --- a/conf/machine/include/rpi-base.inc
>  +++ b/conf/machine/include/rpi-base.inc
>  @@ -38,6 +38,7 @@ KERNEL_DEVICETREE ?= " \
> overlays/w1-gpio-pullup.dtbo \
> overlays/pi3-miniuart-bt.dtbo \
> overlays/vc4-kms-v3d.dtbo \
>  +overlays/vc4-fkms-v3d.dtbo
> >>>
> >>> There is a problem with this change. It seems like this dtb overlay is
> >>> not availble in kernel version above 4.4. Don't know exactly why.
> >>>
> >>
> >> Interesting, did you apply latest firmware patch ?
> >
> > You mean kernel update patch, right? No I haven't but the sources seem
> > to not deploy this dtbo:
> > https://github.com/raspberrypi/linux/tree/rpi-4.8.y/arch/arm/boot/dts/overlays
>
> I see. I think it could be an oversight in 4.8

Looks like indeed.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] Master doesn't seem to be building right...

2016-10-31 Thread Andrei Gherzan

On Fri, Oct 14, 2016 at 03:26:53PM +, Frank Earl wrote:
> It's boggling on the sd card image build.  Attached is the console output 
> from the build (Don't need the log, this one's clear from the build fail 
> output.) and a dump of the directory structures in 
> tmp/deploy/images/raspberrypi2 from my setup.
>
> It's choking on trying to put the overlays onto the sd card image:
>
> /home/frank/git_repos/guardhat/build/tmp/deploy/images/raspberrypi2/Image-hifiberry-amp.dtbo:
>  No such file or directory
> | WARNING: 
> /home/frank/git_repos/guardhat/build/tmp/work/raspberrypi2-poky-linux-gnueabi/gh-base-image/1.0-r0/temp/run.do_image_rpi_sdimg.26079:1
>  exit 1 from 'mcopy -i 
> /home/frank/git_repos/guardhat/build/tmp/work/raspberrypi2-poky-linux-gnueabi/gh-base-image/1.0-r0/boot.img
>  -s 
> /home/frank/git_repos/guardhat/build/tmp/deploy/images/raspberrypi2/Image-${DTB_BASE_NAME}.${DTB_EXT}
>  ::overlays/${DTB_BASE_NAME}.${DTB_EXT}'
>
>
> Directory path:
>
>   4 -rw-r--r-- 2 frank frank  779 Oct 13 20:27 
> /home/frank/git_repos/guardhat/build/tmp/deploy/images/raspberrypi2/Image-1-4.4.23+git0+c2a1d97553-r0-hifiberry-amp.dtbo-20161014012231.dtb
>
> So, the backing file seems to be there...but...
>
> 4 lrwxrwxrwx 1 frank frank   71 Oct 13 20:45 
> /home/frank/git_repos/guardhat/build/tmp/deploy/images/raspberrypi2/Image-hifiberry-amp.dtbo.dtb
>  -> Image-1-4.4.23+git0+c2a1d97553-r0-hifiberry-amp.dtbo-20161014012231.dtb
>
>
> Heh...  Something's not QUITE right there.  The packager is looking for 
> .dtbo's and we're symlinking .dtb's...I'm looking through the path trying 
> to understand how it's setting the 'latest-build' symlinks, but if someone 
> actually has a hint for me, it'd be appreciated.  :-D
>
>
>
> Frank Earl
>
>
>
> Frank Earl
>
>
>
> Legal Disclaimer:
> The information contained in this message may be privileged and confidential. 
> It is intended to be read only by the individual or entity to whom it is 
> addressed or by their designee. If the reader of this message is not the 
> intended recipient, you are on notice that any distribution of this message, 
> in any form, is strictly prohibited. If you have received this message in 
> error, please immediately notify the sender and delete or destroy any copy of 
> this message!

> Loading cache...done.
> Loaded 2741 entries from dependency cache.
> WARNING: No recipes available for:
>   
> /home/frank/git_repos/guardhat/build/../meta-gh/recipes-bsp/u-boot/u-boot-ti-staging_2015.07.bbappend
> NOTE: Resolving any missing task queue dependencies
>
> Build Configuration:
> BB_VERSION= "1.30.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "universal"
> TARGET_SYS= "arm-poky-linux-gnueabi"
> MACHINE   = "raspberrypi2"
> DISTRO= "poky"
> DISTRO_VERSION= "2.1.1"
> TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard 
> cortexa7"
> TARGET_FPU= "hard"
> meta
> meta-poky
> meta-yocto-bsp= "krogoth:e93596fe74927e2e2f4dd7f671994ccb9744cff8"
> meta-linaro-toolchain = "krogoth:85faf6c6824597e7fd9e2d35fc9d8da2e9f90bc7"
> meta-oe
> meta-filesystems
> meta-networking
> meta-multimedia
> meta-initramfs
> meta-systemd
> meta-python   = "krogoth:851a064b53dca3b14dd33eaaaca9573b1a36bf0e"
> meta-telephony= "HEAD:8cf5a67850adf270bc2fdb4c0ed708b0ba037670"
> meta-gh   = "master:12dc12456e7f6f486ca2815603c5f21f74c2d2c2"
> meta-ti   = "master:6cb779a6ba1b0693f6bf82777e1a333effe6fca5"
> meta-raspberrypi  = "master:05be947a31df873405cdd70ada210c9f7f7b132f"
>

I see that you are using master of meta-raspberrypi. Can you try with
the krogoth branch, please?

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][V2]PATCH] smack: Add new package

2016-10-31 Thread Armin Kuster

V2:
Fix typo and add LDFLAG to makefile

Signed-off-by: Armin Kuster 
---
 recipes-security/smack/files/run-ptest |  3 ++
 .../smack/files/smack_generator_make_fixup.patch   | 18 
 recipes-security/smack/smack_1.3.0.bb  | 54 ++
 3 files changed, 75 insertions(+)
 create mode 100644 recipes-security/smack/files/run-ptest
 create mode 100644 
recipes-security/smack/files/smack_generator_make_fixup.patch
 create mode 100644 recipes-security/smack/smack_1.3.0.bb

diff --git a/recipes-security/smack/files/run-ptest 
b/recipes-security/smack/files/run-ptest
new file mode 100644
index 000..049a9b4
--- /dev/null
+++ b/recipes-security/smack/files/run-ptest
@@ -0,0 +1,3 @@
+#!/bin/sh
+./tests/make_policies.bash ./tests/generator
+./tests/make_policies.bash ./tests/generator labels
diff --git a/recipes-security/smack/files/smack_generator_make_fixup.patch 
b/recipes-security/smack/files/smack_generator_make_fixup.patch
new file mode 100644
index 000..4d677e7
--- /dev/null
+++ b/recipes-security/smack/files/smack_generator_make_fixup.patch
@@ -0,0 +1,18 @@
+Upstream-Status: Pending
+
+Signed-off-by: Armin Kuster 
+
+
+Index: git/tests/Makefile
+===
+--- git.orig/tests/Makefile
 git/tests/Makefile
+@@ -4,7 +4,7 @@ clean:
+   rm -rf ./out ./generator
+ 
+ generator: generator.c
+-  gcc -Wall -O3 generator.c -o ./generator
++  ${CC}  ${LDFLAGS} generator.c -o ./generator
+ 
+ policies: ./generator ./make_policies.bash
+   ./make_policies.bash ./generator
diff --git a/recipes-security/smack/smack_1.3.0.bb 
b/recipes-security/smack/smack_1.3.0.bb
new file mode 100644
index 000..4c41f6c
--- /dev/null
+++ b/recipes-security/smack/smack_1.3.0.bb
@@ -0,0 +1,54 @@
+DESCRIPTION = "Selection of tools for developers working with Smack"
+HOMEPAGE = "https://github.com/smack-team/smack";
+SECTION = "Security/Access Control"
+LICENSE = "LGPL-2.1"
+
+LIC_FILES_CHKSUM = "file://COPYING;md5=4fbd65380cdd255951079008b364516c"
+
+SRCREV = "478f68d182c5070f510482194d3e097b11c21907"
+SRC_URI = " \
+   git://github.com/smack-team/smack.git;branch=v1.3.x \
+   file://smack_generator_make_fixup.patch \
+   file://run-ptest"
+
+PV = "1.3.0+git${SRCPV}"
+
+inherit autotools update-rc.d pkgconfig ptest 
${@bb.utils.contains('VIRTUAL-RUNTIME_init_manager','systemd','systemd','', d)}
+
+S = "${WORKDIR}/git"
+
+PACKAGECONFIG ??= ""
+PACKAGECONFIG_append = " ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 
'systemd', '', d)}"
+
+PACKAGECONFIG[systemd] = 
"--with-systemdsystemunitdir=${systemd_system_unitdir}, 
--without-systemdsystemunitdir, systemd"
+
+do_compile_append () {
+   oe_runmake -C ${S}/tests generator
+}
+
+do_install_append () {
+   install -d ${D}${sysconfdir}/init.d
+   install -d ${D}${sysconfdir}/smack
+   install -d ${D}${sysconfdir}/smack/accesses.d
+   install -d ${D}${sysconfdir}/smack/cipso.d
+   install ${S}/init/smack.rc ${D}/${sysconfdir}/init.d/smack
+}
+
+do_install_ptest () {
+   install -d ${D}${PTEST_PATH}/tests
+   install ${S}/tests/generator ${D}/${PTEST_PATH}/tests
+   install ${S}/tests/generate-rules.sh ${D}${PTEST_PATH}/tests
+   install ${S}/tests/make_policies.bash ${D}${PTEST_PATH}/tests
+}
+
+INITSCRIPT_PACKAGES = "${PN}"
+INITSCRIPT_NAME = "smack"
+INITSCRIPT_PARAMS = "start 16 2 3 4 5 . stop 35 0 1 6 ."
+
+FILES_${PN} += "${sysconfdir}/init.d/smack"
+FILES_${PN}-ptest += "generator"
+
+RDEPENDS_${PN} += "coreutils"
+RDEPENDS_${PN}-ptest += "make bash bc"
+
+BBCLASSEXTEND = "native"
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH] nmap: Upgrade package to 7.31

2016-10-31 Thread Armin Kuster

LIC_FILES_CHKSUM change do to yr going from 2015 to 2016 in file.
Added "no update" config option.

Signed-off-by: Armin Kuster 
---
 recipes-security/nmap/{nmap_7.12.bb => nmap_7.31.bb} | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)
 rename recipes-security/nmap/{nmap_7.12.bb => nmap_7.31.bb} (88%)

diff --git a/recipes-security/nmap/nmap_7.12.bb 
b/recipes-security/nmap/nmap_7.31.bb
similarity index 88%
rename from recipes-security/nmap/nmap_7.12.bb
rename to recipes-security/nmap/nmap_7.31.bb
index dadff3d..c50b240 100644
--- a/recipes-security/nmap/nmap_7.12.bb
+++ b/recipes-security/nmap/nmap_7.31.bb
@@ -3,12 +3,12 @@ DESCRIPTION = "Nmap ("Network Mapper") is a free and open 
source (license) utili
 SECTION = "security"
 LICENSE = "GPL-2.0"
 
-LIC_FILES_CHKSUM = 
"file://COPYING;beginline=7;endline=12;md5=51f7052ac85aaf1a2127f7803de1261e"
+LIC_FILES_CHKSUM = 
"file://COPYING;beginline=7;endline=12;md5=bce7593e567a4b12f60c6a04f9b8c1e5"
 
 SRC_URI = "http://nmap.org/dist/${BP}.tar.bz2";
 
-SRC_URI[md5sum] = "0764f4dabe7cccda3c49fc3990b62a8a"
-SRC_URI[sha256sum] = 
"63df082a87c95a189865d37304357405160fc6333addcf5b84204c95e0539b04"
+SRC_URI[md5sum] = "f2f6660142a777862342a58cc54258ea"
+SRC_URI[sha256sum] = 
"cb9f4e03c0771c709cd47dc8fc6ac3421eadbdd313f0aae52276829290583842"
 
 inherit autotools-brokensep pkgconfig python-dir distro_features_check
 
@@ -16,14 +16,14 @@ PACKAGECONFIG ?= "ncat nping ndiff pcap"
 PACKAGECONFIG += " ${@bb.utils.contains('IMAGE_FEATURES', 'x11-base', 
'zenmap', '', d)}"
 
 PACKAGECONFIG[pcap] = "--with-pcap=linux, --without-pcap, libpcap, libpcap"
+PACKAGECONFIG[pcre] = "--with-libpcre=${STAGING_LIBDIR}/.., 
--with-libpcre=included, libpre"
 PACKAGECONFIG[ssl] = "--with-openssl=${STAGING_LIBDIR}/.., --without-openssl, 
openssl, openssl"
 
 #disable/enable packages
 PACKAGECONFIG[nping] = ",--without-nping,"
 PACKAGECONFIG[ncat] = ",--without-ncat,"
 PACKAGECONFIG[ndiff] = ",--without-ndiff,"
-
-PACKAGECONFIG[pcre] = "--with-libpcre=${STAGING_LIBDIR}/.., 
--with-libpcre=included, libpre"
+PACKAGECONFIG[update] = ",--without-nmap-update,"
 
 #Add gui
 PACKAGECONFIG[zenmap] = "--with-zenmap, --without-zenmap, gtk+ python-core 
python-codecs python-io python-logging python-unittest python-xml 
python-netclient python-doctest python-subprocess python-pygtk, python-core 
python-codecs python-io python-logging python-netclient python-xml 
python-unittest python-doctest python-subprocess  python-pygtk gtk+"
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][WIP]PATCH 1/2] yocto-kernel: add apparmor fragments

2016-10-31 Thread Armin Kuster

Signed-off-by: Armin Kuster 
---
 recipes-kernel/linux/linux-yocto-4.8/apparmor.cfg | 13 +
 recipes-kernel/linux/linux-yocto_4.8.bbappend |  1 +
 2 files changed, 14 insertions(+)
 create mode 100644 recipes-kernel/linux/linux-yocto-4.8/apparmor.cfg

diff --git a/recipes-kernel/linux/linux-yocto-4.8/apparmor.cfg 
b/recipes-kernel/linux/linux-yocto-4.8/apparmor.cfg
new file mode 100644
index 000..1dc4168
--- /dev/null
+++ b/recipes-kernel/linux/linux-yocto-4.8/apparmor.cfg
@@ -0,0 +1,13 @@
+CONFIG_AUDIT=y
+CONFIG_AUDITSYSCALL=y
+CONFIG_AUDIT_WATCH=y
+CONFIG_AUDIT_TREE=y
+# CONFIG_NETFILTER_XT_TARGET_AUDIT is not set
+CONFIG_SECURITY_PATH=y
+# CONFIG_SECURITY_SELINUX is not set
+CONFIG_SECURITY_APPARMOR=y
+CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
+CONFIG_SECURITY_APPARMOR_HASH=y
+CONFIG_SECURITY_APPARMOR_HASH_DEFAULT=y
+CONFIG_INTEGRITY_AUDIT=y
+# CONFIG_DEFAULT_SECURITY_APPARMOR is not set
diff --git a/recipes-kernel/linux/linux-yocto_4.8.bbappend 
b/recipes-kernel/linux/linux-yocto_4.8.bbappend
index 048e8fd..78d5101 100644
--- a/recipes-kernel/linux/linux-yocto_4.8.bbappend
+++ b/recipes-kernel/linux/linux-yocto_4.8.bbappend
@@ -4,6 +4,7 @@ FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-4.8:"
 SRC_URI += "\
 ${@bb.utils.contains('DISTRO_FEATURES', 'tpm', ' file://tpm.cfg', '', 
d)} \
 ${@bb.utils.contains('DISTRO_FEATURES', 'tpm', ' file://tpm.scc', '', 
d)} \
+${@bb.utils.contains('DISTRO_FEATURES', 'apparmor', ' 
file://apparmor.cfg', '', d)} \
 "
 
 SRC_URI += "\
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][WIP]PATCH 2/2] apparmor: Add new package

2016-10-31 Thread Armin Kuster

Signed-off-by: Armin Kuster 
---
 recipes-security/AppArmor/apparmor_2.10.95.bb | 116 +
 recipes-security/AppArmor/files/apparmor  | 211 +
 recipes-security/AppArmor/files/apparmor.rc   |  98 
 recipes-security/AppArmor/files/apparmor.service  |  22 ++
 recipes-security/AppArmor/files/disable_pdf.patch |  33 +++
 recipes-security/AppArmor/files/functions | 271 ++
 6 files changed, 751 insertions(+)
 create mode 100644 recipes-security/AppArmor/apparmor_2.10.95.bb
 create mode 100644 recipes-security/AppArmor/files/apparmor
 create mode 100644 recipes-security/AppArmor/files/apparmor.rc
 create mode 100644 recipes-security/AppArmor/files/apparmor.service
 create mode 100644 recipes-security/AppArmor/files/disable_pdf.patch
 create mode 100644 recipes-security/AppArmor/files/functions

diff --git a/recipes-security/AppArmor/apparmor_2.10.95.bb 
b/recipes-security/AppArmor/apparmor_2.10.95.bb
new file mode 100644
index 000..de09e29
--- /dev/null
+++ b/recipes-security/AppArmor/apparmor_2.10.95.bb
@@ -0,0 +1,116 @@
+SUMMARY = "AppArmor another MAC control system"
+DESCRIPTION = "user-space parser utility for AppArmor \
+ This provides the system initialization scripts needed to use the \
+ AppArmor Mandatory Access Control system, including the AppArmor Parser \
+ which is required to convert AppArmor text profiles into machine-readable \
+ policies that are loaded into the kernel for use with the AppArmor Linux \
+ Security Module."
+HOMEAPAGE = "http://apparmor.net/";
+SECTION = "admin"
+
+LICENSE = "GPLv2 & GPLv2+ & BSD-3-Clause & LGPLv2.1+"
+LIC_FILES_CHKSUM = "file://${S}/LICENSE;md5=fd57a4b0bc782d7b80fd431f10bbf9d0"
+
+DEPENDS = "bison-native apr apache2"
+
+SRC_URI = " \
+   
http://archive.ubuntu.com/ubuntu/pool/main/a/${BPN}/${BPN}_${PV}.orig.tar.gz \
+   file://disable_pdf.patch \
+   file://apparmor.rc \
+   file://functions \
+   file://apparmor \
+   file://apparmor.service \
+   "
+
+SRC_URI[md5sum] = "71a13b9d6ae0bca4f5375984df1a51e7"
+SRC_URI[sha256sum] = 
"3f659a599718f4a5e2a33140916715f574a5cb3634a6b9ed6d29f7b0617e4d1a"
+
+PARALLEL_MAKE = ""
+
+inherit pkgconfig autotools-brokensep update-rc.d python-dir 
${@bb.utils.contains('VIRTUAL-RUNTIME_init_manager','systemd','systemd','', d)}
+
+S = "${WORKDIR}/apparmor-${PV}"
+
+PACKAGECONFIG ?="man"
+PACKAGECONFIG[man] = "--enable-man-pages, --disable-man-pages"
+
+PAMLIB="${@bb.utils.contains('DISTRO_FEATURES', 'pam', '1', '0', d)}"
+
+do_configure() {
+   cd ${S}/libraries/libapparmor
+   autoconf --force
+   libtoolize --automake -c
+   automake -ac
+   ./configure ${CONFIGUREOPTS} ${EXTRA_OECONF}
+   sed -i -e 's#^YACC.*#YACC := bison#' ${S}/parser/Makefile
+   sed -i -e 's#^LEX.*#LEX := flex#' ${S}/parser/Makefile
+}
+
+do_compile () {
+   cd ${S}/libraries/libapparmor
+   oe_runmake
+cd ${S}/binutils
+oe_runmake
+cd ${S}/utils
+oe_runmake
+   cd ${S}/parser
+oe_runmake
+   cd ${S}/profiles
+oe_runmake
+
+   cd ${S}/changehat/mod_apparmor
+oe_runmake
+
+   if test -z "${PAMLIB}" ; then
+   cd ${S}/changehat/pam_apparmor
+   oe_runmake
+   fi
+}
+
+do_install () {
+   install -d ${D}/${INIT_D_DIR}
+   install -d ${D}/lib/apparmor
+   
+   cd ${S}/libraries/libapparmor
+   oe_runmake DESTDIR="${D}" install
+
+cd ${S}/binutils
+   oe_runmake DESTDIR="${D}" install
+
+cd ${S}/utils
+   oe_runmake DESTDIR="${D}" install
+
+   cd ${S}/parser
+   oe_runmake DESTDIR="${D}" install
+
+   cd ${S}/profiles
+   oe_runmake DESTDIR="${D}" install
+
+   cd ${S}/changehat/mod_apparmor
+   oe_runmake DESTDIR="${D}" install
+
+   if test -z "${PAMLIB}" ; then
+   cd ${S}/changehat/pam_apparmor
+   oe_runmake DESTDIR="${D}" install
+   fi
+
+   install ${WORKDIR}/apparmor ${D}/${INIT_D_DIR}/apparmor
+
+   install ${WORKDIR}/functions ${D}/lib/apparmor
+}
+
+INITSCRIPT_PACKAGES = "${PN}"
+INITSCRIPT_NAME = "apparmor"
+INITSCRIPT_PARAMS = "start 16 2 3 4 5 . stop 35 0 1 6 ."
+
+SYSTEMD_PACKAGES = "${PN}"
+SYSTEMD_SERVICE_${PN} = "apparmor.service"
+SYSTEMD_AUTO_ENABLE = "disable"
+
+PACKAGES += "python-${PN} mod-${PN}"
+
+FILES_${PN} += "/lib/apparmor/ ${sysconfdir}/apparmor"
+FILES_mod-${PN} = "${libdir}/apache2/modules/*"
+FILES_python-${PN} = "${PYTHON_SITEPACKAGES_DIR}"
+
+RDEPENDS_${PN} += "bash perl"
diff --git a/recipes-security/AppArmor/files/apparmor 
b/recipes-security/AppArmor/files/apparmor
new file mode 100644
index 000..c73c1ce
--- /dev/null
+++ b/recipes-security/AppArmor/files/apparmor
@@ -0,0 +1,211 @@
+#!/bin/sh
+# --
+#Copyright (c) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007
+# NOVELL (All rights reserved

Re: [yocto] [meta-raspberrypi] Master doesn't seem to be building right...

2016-10-31 Thread Khem Raj

For clarity if your workspace is krogoth based used krogoth branch for rpi
layer too. Master has hot incompatible changes which requires morty+ of oe
core

On Oct 31, 2016 10:06 AM, "Andrei Gherzan"  wrote:

> On Fri, Oct 14, 2016 at 03:26:53PM +, Frank Earl wrote:
> > It's boggling on the sd card image build.  Attached is the console
> output from the build (Don't need the log, this one's clear from the build
> fail output.) and a dump of the directory structures in
> tmp/deploy/images/raspberrypi2 from my setup.
> >
> > It's choking on trying to put the overlays onto the sd card image:
> >
> > /home/frank/git_repos/guardhat/build/tmp/deploy/
> images/raspberrypi2/Image-hifiberry-amp.dtbo: No such file or directory
> > | WARNING: /home/frank/git_repos/guardhat/build/tmp/work/
> raspberrypi2-poky-linux-gnueabi/gh-base-image/1.0-r0/
> temp/run.do_image_rpi_sdimg.26079:1 exit 1 from 'mcopy -i
> /home/frank/git_repos/guardhat/build/tmp/work/raspberrypi2-poky-linux-
> gnueabi/gh-base-image/1.0-r0/boot.img -s /home/frank/git_repos/
> guardhat/build/tmp/deploy/images/raspberrypi2/Image-${DTB_BASE_NAME}.${DTB_EXT}
> ::overlays/${DTB_BASE_NAME}.${DTB_EXT}'
> >
> >
> > Directory path:
> >
> >   4 -rw-r--r-- 2 frank frank  779 Oct 13 20:27 /home/frank/git_repos/
> guardhat/build/tmp/deploy/images/raspberrypi2/Image-1-4.
> 4.23+git0+c2a1d97553-r0-hifiberry-amp.dtbo-20161014012231.dtb
> >
> > So, the backing file seems to be there...but...
> >
> > 4 lrwxrwxrwx 1 frank frank   71 Oct 13 20:45
> /home/frank/git_repos/guardhat/build/tmp/deploy/images/raspberrypi2/Image-hifiberry-amp.dtbo.dtb
> -> Image-1-4.4.23+git0+c2a1d97553-r0-hifiberry-amp.dtbo-20161014012231.dtb
> >
> >
> > Heh...  Something's not QUITE right there.  The packager is looking for
> .dtbo's and we're symlinking .dtb's...I'm looking through the path
> trying to understand how it's setting the 'latest-build' symlinks, but if
> someone actually has a hint for me, it'd be appreciated.  :-D
> >
> >
> >
> > Frank Earl
> >
> >
> >
> > Frank Earl
> >
> >
> >
> > Legal Disclaimer:
> > The information contained in this message may be privileged and
> confidential. It is intended to be read only by the individual or entity to
> whom it is addressed or by their designee. If the reader of this message is
> not the intended recipient, you are on notice that any distribution of this
> message, in any form, is strictly prohibited. If you have received this
> message in error, please immediately notify the sender and delete or
> destroy any copy of this message!
>
> > Loading cache...done.
> > Loaded 2741 entries from dependency cache.
> > WARNING: No recipes available for:
> >   /home/frank/git_repos/guardhat/build/../meta-gh/
> recipes-bsp/u-boot/u-boot-ti-staging_2015.07.bbappend
> > NOTE: Resolving any missing task queue dependencies
> >
> > Build Configuration:
> > BB_VERSION= "1.30.0"
> > BUILD_SYS = "x86_64-linux"
> > NATIVELSBSTRING   = "universal"
> > TARGET_SYS= "arm-poky-linux-gnueabi"
> > MACHINE   = "raspberrypi2"
> > DISTRO= "poky"
> > DISTRO_VERSION= "2.1.1"
> > TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4
> callconvention-hard cortexa7"
> > TARGET_FPU= "hard"
> > meta
> > meta-poky
> > meta-yocto-bsp= "krogoth:e93596fe74927e2e2f4dd7f671994ccb9744cff8"
> > meta-linaro-toolchain = "krogoth:85faf6c6824597e7fd9e2d35fc9d8d
> a2e9f90bc7"
> > meta-oe
> > meta-filesystems
> > meta-networking
> > meta-multimedia
> > meta-initramfs
> > meta-systemd
> > meta-python   = "krogoth:851a064b53dca3b14dd33eaaaca9573b1a36bf0e"
> > meta-telephony= "HEAD:8cf5a67850adf270bc2fdb4c0ed708b0ba037670"
> > meta-gh   = "master:12dc12456e7f6f486ca2815603c5f21f74c2d2c2"
> > meta-ti   = "master:6cb779a6ba1b0693f6bf82777e1a333effe6fca5"
> > meta-raspberrypi  = "master:05be947a31df873405cdd70ada210c9f7f7b132f"
> >
>
> I see that you are using master of meta-raspberrypi. Can you try with
> the krogoth branch, please?
>
> --
> Andrei Gherzan
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto 2.2 minimum kernel requirement

2016-10-31 Thread Paul Eggleton

On Mon, 31 Oct 2016 09:37:07 Khem Raj wrote:
> > On Oct 31, 2016, at 7:37 AM, Vuille, Martin (Martin) 
> > wrote:
> > 
> > We are looking at upgrading from Yocto 1.8 to 2.2.
> > 
> > Yocto 2.2 has a minimum kernel requirement of 3.2.0.
> > 
> > This isn’t an issue for our target (ARMv5, Linux 4.4) but may be
> > an issue for our automated build machines (x86, Linux 2.6.32—CentOS 6.)
> > 
> > However, there is a note that says
> > “For x86 and x86_64, you can reset OLDEST_KERNEL
> >  > DEST_KERNEL> to anything down to 2.6.32 if desired.”
> > 
> > Is it possible to configure things such that we can keep supporting the
> > old kernel for the SDK while we support a more up-to-date kernel for the
> > target?
>
> I think that should be the default. We do not set it for x86/nativesdk case.
> File a ticket if thats not the case.

SDK_OLDEST_KERNEL is the variable that's supposed to be controlling this, but 
I noticed a couple of weeks ago that we aren't feeding SDK_OLDEST_KERNEL into 
glibc for nativesdk, so we should fix that - I've filed a bug [1] and will 
sort that out. I think we should probably set the SDK_OLDEST_KERNEL default 
for x86 to 2.6.32 at the same time - I assume there are no objections?

Cheers,
Paul

[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=10561

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] esdk without using Poky?

2016-10-31 Thread Paul Eggleton

Hi Gary,

On Mon, 31 Oct 2016 13:19:18 Gary Thomas wrote:
> I'm trying to build an extensible SDK (eSDK) for my target and running into
> a few problems.
> 
>gthomas@zeus:~$
> /work/tmp/mlb-glibc-x86_64-arm-toolchain-ext-2.2+snapshot.sh MLB
> @SDK_TITLE@ Associates Embedded (Poky/Yocto Powered) Extensible SDK
> installer version 2.2+snapshot
> ===
> Enter target directory for SDK (default:
> ~/mlb_sdk):
>You are about to install the SDK to "/home/gthomas/mlb_sdk".
> Proceed[Y/n]? y Extracting SDK.done
>Setting it up...
>Extracting buildtools...
>Preparing build system...
>Error: 'meta-poky/conf' must be a directory containing local.conf &
> bblayers.conf
> 
> The first thing I notice is the banner which should read:
>MLB & Associates Embedded (Poky/Yocto Powered) Extensible SDK installer
> version 2.2+snapshot
> ===

Ah, I see what's going wrong here - we're doing a sed replacement and the 
ampersand is being interpreted as an "insert matched string" directive - my 
fault. I'll insert some escaping.

> The second is that I use my own distribution (not poky).  How can I
> build an eSDK using my distribution?

FYI the eSDK will use whatever you set in DISTRO - you have your own 
distribution, but I assume you are still referencing poky - perhaps as an 
include from your distro configuration? At least meta-poky must be in your 
bblayers.conf, otherwise I don't think you'd be getting this error.

Regardless of that, there is a bug here somewhere. What do you have under 
layers/ in the generated SDK? Are you setting TEMPLATECONF anywhere?

> Once I ran into this error, I tried rebuilding using the [old] SDK.
> I noticed that it seemed to rebuild [most] everything all over again.
> Is there no shared state / reusable components between the eSDK and SDK?

The extensible SDK and standard SDK are quite different - the host part of the 
extensible SDK is built out of -native rather than nativesdk- components 
(aside from buildtools-tarball, that is) so there are lots of things that need 
to be built if you subsequently build the standard SDK and you haven't done so 
already. It shouldn't be "almost everything", but I appreciate it's often hard 
to tell.

> Finally, since I had to install SDK and not eSDK, I'm missing some tools
> I was hoping to have.  I want to build PRU programs for the BeagleBoneBlack
> and I'm using meta-ti to import those tools and programs.  I was expecting
> the PRU tools which come from ti-cgt-pru-native to be included with my
> eSDK/SDK, but they don't seem to be, at least not in the SDK.  How can I
> get these tools available so I can use the SDK to develop PRU code for the
> BBB?

Not sure exactly, but for the standard SDK I would assume you'd need to append
nativesdk- to TOOLCHAIN_HOST_TASK so that those tools get included. 
Aside from the BSP setting that variable (which probably isn't a good idea) 
there isn't currently a means of host tools automatically getting pulled into 
the SDK based on the target, though it has been discussed [1].

Cheers,
Paul

[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=5429

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto 2.2 minimum kernel requirement

2016-10-31 Thread Khem Raj


> On Oct 31, 2016, at 2:59 PM, Paul Eggleton  
> wrote:
> 
> On Mon, 31 Oct 2016 09:37:07 Khem Raj wrote:
>>> On Oct 31, 2016, at 7:37 AM, Vuille, Martin (Martin) 
>>> wrote:
>>> 
>>> We are looking at upgrading from Yocto 1.8 to 2.2.
>>> 
>>> Yocto 2.2 has a minimum kernel requirement of 3.2.0.
>>> 
>>> This isn’t an issue for our target (ARMv5, Linux 4.4) but may be
>>> an issue for our automated build machines (x86, Linux 2.6.32—CentOS 6.)
>>> 
>>> However, there is a note that says
>>> “For x86 and x86_64, you can reset OLDEST_KERNEL
>>> >> DEST_KERNEL> to anything down to 2.6.32 if desired.”
>>> 
>>> Is it possible to configure things such that we can keep supporting the
>>> old kernel for the SDK while we support a more up-to-date kernel for the
>>> target?
>> 
>> I think that should be the default. We do not set it for x86/nativesdk case.
>> File a ticket if thats not the case.
> 
> SDK_OLDEST_KERNEL is the variable that's supposed to be controlling this, but
> I noticed a couple of weeks ago that we aren't feeding SDK_OLDEST_KERNEL into
> glibc for nativesdk, so we should fix that - I've filed a bug [1] and will
> sort that out. I think we should probably set the SDK_OLDEST_KERNEL default
> for x86 to 2.6.32 at the same time - I assume there are no objections?

Yes, its for nativesdk/glibc, I think for target x86 we should keep 3.2

> 
> Cheers,
> Paul
> 
> [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=10561
> 
> --
> 
> Paul Eggleton
> Intel Open Source Technology Centre



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto 2.2 minimum kernel requirement

2016-10-31 Thread Paul Eggleton

On Mon, 31 Oct 2016 15:36:24 Khem Raj wrote:
> > On Oct 31, 2016, at 2:59 PM, Paul Eggleton 
> > wrote:> 
> > On Mon, 31 Oct 2016 09:37:07 Khem Raj wrote:
> >>> On Oct 31, 2016, at 7:37 AM, Vuille, Martin (Martin) 
> >>> wrote:
> >>> 
> >>> We are looking at upgrading from Yocto 1.8 to 2.2.
> >>> 
> >>> Yocto 2.2 has a minimum kernel requirement of 3.2.0.
> >>> 
> >>> This isn’t an issue for our target (ARMv5, Linux 4.4) but may be
> >>> an issue for our automated build machines (x86, Linux 2.6.32—CentOS 6.)
> >>> 
> >>> However, there is a note that says
> >>> “For x86 and x86_64, you can reset OLDEST_KERNEL
> >>>  >>> L
> >>> DEST_KERNEL> to anything down to 2.6.32 if desired.”
> >>> 
> >>> Is it possible to configure things such that we can keep supporting the
> >>> old kernel for the SDK while we support a more up-to-date kernel for the
> >>> target?
> >> 
> >> I think that should be the default. We do not set it for x86/nativesdk
> >> case. File a ticket if thats not the case.
> > 
> > SDK_OLDEST_KERNEL is the variable that's supposed to be controlling this,
> > but I noticed a couple of weeks ago that we aren't feeding
> > SDK_OLDEST_KERNEL into glibc for nativesdk, so we should fix that - I've
> > filed a bug [1] and will sort that out. I think we should probably set
> > the SDK_OLDEST_KERNEL default for x86 to 2.6.32 at the same time - I
> > assume there are no objections?
>
> Yes, its for nativesdk/glibc, I think for target x86 we should keep 3.2

Right, I'm not proposing changing the target value.

It turns out setting SDK_OLDEST_KERNEL in an arch-specific manner is a little 
awkward since there aren't overrides that can be used for the SDK value, but 
we can do it from conf/machine-sdk/*.conf though.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto 2.2 minimum kernel requirement

2016-10-31 Thread Khem Raj

On Mon, Oct 31, 2016 at 3:44 PM, Paul Eggleton
 wrote:
> On Mon, 31 Oct 2016 15:36:24 Khem Raj wrote:
>> > On Oct 31, 2016, at 2:59 PM, Paul Eggleton 
>> > wrote:>
>> > On Mon, 31 Oct 2016 09:37:07 Khem Raj wrote:
>> >>> On Oct 31, 2016, at 7:37 AM, Vuille, Martin (Martin) 
>> >>> wrote:
>> >>>
>> >>> We are looking at upgrading from Yocto 1.8 to 2.2.
>> >>>
>> >>> Yocto 2.2 has a minimum kernel requirement of 3.2.0.
>> >>>
>> >>> This isn’t an issue for our target (ARMv5, Linux 4.4) but may be
>> >>> an issue for our automated build machines (x86, Linux 2.6.32—CentOS 6.)
>> >>>
>> >>> However, there is a note that says
>> >>> “For x86 and x86_64, you can reset OLDEST_KERNEL
>> >>> > >>> L
>> >>> DEST_KERNEL> to anything down to 2.6.32 if desired.”
>> >>>
>> >>> Is it possible to configure things such that we can keep supporting the
>> >>> old kernel for the SDK while we support a more up-to-date kernel for the
>> >>> target?
>> >>
>> >> I think that should be the default. We do not set it for x86/nativesdk
>> >> case. File a ticket if thats not the case.
>> >
>> > SDK_OLDEST_KERNEL is the variable that's supposed to be controlling this,
>> > but I noticed a couple of weeks ago that we aren't feeding
>> > SDK_OLDEST_KERNEL into glibc for nativesdk, so we should fix that - I've
>> > filed a bug [1] and will sort that out. I think we should probably set
>> > the SDK_OLDEST_KERNEL default for x86 to 2.6.32 at the same time - I
>> > assume there are no objections?
>>
>> Yes, its for nativesdk/glibc, I think for target x86 we should keep 3.2
>
> Right, I'm not proposing changing the target value.
>
> It turns out setting SDK_OLDEST_KERNEL in an arch-specific manner is a little
> awkward since there aren't overrides that can be used for the SDK value, but
> we can do it from conf/machine-sdk/*.conf though.
>

yes understood, we do have aarch64 as another option for nativesdk but
practically
not there yet I guess.

> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH] samhain: update to 4.2.0

2016-10-31 Thread Armin Kuster

* Changes:

  - New option 'SetAuditdFlags = r|w|x|a' to (re-)define the flags supplied
to auditd.

  - New option 'PortCheckDevice = device' for the port check module, to monitor
a device regardless of the address assigned to it.

  - Fix for the case sensitivity of the arguments to the Severity/Class options.

  - Compiler warnings with gcc 6.2 and a few minor bugs have been fixed.

Signed-off-by: Armin Kuster 
---
 .../samhain/{samhain-client_4.1.5.bb => samhain-client_4.2.0.bb}  | 0
 .../samhain/{samhain-server_4.1.5.bb => samhain-server_4.2.0.bb}  | 0
 recipes-security/samhain/samhain.inc  | 4 ++--
 3 files changed, 2 insertions(+), 2 deletions(-)
 rename recipes-security/samhain/{samhain-client_4.1.5.bb => 
samhain-client_4.2.0.bb} (100%)
 rename recipes-security/samhain/{samhain-server_4.1.5.bb => 
samhain-server_4.2.0.bb} (100%)

diff --git a/recipes-security/samhain/samhain-client_4.1.5.bb 
b/recipes-security/samhain/samhain-client_4.2.0.bb
similarity index 100%
rename from recipes-security/samhain/samhain-client_4.1.5.bb
rename to recipes-security/samhain/samhain-client_4.2.0.bb
diff --git a/recipes-security/samhain/samhain-server_4.1.5.bb 
b/recipes-security/samhain/samhain-server_4.2.0.bb
similarity index 100%
rename from recipes-security/samhain/samhain-server_4.1.5.bb
rename to recipes-security/samhain/samhain-server_4.2.0.bb
diff --git a/recipes-security/samhain/samhain.inc 
b/recipes-security/samhain/samhain.inc
index 7987886..789150b 100644
--- a/recipes-security/samhain/samhain.inc
+++ b/recipes-security/samhain/samhain.inc
@@ -9,8 +9,8 @@ SRC_URI = 
"http://la-samhna.de/archive/samhain_signed-${PV}.tar.gz \
   file://${INITSCRIPT_NAME}.default \
  "
 
-SRC_URI[md5sum] = "bdb6d2653d706f3180e37ef3d95c824d"
-SRC_URI[sha256sum] = 
"4ff4c38765c942abbaac2577df4c8c4940482a1bffc4a719f181c4fca6f173a7"
+SRC_URI[md5sum] = "d98a55646b14f9419fcedde909d1bf02"
+SRC_URI[sha256sum] = 
"6b2db91fc92b3a9fc2edcc6ee16438156753c05f69c114856289e9f25ba0e50a"
 
 S = "${WORKDIR}/samhain-${PV}"
 
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] how to copy a tar file to Root file system

2016-10-31 Thread Swapna.Gurumani

Hi, I have a tar file on my local drive and I want to untar this and copy it to 
my rootfilesystem image.
Please find attached the .bb recipe I am using.
When I run bitbake for this recipe, my build breaks with the following error:
ERROR: crank-1.0-r0 do_install: Function failed: do_install (log file is locate 
at 
/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neonpoky-linux-gnueabi/crank/1.0-r0/temp/log.do_install.16738)
ERROR: Logfile of failure stored in: 
/home/swapna/workspace/work/yocto/poky/buid-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/temp/log.do_intall.16738
Log data follows:
| DEBUG: Executing shell function do_install
| make: *** No rule to make target 'install'.  Stop.
| WARNING: 
/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5f-neon-poky-linux-gnueabi/crank/1.0-r0/temp/run.do_install.16738:1
 exit 2 from make 
INSTALL_ROOT=/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/crtexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/image
 install'
| ERROR: Function failed: do_install (log file is located at 
/home/swapna/worksace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crak/1.0-r0/temp/log.do_install.16738)
ERROR: Task 1095 
(/home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipe-qt/apps/crank_1.0.bb,
 do_install) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3563 tasks of which 3562 didn't need to be 
rerunand 1 failed.
No currently running tasks (3056 of 4701)

Summary: 1 task failed:
  
/home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipes-qt/apps/crank_.0.bb,
 do_install
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.



Can someone help me in fixing the .bb recipe?
Regards
Swapna


crank_1.0.bb
Description: crank_1.0.bb
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] how to copy a tar file to Root file system

2016-10-31 Thread Paul Eggleton

Hi Swapna,

On Tue, 01 Nov 2016 01:17:18 swapna.gurum...@microchip.com wrote:
> Hi, I have a tar file on my local drive and I want to untar this and copy it
> to my rootfilesystem image. Please find attached the .bb recipe I am using.
> When I run bitbake for this recipe, my build breaks with the following
> error: ERROR: crank-1.0-r0 do_install: Function failed: do_install (log
> file is locate at
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon
> poky-linux-gnueabi/crank/1.0-r0/temp/log.do_install.16738) ERROR: Logfile of
> failure stored in:
> /home/swapna/workspace/work/yocto/poky/buid-atmel/tmp/work/cortexa5hf-neon-
> poky-linux-gnueabi/crank/1.0-r0/temp/log.do_intall.16738
> Log data follows:
> | DEBUG: Executing shell function do_install
> | make: *** No rule to make target 'install'.  Stop.
> | WARNING:
> | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5f-neo
> | n-poky-linux-gnueabi/crank/1.0-r0/temp/run.do_install.16738:1 exit 2 from
> | make
> | INSTALL_ROOT=/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/
> | crtexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/image install' ERROR:
> | Function failed: do_install (log file is located at
> | /home/swapna/worksace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neo
> | n-poky-linux-gnueabi/crak/1.0-r0/temp/log.do_install.16738)
> ERROR: Task 1095
> (/home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipe-qt/apps/cran
> k_1.0.bb, do_install) failed with exit code '1' NOTE: Tasks Summary:
> Attempted 3563 tasks of which 3562 didn't need to be rerunand 1 failed. No
> currently running tasks (3056 of 4701)

You say that this is a tarball that you want to untar into the image, but 
inheriting qmake5 and setting DEPENDS suggests that there's more to it than 
that.

As for the failure, it's hard to say without seeing what's been unpacked, but 
perhaps the .pro file in this project doesn't actually have any install 
directives needed to create an install target in the Makefile? If that's the 
case you'll need to install the files "manually" within do_install using 
install and/or cp commands.

A couple of other notes:

* You can simply set FILES_${PN} to "/opt/crank" here, no need to list each 
file unless you have more than one package and you want to split the files 
among them.

* Is this really MIT licensed, or should the LICENSE in fact be "CLOSED"? Then 
you wouldn't need to set LIC_FILES_CHKSUM either. (I'm assuming this is closed 
source software you're packaging).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] how to copy a tar file to Root file system

2016-10-31 Thread Paul Eggleton

On Tue, 01 Nov 2016 03:12:15 swapna.gurum...@microchip.com wrote:
> Thank you so much for your speedy response!!! Actually I ended up attaching
> an older bb file. I had some more modifications as attached. I changed
> license to close per your suggestion. Should I change FILES_${PN} to look
> like this:
> 
> FILES_${PN} = "/opt/crank/"

Yes that would be a lot simpler.

> Actually to be honest I took inspiration from another recipe to make mine.
> All I want to do it take a locally stored .tar.gz file, untar it and put it
> in the /opt folder of my RFS. I notice that the tar file has been extracted
> and I see it in the
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-
> poky-linux-gnueabi/crank/1.0-r0/crank Folder.
> Do I need a makefile? I don't know what a .po file is..

No, for something simple like this you can do everything you need from the 
recipe.

> How do I install the files "manually" within do_install using install and/or
> cp commands? Like this?:
> 
> do_install() {
> make INSTALL_ROOT=${D} install<< what does this do>>
> cp -ar ${B}/crank/ ${D}/opt/
> }
> 

I think you want:

do_install() {
cp -a --no-preserve=ownership ${WORKDIR}/crank ${D}/opt/
}

You don't need the "make install" line.

Cheers,
Paul

PS: please keep the mailing list on CC. Thanks.


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Reminder: Yocto Project Technical Team Meeting - Tuesday, Nov. 1, 2016 8:00 AM US Pacific Time

2016-10-31 Thread Jolley, Stephen K

Tuesday, Nov. 1, 2016 8:00 AM US Pacific Time



Agenda:



* Opens collection - 5 min (Stephen)

* Yocto Project status - 5 min (Stephen/team)

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features

* Opens - 10 min

* Team Sharing - 10 min



We encourage people attending the meeting to logon the Yocto Project IRC 
chancel during the meeting (optional):



Yocto IRC: http://webchat.freenode.net/?channels=#yocto

IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html



Conference Details:

Company:   WIND RIVER SYS

Ready-Access Number: 8007302996/9139049836

Access Code: 2705751


For International numbers see: 
https://www.yoctoproject.org/tools-resources/community/monthly-technical-call


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:(503) 712-0534
*Cell:   (208) 244-4460
* Email:stephen.k.jol...@intel.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] how to copy a tar file to Root file system

2016-10-31 Thread Swapna.Gurumani

With the attached recipe I get the following error:
ERROR: crank-1.0-r0 do_package: QA Issue: crank: Files/directories were 
installed but not shipped in any package:
  /opt
  /opt/sb_launch.sh
  /opt/clear_buffers
  /opt/runsb.sh
  /opt/README.txt

..
...
.
.
.

  /opt/WashingMachine_V2/fonts/Roboto-Regular.ttf
Please set FILES such that these items are packaged. Alternatively if they are 
unneeded, avoid installing them or delete them within do_install.
crank: 1733 installed and not shipped files. [installed-vs-shipped]
ERROR: crank-1.0-r0 do_package: Fatal QA errors found, failing task.
ERROR: crank-1.0-r0 do_package: Function failed: do_package
ERROR: Logfile of failure stored in: 
/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/temp/log.do_package.19127
ERROR: Task 1104 
(/home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipes-qt/apps/crank_1.0.bb,
 do_package) failed with exit code '1'

I feel am very close!! 
Regards
Swapna

-Original Message-
From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] 
Sent: Monday, October 31, 2016 8:35 PM
To: Swapna Gurumani - C40450 
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] how to copy a tar file to Root file system

On Tue, 01 Nov 2016 03:12:15 swapna.gurum...@microchip.com wrote:
> Thank you so much for your speedy response!!! Actually I ended up 
> attaching an older bb file. I had some more modifications as attached. 
> I changed license to close per your suggestion. Should I change 
> FILES_${PN} to look like this:
> 
> FILES_${PN} = "/opt/crank/"

Yes that would be a lot simpler.

> Actually to be honest I took inspiration from another recipe to make mine.
> All I want to do it take a locally stored .tar.gz file, untar it and 
> put it in the /opt folder of my RFS. I notice that the tar file has 
> been extracted and I see it in the
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf
> -neon- poky-linux-gnueabi/crank/1.0-r0/crank Folder.
> Do I need a makefile? I don't know what a .po file is..

No, for something simple like this you can do everything you need from the 
recipe.

> How do I install the files "manually" within do_install using install 
> and/or cp commands? Like this?:
> 
> do_install() {
> make INSTALL_ROOT=${D} install<< what does this do>>
> cp -ar ${B}/crank/ ${D}/opt/
> }
> 

I think you want:

do_install() {
cp -a --no-preserve=ownership ${WORKDIR}/crank ${D}/opt/ }

You don't need the "make install" line.

Cheers,
Paul

PS: please keep the mailing list on CC. Thanks.

crank_1.0.bb
Description: crank_1.0.bb
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

49 matches

Mail list logo