Re: yocto-bsp and kconf-check

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

On 13-08-29 5:39 PM, Jate Sujjavanich wrote:
> Some additional information: I noticed that the two CONFIG's are also defined in the fragment features/usb-net/usb-net.cfg. They are defined without using the non-hardware flag.
>

That's could be a contributing factor, if they have their bucket changed
by multiple fragments, the auditing gets harder.

I'll do a run with your BSP and let you know what I find.

Bruce

>
>> -----Original Message-----
>> From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]
>> Sent: Thursday, August 29, 2013 3:45 PM
>> To: Jate Sujjavanich
>> Cc: 'yocto@yoctoproject.org'
>> Subject: Re: [yocto] yocto-bsp and kconf-check
>>
>> On 13-08-29 02:56 PM, Jate Sujjavanich wrote:
>>>> Which kernel version ?
>>>
>>> This is linux-yocto-3.8 and the dylan-9.0.0 yocto.
>>>
>>>> It's not about them being common or not, it's about BSPs following a
>>>> base policy versus having wild, per-board behaviour.
>>>
>>> I've cleaned up many items from the yocto-bsp generated
>>> {{machine}}.cfg that are already added by KTYPE. I have two remaining
>>> warnings for CONFIG_NET and CONFIG_NETDEVICES. Nested includes
>>> eventually lead to the line
>>>
>>> force kconf non-hardware base.cfg
>>>
>>> which adds those config options. I thought the non-hardware would
>> prevent the specified_non_hdw.cfg warning.
>>
>> It should, unless there's a bug. Can you send me the steps to reproduce
>> the config ? i.e. just your generated BSP layer in a .tgz should be
>> enough.
>>
>> Bruce
>>
>>>
>>>
>>> Any ideas?
>>>
>>>> -----Original Message-----
>>>> From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]
>>>> Sent: Thursday, August 29, 2013 11:52 AM
>>>> To: Jate Sujjavanich
>>>> Cc: 'yocto@yoctoproject.org'
>>>> Subject: Re: [yocto] yocto-bsp and kconf-check
>>>>
>>>> On 13-08-29 11:36 AM, Jate Sujjavanich wrote:
>>>>> It appears that the yocto-bsp script generates a kernel
>>>>> configuration
>>>> that creates some warnings during kern-tools' kconf_check. The
>>>> {{machine}}.cfg file has many non-hardware options, therefore the
>>>> script warns.
>>>>>
>>>>> It seems like many of these should be in the standard kernel
>>>> configuration. Is this correct, and does the yocto-bsp data need to
>>>> be updated?
>>>>
>>>> Which kernel version ? But the answer is not necessarily, if a
>>>> machine config is specifying something that hasn't been tagged
>>>> "hardware" or that has a specified exception, you get a warning.
>>>>
>>>> It's not about them being common or not, it's about BSPs following a
>>>> base policy versus having wild, per-board behaviour.
>>>>
>>>> Cheers,
>>>>
>>>> Bruce
>>>>
>>>>>
>>>>> - Jate
>>>>> _______________________________________________
>>>>> yocto mailing list
>>>>> yocto@yoctoproject.org
>>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>>
>>>
>