Re: [yocto] [meta-raspberrypi][PATCH V2] linux-raspberry.inc: add initramfs support

2016-02-28 Thread Petter Mabäcker 
 

5 

Petter Mabäcker

Technux

www.technux.se

2016-02-10 11:26 skrev Stéphane
Cerveau: 

> append initramfs creation to install RPi bootloader
trailer
> 
> Signed-off-by: Stéphane Cerveau 
> ---
>
recipes-kernel/linux/linux-raspberrypi.inc | 9 +
> 1 file
changed, 9 insertions(+)
> 
> diff --git
a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc
> index 70e8bfe..74dbf19
100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++
b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -64,4 +64,13 @@
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_DIR_NATIVE}/usr/lib/rpi-mkimage/mkknlimg --dtok
${KERNEL_OUTPUT}.initramfs ${KERNEL_OUTPUT}.initramfs
> + fi
> + fi
>
+}
> +
> addtask rpiboot_mkimage before do_install after do_compile
> --

> 2.1.4

Hi, 

You should change the path to mkknlimg to use:
${STAGING_LIBEXECDIR_NATIVE}/mkknlimg 

See the discussion about this
in:
https://lists.yoctoproject.org/pipermail/yocto/2016-February/028769.html


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

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

2016-02-28 Thread 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

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

2016-02-28 Thread 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 2/3] linux-raspberrypi: update path to mkknlimg

2016-02-28 Thread 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 3/3] u-boot-rpi: update path to imagetool-uncompressed.py

2016-02-28 Thread 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

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

2016-02-28 Thread 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

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

2016-02-28 Thread 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] linux-raspberry.inc: add initramfs support

2016-02-28 Thread Andrei Gherzan 
On Sun, Feb 28, 2016 at 09:09:33AM +0100, Petter Mabäcker wrote:
>5
> 
> 
> 
> Petter Mab�cker
> 
> Technux 
> www.technux.se
> 
>2016-02-10 11:26 skrev St�phane Cerveau:
> 
> append initramfs creation to install RPi bootloader trailer
> 
> Signed-off-by: St�phane Cerveau <[1]vox...@voxtok.com>
> ---
>  recipes-kernel/linux/linux-raspberrypi.inc | 9 +
>  1 file changed, 9 insertions(+)
> 
> diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
> b/recipes-kernel/linux/l
> inux-raspberrypi.inc
> index 70e8bfe..74dbf19 100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++ b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -64,4 +64,13 @@ 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 s
> upport
> +${STAGING_DIR_NATIVE}/usr/lib/rpi-mkimage/mkknlimg --dtok 
> ${KERNEL_
> OUTPUT}.initramfs ${KERNEL_OUTPUT}.initramfs
> +fi
> +fi
> +}
> +
>  addtask rpiboot_mkimage before do_install after do_compile
> --
> 2.1.4
> 
>Hi,
> 
>You should change the path to mkknlimg to use:
>${STAGING_LIBEXECDIR_NATIVE}/mkknlimg
> 
>See the discussion about this in:
>https://lists.yoctoproject.org/pipermail/yocto/2016-February/028769.htm
>l
> 
>BR Petter
> 
> References
> 
>1. mailto:vox...@voxtok.com

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

Hi Peter. I pushed a v3 patch which adds this change. Thanks.

-- 
Andrei Gherzan
-- 
___
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

2016-02-28 Thread Andrei Gherzan 
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. 

-- 
Andrei Gherzan
-- 
___
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

2016-02-28 Thread 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 v4 1/2] linux-raspberry.inc: add initramfs support

2016-02-28 Thread 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 v4 2/2] linux-raspberrypi: Make sure we have initramfs image before running mkknlimg

2016-02-28 Thread 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

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

2016-02-28 Thread 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 v3 2/6] .gitignore: Ignore .swp files

2016-02-28 Thread 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

[yocto] [meta-raspberrypi][PATCH v3 1/6] README: Add SPI bus chapter to content

2016-02-28 Thread Petter Mabäcker 
The optional SPI bus chapter was missing in the content list.

While at it also place it together with the other "optional" chapters,
instead of in the end.

Signed-off-by: Petter Mabäcker 
---
 README | 28 +++-
 1 file changed, 15 insertions(+), 13 deletions(-)

diff --git a/README b/README
index 16ac1cb..a168692 100644
--- a/README
+++ b/README
@@ -20,10 +20,11 @@ Contents:
 2.F. Optional - Video camera support with V4L2 drivers
 2.G. Optional - Enable offline compositing support
 2.H. Optional - Enable kgdb over console support
-2.I. Images
-2.J. Boot to U-Boot
-2.K. Image with Initramfs
-2.L. Device tree support
+2.I. Optional - Enable SPI bus
+2.J. Images
+2.K. Boot to U-Boot
+2.L. Image with Initramfs
+2.M. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -145,7 +146,13 @@ To add the kdbg over console (kgdboc) parameter to the 
kernel command line,
 set this variable in local.conf:
 ENABLE_KGDB = "1"
 
-2.I. Images
+2.I. Optional - Enable SPI bus
+==
+When using device tree kernels, set this variable to enable the SPI bus
+ENABLE_SPI_BUS = "1"
+
+
+2.J. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -155,7 +162,7 @@ ENABLE_KGDB = "1"
 Image based on rpi-basic-image which includes most of the packages in this
 layer and some media samples.
 
-2.J. Boot to U-Boot
+2.K. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -163,7 +170,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).
 
-2.K. Image with Initramfs
+2.L. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
@@ -176,7 +183,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
 - KERNEL_INITRAMFS = "-initramfs"
 
-2.L. Device tree support
+2.M. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 3.18+
 kernels.
@@ -189,11 +196,6 @@ kernels.
 NOTE: KERNEL_DEVICETREE is default enabled for kernel >= 3.18 and always 
disabled for
   older kernel versions.
 
-2.M. Optional - enable SPI bus
-==
-When using device tree kernels, set this variable to enable the SPI bus
-ENABLE_SPI_BUS = "1"
-
 3. Extra apps
 =
 
-- 
1.9.1

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

[yocto] [meta-raspberrypi][PATCH v3 3/6] rpi-config: I2C support

2016-02-28 Thread Petter Mabäcker 
With newer kernels (>=3.18) that supports device-trees I2C
should be enabled with device-trees.

This is now support by adding:
ENABLE_I2C = "1"
in local.conf

This will enable the dtparams:
i2c1
i2c_arm

Signed-off-by: Petter Mabäcker 
---
 README  | 21 +
 recipes-bsp/bootfiles/rpi-config_git.bb |  6 ++
 2 files changed, 19 insertions(+), 8 deletions(-)

diff --git a/README b/README
index a168692..8ef4e7a 100644
--- a/README
+++ b/README
@@ -21,10 +21,11 @@ Contents:
 2.G. Optional - Enable offline compositing support
 2.H. Optional - Enable kgdb over console support
 2.I. Optional - Enable SPI bus
-2.J. Images
-2.K. Boot to U-Boot
-2.L. Image with Initramfs
-2.M. Device tree support
+2.J. Optional - Enable I2C
+2.K. Images
+2.L. Boot to U-Boot
+2.M. Image with Initramfs
+2.N. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -151,8 +152,12 @@ ENABLE_KGDB = "1"
 When using device tree kernels, set this variable to enable the SPI bus
 ENABLE_SPI_BUS = "1"
 
+2.J. Optional - Enable I2C
+==
+When using device tree kernels, set this variable to enable I2C
+ENABLE_I2C = "1"
 
-2.J. Images
+2.K. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -162,7 +167,7 @@ ENABLE_SPI_BUS = "1"
 Image based on rpi-basic-image which includes most of the packages in this
 layer and some media samples.
 
-2.K. Boot to U-Boot
+2.L. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -170,7 +175,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).
 
-2.L. Image with Initramfs
+2.M. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
@@ -183,7 +188,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
 - KERNEL_INITRAMFS = "-initramfs"
 
-2.M. Device tree support
+2.N. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 3.18+
 kernels.
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index aa11b25..ccb9b7f 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -72,6 +72,12 @@ do_deploy() {
 echo "# Enable SPI bus" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=spi=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+if [ -n "${ENABLE_I2C}" ]; then
+echo "# Enable I2C" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
 }
 
 addtask deploy before do_package after do_install
-- 
1.9.1

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

[yocto] [meta-raspberrypi][PATCH v3 0/6] Various upgrade/fixes from Technux

2016-02-28 Thread Petter Mabäcker 
Various fixes from Technux, with focus on PiTFT support.

Petter Mabäcker (6):
  README: Add SPI bus chapter to content
  .gitignore: Ignore .swp files
  rpi-config: I2C support
  rpi-base.inc: Allow MACHINE_FEATURES appends
  pitft: Add basic support for PiTFT
  pitft: Add PiTFT22 support

 .gitignore |   1 +
 README |  55 ---
 conf/machine/include/rpi-base.inc  |   3 +-
 recipes-bsp/bootfiles/rpi-config_git.bb|  17 +++-
 .../rpi/xorg.conf.d/99-pitft.conf  |   5 +
 .../xorg-xserver/xserver-xf86-config_0.1.bbappend  |  11 ++-
 recipes-kernel/linux/linux-raspberrypi.inc |   6 +-
 ...dts-add-overlay-for-pitft22-in-linux-3.18.patch | 110 +
 .../0001-dts-add-overlay-for-pitft22.patch | 110 +
 recipes-kernel/linux/linux-raspberrypi_3.18.bb |   5 +-
 recipes-kernel/linux/linux-raspberrypi_4.1.bb  |   4 +-
 11 files changed, 306 insertions(+), 21 deletions(-)
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22.patch

-- 
1.9.1

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

[yocto] [meta-raspberrypi][PATCH v3 5/6] pitft: Add basic support for PiTFT

2016-02-28 Thread Petter Mabäcker 
Add basic support for PiTFT display by using device-trees.

In order get it working below configurations must be active in
local.conf:

MACHINE_FEATURES += "pitft"
 - This will enable SPI bus and i2c device-trees, it will also setup
   framebuffer for console and x server on PiTFT.

[Support #70]

Signed-off-by: Petter Mabäcker 
---
 README | 29 --
 recipes-bsp/bootfiles/rpi-config_git.bb|  6 +++--
 .../rpi/xorg.conf.d/99-pitft.conf  |  5 
 .../xorg-xserver/xserver-xf86-config_0.1.bbappend  | 11 ++--
 recipes-kernel/linux/linux-raspberrypi.inc |  6 -
 5 files changed, 44 insertions(+), 13 deletions(-)
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf

diff --git a/README b/README
index 8ef4e7a..6a6c398 100644
--- a/README
+++ b/README
@@ -22,10 +22,11 @@ Contents:
 2.H. Optional - Enable kgdb over console support
 2.I. Optional - Enable SPI bus
 2.J. Optional - Enable I2C
-2.K. Images
-2.L. Boot to U-Boot
-2.M. Image with Initramfs
-2.N. Device tree support
+2.K. Optional - Enable PiTFT support
+2.L. Images
+2.M. Boot to U-Boot
+2.N. Image with Initramfs
+2.O. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -157,7 +158,19 @@ ENABLE_SPI_BUS = "1"
 When using device tree kernels, set this variable to enable I2C
 ENABLE_I2C = "1"
 
-2.K. Images
+2.K. Optional - Enable PiTFT support
+
+Basic support for using PiTFT screens can be enabled by adding
+below in local.conf:
+
+MACHINE_FEATURES += "pitft"
+  - This will enable SPI bus and i2c device-trees, it will also setup
+framebuffer for console and x server on PiTFT.
+
+NOTE: To get this working the overlay for the PiTFT model must be build,
+  added and specified as well (dtoverlay= in config.txt)
+
+2.L. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -167,7 +180,7 @@ ENABLE_I2C = "1"
 Image based on rpi-basic-image which includes most of the packages in this
 layer and some media samples.
 
-2.L. Boot to U-Boot
+2.M. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -175,7 +188,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).
 
-2.M. Image with Initramfs
+2.N. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
@@ -188,7 +201,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
 - KERNEL_INITRAMFS = "-initramfs"
 
-2.N. Device tree support
+2.O. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 3.18+
 kernels.
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index ccb9b7f..236a359 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -15,6 +15,8 @@ S = "${WORKDIR}/git"
 
 PR = "r4"
 
+PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
+
 inherit deploy
 
 do_deploy() {
@@ -68,12 +70,12 @@ do_deploy() {
 fi
 
 # SPI bus support
-if [ -n "${ENABLE_SPI_BUS}" ]; then
+if [ -n "${ENABLE_SPI_BUS}" ] || [ "${PITFT}" = "1" ]; then
 echo "# Enable SPI bus" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=spi=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
 
-if [ -n "${ENABLE_I2C}" ]; then
+if [ -n "${ENABLE_I2C}" ] || [ "${PITFT}" = "1" ]; then
 echo "# Enable I2C" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
diff --git 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
new file mode 100644
index 000..0d2b36b
--- /dev/null
+++ 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
@@ -0,0 +1,5 @@
+Section "Device"
+Identifier "Adafruit PiTFT"
+Driver "fbdev"
+Option "fbdev" "/dev/fb1"
+EndSection
diff --git a/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend 
b/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
index 2cf40f8..0ae2ee0 100644
--- a/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
+++ b/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
@@ -1,10 +1,17 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
 
-SRC_URI_append_rpi = " file://xorg.conf.d/10-evdev.conf "
+SRC_URI_append_rpi = " file://

[yocto] [meta-raspberrypi][PATCH v3 4/6] rpi-base.inc: Allow MACHINE_FEATURES appends

2016-02-28 Thread Petter Mabäcker 
Ensure that it's possible to add MACHINE_FEATURES from places that will
be executed before rpi-base.inc (like e.g. local.conf), without having
them overrided.

Signed-off-by: Petter Mabäcker 
---
 conf/machine/include/rpi-base.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index e097702..c8f6cd6 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -37,7 +37,7 @@ KERNEL_DEVICETREE ?= " \
 "
 KERNEL_IMAGETYPE ?= "Image"
 
-MACHINE_FEATURES = "kernel26 apm usbhost keyboard vfat ext2 screen touchscreen 
alsa bluetooth wifi sdio"
+MACHINE_FEATURES += "kernel26 apm usbhost keyboard vfat ext2 screen 
touchscreen alsa bluetooth wifi sdio"
 
 # Raspberry Pi has no hardware clock
 MACHINE_FEATURES_BACKFILL_CONSIDERED = "rtc"
-- 
1.9.1

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

[yocto] [meta-raspberrypi][PATCH v3 6/6] pitft: Add PiTFT22 support

2016-02-28 Thread Petter Mabäcker 
- Add support to build overlays for PiTFT22 in the kernel.
- Setup a basic configuration for the driver

The PiTFT22 support is optional and can be enabled by adding below in
local.conf:

MACHINE_FEATURES += "pitft pitft22"

[Support #70]

Signed-off-by: Petter Mabäcker 
---
 README |   9 ++
 conf/machine/include/rpi-base.inc  |   1 +
 recipes-bsp/bootfiles/rpi-config_git.bb|   7 ++
 ...dts-add-overlay-for-pitft22-in-linux-3.18.patch | 110 +
 .../0001-dts-add-overlay-for-pitft22.patch | 110 +
 recipes-kernel/linux/linux-raspberrypi_3.18.bb |   5 +-
 recipes-kernel/linux/linux-raspberrypi_4.1.bb  |   4 +-
 7 files changed, 243 insertions(+), 3 deletions(-)
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22.patch

diff --git a/README b/README
index 6a6c398..4114ccc 100644
--- a/README
+++ b/README
@@ -170,6 +170,15 @@ MACHINE_FEATURES += "pitft"
 NOTE: To get this working the overlay for the PiTFT model must be build,
   added and specified as well (dtoverlay= in config.txt)
 
+Below is a list of currently supported PiTFT models in meta-raspberrypi,
+the modelname should be added as a MACHINE_FEATURES in local.conf like below:
+
+   - MACHINE_FEATURES += "pitft "
+
+List of currently supported models
+---
+pitft22
+
 2.L. Images
 ===
 * rpi-hwup-image
diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index c8f6cd6..27f09ad 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -31,6 +31,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/iqaudio-dac-overlay.dtb \
 overlays/iqaudio-dacplus-overlay.dtb \
 overlays/lirc-rpi-overlay.dtb \
+overlays/pitft22-overlay.dtb \
 overlays/pps-gpio-overlay.dtb \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index 236a359..631ff42 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -16,6 +16,7 @@ S = "${WORKDIR}/git"
 PR = "r4"
 
 PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
+PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
 
 inherit deploy
 
@@ -80,6 +81,12 @@ do_deploy() {
 echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+# PiTFT22 display support
+if [ "${PITFT22}" = "1" ]; then
+echo "# Enable PITFT22 display" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
 }
 
 addtask deploy before do_package after do_install
diff --git 
a/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 
b/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
new file mode 100644
index 000..fa73599
--- /dev/null
+++ 
b/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
@@ -0,0 +1,110 @@
+From 2f44861e2a2d651a9aa62a75343a032fee33e93b Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
+Date: Fri, 8 Jan 2016 09:02:44 +0100
+Subject: [PATCH] dts: add overlay for pitft22 in linux 3.18
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Upstream-Status: Pending
+
+Add the pitft22 overlay from adafruit Adafruit-Pi-Kernel-o-Matic repo:
+https://github.com/adafruit/Adafruit-Pi-Kernel-o-Matic
+
+Signed-off-by: Petter Mabäcker 
+---
+ arch/arm/boot/dts/overlays/Makefile|  1 +
+ arch/arm/boot/dts/overlays/pitft22-overlay.dts | 69 ++
+ 2 files changed, 70 insertions(+)
+ create mode 100755 arch/arm/boot/dts/overlays/pitft22-overlay.dts
+
+diff --git a/arch/arm/boot/dts/overlays/Makefile 
b/arch/arm/boot/dts/overlays/Makefile
+index c766616..1eaaf81 100644
+--- a/arch/arm/boot/dts/overlays/Makefile
 b/arch/arm/boot/dts/overlays/Makefile
+@@ -27,6 +27,7 @@ dtb-$(RPI_DT_OVERLAYS) += mcp2515-can0-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += mmc-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += mz61581-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += piscreen-overlay.dtb
++dtb-$(RPI_DT_OVERLAYS) += pitft22-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += pitft28-resistive-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += pps-gpio-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += rpi-dac-overlay.dtb
+diff --git a/arch/arm/boot/dts/overlays/pitft22-overlay.dts 
b/arch/arm/boot/dts/overlays/pitft22-overlay.dts
+new file mode 100755
+index 000..894ba22
+--- /dev/null

Re: [yocto] [meta-raspberrypi][PATCH v3 3/6] rpi-config: I2C support

2016-02-28 Thread Leon Anavi 

Hi Petter,

On 2016-02-28 15:46, Petter Mabäcker wrote:

With newer kernels (>=3.18) that supports device-trees I2C
should be enabled with device-trees.

This is now support by adding:
ENABLE_I2C = "1"
in local.conf

This will enable the dtparams:
i2c1
i2c_arm


Nice, this is exactly what I needed. Actually, yesterday I was searching 
how to enable I2C through local.conf on rpi. I hope your patch will be 
soon merged.


Thanks, Leon



Signed-off-by: Petter Mabäcker 
---
 README  | 21 +
 recipes-bsp/bootfiles/rpi-config_git.bb |  6 ++
 2 files changed, 19 insertions(+), 8 deletions(-)

diff --git a/README b/README
index a168692..8ef4e7a 100644
--- a/README
+++ b/README
@@ -21,10 +21,11 @@ Contents:
 2.G. Optional - Enable offline compositing support
 2.H. Optional - Enable kgdb over console support
 2.I. Optional - Enable SPI bus
-2.J. Images
-2.K. Boot to U-Boot
-2.L. Image with Initramfs
-2.M. Device tree support
+2.J. Optional - Enable I2C
+2.K. Images
+2.L. Boot to U-Boot
+2.M. Image with Initramfs
+2.N. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -151,8 +152,12 @@ ENABLE_KGDB = "1"
 When using device tree kernels, set this variable to enable the SPI 
bus

 ENABLE_SPI_BUS = "1"

+2.J. Optional - Enable I2C
+==
+When using device tree kernels, set this variable to enable I2C
+ENABLE_I2C = "1"

-2.J. Images
+2.K. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -162,7 +167,7 @@ ENABLE_SPI_BUS = "1"
 Image based on rpi-basic-image which includes most of the packages 
in this

 layer and some media samples.

-2.K. Boot to U-Boot
+2.L. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -170,7 +175,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).

-2.L. Image with Initramfs
+2.M. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for 
example)

@@ -183,7 +188,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for 
example)

 - KERNEL_INITRAMFS = "-initramfs"

-2.M. Device tree support
+2.N. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 
3.18+

 kernels.
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb
b/recipes-bsp/bootfiles/rpi-config_git.bb
index aa11b25..ccb9b7f 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -72,6 +72,12 @@ do_deploy() {
 echo "# Enable SPI bus" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=spi=on" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt

 fi
+
+if [ -n "${ENABLE_I2C}" ]; then
+echo "# Enable I2C" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=i2c1=on" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=i2c_arm=on" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt

+fi
 }

 addtask deploy before do_package after do_install
--
1.9.1


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

Re: [yocto] [Openembedded-architecture] Removing Hob for 2.1

2016-02-28 Thread Paul Eggleton 
On Fri, 26 Feb 2016 09:26:43 nick wrote:
> I haven't been using the last few versions of Yocto, last I used was 1.8 I
> believe unless we just jumped to 2.0/2.1. I was wondering for people
> somewhat used to using HOB for easier distribution build tuning how big is
> the learning curve(I assume it isn't much). 

Shouldn't be a big deal. If anything it's been much more carefully designed 
with new users in mind.

> Further more can Toaster be configured to make iso/vmware images as I find
> this very useful 

Certainly, any image type you can produce from Hob you can produce from 
Toaster.

> plus from what I known Toaster needs to be run with a browser can it be made
> to run as a non browser based service similar to Hob if not already done so.

Toaster is entirely web-based so that isn't possible I'm afraid. It doesn't 
require a separate web server though if that's what you're concerned about - 
the default configuration is to run on a single machine and not listen 
externally.

Cheers,
Paul

-- 

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

Re: [yocto] Source for recipe on local drive

2016-02-28 Thread Paul Eggleton 
With 1.8 and later, if it's purely the source you want there is the "devtool 
extract" command which will extract the sources of the specified recipe to a 
directory of your choosing with all of the patches applied, tracked in the 
form of a git tree.

Cheers,
Paul

On Fri, 26 Feb 2016 15:38:38 Oliver wrote:
> Additionally, I use the following sentence to get directly the location
> where these sources are:
> 
> bitbake  -e | grep "^WORKDIR="
> 
> 
> 
> El Viernes 26 de febrero de 2016 16:00, "Burton, Ross"
>  escribió:
> 
> 
> 
> 
> 
> On 26 February 2016 at 14:55, Marius Liebenberg 
> wrote:
> 
> How do I get all the source code for a specific recipe onto my local drive.
> That is without sifting through all the config files to try and get url's
> 
> 
> "bitbake [recipe] -c fetch" will just run the fetch task. 
> Ross

-- 

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

[yocto] Standalone image writer

2016-02-28 Thread Paul Eggleton 
(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?

Cheers,
Paul

-- 

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

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

2016-02-28 Thread 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

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

2016-02-28 Thread 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

2016-02-28 Thread 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

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

2016-02-28 Thread 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 Limon  
-- 
___
yocto mailin

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

2016-02-28 Thread 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