From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Andrea Galbusera <gizero@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Suspicious warnings while beta testing yocto 1.2
Date: Fri, 30 Mar 2012 13:20:28 -0400 [thread overview]
Message-ID: <4F75EB5C.3020909@windriver.com> (raw)
In-Reply-To: <CAC+thW2bpSsoHOC2feOEowp1POB2zFG4eSDiiKs6xa7xP+qwDg@mail.gmail.com>
On 12-03-30 01:18 PM, Andrea Galbusera wrote:
> While beta testing yocto 1.2 I'm building for beagleboard with:
>
> OE Build Configuration:
> BB_VERSION = "1.15.1"
> TARGET_ARCH = "arm"
> TARGET_OS = "linux-gnueabi"
> MACHINE = "beagleboard"
> DISTRO = "poky"
> DISTRO_VERSION = "1.1+snapshot-20120330"
> TUNE_FEATURES = "armv7a vfp neon cortexa8"
> TARGET_FPU = "vfp-neon"
> meta
> meta-yocto = "<unknown>:<unknown>"
>
> I see warnings complaining that some options set by the BSP are not
> valid for the kernel being built. This is the first time I noticed and
> it's confusing me. After some search I find a past conversation where
> it was suggested that warnings like this for a Yocto maintained BSP
> should be considered bugs. Can anyone explain this? Build is
> completing successfully. Not yet tested the kernel on actual hardware.
> Later I will see if something similar also happens in edison not.
There are a few outstanding items for 1.2 as part of M4 .. one of
them is squashing the remaining configuration values that are
causing warnings.
Cheers,
Bruce
>
> Here is the log:
>
> This BSP sets 15 invalid/obsolete kernel options.
> These config options are not offered anywhere within this kernel.
> The full list can be found in your workspace at:
> /home/gizero/Documents/research/yocto-1.2-beta/yp-beta-build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.0.23+git1+e559129b4a6f39f68b75141096b2d516cf7a7f35_1+fccd4e4041454f16f1e7a25569ec530eaa1bf89e-r4/linux/meta/cfg/yocto/standard/beagleboard/invalid.cfg
>
> This BSP sets 50 kernel options that are possibly non-hardware related.
> The full list can be found in your workspace at:
> /home/gizero/Documents/research/yocto-1.2-beta/yp-beta-build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.0.23+git1+e559129b4a6f39f68b75141096b2d516cf7a7f35_1+fccd4e4041454f16f1e7a25569ec530eaa1bf89e-r4/linux/meta/cfg/yocto/standard/beagleboard/specified_non_hdw.cfg
>
> WARNING: There were 12 hardware options requested that do not
> have a corresponding value present in the final ".config" file.
> This probably means you aren't getting the config you wanted.
> The full list can be found in your workspace at:
> /home/gizero/Documents/research/yocto-1.2-beta/yp-beta-build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.0.23+git1+e559129b4a6f39f68b75141096b2d516cf7a7f35_1+fccd4e4041454f16f1e7a25569ec530eaa1bf89e-r4/linux/meta/cfg/yocto/standard/beagleboard/mismatch.cfg
>
> Waiting a second to make sure you get a chance to see this...
>
> If useful I can provide the list of options as per given log files.
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2012-03-30 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 17:18 Suspicious warnings while beta testing yocto 1.2 Andrea Galbusera
2012-03-30 17:20 ` Bruce Ashfield [this message]
2012-03-30 17:27 ` Bob Cochran
2012-03-30 17:30 ` Bruce Ashfield
2012-03-31 12:46 ` Andrea Galbusera
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=4F75EB5C.3020909@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=gizero@gmail.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.