[OE-core] [PATCH 2/2] kernel-fitimage.bbclass: Introduce a way to provide external dtb

[akuster808]

On 4/3/19 10:35 AM, Philip Balister wrote:
> I appreciate the nagging about testing, but I just did an update and
> realized these patches never made it into master so I could request they
> move into thud.
Thud needs testing too, its not just a master thing.

It needs to be in warrior first ; )

Either send me the master/warrior commit ids or send a patch with the
proper subject so its clear to me. 
But this looks like a new feature or am I misunderstanding?

- armin
>
> Philip
>
> On 02/21/2019 03:37 AM, Richard Purdie wrote:
>> On Thu, 2019-02-21 at 03:53 +0000, Manjukumar Harthikote Matha wrote:
>>> From: Richard Purdie [mailto:richard.purdie at linuxfoundation.org]
>>>> On Tue, 2019-02-19 at 19:34 +0000, Manjukumar Harthikote Matha
>>>>
>>>>>> PREFERRED_PROVIDER_virtual/dtb = "devicetree"
>>>>>>
>>>>> Yes, I should have added this in the commit message. I will
>>>>> update it
>>>>> and re-send V2
>>>> What may also help a lot here would be some tests. This is
>>>> currently a blackhole in
>>>> the tests :(
>>>>
>>> Are there examples of having tests only for bbclass in OE-Core? 
>> There are. See meta/lib/oeqa/selftest/cases/wic.py
>>
>> I appreciate wic is a tool, not a class but the examples there should
>> help. You can trigger them with oe-selftest -r wic.
>>
>> Another example which is a bbclass is selftest/cases/archiver.py which
>> does use a class inherit.
>>
>>> We need a recipe or create-one to inherit this class and probably add
>>> that as a testcase. 
>>> I am not sure how to proceed, any example would help to implement the
>>> same
>> See above, they show how to add small config fragments. If you do need
>> a full recipe, then the meta-selftest layer of OE-Core should be able
>> to help too.
>>
>> If you have any other questions or run into issues please do ask!
>>
>> Cheers,
>>
>> Richard
>>
>>
>>
>>