From: Philipp Wagner <lists@philipp-wagner.com>
To: yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi][PATCH] linux: Update to 3.12.3 (latest RPI upstream)
Date: Mon, 16 Dec 2013 21:44:00 +0100 [thread overview]
Message-ID: <52AF6610.9040102@philipp-wagner.com> (raw)
In-Reply-To: <52A8B299.3000704@mlbassoc.com>
Am 11.12.2013 19:44, Gary Thomas wrote:
> On 2013-12-11 11:23, Andrei Gherzan wrote:
>>
>>
>>
>> On Wed, Dec 11, 2013 at 8:14 PM, Gary Thomas <gary@mlbassoc.com
>> <mailto:gary@mlbassoc.com>> wrote:
>>
>> On 2013-12-11 11:08, Andrei Gherzan wrote:
>>
>>
>>
>>
>> On Sun, Dec 8, 2013 at 2:17 PM, <lists@philipp-wagner.com
>> <mailto:lists@philipp-wagner.com> <mailto:lists@philipp-wagner.__com
>> <mailto:lists@philipp-wagner.com>>> wrote:
>>
>> From: Philipp Wagner <mail@philipp-wagner.com
>> <mailto:mail@philipp-wagner.com> <mailto:mail@philipp-wagner.__com
>> <mailto:mail@philipp-wagner.com>>>
>>
>> Signed-off-by: Philipp Wagner <mail@philipp-wagner.com
>> <mailto:mail@philipp-wagner.com> <mailto:mail@philipp-wagner.__com
>> <mailto:mail@philipp-wagner.com>>>
>> ---
>> recipes-kernel/linux/linux-__raspberrypi_3.12.0.bb
>> <http://linux-raspberrypi_3.12.0.bb>
>> <http://linux-raspberrypi_3.__12.0.bb
>> <http://linux-raspberrypi_3.12.0.bb>> |
>> 6 ------
>> recipes-kernel/linux/linux-__raspberrypi_3.12.3.bb
>> <http://linux-raspberrypi_3.12.3.bb>
>> <http://linux-raspberrypi_3.__12.3.bb
>> <http://linux-raspberrypi_3.12.3.bb>> |
>> 6 ++++++
>>
>> 2 files changed, 6 insertions(+), 6 deletions(-)
>> delete mode 100644
>> recipes-kernel/linux/linux-__raspberrypi_3.12.0.bb
>> <http://linux-raspberrypi_3.12.0.bb>
>> <http://linux-raspberrypi_3.__12.0.bb
>> <http://linux-raspberrypi_3.12.0.bb>>
>> create mode 100644
>> recipes-kernel/linux/linux-__raspberrypi_3.12.3.bb
>> <http://linux-raspberrypi_3.12.3.bb>
>> <http://linux-raspberrypi_3.__12.3.bb
>> <http://linux-raspberrypi_3.12.3.bb>>
>>
>> diff --git
>> a/recipes-kernel/linux/linux-__raspberrypi_3.12.0.bb
>> <http://linux-raspberrypi_3.12.0.bb>
>> <http://linux-raspberrypi_3.__12.0.bb
>> <http://linux-raspberrypi_3.12.0.bb>>
>> b/recipes-kernel/linux/linux-__raspberrypi_3.12.0.bb
>> <http://linux-raspberrypi_3.12.0.bb>
>> <http://linux-raspberrypi_3.__12.0.bb
>> <http://linux-raspberrypi_3.12.0.bb>>
>>
>> deleted file mode 100644
>> index 3631da5..0000000
>> --- a/recipes-kernel/linux/linux-__raspberrypi_3.12.0.bb
>> <http://linux-raspberrypi_3.12.0.bb>
>> <http://linux-raspberrypi_3.__12.0.bb
>> <http://linux-raspberrypi_3.12.0.bb>>
>>
>> +++ /dev/null
>> @@ -1,6 +0,0 @@
>> -SRCREV = "__839f349b6ed2a63a2bff0b5f0d718a__7b07ca2316"
>> -SRC_URI =
>> "git://github.com/raspberrypi/__linux.git;protocol=git;branch=__rpi-3.12.y
>> <http://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.12.y>
>>
>> <http://github.com/__raspberrypi/linux.git;__protocol=git;branch=rpi-3.12.y
>> <http://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.12.y>__>
>> \
>>
>> - file://__sl030raspberrypii2ckernel.__patch \
>> - "
>> -
>> -require linux-raspberrypi.inc
>> diff --git
>> a/recipes-kernel/linux/linux-__raspberrypi_3.12.3.bb
>> <http://linux-raspberrypi_3.12.3.bb>
>> <http://linux-raspberrypi_3.__12.3.bb
>> <http://linux-raspberrypi_3.12.3.bb>>
>> b/recipes-kernel/linux/linux-__raspberrypi_3.12.3.bb
>> <http://linux-raspberrypi_3.12.3.bb>
>> <http://linux-raspberrypi_3.__12.3.bb
>> <http://linux-raspberrypi_3.12.3.bb>>
>>
>> new file mode 100644
>> index 0000000..304c1ad
>> --- /dev/null
>> +++ b/recipes-kernel/linux/linux-__raspberrypi_3.12.3.bb
>> <http://linux-raspberrypi_3.12.3.bb>
>> <http://linux-raspberrypi_3.__12.3.bb
>> <http://linux-raspberrypi_3.12.3.bb>>
>>
>> @@ -0,0 +1,6 @@
>> +SRCREV = "__7dac37b9865ab51f7a68b7703bf679__2b698fee1b"
>>
>>
>>
>> As pointed in https://review.gherzan.ro:__8443/#/c/27/
>> <https://review.gherzan.ro:8443/#/c/27/>, it seems this SRCREV is
>> invalid.
>>
>>
>> Since that note has little detail, are you sure that this is not
>> just a case where the desired SRCREV is on a branch other than
>> 'master'?
>> With the latest bitbake master, you have to explicitly specify the
>> branch
>> if the desired revision is on a different branch.
>>
>>
>> I know. But the branch is already specified in SRC_URI. So most
>> probably upstream sqashed the repo?
>
> Indeed, I just checked the repo and it's not there.
>
> Looks like the correct rev might be
> 9fbb114990c409406ae20c56871727ff8d4fa6ca
> I may give this a go as it has V4L2 drivers for my camera which I'm anxious
> to get going with Yocto :-)
Oops, I totally forgot to reply. Yes, the revision existed but upstream
seems to be great at modifying a published repository (this has happened
before). [Maybe someone could give them an introduction how to handle
published git repositories ... argh]
To go forward, just drop this patch and go with the one Gary posted today.
Philipp
next prev parent reply other threads:[~2013-12-16 20:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 12:17 [meta-raspberrypi][PATCH] linux: Update to 3.12.3 (latest RPI upstream) lists
2013-12-11 18:08 ` Andrei Gherzan
2013-12-11 18:14 ` Gary Thomas
2013-12-11 18:23 ` Andrei Gherzan
2013-12-11 18:44 ` Gary Thomas
2013-12-11 19:13 ` Andrei Gherzan
2013-12-16 20:44 ` Philipp Wagner [this message]
2013-12-17 16:05 ` Andrei Gherzan
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=52AF6610.9040102@philipp-wagner.com \
--to=lists@philipp-wagner.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.