Re: [yocto] [Openembedded-architecture] Standalone image writer

[Paul Eggleton]

On Mon, 29 Feb 2016 04:48:57 Gary Thomas wrote:
> On 02/29/2016 04:31 AM, Trevor Woerner wrote:
> > On 02/28/16 20:46, Khem Raj wrote:
> >>> On Feb 28, 2016, at 4:17 PM, Paul Eggleton
> >>>  wrote:
> >>> 
> >>> (changing subject line so people don't miss this slight tangent)
> >>> 
> >>> I'd almost completely forgotten, but the part of what we wrote for Hob
> >>> to
> >>> write images to a USB stick or SD card (bitbake/bin/image-writer) is
> >>> actually a standalone application. There's not a lot to it - pick your
> >>> image file and then the device you want to write it to; it has some
> >>> logic in it to not let you accidentally write to devices that aren't
> >>> USB sticks.
> >>> 
> >>> A few points:
> >>> 
> >>> - I'm not sure very many people know this tool exists, so it's likely
> >>> it's not being widely used. Having said that it is a nice simple UI
> >>> that does the job.
> >>> 
> >>> - It shares some code with Hob, but mostly not the bits with code
> >>> quality
> >>> issues, though it is still GTK+ 2 based.
> >>> 
> >>> - It doesn't support the advanced SD card writing functionality that has
> >>> been implented within wic over the last few releases, which is pretty
> >>> important for devices where a special partition layout is expected by
> >>> the bootloader.
> >>> 
> >>> - Toaster can't really have this functionality in it because it's web
> >>> based
> >>> and the web server might not be running locally, so writing to a local
> >>> USB
> >>> stick or SD card isn't going to be practical from there; about all it
> >>> could do is provide instructions on how to write the image once you've
> >>> downloaded it.
> >>> 
> >>> - I believe there are other equivalent tools out there that various
> >>> distros
> >>> use for taking a downloadable ISO image and writing it to a USB stick. I
> >>> haven't done a survey to find out if if any of them work in quite the
> >>> same way; I know some of them actually unpack the image and then
> >>> re-create a filesystem on the device, which isn't the right thing for
> >>> our images.
> >>> 
> >>> - We do have a command-line equivalent in the form of
> >>> scripts/contrib/ddimage in OE-Core. Of course it's command-line and
> >>> thus less friendly but it does the job (and also has some safeguards
> >>> against writing to the wrong device).
> >>> 
> >>> So what do we do with this? We have two choices really:
> >>> 
> >>> A) Drop bitbake/bin/imagewriter along with Hob; we could potentially
> >>> resurrect it again later if desired
> >>> 
> >>> B) Preserve it along with the shared modules that it requires
> >>> 
> >>> Thoughts?
> >> 
> >> Option A. There are USB writer tool in your favorite distros and OSes,
> >> and I have seen people use those tools more often.
> > 
> > Some platforms, e.g. Minnow, use their own image writing script (i.e.
> > mkefidisk.sh). If there are other platforms which need some special tool
> > that isn't generically available from the host and the hob tool could be
> > made to accommodate them all, I'd prefer to see one tool that can do all
> > of them instead of a bunch of tools, one for each platform.
>
> As Paul mentioned, each platform seems to want to do this "their
> own way" which is troublesome at best for embedded systems.  I think
> it would be much better to maintain one way that works with what we
> are building (OE based embedded devices) rather than relying on the
> whims of others.  So, if it's not too hard, I'd prefer that this
> ability be kept, even as a stand-alone script.

Well, arguably the "one way that works" is supposed to be wic as far as the 
actual image writing is concerned. There's a bug open to ensure we support all 
of the reference platforms [1], and I'd encourage anyone developing a BSP with 
unusual partition/formatting requirements to work out how those can be 
supported in wic if they aren't already so we can get away from these BSP-
specific classes and scripts.

There isn't a frontend UI for wic that I am aware of though - as I mentioned 
earlier image-writer has no support for it, it's just doing a straight dd to 
the device.

Cheers,
Paul

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

-- 

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

[yocto] [Recipe reporting system] Upgradable recipe name list

[recipe-report]

This mail was sent out by Recipe reporting system.

This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version was detected.

Example:
RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable"

You can check the detail information at:

http://recipes.yoctoproject.org/

Package   VersionUpstream version  Maintainer   
NoUpgradeReason
  -    ---  
--
texinfo   6.06.1   Alejandro Hernandez
python-dbus   1.2.0  1.2.2 Alejandro Hernandez
python3-pip   8.0.0  8.0.3 Alejandro Hernandez
python3-setuptools19.4   20.2.2Alejandro Hernandez
python-pygobject  2.28.3 3.19.90   Alejandro Hernandez  
Newer versions of python-py...
python-setuptools 19.4   20.2.2Alejandro Hernandez
liberation-fonts  1.04   2.00.1Alexander Kanavin2.x 
depends on fontforge pa...
btrfs-tools   4.44.4.1 Alexander Kanavin
watchdog  5.14   5.15  Alexander Kanavin
nss   3.21   3.22.1Alexander Kanavin
mkelfimage4.0+gitX   4.3+gitAUTOINC+1b...  Alexander Kanavin
mkelfimage has been removed...
apt   1.0.10.1   1.2.4 Aníbal Limón
pinentry  0.9.2  0.9.7 Armin Kuster
linux-libc-headers4.44.4.3 Bruce Ashfield
guilt-native  0.35+gitX  0.36+gitAUTOINC+2...  Bruce Ashfield
sysstat   11.2.0 11.3.1Chen Qi
createrepo0.4.11 0.10.4Hongxu Jia   
Versions after 0.9.* use YU...
ghostscript   9.16   9.18  Hongxu Jia
elfutils  0.164  0.165 Hongxu Jia
libinput  1.1.4  1.2.1 Jussi Kukkonen
wayland   1.9.0  1.10.0Jussi Kukkonen
xrandr1.4.3  1.5.0 Jussi Kukkonen
openssh   7.1p2  7.2p1 Jussi Kukkonen
docbook-xsl-style...  1.78.1 1.79.1Jussi Kukkonen
gsettings-desktop...  3.19.3 3.19.90   Jussi Kukkonen
xserver-xorg  1.18.0 1.18.1Jussi Kukkonen
weston1.9.0  1.10.0Jussi Kukkonen
pixman0.32.8 0.34.0Jussi Kukkonen
xkeyboard-config  2.16   2.17  Jussi Kukkonen
vte   0.28.2 0.42.4Jussi Kukkonen   
matchbox-terminal needs to ...
linuxdoc-tools-na...  0.9.69 0.9.71Jussi Kukkonen
slang 2.2.4  2.3.0 Kai Kang
prelink   1.0+gitX   20151030.+gitAUTO...  Mark Hatle
rpm   5.4.14 5.4.15Mark Hatle   
5.4.15 has a package databa...
libpfm4   4.6.0  4.7.0 Matthew McClintock
db6.0.30 6.1.26Maxin B. John
Updating to 6.1.x requires ...
harfbuzz  1.2.1  1.2.3 Maxin B. John
xf86-input-libinput   0.16.0 0.17.0No maintainer
gdb-cross-canadia...  7.10.1 7.11  No maintainer
gdb-cross-i5867.10.1 7.11  No maintainer
apt-native1.0.10.1   1.2.4 No maintainer
ifupdown  0.8.2  0.8.10No maintainer
sgmlspl-native1.1+gitX   1.03+gitAUTOINC+f...  No maintainer
gdb   7.10.1 7.11  Richard Purdie
nasm  2.11.082.12  Richard Purdie
libcap2.24   2.25  Robert Yang
mklibs-native 0.1.40 0.1.41Robert Yang
lsbinitscripts9.64   9.65  Ross Burton
base-passwd   3.5.29 3.5.39Ross Burton  
Version 3.5.38 requires cde...
gettext   0.19.6 0.19.7Wenzong Fan
chkconfig 1.3.58 1.7   Wenzong Fan  
Version 1.5 requires selinux

Upgradable count: 42
Upgradable total count: 51

The based commit is:

commit 390bad905537820f49add855c95d726b5b55c8fa
Author: Richard Purdie 
Date:   Sun Feb 28 22:53:03 2016 +

sanity: Fix int verses string reference

The sanity update code needs to be passed an int, not string.

Signed-off-by: Richard Purdie 

Any problem, please contact Anibal 

Re: [yocto] [Openembedded-architecture] Standalone image writer

[Gary Thomas]

On 02/29/2016 04:31 AM, Trevor Woerner wrote:



On 02/28/16 20:46, Khem Raj wrote:

On Feb 28, 2016, at 4:17 PM, Paul Eggleton  
wrote:

(changing subject line so people don't miss this slight tangent)

I'd almost completely forgotten, but the part of what we wrote for Hob to
write images to a USB stick or SD card (bitbake/bin/image-writer) is actually
a standalone application. There's not a lot to it - pick your image file and
then the device you want to write it to; it has some logic in it to not let
you accidentally write to devices that aren't USB sticks.

A few points:

- I'm not sure very many people know this tool exists, so it's likely it's not
being widely used. Having said that it is a nice simple UI that does the job.

- It shares some code with Hob, but mostly not the bits with code quality
issues, though it is still GTK+ 2 based.

- It doesn't support the advanced SD card writing functionality that has been
implented within wic over the last few releases, which is pretty important for
devices where a special partition layout is expected by the bootloader.

- Toaster can't really have this functionality in it because it's web based
and the web server might not be running locally, so writing to a local USB
stick or SD card isn't going to be practical from there; about all it could do
is provide instructions on how to write the image once you've downloaded it.

- I believe there are other equivalent tools out there that various distros
use for taking a downloadable ISO image and writing it to a USB stick. I
haven't done a survey to find out if if any of them work in quite the same way;
I know some of them actually unpack the image and then re-create a filesystem
on the device, which isn't the right thing for our images.

- We do have a command-line equivalent in the form of scripts/contrib/ddimage
in OE-Core. Of course it's command-line and thus less friendly but it does the
job (and also has some safeguards against writing to the wrong device).

So what do we do with this? We have two choices really:

A) Drop bitbake/bin/imagewriter along with Hob; we could potentially
resurrect it again later if desired

B) Preserve it along with the shared modules that it requires

Thoughts?


Option A. There are USB writer tool in your favorite distros and OSes, and I 
have
seen people use those tools more often.


Some platforms, e.g. Minnow, use their own image writing script (i.e. 
mkefidisk.sh). If there are other platforms which
need some special tool that isn't generically available from the host and the 
hob tool could be made to accommodate them
all, I'd prefer to see one tool that can do all of them instead of a bunch of 
tools, one for each platform.


As Paul mentioned, each platform seems to want to do this "their
own way" which is troublesome at best for embedded systems.  I think
it would be much better to maintain one way that works with what we
are building (OE based embedded devices) rather than relying on the
whims of others.  So, if it's not too hard, I'd prefer that this
ability be kept, even as a stand-alone script.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

Re: [yocto] [Openembedded-architecture] Standalone image writer

[Trevor Woerner]

On 02/28/16 20:46, Khem Raj wrote:

On Feb 28, 2016, at 4:17 PM, Paul Eggleton  
wrote:

(changing subject line so people don't miss this slight tangent)

I'd almost completely forgotten, but the part of what we wrote for Hob to
write images to a USB stick or SD card (bitbake/bin/image-writer) is actually
a standalone application. There's not a lot to it - pick your image file and
then the device you want to write it to; it has some logic in it to not let
you accidentally write to devices that aren't USB sticks.

A few points:

- I'm not sure very many people know this tool exists, so it's likely it's not
being widely used. Having said that it is a nice simple UI that does the job.

- It shares some code with Hob, but mostly not the bits with code quality
issues, though it is still GTK+ 2 based.

- It doesn't support the advanced SD card writing functionality that has been
implented within wic over the last few releases, which is pretty important for
devices where a special partition layout is expected by the bootloader.

- Toaster can't really have this functionality in it because it's web based
and the web server might not be running locally, so writing to a local USB
stick or SD card isn't going to be practical from there; about all it could do
is provide instructions on how to write the image once you've downloaded it.

- I believe there are other equivalent tools out there that various distros
use for taking a downloadable ISO image and writing it to a USB stick. I
haven't done a survey to find out if if any of them work in quite the same way;
I know some of them actually unpack the image and then re-create a filesystem
on the device, which isn't the right thing for our images.

- We do have a command-line equivalent in the form of scripts/contrib/ddimage
in OE-Core. Of course it's command-line and thus less friendly but it does the
job (and also has some safeguards against writing to the wrong device).

So what do we do with this? We have two choices really:

A) Drop bitbake/bin/imagewriter along with Hob; we could potentially
resurrect it again later if desired

B) Preserve it along with the shared modules that it requires

Thoughts?


Option A. There are USB writer tool in your favorite distros and OSes, and I 
have
seen people use those tools more often.


Some platforms, e.g. Minnow, use their own image writing script (i.e. 
mkefidisk.sh). If there are other platforms which need some special tool 
that isn't generically available from the host and the hob tool could be 
made to accommodate them all, I'd prefer to see one tool that can do all 
of them instead of a bunch of tools, one for each platform.

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

Re: [yocto] [Openembedded-architecture] Standalone image writer

[Khem Raj]

> On Feb 28, 2016, at 4:17 PM, Paul Eggleton  
> wrote:
> 
> (changing subject line so people don't miss this slight tangent)
> 
> I'd almost completely forgotten, but the part of what we wrote for Hob to
> write images to a USB stick or SD card (bitbake/bin/image-writer) is actually
> a standalone application. There's not a lot to it - pick your image file and
> then the device you want to write it to; it has some logic in it to not let
> you accidentally write to devices that aren't USB sticks.
> 
> A few points:
> 
> - I'm not sure very many people know this tool exists, so it's likely it's not
> being widely used. Having said that it is a nice simple UI that does the job.
> 
> - It shares some code with Hob, but mostly not the bits with code quality
> issues, though it is still GTK+ 2 based.
> 
> - It doesn't support the advanced SD card writing functionality that has been
> implented within wic over the last few releases, which is pretty important for
> devices where a special partition layout is expected by the bootloader.
> 
> - Toaster can't really have this functionality in it because it's web based
> and the web server might not be running locally, so writing to a local USB
> stick or SD card isn't going to be practical from there; about all it could do
> is provide instructions on how to write the image once you've downloaded it.
> 
> - I believe there are other equivalent tools out there that various distros
> use for taking a downloadable ISO image and writing it to a USB stick. I
> haven't done a survey to find out if if any of them work in quite the same 
> way;
> I know some of them actually unpack the image and then re-create a filesystem
> on the device, which isn't the right thing for our images.
> 
> - We do have a command-line equivalent in the form of scripts/contrib/ddimage
> in OE-Core. Of course it's command-line and thus less friendly but it does the
> job (and also has some safeguards against writing to the wrong device).
> 
> So what do we do with this? We have two choices really:
> 
> A) Drop bitbake/bin/imagewriter along with Hob; we could potentially
> resurrect it again later if desired
> 
> B) Preserve it along with the shared modules that it requires
> 
> Thoughts?


Option A. There are USB writer tool in your favorite distros and OSes, and I 
have
seen people use those tools more often.

> 
> Cheers,
> Paul
> 
> --
> 
> Paul Eggleton
> Intel Open Source Technology Centre
> ___
> Openembedded-architecture mailing list
> openembedded-architect...@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture



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

[yocto] [meta-raspberrypi][PATCH v3 2/6] .gitignore: Ignore .swp files

[Petter Mabäcker]

Signed-off-by: Petter Mabäcker 
---
 .gitignore | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitignore b/.gitignore
index 1677b58..f235765 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
 build*
 *~
+.*.swp
-- 
1.9.1

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

Re: [yocto] [meta-raspberrypi][PATCH v2 3/7] linux-raspberrypi: Update 4.1 recipe to 4.1.15

[Petter Mabäcker]

 

2016-02-28 12:02 skrev Andrei Gherzan: 

> On Sun, Feb 28, 2016 at
11:51:58AM +0100, Andrei Gherzan wrote:
> 
>> On Sun, Feb 28, 2016 at
08:56:33AM +0100, Petter Mabäcker wrote: 
>> 
>>> 2016-01-14 17:40 skrev
Petter Mab?cker: [Support #69] Signed-off-by: Petter Mab?cker
<[1]pet...@technux.se> --- recipes-kernel/linux/linux-raspberrypi_4.1.bb
| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git
a/recipes-kernel/linux/linux-raspberrypi_4.1.bb b/recipes-kernel/linu
x/linux-raspberrypi_4.1.bb index 3a3cf40..cae459a 100644 ---
a/recipes-kernel/linux/linux-raspberrypi_4.1.bb +++
b/recipes-kernel/linux/linux-raspberrypi_4.1.bb @@ -1,6 +1,6 @@
-LINUX_VERSION ?= "4.1.10" +LINUX_VERSION ?= "4.1.15" -SRCREV =
"b74df9228c27f55361c065bc5dbfba88861cc771" +SRCREV =
"02a8ee530e32b08e5df44f10e24d5fd82bb960e3" SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.1.y "
require linux-raspberrypi.inc Hi Andrei, This commit can be skipped,
since Khem have done an even newer update of the 4.1 kernel (4.1.10 -->
4.1.17) in the large series of commits from yesterday
(https://lists.yoctoproject.org/pipermail/yocto/2016-February/028754.ht
[1] ml). Do you want me to send an updated version of this series of
commit without it or not? BR Petter References 1.
mailto:pet...@technux.se
>> Thanks Peter. No need to bother. I'll keep
in mind not to pull this patch.
> 
> Petter,
> 
> Actually I do have a
request. Could you please send the v2 again (or a v3)
> cause even if
they are on the ml archive I don't have it in my mailbox (this
> kinda
worries me). Sorry for this and thank you in advance.
> 
> --
> Andrei
Gherzan

I will send up a v3 with the kernel bump commit removed (and
also a fix for a minor typo in the README..). 

BR Petter 

Petter
Mabäcker

Technux 
www.technux.se



Links:
--
[1]
https://lists.yoctoproject.org/pipermail/yocto/2016-February/028754.ht
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v4 2/2] linux-raspberrypi: Make sure we have initramfs image before running mkknlimg

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan 
---
 recipes-kernel/linux/linux-raspberrypi.inc | 10 ++
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
b/recipes-kernel/linux/linux-raspberrypi.inc
index 1befee4..5a8a175 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -66,10 +66,12 @@ do_rpiboot_mkimage() {
 }
 
 do_bundle_initramfs_append() {
-if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
-if test -n "${KERNEL_DEVICETREE}"; then
-# Add RPi bootloader trailer to kernel image to enable DeviceTree 
support
-${STAGING_LIBEXECDIR_NATIVE}/mkknlimg --dtok 
${KERNEL_OUTPUT}.initramfs ${KERNEL_OUTPUT}.initramfs
+if [ ! -z "${INITRAMFS_IMAGE}" -a x"${INITRAMFS_IMAGE_BUNDLE}" = x1 ]; then
+if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
+if test -n "${KERNEL_DEVICETREE}"; then
+# Add RPi bootloader trailer to kernel image to enable 
DeviceTree support
+${STAGING_LIBEXECDIR_NATIVE}/mkknlimg --dtok 
${KERNEL_OUTPUT}.initramfs ${KERNEL_OUTPUT}.initramfs
+fi
 fi
 fi
 }
-- 
2.7.0

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

[yocto] [meta-raspberrypi][PATCH v4 1/2] linux-raspberry.inc: add initramfs support

[Andrei Gherzan]

From: Stéphane Cerveau 

append initramfs creation to install RPi bootloader trailer

Signed-off-by: Stéphane Cerveau 
Signed-off-by: Andrei Gherzan 
---
 recipes-kernel/linux/linux-raspberrypi.inc | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
b/recipes-kernel/linux/linux-raspberrypi.inc
index 8c7c46c..1befee4 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -64,4 +64,14 @@ do_rpiboot_mkimage() {
 fi
 fi
 }
+
+do_bundle_initramfs_append() {
+if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
+if test -n "${KERNEL_DEVICETREE}"; then
+# Add RPi bootloader trailer to kernel image to enable DeviceTree 
support
+${STAGING_LIBEXECDIR_NATIVE}/mkknlimg --dtok 
${KERNEL_OUTPUT}.initramfs ${KERNEL_OUTPUT}.initramfs
+fi
+fi
+}
+
 addtask rpiboot_mkimage before do_install after do_compile
-- 
2.7.0

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

Re: [yocto] [meta-raspberrypi][PATCH v2 3/7] linux-raspberrypi: Update 4.1 recipe to 4.1.15

[Andrei Gherzan]

On Sun, Feb 28, 2016 at 11:51:58AM +0100, Andrei Gherzan wrote:
> On Sun, Feb 28, 2016 at 08:56:33AM +0100, Petter Mabäcker wrote:
> >2016-01-14 17:40 skrev Petter Mab?cker:
> >
> > [Support #69]
> >
> > Signed-off-by: Petter Mab?cker <[1]pet...@technux.se>
> > ---
> >  recipes-kernel/linux/linux-raspberrypi_4.1.bb | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/recipes-kernel/linux/linux-raspberrypi_4.1.bb 
> > b/recipes-kernel/linu
> > x/linux-raspberrypi_4.1.bb
> > index 3a3cf40..cae459a 100644
> > --- a/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> > +++ b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> > @@ -1,6 +1,6 @@
> > -LINUX_VERSION ?= "4.1.10"
> > +LINUX_VERSION ?= "4.1.15"
> >
> > -SRCREV = "b74df9228c27f55361c065bc5dbfba88861cc771"
> > +SRCREV = "02a8ee530e32b08e5df44f10e24d5fd82bb960e3"
> >  SRC_URI = 
> > "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.1.y
> > "
> >
> >  require linux-raspberrypi.inc
> >
> >Hi Andrei,
> >
> >This commit can be skipped, since Khem have done an even newer update
> >of the 4.1 kernel (4.1.10 --> 4.1.17) in the large series of commits
> >from yesterday
> >(https://lists.yoctoproject.org/pipermail/yocto/2016-February/028754.ht
> >ml). Do you want me to send an updated version of this series of commit
> >without it or not?
> >
> >BR Petter
> >
> > References
> >
> >1. mailto:pet...@technux.se
>
> Thanks Peter. No need to bother. I'll keep in mind not to pull this patch.

Petter,

Actually I do have a request. Could you please send the v2 again (or a v3)
cause even if they are on the ml archive I don't have it in my mailbox (this
kinda worries me). Sorry for this and thank you in advance.

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

[yocto] [meta-raspberrypi][PATCH v3 1/1] linux-raspberry.inc: add initramfs support

[Andrei Gherzan]

From: Stéphane Cerveau 

append initramfs creation to install RPi bootloader trailer

Signed-off-by: Stéphane Cerveau 
Signed-off-by: Andrei Gherzan 
---
 recipes-kernel/linux/linux-raspberrypi.inc | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
b/recipes-kernel/linux/linux-raspberrypi.inc
index 8c7c46c..1befee4 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -64,4 +64,14 @@ do_rpiboot_mkimage() {
 fi
 fi
 }
+
+do_bundle_initramfs_append() {
+if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
+if test -n "${KERNEL_DEVICETREE}"; then
+# Add RPi bootloader trailer to kernel image to enable DeviceTree 
support
+${STAGING_LIBEXECDIR_NATIVE}/mkknlimg --dtok 
${KERNEL_OUTPUT}.initramfs ${KERNEL_OUTPUT}.initramfs
+fi
+fi
+}
+
 addtask rpiboot_mkimage before do_install after do_compile
-- 
2.7.0

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

[yocto] [meta-raspberrypi][PATCH 1/1] omxplayer: Add patch to fix host-user-contaminated QA

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan 
Signed-off-by: Jonathan Liu 
---
 .../don-t-preserve-file-attributes-when-cp.patch   | 18 ++
 recipes-multimedia/omxplayer/omxplayer_git.bb  |  1 +
 2 files changed, 19 insertions(+)
 create mode 100644 
recipes-multimedia/omxplayer/omxplayer/don-t-preserve-file-attributes-when-cp.patch

diff --git 
a/recipes-multimedia/omxplayer/omxplayer/don-t-preserve-file-attributes-when-cp.patch
 
b/recipes-multimedia/omxplayer/omxplayer/don-t-preserve-file-attributes-when-cp.patch
new file mode 100644
index 000..08df12e
--- /dev/null
+++ 
b/recipes-multimedia/omxplayer/omxplayer/don-t-preserve-file-attributes-when-cp.patch
@@ -0,0 +1,18 @@
+When running install (fakeroot) host-user-contaminated will fail because dist
+rule copies files while preserving file attributes like user ID.
+
+Upstream-Status: Submitted [https://github.com/popcornmix/omxplayer/pull/431]
+Signed-off-by: Andrei Gherzan 
+
+Index: git/Makefile
+===
+--- git.orig/Makefile
 git/Makefile
+@@ -87,5 +87,5 @@ dist: omxplayer.bin omxplayer.1
+   cp COPYING $(DIST)/usr/share/doc/omxplayer
+   cp README.md $(DIST)/usr/share/doc/omxplayer/README
+   cp omxplayer.1 $(DIST)/usr/share/man/man1
+-  cp -a ffmpeg_compiled/usr/lib/*.so* $(DIST)/usr/lib/omxplayer/
++  cp -P ffmpeg_compiled/usr/lib/*.so* $(DIST)/usr/lib/omxplayer/
+   tar -czf omxplayer-dist.tar.gz $(DIST)
+\ No newline at end of file
diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb 
b/recipes-multimedia/omxplayer/omxplayer_git.bb
index a0690a0..c8251fe 100644
--- a/recipes-multimedia/omxplayer/omxplayer_git.bb
+++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
@@ -18,6 +18,7 @@ SRC_URI = 
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master
file://0004-Add-FFMPEG_EXTRA_CFLAGS-and-FFMPEG_EXTRA_LDFLAGS.patch \
file://fix-tar-command-with-DIST.patch \
file://use-native-pkg-config.patch \
+   file://don-t-preserve-file-attributes-when-cp.patch \
"
 S = "${WORKDIR}/git"
 
-- 
2.7.0

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

Re: [yocto] [meta-raspberrypi][PATCH 3/3] u-boot-rpi: update path to imagetool-uncompressed.py

[Andrei Gherzan]

On Sun, Feb 28, 2016 at 12:46:49AM +1100, Jonathan Liu wrote:
> Signed-off-by: Jonathan Liu 
> ---
>  recipes-bsp/u-boot/u-boot-rpi_git.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/recipes-bsp/u-boot/u-boot-rpi_git.bb 
> b/recipes-bsp/u-boot/u-boot-rpi_git.bb
> index ea0c173..8bffaa3 100644
> --- a/recipes-bsp/u-boot/u-boot-rpi_git.bb
> +++ b/recipes-bsp/u-boot/u-boot-rpi_git.bb
> @@ -24,6 +24,6 @@ COMPATIBLE_MACHINE = "raspberrypi"
>  
>  do_compile_append() {
>  # Create kernel.img from uboot.bin and name it u-boot.img
> -${STAGING_LIBEXECDIR_NATIVE}/rpi-mkimage/imagetool-uncompressed.py 
> u-boot.bin
> +${STAGING_LIBEXECDIR_NATIVE}/imagetool-uncompressed.py u-boot.bin
>  mv kernel.img u-boot.img
>  }
> -- 
> 2.7.1
> 
> -- 

Merged to master. Thanks.

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

Re: [yocto] [meta-raspberrypi][PATCH 2/3] linux-raspberrypi: update path to mkknlimg

[Andrei Gherzan]

On Sun, Feb 28, 2016 at 12:46:48AM +1100, Jonathan Liu wrote:
> Signed-off-by: Jonathan Liu 
> ---
>  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 05f2d2b..8c7c46c 100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++ b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -60,7 +60,7 @@ do_rpiboot_mkimage() {
>  if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
>  if test -n "${KERNEL_DEVICETREE}"; then
>  # Add RPi bootloader trailer to kernel image to enable 
> DeviceTree support
> -${STAGING_LIBEXECDIR_NATIVE}/rpi-mkimage/mkknlimg --dtok 
> ${KERNEL_OUTPUT} ${KERNEL_OUTPUT}
> +${STAGING_LIBEXECDIR_NATIVE}/mkknlimg --dtok ${KERNEL_OUTPUT} 
> ${KERNEL_OUTPUT}
>  fi
>  fi
>  }
> -- 
> 2.7.1
> 
> -- 
Merged to master. Thanks.
-- 
Andrei Gherzan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/3] rpi-mkimage: install to ${libexecdir}

[Andrei Gherzan]

On Sun, Feb 28, 2016 at 12:46:47AM +1100, Jonathan Liu wrote:
> It doesn't make sense to install to ${libexecdir}/rpi-mkimage as it
> changes the path on fido and earlier branches from:
>   [...]/sysroots/x86_64-linux/usr/lib/rpi-mkimage
> to:
>   [...]/sysroots/x86_64-linux/usr/lib/rpi-mkimage/rpi-mkimage
> 
> Using ${libexecdir} instead of ${libexecdir}/rpi-mkimage preserves
> the path for fido and earlier.
> 
> Signed-off-by: Jonathan Liu 
> ---
>  recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb 
> b/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb
> index 2c8ecb1..7dea43d 100644
> --- a/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb
> +++ b/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb
> @@ -15,8 +15,8 @@ SRC_URI = " \
>  S = "${WORKDIR}/git"
>  
>  do_install () {
> -install -d ${D}${libexecdir}/rpi-mkimage
> -install -t ${D}${libexecdir}/rpi-mkimage ./mkimage/*
> +install -d ${D}${libexecdir}
> +install -t ${D}${libexecdir} mkimage/*
>  }
>  
>  BBCLASSEXTEND = "native"
> -- 
> 2.7.1
> 
Merged to master. Thanks.
-- 
Andrei Gherzan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] omxplayer: fix host-user-contaminated QA warnings

[Andrei Gherzan]

On Sun, Feb 28, 2016 at 12:49:07AM +1100, Jonathan Liu wrote:
> On 27 February 2016 at 23:56, Andrei Gherzan  wrote:
> > On Sat, Feb 27, 2016 at 12:21:08AM +1100, Jonathan Liu wrote:
> >> Explicitly chown the installed files to fix host-user-contaminated QA
> >> warnings for libavcodec, libavdevice, libavfilter, libavformat,
> >> libavutil and libswresample shared libraries.
> >>
> >> Signed-off-by: Jonathan Liu 
> >> ---
> >>  recipes-multimedia/omxplayer/omxplayer_git.bb | 1 +
> >>  1 file changed, 1 insertion(+)
> >>
> >> diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb 
> >> b/recipes-multimedia/omxplayer/omxplayer_git.bb
> >> index a0690a0..8816273 100644
> >> --- a/recipes-multimedia/omxplayer/omxplayer_git.bb
> >> +++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
> >> @@ -61,6 +61,7 @@ do_install() {
> >>  oe_runmake STRIP='echo skipping strip' dist
> >>  mkdir -p ${D}${datadir}/fonts/truetype/freefont/
> >>  install ${S}/fonts/* ${D}${datadir}/fonts/truetype/freefont/
> >> +chown root:root -R ${D}
> >>  }
> >>
> >>  FILES_${PN} = "${bindir}/omxplayer* \
> >> --
> >> 2.7.1
> >>
> >
> > Actually the problem here is how the package does the dist target.
> >
> > Makefile:
> > ...
> > <-->cp -a ffmpeg_compiled/usr/lib/*.so* $(DIST)/usr/lib/omxplayer/
> > ...
> >
> > This means that even if ran in a fackroot environment, this will preserve 
> > the
> > user id and other file attributes generating the warnings you pointed out.
> >
> > In order to fix this I would vote for a patch that would change the archive
> > flag to a simple -R (-P is default anyway). What do you think?
> >
> > As well this patch should go upstream too as I don't see the idea behind
> > copying those while preserving the file attributes.
> >
> >> --
> >> ___
> >> yocto mailing list
> >> yocto@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/yocto
> >
> > --
> > Andrei Gherzan
> 
> I have submitted a pull request to omxplayer to use -P. No point using
> -R as it is just copying libraries rather than directories.
> 
> Regards,
> Jonathan

Indeed you are right. -P should be just enough. Good job!
-- 
Andrei Gherzan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto