From: Andrei Gherzan <andrei@gherzan.ro>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi][PATCH V3 0/4] Drop rpi-mkimage and use upstream u-boot
Date: Fri, 8 Jul 2016 12:31:51 +0100 [thread overview]
Message-ID: <20160708113151.GC14479@resin.home> (raw)
In-Reply-To: <1466248026-4838-1-git-send-email-paul@paulbarker.me.uk>
[-- Attachment #1: Type: text/plain, Size: 2173 bytes --]
On Sat, Jun 18, 2016 at 12:07:02PM +0100, Paul Barker wrote:
> Following discussion on the Raspberry Pi tools bug tracker it was found that
> rpi-mkimage is no longer needed with recent firmware. It can therefore be
> dropped from the layer completely.
>
> Whilst looking into this I also found that the u-boot-rpi recipe in
> meta-raspberrypi can now be replaced by direct use of the mainline u-boot recipe
> from oe-core. The 2016.03 release of u-boot supports the original Raspberry Pi
> and the Raspberry Pi 2. Configuration of the u-boot environment to directly boot
> the uImage file on the SD card must still be done manually - I'm going to look
> into making this work by default in the near future.
>
> Changes for V2:
> * Don't remove linux-raspberrypi 3.18 just yet
> * Drop move of PV setting out of linux-raspberrypi.inc
>
> Changes for V3:
> * Rebase onto latest master
>
> 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 | 20 -----------
> 9 files changed, 25 insertions(+), 135 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
>
Merged to master. Thank you.
--
Andrei Gherzan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2016-07-08 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 11:07 [meta-raspberrypi][PATCH V3 0/4] Drop rpi-mkimage and use upstream u-boot Paul Barker
2016-06-18 11:07 ` [meta-raspberrypi][PATCH V3 1/4] linux-raspberrypi: rpi-mkimage is no longer needed Paul Barker
2016-06-18 11:07 ` [meta-raspberrypi][PATCH V3 2/4] u-boot: Use mainline u-boot recipe from oe-core Paul Barker
2016-06-18 11:07 ` [meta-raspberrypi][PATCH V3 3/4] rpi-mkimage: Remove unused recipe Paul Barker
2016-06-18 11:07 ` [meta-raspberrypi][PATCH V3 4/4] sdcard_image-rpi: Always install dtb files Paul Barker
2016-07-06 22:53 ` [meta-raspberrypi][PATCH V3 0/4] Drop rpi-mkimage and use upstream u-boot Paul Barker
2016-07-08 11:31 ` Andrei Gherzan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160708113151.GC14479@resin.home \
--to=andrei@gherzan.ro \
--cc=paul@paulbarker.me.uk \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.