[poky] Using linux-yocto_3.10 with dylan

[Bruce Ashfield]

On Wed, Oct 23, 2013 at 6:40 PM, Colin Walters <walters at verbum.org> wrote:
> Hi, I have a system derived from Poky Dylan, it is currently using
> linux-yocto-dev.bb.  Things were working fine up until recently when
> that branch was rebased to 3.12, and the new linux-yocto-3.10 git repo
> was made.  I had actually been unaware up until then that I was tracking
> a git branch instead of a fixed revision.
>
> Anyways, I'm trying now to continue using 3.10 with Dylan, but I'll be
> honest - the way the linux-yocto kernel has the configuation built and
> patches are applied is convoluted enough I'm having a lot of trouble
> figuring out what's going wrong.  The error looks like this in do_patch:
>
> DEBUG: Executing shell function do_patch
> Deleted branch meta-temp (was f58e62b).
> [INFO] validating against known patches  (qemux86-64-standard-meta)
>
> ... snip progress bar ...
>
> error: patch failed: arch/arm/mm/fault.c:448
> error: arch/arm/mm/fault.c: patch does not apply
> To force apply this patch, use 'guilt push -f'
> [ERROR] unable to complete push
> pending patches are:
> links/kernel-cache/arch/arm/v7-A15/ARM-LPAE-Invalidate-the-TLB-for-module-addresses-dur.patch
> links/kernel-cache/arch/arm/arm-ARM-EABI-socketcall.patch
> links/kernel-cache/arch/mips/malta-uhci-quirks-make-allowance-for-slow-4k-e-c.patch
> links/kernel-cache/arch/mips/4kc-cache-tlb-hazard-tlbp-cache-coherency.patch
> ... continued
>
> I've verified I can take current oe-core git master, change the kernel
> to 3.10, and it builds OK.   The main variation is I have a small set of
> config additions, but I don't know why this would result in the set of
> patches changing.  Is there an way I can see which patches are being
> applied and why?
>
> At the moment I'm trying to isolate what configuration change is causing
> this, but hopefully someone here will have a useful hint.  Thanks!

It's the kernel tools. You need to bring back the matched tools -> the new 3.10
kernel tree, since they no longer use guilt to manage patches on branches, but
instead use pure git. The guilt tools can't detect that the patches are in fact
already applied to the tree, and try to push changes again, which lead to your
error.

Bruce

>
>
> _______________________________________________
> poky mailing list
> poky at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"