[yocto] linux-yocto: doesn't maintain patch order from SRC_URI?

[Bruce Ashfield]

On Tue, Nov 29, 2011 at 8:21 PM, Darren Hart <darren.hart at intel.com> wrote:
> On 11/29/2011 05:15 PM, Darren Hart wrote:
>> On 11/29/2011 04:41 PM, Darren Hart wrote:
>>>
>>>
>>> On 11/29/2011 03:14 PM, Bruce Ashfield wrote:
>>>> On 11-11-29 04:39 PM, Darren Hart wrote:
>>>>> I'm experimenting with Matt Fleming's EFI_STUB patches. The first 10 patches were working fine, but when I try to add the 11th, the do_patch fails. I found that it isn't trying to apply the patches in the order listed in the recipe - no in any other recognizable pattern for that matter.
>>>>>
>>>>
>>>> It's shell order. You really should just create a .scc file, put IT
>>>> on the SRC_URI and list the patches. You'll have no problems after
>>>> that.
>>>>
>>>> I do have a fix for this, but can't send it right now due to travel.
>>>>
>>>> You are using the compatibility mode for more than I originally intended
>>>> it for. So just dropping a .scc file into place will fix things
>>>> up nicely.
>>>
>>> OK, I like that better than the monolith patch I plugged the leak with :-)
>>
>> So I'm trying this:
>>
>> $ cat linux-yocto-dvhart/efi-stub.scc
>> patch 0001-x86-Add-missing-bzImage-fields-to-struct-setup_heade.patch
>> patch 0002-x86-efi-Make-efi_call_phys_prelog-CONFIG_RELOCATABLE.patch
>> patch 0003-x86-Don-t-use-magic-strings-for-EFI-loader-signature.patch
>> patch 0004-efi.h-Add-struct-definition-for-boot-time-services.patch
>> patch 0005-efi.h-Add-efi_image_loaded_t.patch
>> patch 0006-efi.h-Add-allocation-types-for-boottime-allocate_pag.patch
>> patch 0007-efi.h-Add-graphics-protocol-guids.patch
>> patch 0008-efi.h-Add-boottime-locate_handle-search-types.patch
>> patch 0009-efi-Add-EFI-file-I-O-data-types.patch
>> patch 0010-x86-efi-EFI-boot-stub-support.patch
>> patch 0011-x86-efi-Break-up-large-initrd-reads.patch
>>
>> And in the recipe:
>> SRC_URI += "file://efi-stub.scc"
>>
>> In the meta-series I see:
>>
>> # _mark efi_stub_947530aea4d2a819b340fe2b49d765de start
>> # _mark efi_stub_947530aea4d2a819b340fe2b49d765de end
>>
>> But the patches do not get applied.
>>
>> The Yocto Kernel Architecture and Use Manual does not appear to cover
>> this case. Do I need to do something more?
>
> Ah, I need to include the patches explicitly too. That makes sense from
> a bitbake perspective. OK, I'm rolling again, nice.

Glad to hear you got to this, after I sent that email and headed for some sleep,
I realized that I forgot to point out that detail.

Cheers

Bruce

>
> --
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Linux Kernel
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



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