[oe] [PATCH] u-boot-sakoman_git.bb: updated SRCREV to head to make it building again

Frans Meulenbroeks fransmeulenbroeks at gmail.com
Sun Oct 24 07:41:57 UTC 2010


2010/10/23 Steve Sakoman <sakoman at gmail.com>:
> On Sat, Oct 23, 2010 at 10:36 AM, Frans Meulenbroeks
> <fransmeulenbroeks at gmail.com> wrote:
>> 2010/10/23 Koen Kooi <k.kooi at student.utwente.nl>:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> On 23-10-10 17:41, Frans Meulenbroeks wrote:
>>>> SRCREV was "ccd0c67858c6e2807c695e2c8f545284cb871866", but that is not in the
>>>> omap4s-exp branch any more. Guess it was gone after a merge. To make things
>>>> building I moved the the head of the branch
>>>> SRCREV = "8b931e51f46acffd61096553ae89dfb3ee30d398"
>>>
>>> That branch is rebased frequently, so this won't help much. The tarball
>>> snapshot for the current revision is available on the angstrom source
>>> mirror, so if you are using angstrom and a recent bitbake you won't get
>>> bothered by the rebasing.
>>> Having said all that, we should find a working repo for panda uboot and
>>> use that. AIUI denx git should work soon.
>>>
>>> regards,
>>>
>>> Koen
>>
>> Guess that is why it was autorev, but on oct 12 you pinned it to the
>> SRCREV that I could not fetch.
>> A solution could be to pin on a rev that is a merge with the denx git.
>> Not sure what the status is of the panda code in the u-boot git.
>> I see quite some patches from Steve (but no idea how much of them are
>> accepted/integrated by Wolfgang.
>
> Using the upstream v2010.09 tag should give you a reasonable u-boot.
>
> The exp in my my omap4-exp branch stands for "experimental", so it
> probably is not a good place to pull from unless you are willing to
> deal with frequent rebases and occasional breakage.
>
> Steve

I figured it would, but as that might have a more severe impact and I
have not pandaboard to test on, it was too much risk to make that
move.
Either someone else need to do this, or as an alternative we could
move to e.g. SRCREV 	b18815752f3d6db27877606e4e069e3f6cfe3a19 which is
a merge from Wolfgang from 4 days ago, which I expect not to
disappear.

Basically my concern was to create a buildable recipe (which I needed
in order to be able to verify whether my james-image build for panda)
(I'll push the james recipes soon, still maturing them)

Have fun! Frans




More information about the Openembedded-devel mailing list