[oe] bitbake virtual/kernel fails for davinci

[Denys Dmytriyenko]

On Tue, Jun 30, 2009 at 09:14:30PM +0200, Bj??rn Forsman wrote:
> 2009/6/30 Denys Dmytriyenko <denis at denix.org>:
> > Since then linux-davinci tree was updated to 2.6.30 final and more
> > specifically, staging/vpfe branch was rebased from v2 to v3 vpfe patches.
> > Unfortunately, rebase rewrites the history and changes commit numbers, hence
> > the old commit cannot be found any more...
> 
> Ok. Thanks for explaining.
> 
> > I'll update the recipe with the latest state of the linux-davinci tree. But,
> > it may brake in the future again, as this is a moving target. If you want
> > something, which does not break that often, I'd suggest you don't use the
> > "git" version of the recipe - try setting PREFFERED_PROVIDER/VERSION for
> > 2.6.28 or 2.6.29...
> 
> Ok. I'll try setting PREFERRED_PROVIDER/VERSION next thing tomorrow.

I guess I should also add 2.6.30 version of the recipe. Although I've seen 
Kevin updating/moving the "v2.6.30-davinci1" tag...

> BTW, the currently missing git object was specified as a SHA1 hash in
> a variable called SRCREV. Could this variable be used for specifying
> git objects in other formats? For example "staging/vpfe" or "HEAD"? Or
> is it unwise to have recipes which uses "floating" revisions?

The branch "staging/vpfe" is already specified in the SRC_URI. As of pointing 
to the HEAD, you can check the comments in the linux-davinci_2.6.27.bb, if it 
still works. But it is not recommended, as it would be hard to manage 
different builds and support the correct upgrade path. You can still do it 
locally, as long as you keep updating the MACHINE_KERNEL_PR in the 
conf/machine/include/davinci.inc

-- 
Denys