From: Andrei Gherzan <andrei@gherzan.ro>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Gary Thomas <gary@mlbassoc.com>
Subject: Re: [meta-raspberrypi][PATCH 1/2] firmware: Use release tarballs
Date: Sat, 12 Nov 2016 18:45:22 +0000 [thread overview]
Message-ID: <20161112184522.GA32346@carbonA.lan> (raw)
In-Reply-To: <d62052d0-a042-312c-cef9-e184def18bc5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2559 bytes --]
On Sat, Nov 12, 2016 at 07:34:43AM -0800, Khem Raj wrote:
>
>
> On 11/12/16 4:23 AM, Andrei Gherzan wrote:
> > On Tue, Nov 08, 2016 at 06:46:45AM -0800, Khem Raj wrote:
> >> On Tue, Nov 8, 2016 at 3:38 AM, Andrei Gherzan <andrei@gherzan.ro> wrote:
> >>> On Tue, Nov 08, 2016 at 12:35:47PM +0100, Gary Thomas wrote:
> >>>> On 2016-11-08 12:16, Andrei Gherzan wrote:
> >>>>> On Sun, Nov 6, 2016 at 7:25 AM, Khem Raj <raj.khem@gmail.com> wrote:
> >>>>>> This is a binary repo and its quite large in size
> >>>>>> we do not need the whole history of this repo since
> >>>>>> most of stuff needed is binaries, therefore switch
> >>>>>> to release tarballs
> >>>>>>
> >>>>>> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> >>>>>> ---
> >>>>>> recipes-bsp/common/firmware.inc | 12 +++++++-----
> >>>>>> 1 file changed, 7 insertions(+), 5 deletions(-)
> >>>>>>
> >>>>>> diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
> >>>>>> index ed0782f..8862f58 100644
> >>>>>> --- a/recipes-bsp/common/firmware.inc
> >>>>>> +++ b/recipes-bsp/common/firmware.inc
> >>>>>> @@ -1,8 +1,10 @@
> >>>>>> -RPIFW_SRCREV ?= "413fc664838e81caeabdc4118dc51e138d5d6c71"
> >>>>>> -RPIFW_DATE ?= "20161030"
> >>>>>> -RPIFW_SRC_URI ?= "git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
> >>>>>> -RPIFW_S ?= "${WORKDIR}/git"
> >>>>>> +RPIFW_DATE ?= "20161020"
> >>>>>> +RPIFW_SRC_URI ?= "https://github.com/raspberrypi/firmware/archive/1.${RPIFW_DATE}.tar.gz"
> >>>>>> +RPIFW_S ?= "${WORKDIR}/firmware-1.${RPIFW_DATE}"
> >>>>>>
> >>>>>> SRC_URI = "${RPIFW_SRC_URI}"
> >>>>>> -SRCREV = "${RPIFW_SRCREV}"
> >>>>>> +SRC_URI[md5sum] = "d3c388c114af4c672dd3ee0ed8e984d3"
> >>>>>> +SRC_URI[sha256sum] = "1c7c49d58800aab2dd1b5ff59a1e297934f9ea6f47ebdf0a3f90632561dc690b"
> >>>>>> +
> >>>>>> PV = "${RPIFW_DATE}"
> >>>>>
> >>>>> Merged to master. Thanks.
> >>>>
> >>>> Sadly, the firmware revision went backwards in this change.
> >>>> Do you want a new patch to play catch-up?
> >>>>
> >>>
> >>> Good catch. I'll fix it. Thanks.
> >>
> >> ah sorry about that.
> >> just hardcode PV = "20161030" for now. with next release we will get it right
> >> since its already past oct 30.
> >
> > Actually the last archive is 1.20161020.
> > https://github.com/raspberrypi/firmware/releases
>
> thats what i mean, when there is next release whenever that is,
> it will be newer than todays date. The problem here is that we went backwards
> for once only.
Got it now. Thanks.
--
Andrei Gherzan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 817 bytes --]
prev parent reply other threads:[~2016-11-12 18:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 7:25 [meta-raspberrypi][PATCH 1/2] firmware: Use release tarballs Khem Raj
2016-11-06 7:25 ` [meta-raspberrypi][PATCH 2/2] userland: Bump to latest and add ASNEEDED = "" Khem Raj
2016-11-06 10:57 ` Andrei Gherzan
2016-11-06 17:16 ` Khem Raj
2016-11-08 11:28 ` Andrei Gherzan
2016-11-06 10:14 ` [meta-raspberrypi][PATCH 1/2] firmware: Use release tarballs Paul Barker
2016-11-06 10:56 ` Andrei Gherzan
2016-11-06 17:17 ` Khem Raj
2016-11-08 11:16 ` Andrei Gherzan
2016-11-08 11:35 ` Gary Thomas
2016-11-08 11:38 ` Andrei Gherzan
2016-11-08 14:46 ` Khem Raj
2016-11-12 12:23 ` Andrei Gherzan
2016-11-12 15:34 ` Khem Raj
2016-11-12 18:45 ` 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=20161112184522.GA32346@carbonA.lan \
--to=andrei@gherzan.ro \
--cc=gary@mlbassoc.com \
--cc=raj.khem@gmail.com \
--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.