[yocto] rootfs mounted read-only on Live USB (x86-64)
Hi all Has anyone else noticed that the root file-system appears to be mounted read-only when booting a Live USB image from Yocto 2.1. This is on a sato build from the krogoth branch of poky and meta-intel, for a generic x86-64 machine (4.4 kernel). I'm transferring the resulting .iso image to a usb stick using 'dd', and then picking the 'boot' option at startup. As well as a bunch of errors about the read-only filesystem (e.g. failing to create files in /var and other locations), the desktop UI fails to load. This worked fine with Yocto 2.0. I have a hunch that it might be caused by a lack of aufs support. Is it possible that aufs patches were omitted from the x86 kernels in Yocto 2.1? Thanks, -Dan P.S. It works fine if I just install it directly, or if I use the .hddimg, instead of trying to boot the live image from the .iso. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] rootfs mounted read-only on Live USB (x86-64)
Hi, Check if "read-only-rootfs" feature is added to any of these variables either in your local.conf or your image bitbake recipe: Something like that: IMAGE_FEATURES = "read-only-rootfs" EXTRA_IMAGE_FEATURES += "read-only-rootfs" Thanks, Oleksandr Poznyak! On Fri, Jun 3, 2016 at 12:06 PM, Dan O'Donovan wrote: > Hi all > > Has anyone else noticed that the root file-system appears to be mounted > read-only when booting a Live USB image from Yocto 2.1. > > This is on a sato build from the krogoth branch of poky and meta-intel, > for a generic x86-64 machine (4.4 kernel). > > I'm transferring the resulting .iso image to a usb stick using 'dd', and > then picking the 'boot' option at startup. > > As well as a bunch of errors about the read-only filesystem (e.g. failing > to create files in /var and other locations), the desktop UI fails to load. > > This worked fine with Yocto 2.0. > > I have a hunch that it might be caused by a lack of aufs support. Is it > possible that aufs patches were omitted from the x86 kernels in Yocto 2.1? > > Thanks, > -Dan > > P.S. It works fine if I just install it directly, or if I use the .hddimg, > instead of trying to boot the live image from the .iso. > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Per image customizations
Hi Oleksandr,
In data mercoledì 1 giugno 2016 21:57:32, Oleksandr Poznyak ha scritto:
> Here is the content of bbappend recipe for base-files recipe:
>
> FILESEXTRAPATHS_append := "${THISDIR}/${PN}"
>
> SRC_URI += "file://fstab-flash \
> file://fstab-regular \
> "
>
> PACKAGES += " ${PN}-flash ${PN}-regular"
> CONFFILES_${PN}-flash = "${CONFFILES_${PN}}"
> CONFFILES_${PN}-regular = "${CONFFILES_${PN}}"
>
> pkg_preinst_${PN}-flash = "${pkg_preinst_${PN}}"
> pkg_preinst_${PN}-regular = "${pkg_preinst_${PN}}"
>
> RREPLACES_${PN}-flash = "${PN}"
> RPROVIDES_${PN}-flash = "${PN}"
> RCONFLICTS_${PN}-flash = "${PN}"
>
> RREPLACES_${PN}-regular = "${PN}"
> RPROVIDES_${PN}-regular = "${PN}"
> RCONFLICTS_${PN}-regular = "${PN}"
>
> python populate_packages_prepend() {
> import shutil
>
> packages = ("${PN}-flash", "${PN}-regular")
> for package in packages:
> # copy ${PN} content to packages
> shutil.copytree("${PKGD}", "${PKGDEST}/%s" % package, symlinks=True)
> # replace fstab
> if package == "${PN}-flash":
> shutil.copy("${WORKDIR}/fstab-flash",
> "${PKGDEST}/${PN}-flash/etc/fstab")
> else:
> shutil.copy("${WORKDIR}/fstab-regular",
> "${PKGDEST}/${PN}-regular/etc/fstab")
> }
>
>
> This will produce two separate packages that will replace base-files
> package.
> Moreover, this trick allows You to modify base-files package separately for
> flash-OS and regular-OS
>
This is very useful, thank you. With this code I'm able to have two different
fstab files under packages-split:
./packages-split/base-files-regular/etc/fstab
./packages-split/base-files-flash/etc/fstab
Regardless of that though, the resulting rpm packages for "base-files-regular"
and "base-files-flash" have the original fstab as in "base-files", which is
different to both the fstabs in packages-split mentioned above.
I'm looking at what might be causing this, but any idea is welcome.
Thanks,
Diego
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] rootfs mounted read-only on Live USB (x86-64)
On 06/03/2016 10:54 AM, Oleksandr Poznyak wrote:
> Hi,
Hi Oleksandr
> Check if "read-only-rootfs" feature is added to any of these variables either
> in your local.conf or your image bitbake recipe:
>
> Something like that:
>
> IMAGE_FEATURES = "read-only-rootfs"
>
> EXTRA_IMAGE_FEATURES += "read-only-rootfs"
Thanks for your suggestion. I didn't find "read-only-rootfs" specified in the
IMAGE_FEATURES in local.conf or elsewhere. I suspect it might be a different
issue because it only affects the live-boot of the .iso image. If I install
the .hddimage directly to the storage device instead, then it boots fine and
the rootfs is read/write.
[update]
It looks like the problem was indeed the lack of aufs.
I added this in conf/local.conf
DISTRO_FEATURES_append = " aufs"
and this in the kernel recipe
KERNEL_FEATURES_append += "${@bb.utils.contains('DISTRO_FEATURES', 'aufs',
' features/aufs/aufs-enable.scc', '', d)}"
and now the live USB image boots correctly with a read-write filesystem.
Considering that the default images built for a generic x86-64 machine include
a live-boot image (.iso) which is effectively broken, I assume the aufs feature
(or another solution for the live-boot use case) should really be added by
default for those builds as well.
>
> Thanks,
> Oleksandr Poznyak!
>
> On Fri, Jun 3, 2016 at 12:06 PM, Dan O'Donovan > wrote:
>
> Hi all
>
> Has anyone else noticed that the root file-system appears to be mounted
> read-only when booting a Live USB image from Yocto 2.1.
>
> This is on a sato build from the krogoth branch of poky and meta-intel,
> for a generic x86-64 machine (4.4 kernel).
>
> I'm transferring the resulting .iso image to a usb stick using 'dd', and
> then picking the 'boot' option at startup.
>
> As well as a bunch of errors about the read-only filesystem (e.g. failing
> to create files in /var and other locations), the desktop UI fails to load.
>
> This worked fine with Yocto 2.0.
>
> I have a hunch that it might be caused by a lack of aufs support. Is it
> possible that aufs patches were omitted from the x86 kernels in Yocto 2.1?
>
> Thanks,
> -Dan
>
> P.S. It works fine if I just install it directly, or if I use the
> .hddimg, instead of trying to boot the live image from the .iso.
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Project Status WW23
Current Dev Position: YP 2.2 M1 Next Deadline: YP 2.2 cut off: June 13, 2016 SWAT team rotation: Alejandro -> Jussi https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: *Python 3 has now merged, BitBake (inc. Toaster) and OE-Core now use python3 instead of python2. *We are experiencing problems with the buildtools tarball on the Centos 7 autobuilder with slowdowns/hangs. *gcc6 has merged *Our userspace has also converted mostly to python3 where we can (Thanks Alexander K!) *We're expecting some large patchsets for toaster bootstrap v2 -> v3 and changes to move OE-Core/Sato to gtk3+. *YP 1.8.2 has been released *YP 2.0.2 is due for release imminently *We're now working on 2.1.1 with trial builds in preparation for a release Key YP 2.2 Dates: *YP 2.2 M1 cut off would be: 6/13/16 *YP 2.2 M1 release would be: 6/24/16 *YP 2.2 M2 cut off would be: 7/18/16 *YP 2.2 M2 release would be: 7/29/16 *YP 2.2 M3 cut off would be: 8/29/16 *YP 2.2 M3 release would be: 9/9/16 *YP 2.2 M4 cut off would be: 10/3/16 *YP 2.2 M4 release would be: 10/28/16 Tracking Metrics: WDD 2622 (last week 2574) (https://wiki.yoctoproject.org/charts/combo.html) Key Status Links for YP: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features [If anyone has suggestions for other information you'd like to see on this weekly status update, let us know!] Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 * Work Telephone:(503) 712-0534 *Cell: (208) 244-4460 * Email:stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] rootfs mounted read-only on Live USB (x86-64)
On 2016-06-03 10:15 AM, Dan O'Donovan wrote:
On 06/03/2016 10:54 AM, Oleksandr Poznyak wrote:
Hi,
Hi Oleksandr
Check if "read-only-rootfs" feature is added to any of these variables
either in your local.conf or your image bitbake recipe:
Something like that:
IMAGE_FEATURES = "read-only-rootfs"
EXTRA_IMAGE_FEATURES += "read-only-rootfs"
Thanks for your suggestion. I didn't find "read-only-rootfs" specified
in the IMAGE_FEATURES in local.conf or elsewhere. I suspect it might be
a different issue because it only affects the live-boot of the .iso
image. If I install the .hddimage directly to the storage device
instead, then it boots fine and the rootfs is read/write.
[update]
It looks like the problem was indeed the lack of aufs.
I added this in conf/local.conf
DISTRO_FEATURES_append = " aufs"
and this in the kernel recipe
KERNEL_FEATURES_append += "${@bb.utils.contains('DISTRO_FEATURES',
'aufs', ' features/aufs/aufs-enable.scc', '', d)}"
and now the live USB image boots correctly with a read-write filesystem.
Considering that the default images built for a generic x86-64 machine
include a live-boot image (.iso) which is effectively broken, I assume
the aufs feature (or another solution for the live-boot use case) should
really be added by default for those builds as well.
aufs is in the linux-yocto-4.1 and 4.4 kernels. It may be that the
SRCREVs for older branches haven't been updated yet.
commit ed2314d234ff26ed50342264e432392c8908c66b
Author: Bruce Ashfield
Date: Wed Jul 8 15:46:25 2015 -0400
aufs4: core support
Integrating the core aufs4 support from:
git://github.com/sfjro/aufs4-standalone.git
Signed-off-by: Bruce Ashfield
Bruce
Thanks,
Oleksandr Poznyak!
On Fri, Jun 3, 2016 at 12:06 PM, Dan O'Donovan mailto:d...@emutex.com>> wrote:
Hi all
Has anyone else noticed that the root file-system appears to be
mounted read-only when booting a Live USB image from Yocto 2.1.
This is on a sato build from the krogoth branch of poky and
meta-intel, for a generic x86-64 machine (4.4 kernel).
I'm transferring the resulting .iso image to a usb stick using
'dd', and then picking the 'boot' option at startup.
As well as a bunch of errors about the read-only filesystem (e.g.
failing to create files in /var and other locations), the desktop
UI fails to load.
This worked fine with Yocto 2.0.
I have a hunch that it might be caused by a lack of aufs support.
Is it possible that aufs patches were omitted from the x86 kernels
in Yocto 2.1?
Thanks,
-Dan
P.S. It works fine if I just install it directly, or if I use the
.hddimg, instead of trying to boot the live image from the .iso.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] rootfs mounted read-only on Live USB (x86-64)
On 2016-06-03 11:33 AM, Bruce Ashfield wrote:
On 2016-06-03 10:15 AM, Dan O'Donovan wrote:
On 06/03/2016 10:54 AM, Oleksandr Poznyak wrote:
Hi,
Hi Oleksandr
Check if "read-only-rootfs" feature is added to any of these variables
either in your local.conf or your image bitbake recipe:
Something like that:
IMAGE_FEATURES = "read-only-rootfs"
EXTRA_IMAGE_FEATURES += "read-only-rootfs"
Thanks for your suggestion. I didn't find "read-only-rootfs" specified
in the IMAGE_FEATURES in local.conf or elsewhere. I suspect it might be
a different issue because it only affects the live-boot of the .iso
image. If I install the .hddimage directly to the storage device
instead, then it boots fine and the rootfs is read/write.
[update]
It looks like the problem was indeed the lack of aufs.
I added this in conf/local.conf
DISTRO_FEATURES_append = " aufs"
and this in the kernel recipe
KERNEL_FEATURES_append += "${@bb.utils.contains('DISTRO_FEATURES',
'aufs', ' features/aufs/aufs-enable.scc', '', d)}"
and now the live USB image boots correctly with a read-write filesystem.
Considering that the default images built for a generic x86-64 machine
include a live-boot image (.iso) which is effectively broken, I assume
the aufs feature (or another solution for the live-boot use case) should
really be added by default for those builds as well.
aufs is in the linux-yocto-4.1 and 4.4 kernels. It may be that the
SRCREVs for older branches haven't been updated yet.
ah crap. I see you did find the aufs support, just that it wasn't
enabled by the right images.
Bruce
commit ed2314d234ff26ed50342264e432392c8908c66b
Author: Bruce Ashfield
Date: Wed Jul 8 15:46:25 2015 -0400
aufs4: core support
Integrating the core aufs4 support from:
git://github.com/sfjro/aufs4-standalone.git
Signed-off-by: Bruce Ashfield
Bruce
Thanks,
Oleksandr Poznyak!
On Fri, Jun 3, 2016 at 12:06 PM, Dan O'Donovan mailto:d...@emutex.com>> wrote:
Hi all
Has anyone else noticed that the root file-system appears to be
mounted read-only when booting a Live USB image from Yocto 2.1.
This is on a sato build from the krogoth branch of poky and
meta-intel, for a generic x86-64 machine (4.4 kernel).
I'm transferring the resulting .iso image to a usb stick using
'dd', and then picking the 'boot' option at startup.
As well as a bunch of errors about the read-only filesystem (e.g.
failing to create files in /var and other locations), the desktop
UI fails to load.
This worked fine with Yocto 2.0.
I have a hunch that it might be caused by a lack of aufs support.
Is it possible that aufs patches were omitted from the x86 kernels
in Yocto 2.1?
Thanks,
-Dan
P.S. It works fine if I just install it directly, or if I use the
.hddimg, instead of trying to boot the live image from the .iso.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Per image customizations
I found that that’s an issue with rpm packages. I didn't expect there might
be some issue with rpm. If you really don't care which package management
system to use, switch to deb:
PACKAGE_CLASSES = "package_deb"
On Fri, Jun 3, 2016 at 4:52 PM, Diego wrote:
> Hi Oleksandr,
>
> In data mercoledì 1 giugno 2016 21:57:32, Oleksandr Poznyak ha scritto:
> > Here is the content of bbappend recipe for base-files recipe:
> >
> > FILESEXTRAPATHS_append := "${THISDIR}/${PN}"
> >
> > SRC_URI += "file://fstab-flash \
> > file://fstab-regular \
> > "
> >
> > PACKAGES += " ${PN}-flash ${PN}-regular"
> > CONFFILES_${PN}-flash = "${CONFFILES_${PN}}"
> > CONFFILES_${PN}-regular = "${CONFFILES_${PN}}"
> >
> > pkg_preinst_${PN}-flash = "${pkg_preinst_${PN}}"
> > pkg_preinst_${PN}-regular = "${pkg_preinst_${PN}}"
> >
> > RREPLACES_${PN}-flash = "${PN}"
> > RPROVIDES_${PN}-flash = "${PN}"
> > RCONFLICTS_${PN}-flash = "${PN}"
> >
> > RREPLACES_${PN}-regular = "${PN}"
> > RPROVIDES_${PN}-regular = "${PN}"
> > RCONFLICTS_${PN}-regular = "${PN}"
> >
> > python populate_packages_prepend() {
> > import shutil
> >
> > packages = ("${PN}-flash", "${PN}-regular")
> > for package in packages:
> > # copy ${PN} content to packages
> > shutil.copytree("${PKGD}", "${PKGDEST}/%s" % package,
> symlinks=True)
> > # replace fstab
> > if package == "${PN}-flash":
> > shutil.copy("${WORKDIR}/fstab-flash",
> > "${PKGDEST}/${PN}-flash/etc/fstab")
> > else:
> > shutil.copy("${WORKDIR}/fstab-regular",
> > "${PKGDEST}/${PN}-regular/etc/fstab")
> > }
> >
> >
> > This will produce two separate packages that will replace base-files
> > package.
> > Moreover, this trick allows You to modify base-files package separately
> for
> > flash-OS and regular-OS
> >
>
> This is very useful, thank you. With this code I'm able to have two
> different
> fstab files under packages-split:
> ./packages-split/base-files-regular/etc/fstab
> ./packages-split/base-files-flash/etc/fstab
>
> Regardless of that though, the resulting rpm packages for
> "base-files-regular"
> and "base-files-flash" have the original fstab as in "base-files", which is
> different to both the fstabs in packages-split mentioned above.
>
> I'm looking at what might be causing this, but any idea is welcome.
>
> Thanks,
> Diego
>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 1/6] linux-raspberrypi: Allow override of PV
On Fri, 3 Jun 2016 09:07:37 +0300
Ionel Badisor wrote:
> On 06/03/2016 12:25 AM, Paul Barker wrote:
> > On Thu, 2 Jun 2016 10:59:37 +0300
> > Ionel Badisor wrote:
> >
> >> On 06/01/2016 08:55 PM, Paul Barker wrote:
> >>> On Tue, 31 May 2016 10:39:03 +0300
> >>> Khem Raj wrote:
> >>>
> On May 30, 2016 3:15 PM, "Paul Barker"
> wrote:
> >
> >
> > I'm trying to build from a source archive instead of a git
> > repository (to avoid a ~1.3GB git clone operation) so the use of
> > ${SRCPV} is causing me trouble.
> >
>
> Can you override the whole PV
> >>>
> >>> I've given this another look and I can get the recipe to parse if
> >>> I require linux-raspberrypi.inc before setting PV instead of
> >>> afterwards. However do_kernel_configme then gets confused looking
> >>> for a "standard/raspberrypi" configuration. It only works if I
> >>> modify linux-raspberrypi.inc as per my patch and set PV before
> >>> requiring that include file.
> >>>
> >>> I'm starting to think that I might be doing something wrong here -
> >>> is there a supported way to build a kernel from an archive instead
> >>> of a git repository within OE?
> >>>
> >>> Thanks,
> >>> Paul Barker
> >>>
> >> Are you trying to avoid repeated cloning operation to save bandwith
> >> and time or you are trying to save disk space?
> >
> > I'm trying to reduce "time to first build" on a new build machine as
> > well as the amount of space/bandwidth needed to mirror downloaded
> > files.
> >
> > Instead of setting PV in each recipe I could just duplicate
> > linux-raspberrypi.inc into my own layer with the change I need.
> > That's probably the simplest approach for now, I'll just have to
> > keep my eye on meta-raspberrypi going forward for any changes to
> > linux-raspberrypi.inc which I'd need to incorporate.
> >
> Maybe you can use the `DL_DIR ?= "/path/to/downloads/"` in your
> conf/local.conf file for multiple build directories and if you want
> you can copy downloads directory to new machine and point to it the
> new local.conf then all do_fetch operations are already performed,
> except new changes in which case the git fetch operation is performed
> when git is used and takes less time then when fetching entire
> archive.
>
> note: multiple builds on same machine can use same downloads
> directory.
I'm planning to release this as part of a distro layer in the future.
Not all build machines will be under my control if others use the
layer.
I'm going to drop this patch for now as I can maintain my own copy of
linux-raspberrypi.inc. I think it'd be good to get the other changes
into master.
V2 incoming.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH V2 0/4] Drop rpi-mkimage and use upstream u-boot
Changes for V2: * Don't remove linux-raspberrypi 3.18 just yet * Drop move of PV setting out of linux-raspberrypi.inc Paul Barker (4): linux-raspberrypi: rpi-mkimage is no longer needed u-boot: Use mainline u-boot recipe from oe-core rpi-mkimage: Remove unused recipe sdcard_image-rpi: Always install dtb files classes/sdcard_image-rpi.bbclass | 42 +++--- conf/machine/include/rpi-default-providers.inc | 1 - conf/machine/raspberrypi.conf | 2 ++ conf/machine/raspberrypi2.conf | 2 ++ recipes-bsp/rpi-mkimage/rpi-mkimage/License| 25 - .../open-files-relative-to-script.patch| 17 - recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb | 22 recipes-bsp/u-boot/u-boot-rpi_git.bb | 29 --- recipes-kernel/linux/linux-raspberrypi.inc | 18 -- 9 files changed, 25 insertions(+), 133 deletions(-) delete mode 100644 recipes-bsp/rpi-mkimage/rpi-mkimage/License delete mode 100644 recipes-bsp/rpi-mkimage/rpi-mkimage/open-files-relative-to-script.patch delete mode 100644 recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb delete mode 100644 recipes-bsp/u-boot/u-boot-rpi_git.bb -- 2.1.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH V2 2/4] u-boot: Use mainline u-boot recipe from oe-core
The repository used by u-boot-rpi has not been updated since 2012. In the
meantime, mailine u-boot has gained Raspberry Pi support. All we need to do is
set UBOOT_MACHINE to an appropriate value in the machine config files.
Currently configs are only provided for raspberrypi and raspberrypi2. The master
branch of u-boot now also appears to have a config file for raspberrypi3 so
support for this can be added in the future when u-boot is upgraded in oe-core.
The mainline u-boot recipe creates the file "u-boot.bin" instead of
"u-boot.img".
Signed-off-by: Paul Barker
---
classes/sdcard_image-rpi.bbclass | 2 +-
conf/machine/include/rpi-default-providers.inc | 1 -
conf/machine/raspberrypi.conf | 2 ++
conf/machine/raspberrypi2.conf | 2 ++
recipes-bsp/u-boot/u-boot-rpi_git.bb | 29 --
5 files changed, 5 insertions(+), 31 deletions(-)
delete mode 100644 recipes-bsp/u-boot/u-boot-rpi_git.bb
diff --git a/classes/sdcard_image-rpi.bbclass b/classes/sdcard_image-rpi.bbclass
index 4dfd7a3..20bd314 100644
--- a/classes/sdcard_image-rpi.bbclass
+++ b/classes/sdcard_image-rpi.bbclass
@@ -105,7 +105,7 @@ IMAGE_CMD_rpi-sdimg () {
mcopy -i ${WORKDIR}/boot.img -s ${DEPLOY_DIR_IMAGE}/bcm2835-bootfiles/*
::/
case "${KERNEL_IMAGETYPE}" in
"uImage")
- mcopy -i ${WORKDIR}/boot.img -s ${DEPLOY_DIR_IMAGE}/u-boot.img
::${SDIMG_KERNELIMAGE}
+ mcopy -i ${WORKDIR}/boot.img -s ${DEPLOY_DIR_IMAGE}/u-boot.bin
::${SDIMG_KERNELIMAGE}
mcopy -i ${WORKDIR}/boot.img -s
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}${KERNEL_INITRAMFS}-${MACHINE}.bin
::uImage
;;
*)
diff --git a/conf/machine/include/rpi-default-providers.inc
b/conf/machine/include/rpi-default-providers.inc
index cabbd43..359870d 100644
--- a/conf/machine/include/rpi-default-providers.inc
+++ b/conf/machine/include/rpi-default-providers.inc
@@ -1,7 +1,6 @@
# RaspberryPi BSP default providers
PREFERRED_PROVIDER_virtual/kernel ?= "linux-raspberrypi"
-PREFERRED_PROVIDER_u-boot ?= "u-boot-rpi"
PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg"
PREFERRED_PROVIDER_virtual/egl ?= "userland"
PREFERRED_PROVIDER_virtual/libgles2 ?= "userland"
diff --git a/conf/machine/raspberrypi.conf b/conf/machine/raspberrypi.conf
index 0f95f1a..72beeb8 100644
--- a/conf/machine/raspberrypi.conf
+++ b/conf/machine/raspberrypi.conf
@@ -8,3 +8,5 @@ require conf/machine/include/tune-arm1176jzf-s.inc
include conf/machine/include/rpi-base.inc
SERIAL_CONSOLE = "115200 ttyAMA0"
+
+UBOOT_MACHINE = "rpi_config"
diff --git a/conf/machine/raspberrypi2.conf b/conf/machine/raspberrypi2.conf
index b6346e6..d50ef70 100644
--- a/conf/machine/raspberrypi2.conf
+++ b/conf/machine/raspberrypi2.conf
@@ -8,3 +8,5 @@ require conf/machine/include/tune-cortexa7.inc
include conf/machine/include/rpi-base.inc
SERIAL_CONSOLE = "115200 ttyAMA0"
+
+UBOOT_MACHINE = "rpi_2_config"
diff --git a/recipes-bsp/u-boot/u-boot-rpi_git.bb
b/recipes-bsp/u-boot/u-boot-rpi_git.bb
deleted file mode 100644
index 3e8d377..000
--- a/recipes-bsp/u-boot/u-boot-rpi_git.bb
+++ /dev/null
@@ -1,29 +0,0 @@
-DESCRIPTION = "U-Boot port for RaspberryPi"
-
-require recipes-bsp/u-boot/u-boot.inc
-
-DEPENDS += "rpi-mkimage-native"
-
-PROVIDES += "u-boot"
-
-LICENSE = "GPLv2+"
-LIC_FILES_CHKSUM = "file://COPYING;md5=1707d6db1d42237583f50183a5651ecb"
-
-SRCREV = "6709570cdc947c2a546f96d571551acf4474778c"
-SRC_URI = "git://github.com/gonzoua/u-boot-pi.git;branch=rpi"
-
-S = "${WORKDIR}/git"
-
-UBOOT_MACHINE = "rpi_b"
-UBOOT_MAKE_TARGET = "u-boot.bin"
-UBOOT_SUFFIX = "img"
-
-PACKAGE_ARCH = "${MACHINE_ARCH}"
-
-COMPATIBLE_MACHINE = "raspberrypi"
-
-do_compile_append() {
-# Create kernel.img from uboot.bin and name it u-boot.img
-${STAGING_BINDIR_NATIVE}/imagetool-uncompressed.py u-boot.bin
-mv kernel.img u-boot.img
-}
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH V2 1/4] linux-raspberrypi: rpi-mkimage is no longer needed
Recent versions of the Raspberry Pi firmware can directly handle kernel images
which use device tree. The modifications made by rpi-mkimage are no longer
needed.
Signed-off-by: Paul Barker
---
recipes-kernel/linux/linux-raspberrypi.inc | 18 --
1 file changed, 18 deletions(-)
diff --git a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc
index 4799c74..ddf4785 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -35,13 +35,6 @@ python __anonymous () {
kerneltype = d.getVar('KERNEL_IMAGETYPE', True)
kerneldt = get_dts(d, d.getVar('LINUX_VERSION', True))
d.setVar("KERNEL_DEVICETREE", kerneldt)
-
-# Add dependency to 'rpi-mkimage-native' package only if RPi bootloader is
used with DT-enable kernel
-if kerneldt:
-if kerneltype != 'uImage' and len(kerneldt.strip()) > 1:
-depends = d.getVar("DEPENDS", True)
-depends = "%s rpi-mkimage-native" % depends
-d.setVar("DEPENDS", depends)
}
do_kernel_configme_prepend() {
@@ -62,15 +55,6 @@ do_deploy_append() {
echo "${CMDLINE}${PITFT_PARAMS}" >
${DEPLOYDIR}/bcm2835-bootfiles/cmdline.txt
}
-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_BINDIR_NATIVE}/mkknlimg --dtok ${KERNEL_OUTPUT}
${KERNEL_OUTPUT}
-fi
-fi
-}
-
do_bundle_initramfs_append() {
if [ ! -z "${INITRAMFS_IMAGE}" -a x"${INITRAMFS_IMAGE_BUNDLE}" = x1 ]; then
if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
@@ -81,5 +65,3 @@ do_bundle_initramfs_append() {
fi
fi
}
-
-addtask rpiboot_mkimage before do_install after do_compile
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH V2 3/4] rpi-mkimage: Remove unused recipe
The rpi-mkimage tools are no longer used. Recent Raspberry Pi firmware can
directly boot a Linux kernel image using device tree and mainline u-boot
supports Raspberry Pi without the use of these tools.
Signed-off-by: Paul Barker
---
recipes-bsp/rpi-mkimage/rpi-mkimage/License| 25 --
.../open-files-relative-to-script.patch| 17 ---
recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb | 22 ---
3 files changed, 64 deletions(-)
delete mode 100644 recipes-bsp/rpi-mkimage/rpi-mkimage/License
delete mode 100644
recipes-bsp/rpi-mkimage/rpi-mkimage/open-files-relative-to-script.patch
delete mode 100644 recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb
diff --git a/recipes-bsp/rpi-mkimage/rpi-mkimage/License
b/recipes-bsp/rpi-mkimage/rpi-mkimage/License
deleted file mode 100644
index 2582681..000
--- a/recipes-bsp/rpi-mkimage/rpi-mkimage/License
+++ /dev/null
@@ -1,25 +0,0 @@
-Copyright (c) 2012, Broadcom Europe Ltd
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-* Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-* Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
-* Neither the name of the copyright holder nor the
- names of its contributors may be used to endorse or promote products
- derived from this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY
-DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
-ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
diff --git
a/recipes-bsp/rpi-mkimage/rpi-mkimage/open-files-relative-to-script.patch
b/recipes-bsp/rpi-mkimage/rpi-mkimage/open-files-relative-to-script.patch
deleted file mode 100644
index fa9e88b..000
--- a/recipes-bsp/rpi-mkimage/rpi-mkimage/open-files-relative-to-script.patch
+++ /dev/null
@@ -1,17 +0,0 @@
-When using open, use path relative to imagetool-uncompressed.py
-
-Signed-off-by: Andrei Gherzan
-
-Index: git/mkimage/imagetool-uncompressed.py
-===
a/mkimage/imagetool-uncompressed.py
-+++ b/mkimage/imagetool-uncompressed.py
-@@ -18,7 +18,7 @@ re_line = re.compile(r"0x(?P[0-9a
- mem = [0 for i in range(32768)]
-
- def load_to_mem(name, addr):
-- f = open(name)
-+ f = open(os.path.dirname(__file__) + '/' + name)
-
-for l in f.readlines():
- m = re_line.match(l)
diff --git a/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb
b/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb
deleted file mode 100644
index cce91d7..000
--- a/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb
+++ /dev/null
@@ -1,22 +0,0 @@
-SUMMARY = "RaspberryPi tool to produce kernel.img"
-LICENSE = "Broadcom"
-LIC_FILES_CHKSUM =
"file://${WORKDIR}/License;md5=957f6640d5e2d2acfce73a36a56cb32f"
-SECTION = "bootloader"
-
-DEPENDS = "python"
-
-SRCREV = "f5642106425d430e1f82ee064121a5fd0e05a386"
-SRC_URI = " \
-git://github.com/raspberrypi/tools.git;branch=master;protocol=git \
-file://License \
-file://open-files-relative-to-script.patch \
-"
-
-S = "${WORKDIR}/git"
-
-do_install () {
-install -d ${D}${bindir}
-install -t ${D}${bindir} mkimage/*
-}
-
-BBCLASSEXTEND = "native"
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH V2 4/4] sdcard_image-rpi: Always install dtb files
We now need dtb files when booting via u-boot.
Signed-off-by: Paul Barker
---
classes/sdcard_image-rpi.bbclass | 40
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/classes/sdcard_image-rpi.bbclass b/classes/sdcard_image-rpi.bbclass
index 20bd314..3b4f13f 100644
--- a/classes/sdcard_image-rpi.bbclass
+++ b/classes/sdcard_image-rpi.bbclass
@@ -103,32 +103,32 @@ IMAGE_CMD_rpi-sdimg () {
rm -f ${WORKDIR}/boot.img
mkfs.vfat -n "${BOOTDD_VOLUME_ID}" -S 512 -C ${WORKDIR}/boot.img
$BOOT_BLOCKS
mcopy -i ${WORKDIR}/boot.img -s ${DEPLOY_DIR_IMAGE}/bcm2835-bootfiles/*
::/
+ if test -n "${DTS}"; then
+ # Device Tree Overlays are assumed to be suffixed by
'-overlay.dtb' string and will be put in a dedicated folder
+ DT_OVERLAYS="${@split_overlays(d, 0)}"
+ DT_ROOT="${@split_overlays(d, 1)}"
+
+ # Copy board device trees to root folder
+ for DTB in ${DT_ROOT}; do
+ DTB_BASE_NAME=`basename ${DTB} .dtb`
+
+ mcopy -i ${WORKDIR}/boot.img -s
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.dtb
::${DTB_BASE_NAME}.dtb
+ done
+
+ # Copy device tree overlays to dedicated folder
+ mmd -i ${WORKDIR}/boot.img overlays
+ for DTB in ${DT_OVERLAYS}; do
+ DTB_BASE_NAME=`basename ${DTB} .dtb`
+
+ mcopy -i ${WORKDIR}/boot.img -s
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.dtb
::overlays/${DTB_BASE_NAME}.dtb
+ done
+ fi
case "${KERNEL_IMAGETYPE}" in
"uImage")
mcopy -i ${WORKDIR}/boot.img -s ${DEPLOY_DIR_IMAGE}/u-boot.bin
::${SDIMG_KERNELIMAGE}
mcopy -i ${WORKDIR}/boot.img -s
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}${KERNEL_INITRAMFS}-${MACHINE}.bin
::uImage
;;
*)
- if test -n "${DTS}"; then
- # Device Tree Overlays are assumed to be suffixed by
'-overlay.dtb' string and will be put in a dedicated folder
- DT_OVERLAYS="${@split_overlays(d, 0)}"
- DT_ROOT="${@split_overlays(d, 1)}"
-
- # Copy board device trees to root folder
- for DTB in ${DT_ROOT}; do
- DTB_BASE_NAME=`basename ${DTB} .dtb`
-
- mcopy -i ${WORKDIR}/boot.img -s
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.dtb
::${DTB_BASE_NAME}.dtb
- done
-
- # Copy device tree overlays to dedicated folder
- mmd -i ${WORKDIR}/boot.img overlays
- for DTB in ${DT_OVERLAYS}; do
- DTB_BASE_NAME=`basename ${DTB} .dtb`
-
- mcopy -i ${WORKDIR}/boot.img -s
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.dtb
::overlays/${DTB_BASE_NAME}.dtb
- done
- fi
mcopy -i ${WORKDIR}/boot.img -s
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}${KERNEL_INITRAMFS}-${MACHINE}.bin
::${SDIMG_KERNELIMAGE}
;;
esac
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [opkg-utils PATCH] arfile.py: remove dependency on python-future
Python-future provides a python2 compatible object class (provides next method). Since method is not used, remove dependency. Signed-off-by: Alejandro del Castillo --- arfile.py | 1 - 1 file changed, 1 deletion(-) diff --git a/arfile.py b/arfile.py index 4bab526..1c42bc7 100644 --- a/arfile.py +++ b/arfile.py @@ -7,7 +7,6 @@ of GNU General Public License v2 or later. """ from __future__ import absolute_import from __future__ import print_function -from builtins import object import sys import os import tarfile -- 1.9.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [ANNOUNCEMENT] Yocto Project 2.0.2 (Jethro 14.0.2) Released
Hello, The latest release of the Yocto Project 2.0.2 (jethro-14.0.2) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/poky-jethro-14.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.0.2/poky-fido-14.0.2.tar.bz2 A gpg signed version of these release notes is available at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/RELEASENOTES Full pass test report is available at: https://wiki.yoctoproject.org/wiki/WW23_-_2016-05-24_-_Full_Pass_2.0.2.rc1 Thanks to everyone for all their hard work on this release! Sincerely, Tracy Graydon Yocto Project Build and Release -- yocto-2.0.2 Errata Release Name: eclipse-poky-kepler-jethro-14.0.2 Branch: kepler/jethro Tag: kepler/jethro-14.0.2 Hash: cf60ac293629fc8ecd6c4eb3709a6f334b499d0c md5: 1a542aecf32a80e546689a435bf53d11 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/eclipse-poky-kepler-jethro-14.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.0.2/eclipse-poky-kepler-jethro-14.0.2.tar.bz2 Release Name: eclipse-poky-luna-jethro-14.0.2 Branch: luna/jethro Tag: luna/jethro-14.0.2 Hash: 45aa5c77523bdf051d548fff4305382942db2ebb md5: e8c251d3e469d260b6beea00b00dc614 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/eclipse-poky-luna-jethro-14.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.0.2/eclipse-poky-luna-jethro-14.0.2.tar.bz2 Release Name: eclipse-poky-mars-jethro-14.0.2 Branch: mars/jethro Tag: mars/jethro-14.0.2 Hash: 1d179ddcbd1983bf7bcfe98efdcbb186bdccca4f md5: 14e7528f8b13bb9b31fdb2be3da0a3f1 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/eclipse-poky-mars-jethro-14.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.0.2/eclipse-poky-mars-jethro-14.0.2.tar.bz2 Release Name: meta-qt3-jethro-14.0.2 Branch: jethro Tag: jethro-14.0.2 Hash: b08996efbfb3b26e62b608f34ebf5e671b36ec61 md5: ffb7af0fef8e3c1f04e0a595848a102e Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/meta-qt3-jethro-14.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.0.2/meta-qt3-jethro-14.0.2.tar.bz2 Release Name: poky-jethro-14.0.2 Branch: jethro Tag: jethro-14.0.2 Hash: dade0e68c645473d94e1b05020b064df40677e81 md5: 854586669612e553f9cb59bf8c329a65 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.0.2/poky-jethro-14.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.0.2/poky-jethro-14.0.2.tar.bz2 --- Known Issues --- n/a --- Security Fixes --- gcc: Security Fix CVE-2016-4490 gcc: Security fix CVE-2016-2226 gcc: Security fix CVE-2016-4489 gcc: Security fix CVE-2016-4488 openssh: Security Fix CVE-2016-3115 busybox: Security fix CVE-2016-2147 busybox: Security Fix CVE-2016-2148 libtiff: Security fix CVE-2015-8664 and 8683 openssl: 1.0.2d -> 1.0.2h (mainly for CVEs) glibc: Fix CVE-2015-8778 bind: CVE-2016-1285 CVE-2016-1286 dhcp: CVE-2015-8605 openssl: Security fix CVE-2016-0800 wpa-supplicant: Fix CVE-2015-8041 --- Fixes --- wic: insert local Python paths at front build-appliance-image: Update to jethro head revision poky.conf: Bump version for 2.0.2 jethro release build-appliance-image: Update to jethro head revision gdb: Backport patch to changes with AVX and MPX yocto-bsp: Set correct default branches and branches base for i386, qemu and x86_64 archs yocto-bsp: fix default kernel for x86_64 arch conf/distro/poky.conf: use example.com for connectivity check openssl: prevent ABI break from earlier jethro releases Revert "kernel/kernel-arch: Explicitly mapping between, i386/x86_64 and x86 for kernel ARCH" glew: Correct version in autotooling patches gdb: fix QA warning (uClibc) binutils: backport bug fix to the 2.25 branch for jethro boot-directdisk.bbclass: remove HDDIMG before create opkg: backport fix for double remove of packges license.bbclass: fix warnings when run in unprivileged "container" env tzdata: update to 2016d tzcode: update to 2016d tzcode: update to 2016c tzdata: update to 2016c tzcode: update to 2016b tzdata: update to 2016b yocto-project-qs: Updated the minnowboard example. poky.ent: Added lower-case distro name variable. lttng-tools: fix regression tests hang ncurses: update SRC_URI python3: fix building nativesdk-python3 systemd-serialgetty: allow baud rate overriding boost: ensure boost to remain an empty metapackage systemd: chown hwdb.bin to root:root for do_rootfs cdrtools: update SRC_URI gcc-cross-canadian.inc: add INSANE_SKIP_ to avoid build warning systemd: fix segfault on shutdown nfs-utils: bugfix: adjust name of statd service unit busybox_git: Fix SRCREV busybox-1.23: Backport patch to fix zcip false-conflict bluez5: allow D-Bus to spawn obexd in systems without systemd ruby-native: Depend on openssl-native devtool: extract: update SRCTREECOVEREDTASKS for kernel devtool: extract: co
