From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: BSP kernel configuration redefines config options
Date: Mon, 30 Apr 2012 10:23:35 -0400 [thread overview]
Message-ID: <4F9EA067.5030806@windriver.com> (raw)
In-Reply-To: <82CCA538-B495-44B3-8E06-F13282FAC541@keylevel.com>
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
next prev parent reply other threads:[~2012-04-30 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 14:20 BSP kernel configuration redefines config options Chris Tapp
2012-04-30 14:23 ` Bruce Ashfield [this message]
2012-04-30 20:16 ` Chris Tapp
2012-05-01 0:16 ` Bruce Ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F9EA067.5030806@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=opensource@keylevel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.