[yocto] [ANNOUNCEMENT] Yocto Project 2.0.2 (Jethro 14.0.2) Released

2016-06-03 Thread Tracy Graydon
Hello, The latest release of the Yocto Project 2.0.2 (jethro-14.0.2) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/poky-jethro-14.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.0.2/poky-fido-14.0.2.tar.bz2 A gpg signed version of these

[yocto] [opkg-utils PATCH] arfile.py: remove dependency on python-future

2016-06-03 Thread Alejandro del Castillo
Python-future provides a python2 compatible object class (provides next method). Since method is not used, remove dependency. Signed-off-by: Alejandro del Castillo --- arfile.py | 1 - 1 file changed, 1 deletion(-) diff --git a/arfile.py b/arfile.py index 4bab526..1c42bc7 100644 --- a/arfile.py

[yocto] [meta-raspberrypi][PATCH V2 4/4] sdcard_image-rpi: Always install dtb files

2016-06-03 Thread Paul Barker
We now need dtb files when booting via u-boot. Signed-off-by: Paul Barker --- classes/sdcard_image-rpi.bbclass | 40 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/classes/sdcard_image-rpi.bbclass b/classes/sdcard_image-rpi.bbclass index

[yocto] [meta-raspberrypi][PATCH V2 3/4] rpi-mkimage: Remove unused recipe

2016-06-03 Thread Paul Barker
The rpi-mkimage tools are no longer used. Recent Raspberry Pi firmware can directly boot a Linux kernel image using device tree and mainline u-boot supports Raspberry Pi without the use of these tools. Signed-off-by: Paul Barker --- recipes-bsp/rpi-mkimage/rpi-mkimage/License| 25 ---

[yocto] [meta-raspberrypi][PATCH V2 1/4] linux-raspberrypi: rpi-mkimage is no longer needed

2016-06-03 Thread Paul Barker
Recent versions of the Raspberry Pi firmware can directly handle kernel images which use device tree. The modifications made by rpi-mkimage are no longer needed. Signed-off-by: Paul Barker --- recipes-kernel/linux/linux-raspberrypi.inc | 18 -- 1 file changed, 18 deletions(-) di

[yocto] [meta-raspberrypi][PATCH V2 2/4] u-boot: Use mainline u-boot recipe from oe-core

2016-06-03 Thread Paul Barker
The repository used by u-boot-rpi has not been updated since 2012. In the meantime, mailine u-boot has gained Raspberry Pi support. All we need to do is set UBOOT_MACHINE to an appropriate value in the machine config files. Currently configs are only provided for raspberrypi and raspberrypi2. The

[yocto] [meta-raspberrypi][PATCH V2 0/4] Drop rpi-mkimage and use upstream u-boot

2016-06-03 Thread Paul Barker
Changes for V2: * Don't remove linux-raspberrypi 3.18 just yet * Drop move of PV setting out of linux-raspberrypi.inc Paul Barker (4): linux-raspberrypi: rpi-mkimage is no longer needed u-boot: Use mainline u-boot recipe from oe-core rpi-mkimage: Remove unused recipe sdcard_image-r

Re: [yocto] [meta-raspberrypi][PATCH 1/6] linux-raspberrypi: Allow override of PV

2016-06-03 Thread Paul Barker
On Fri, 3 Jun 2016 09:07:37 +0300 Ionel Badisor wrote: > On 06/03/2016 12:25 AM, Paul Barker wrote: > > On Thu, 2 Jun 2016 10:59:37 +0300 > > Ionel Badisor wrote: > > > >> On 06/01/2016 08:55 PM, Paul Barker wrote: > >>> On Tue, 31 May 2016 10:39:03 +0300 > >>> Khem Raj wrote: > >>> > On M

Re: [yocto] Per image customizations

2016-06-03 Thread Oleksandr Poznyak
I found that that’s an issue with rpm packages. I didn't expect there might be some issue with rpm. If you really don't care which package management system to use, switch to deb: PACKAGE_CLASSES = "package_deb" On Fri, Jun 3, 2016 at 4:52 PM, Diego wrote: > Hi Oleksandr, > > In data mercoledì

Re: [yocto] rootfs mounted read-only on Live USB (x86-64)

2016-06-03 Thread Bruce Ashfield
On 2016-06-03 11:33 AM, Bruce Ashfield wrote: On 2016-06-03 10:15 AM, Dan O'Donovan wrote: On 06/03/2016 10:54 AM, Oleksandr Poznyak wrote: Hi, Hi Oleksandr Check if "read-only-rootfs" feature is added to any of these variables either in your local.conf or your image bitbake recipe: Somethin

Re: [yocto] rootfs mounted read-only on Live USB (x86-64)

2016-06-03 Thread Bruce Ashfield
On 2016-06-03 10:15 AM, Dan O'Donovan wrote: On 06/03/2016 10:54 AM, Oleksandr Poznyak wrote: Hi, Hi Oleksandr Check if "read-only-rootfs" feature is added to any of these variables either in your local.conf or your image bitbake recipe: Something like that: IMAGE_FEATURES = "read-only-rootf

[yocto] Yocto Project Status WW23

2016-06-03 Thread Jolley, Stephen K
Current Dev Position: YP 2.2 M1 Next Deadline: YP 2.2 cut off: June 13, 2016 SWAT team rotation: Alejandro -> Jussi https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: *Python 3 has now merged, BitBake (inc. Toaster) and OE-Core now use python3 inste

Re: [yocto] rootfs mounted read-only on Live USB (x86-64)

2016-06-03 Thread Dan O'Donovan
On 06/03/2016 10:54 AM, Oleksandr Poznyak wrote: > Hi, Hi Oleksandr > Check if "read-only-rootfs" feature is added to any of these variables either > in your local.conf or your image bitbake recipe: > > Something like that: > > IMAGE_FEATURES = "read-only-rootfs" > > EXTRA_IMAGE_FEATURES += "read-

Re: [yocto] Per image customizations

2016-06-03 Thread Diego
Hi Oleksandr, In data mercoledì 1 giugno 2016 21:57:32, Oleksandr Poznyak ha scritto: > Here is the content of bbappend recipe for base-files recipe: > > FILESEXTRAPATHS_append := "${THISDIR}/${PN}" > > SRC_URI += "file://fstab-flash \ > file://fstab-regular \ > " > > PACKAGES +

Re: [yocto] rootfs mounted read-only on Live USB (x86-64)

2016-06-03 Thread Oleksandr Poznyak
Hi, Check if "read-only-rootfs" feature is added to any of these variables either in your local.conf or your image bitbake recipe: Something like that: IMAGE_FEATURES = "read-only-rootfs" EXTRA_IMAGE_FEATURES += "read-only-rootfs" Thanks, Oleksandr Poznyak! On Fri, Jun 3, 2016 at 12:06 PM, Da

[yocto] rootfs mounted read-only on Live USB (x86-64)

2016-06-03 Thread Dan O'Donovan
Hi all Has anyone else noticed that the root file-system appears to be mounted read-only when booting a Live USB image from Yocto 2.1. This is on a sato build from the krogoth branch of poky and meta-intel, for a generic x86-64 machine (4.4 kernel). I'm transferring the resulting .iso image to