Re: Custom kernel in Yocto/dylan branch.

[Bruce Ashfield <bruce.ashfield@windriver.com>]

On 13-06-12 08:37 AM, Javi Roman wrote:
> Hi!
>
> Thank you for your help.
>
> Finally I've had to change the meta/classes/kernel.bbclass in order to
> fix the copy of defconfig to .config:
>
> -  if [ -f "${WORKDIR}/defconfig" ] && [ ! -f "${B}/.config" ]; then
> + if [ -f "${WORKDIR}/defconfig" ]; then
>                  cp "${WORKDIR}/defconfig" "${B}/.config"
> fi
>

Right. That check is what prevents the fallback defconfig processing
from clobbering the .config which is generated by a linux-yocto* based
kernel configuration task (which gives you defconfig + fragments).

The point is that in the linux-yocto "configme" task essentially the
same thing that happens. The defconfig is fed into the configuration
as the baseline config, applied after a "allnoconfig" and then has
any fragments layered on top.

Which again leads me to my question about what exactly you were
seeing before that change in the linux build directory as the .config ?

Cheers,

Bruce

> I don't know the exact problem, and I'm trying to find out it.
>
> Cheers.
>
> Javi Roman
>
>
> On Tue, Jun 11, 2013 at 5:34 PM, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
>> On Tuesday 11 June 2013 16:47:53 Javi Roman wrote:
>>> With
>>>
>>> SRC_URI_append = "file://defconfig"
>>
>> Does your actual recipe have a leading space in the value? _append won't add
>> this for you so you have to do it explicitly.
>>
>> Cheers,
>> Paul
>>
>> --
>>
>> Paul Eggleton
>> Intel Open Source Technology Centre