All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
	 "zhenhua.luo@freescale.com" <zhenhua.luo@freescale.com>
Cc: "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	"White.Weng@freescale.com" <White.Weng@freescale.com>,
	Phil Brownfield <P.Brownfield@freescale.com>,
	Richard Schmitt <richard.schmitt@freescale.com>
Subject: Re: The Yocto layer re-architect for FSL QorIQ SDK
Date: Mon, 22 Sep 2014 09:43:58 -0400	[thread overview]
Message-ID: <5420279E.1090701@mindchasers.com> (raw)
In-Reply-To: <CAP9ODKpeL-+ZgC3B3q13LOjr0jH8bXBLXP4W2SGEHAH5TCdfbg@mail.gmail.com>

On 09/22/2014 08:51 AM, Otavio Salvador wrote:
>
>
> On Mon, Sep 22, 2014 at 7:20 AM, zhenhua.luo@freescale.com
> <mailto:zhenhua.luo@freescale.com> <zhenhua.luo@freescale.com
> <mailto:zhenhua.luo@freescale.com>> wrote:
>
>
>     __
>
>     Following is the structure of the meta-fsl-qoriq layer. __ __
>
>     meta-fsl-qoriq____
>
>     |--- common                   # the common recipes for QorIQ ARM and



[snip]


>     __ __
>
>     Can you please review? Your comments and suggestions are welcome.
>
>
> I think it is too soon to talk about any reorganization of the layers. I
> am still awaiting for the layers cleanup on the meta-fsl-ppc as several
> recipes there belong to other layers (meta-networking, meta-oe and so on).
>
> We also don't have the list of common recipes, so at this moment this is
> still a guess about the common recipes.
>
> LS1 is merged in fsl-arm so you can include it into FSL SDK in your git
> submodules/supergit/repo file.
>
> I see no benefit merging it, just cons ...


The benefit I see is that it logically groups all QorIQ parts together, 
which I believe is important.

When Freescale needs to provide support for LS2A (next generation) DPAA, 
the current organization will become a mess.  A lot (if not most) of the 
QorIQ BSP layer is for DPAA / networking, and I don't think it will make 
sense to have these duplicated in both meta-fsl-ppc and meta-fsl-arm, or 
have DPAA code that will be built for the ARM in meta-fsl-ppc (or vice 
versa).

I would hope that having this code organized in logical layers under the 
scope of QorIQ would make it more manageable in migrating from something 
like a TXXX device to an LS2A device.

However, I certainly understand you not wanting to change everything 
before there is stability in what we currently have.

I'm building with meta-fsl-ppc on a daily basis, but I'm not using 
anything else in the community tree (e.g., demos, meta-fsl-arm, repo, 
etc.) because my perception is it isn't ready for me as a QorIQ developer.

Zhenhua, when are you looking to make these changes?  Will this be a 
master-next sort of thing after the end of the year, or do you want to 
do all this now?


>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>
>



  reply	other threads:[~2014-09-22 13:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 10:20 The Yocto layer re-architect for FSL QorIQ SDK zhenhua.luo
2014-09-22 11:54 ` Daiane Angolini
2014-09-23  3:16   ` zhenhua.luo
2014-09-22 12:51 ` Otavio Salvador
2014-09-22 13:43   ` Bob Cochran [this message]
2014-09-22 14:14     ` Otavio Salvador
2014-09-22 14:32       ` Richard Schmitt
2014-09-23 18:32         ` Otavio Salvador
2014-10-01 21:42         ` Bob Cochran
2014-09-23  3:45     ` zhenhua.luo

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=5420279E.1090701@mindchasers.com \
    --to=yocto@mindchasers.com \
    --cc=P.Brownfield@freescale.com \
    --cc=White.Weng@freescale.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    --cc=richard.schmitt@freescale.com \
    --cc=zhenhua.luo@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 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.