* BSP kernel configuration redefines config options
@ 2012-04-30 14:20 Chris Tapp
2012-04-30 14:23 ` Bruce Ashfield
0 siblings, 1 reply; 4+ messages in thread
From: Chris Tapp @ 2012-04-30 14:20 UTC (permalink / raw)
To: Yocto Project
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' ?
I'm running under 6.0.1 and haven't spotted anything in the user manuals that I think would help.
Chris Tapp
opensource@keylevel.com
www.keylevel.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: BSP kernel configuration redefines config options
2012-04-30 14:20 BSP kernel configuration redefines config options Chris Tapp
@ 2012-04-30 14:23 ` Bruce Ashfield
2012-04-30 20:16 ` Chris Tapp
0 siblings, 1 reply; 4+ messages in thread
From: Bruce Ashfield @ 2012-04-30 14:23 UTC (permalink / raw)
To: Chris Tapp; +Cc: Yocto Project
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 :)
But to make it go away, I'd just suggest overriding do_kernel_configcheck()
in your layer.
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
>
> opensource@keylevel.com
> www.keylevel.com
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: BSP kernel configuration redefines config options
2012-04-30 14:23 ` Bruce Ashfield
@ 2012-04-30 20:16 ` Chris Tapp
2012-05-01 0:16 ` Bruce Ashfield
0 siblings, 1 reply; 4+ messages in thread
From: Chris Tapp @ 2012-04-30 20:16 UTC (permalink / raw)
To: Yocto Project
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
>>
>> opensource@keylevel.com
>> www.keylevel.com
>>
>>
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: BSP kernel configuration redefines config options
2012-04-30 20:16 ` Chris Tapp
@ 2012-05-01 0:16 ` Bruce Ashfield
0 siblings, 0 replies; 4+ messages in thread
From: Bruce Ashfield @ 2012-05-01 0:16 UTC (permalink / raw)
To: Chris Tapp; +Cc: Yocto Project
On Mon, Apr 30, 2012 at 4:16 PM, Chris Tapp <opensource@keylevel.com> wrote:
> 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?
It tells you about overrides, invalid, duplicate, redefined, hardware
and non-hardware options.
But it's all 'configure validation and reporting'. So if you don't
want that, just clobber the routine.
Cheers,
Bruce
>
>> 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
>>>
>>> opensource@keylevel.com
>>> www.keylevel.com
>>>
>>>
>>>
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-05-01 0:16 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-04-30 14:20 BSP kernel configuration redefines config options Chris Tapp
2012-04-30 14:23 ` Bruce Ashfield
2012-04-30 20:16 ` Chris Tapp
2012-05-01 0:16 ` Bruce Ashfield
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.