linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Bob Cochran <ppc@mindchasers.com>
Cc: Pan Lijun-B44306 <Lijun.Pan@freescale.com>,
	Schmitt Richard-B43082 <richard.schmitt@freescale.com>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: new way of writing defconfigs for freescale's powerpc platforms
Date: Thu, 16 Apr 2015 13:39:15 -0500	[thread overview]
Message-ID: <1429209555.32545.14.camel@freescale.com> (raw)
In-Reply-To: <552F3E37.7030507@mindchasers.com>

On Thu, 2015-04-16 at 00:44 -0400, Bob Cochran wrote:
> As you probably know, Freescale makes use of the Yocto Project build 
> system for its SDK and submits patches to the SDK at a public 
> meta-fsl-ppc repo at http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/
> 
> I have seen some kernel related patches in the past come across the 
> Yocto Project site that made use of the Yocto Project kernel tools, 
> which includes a process for maintaining kernel configuration fragments. 
>   It sounds like the requirements you have could be met with Yocto's 
> existing process.
> 
> I was hoping to see Freescale continue to move in the direction of using 
> the Yocto kernel tools rather than roll its own solution.
> 
> The Yocto kernel tools make use of description files (*.scc) and 
> configuration fragments (*.cfg).

We do use Yocto for our SDK, but there's always going to be a need to be
able to build kernels outside of Yocto.  The kernel should be
self-contained regarding its own configuration.

merge_config.sh isn't "rolling our own solution". It's a standard kernel
tool.  x86 already has a couple config fragments defined.

-Scott

  parent reply	other threads:[~2015-04-16 18:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 21:52 new way of writing defconfigs for freescale's powerpc platforms Lijun Pan
2015-04-09 22:31 ` Scott Wood
2015-04-16  4:44   ` Bob Cochran
2015-04-16 13:20     ` Bob Cochran
2015-04-16 13:37       ` Richard Schmitt
2015-04-16 18:39     ` Scott Wood [this message]
2015-04-16 17:04   ` Lijun Pan
2015-04-17  0:54 ` Michael Ellerman
2015-04-17  4:13   ` Scott Wood
2015-04-17  6:18     ` Michael Ellerman
2015-04-17 18:50       ` Lijun Pan
2015-04-17 18:52         ` Scott Wood
2015-04-18  4:53           ` Lijun Pan
2015-04-18 13:46             ` Timur Tabi
2015-04-20 20:31               ` Scott Wood
2015-04-21  2:02                 ` Timur Tabi
2015-04-21  2:09                   ` Scott Wood
2015-04-21  3:42                     ` Timur Tabi
2015-04-21  5:01                       ` Scott Wood
2015-04-21 13:25                         ` Timur Tabi
2015-04-21 17:55                           ` Scott Wood
2015-04-21 18:11                             ` Timur Tabi
2015-04-21 18:12                               ` Scott Wood
2015-04-21  3:27                   ` Michael Ellerman

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=1429209555.32545.14.camel@freescale.com \
    --to=scottwood@freescale.com \
    --cc=Lijun.Pan@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ppc@mindchasers.com \
    --cc=richard.schmitt@freescale.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).