[OE-core] [RFC PATCH 1/4] u-boot: basic support of device tree blob reassembly

Yannick GICQUEL yannick.gicquel at iot.bzh
Wed Apr 20 13:36:45 UTC 2016



Le 20/04/2016 10:37, Anders Darander a écrit :
> Just a comment on task ordering. Not sure that it really matters
> though...
>
> * Yannick GICQUEL <yannick.gicquel at iot.bzh> [160420 10:28]:
>> Le 19/04/2016 16:30, Andreas Oberritter a écrit :
>>> Hello Yannick,
>> Hi Andreas,
>>> On 19.04.2016 14:46, Yannick Gicquel wrote:
>>>> +addtask assemble_dtb after do_deploy before do_install
>>> The task do_deploy executes after do_install. Does it really work this
>>> way? I think bitbake should try to detect this and error out.
>> I confirm do_deploy is executed before do_install.
>> It looks like it is schedule this way by the last line of the file:
>> addtask deploy before do_build after do_compile
> Well, if task do_deploy is scheduled before do_install, that's just by
> luck.
>
> The following line adds do_install:
>
> addtask install after do_compile
>
> Thus, the ordering between do_install and do_deploy isn't fixed. It
> could be random, it could be based on alphabetical sorting, or the order
> the tasks are added. However, it could easily change...

Thanks for the precision.
I understand that ordering is not fixed as both tasks depends on do_compile.

I am on the way to send a v2 and the tasks are now sequenced as below :
    u-boot:do_deploy -> virtual/kernel:do_assemble_fitimage -> 
u-boot:do_install

Best regards,

>
> Cheers,
> Anders
>
>> (I attached the log.task_order for reference - FYI, behavior is the same on
>> jethro or today's master branch)




More information about the Openembedded-core mailing list