All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: Jate Sujjavanich <Jate.Sujjavanich@myfuelmaster.com>
Cc: "'yocto@yoctoproject.org'" <yocto@yoctoproject.org>
Subject: Re: yocto-bsp and kconf-check
Date: Thu, 29 Aug 2013 14:46:12 -0500	[thread overview]
Message-ID: <1377805572.1643.90.camel@empanada> (raw)
In-Reply-To: <6C2434209962DC46B88345CA85C334A201CAAD7035ED@Courier.syntech.org>

On Thu, 2013-08-29 at 11:36 -0400, 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?
> 

The templates in yocto-bsp are derived from the reference and qemu BSPs,
and have basically inherited the kernel config from those.

Now that the new kernel has landed, I've started updating the templates
for 3.10, and yes, if all the reference and qemu BSPs have been fixed in
this regard, I need to update the yocto-bsp templates with the new
options as well.

BTW, which arch did you use to generate your BSP?

Tom

> - Jate
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto




      parent reply	other threads:[~2013-08-29 19:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 15:36 yocto-bsp and kconf-check Jate Sujjavanich
2013-08-29 15:51 ` Bruce Ashfield
2013-08-29 18:56   ` Jate Sujjavanich
2013-08-29 19:45     ` Bruce Ashfield
2013-08-29 21:39       ` Jate Sujjavanich
2013-08-30  4:47         ` Bruce Ashfield
2013-08-29 19:46 ` Tom Zanussi [this message]

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=1377805572.1643.90.camel@empanada \
    --to=tom.zanussi@intel.com \
    --cc=Jate.Sujjavanich@myfuelmaster.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.