On 30 Apr 2012, at 15:23, Bruce Ashfield wrote:
> On 12-04-30 10:20 AM, Chris Tapp wrote:
>> I've got a BSP that has the following kernel configuration
>> linux-yocto_3.0.bbappend:
>>
>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>>
>> COMPATIBLE_MACHINE_mybsp = "mybsp"
>> KMACHINE_mybsp = "yocto/standard/common-pc/base"
>>
>> SRC_URI += " file://defconfig"
>>
>> SRCREV_machine_pn-linux-yocto_mybsp ?=
>> "d7e81e7f975c57c581ce13446adf023f95d9fd9f"
>> SRCREV_meta_pn-linux-yocto_mybsp ?=
>> "d386e09f316e03061c088d2b13a48605c20fb3a6"
>>
>> This builds ok, but I get a note that says "There were 43 kernel config
>> options redefined during processing this BSP". I assume this is because the
>> defconfig file is at odds with the kernel I've selected as the base for the
>> BSP. Is it possible to get this note to 'go away' ?
>
> Yes, that's exactly what would be triggering it. It's currently
> not controlled via a flag, since it is technically a value add :)
Yes, I suspected a 'conflict of interest' here ;-)
> But to make it go away, I'd just suggest overriding do_kernel_configcheck()
> in your layer.
Is that all that happens in here, or would I be losing something I may want to
know about as well?
> Cheers,
>
> Bruce
>
>>
>> I'm running under 6.0.1 and haven't spotted anything in the user manuals
>> that I think would help.
>>
>> Chris Tapp
>>
>> [email protected]
>> www.keylevel.com
>>
>>
>>
>> _______________________________________________
>> yocto mailing list
>> [email protected]
>> https://lists.yoctoproject.org/listinfo/yocto
>
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
