From: Bob Cochran <yocto@mindchasers.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
"yocto@linux.freescale.net" <yocto@linux.freescale.net>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: Please review the proposal of FSL Yocto layers reorg
Date: Thu, 28 Feb 2013 09:32:54 -0500 [thread overview]
Message-ID: <512F6A96.8050102@mindchasers.com> (raw)
In-Reply-To: <70CC66F5C30A414DADDA6973E4CA391A893604@039-SN1MPN1-001.039d.mgd.msft.net>
On 02/27/2013 04:07 PM, McClintock Matthew-B29882 wrote:
> On Wed, Feb 27, 2013 at 3:03 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> On Wed, Feb 27, 2013 at 5:57 PM, McClintock Matthew-B29882
>> <B29882@freescale.com> wrote:
>>> On Wed, Feb 27, 2013 at 2:08 PM, Bob Cochran <yocto@mindchasers.com> wrote:
>>>>
>>>>>
>>>>> The FSL Yocto layers reorg proposal is attached, can you please take a
>>>>> look? Any comment and suggestion is welcome and appreciated.
>>>>>
>>>>
>>>> Thanks Zhenhua. I have a few questions and comments about your slides.
>>>>
>>>> *** Slide 2: "Move all FSL specific layers to totally open source, or as
>>>> much as possible"
>>>>
>>>> I'm all for this. Will this include your PowerPC Linux Tree? I didn't see
>>>> mention of this in your slides. This can be found today on your public git,
>>>> but it hasn't been updated in months.
>>>>
>>>> I assume there's lots of kernel activity (as can be witnessed on the
>>>> linuxppc-dev@lists.ozlabs.org list), so I'm assuming an internal Linux tree
>>>> is being patched often. It would be great to be able to see your Linux tree
>>>> patched as issues are being discussed & resolved on yocto & ozlabs mail
>>>> lists.
>>>
>>> We work on the upstream tree and also release an SDK kernel tree
>>> that's fully tested. The layers tend to use the latter since it
>>> supports all features. Nothing stopping users from adding a version
>>> using the upstream tree.
>>
>> And from now on, what are the plans?
>
> Same using SDK kernel release, I don't think the kernel team will ever
> have everything upstreamed for an SDK release and supporting all
> feature and bug fixes. Besides we will pick a kernel and test and fix
> it so it will always fall out of sync. (e.g. latest kernel release - 1
> release + fixes)
>
>>
>>>> **** Slide 3: "FSL Layers maintained in git.am.freescale.net,
>>>> gitfrescale.com, and git.yoctoproject.org"
>>>>
>>>> Is your goal to have these layers in sync? Today, I can find a meta-fsl-ppc
>>>> layer on yoctoproject and at git.freescale.com. However, they are not in
>>>> sync, and I have no idea why one is patched and one isn't.
>>>
>>> They are somewhat in sync.
That's today. What about next week or next month? As Zhenhua develops
the revised Yocto layer strategy, I ask that he clarifies the policy on
how the same named tree on different servers will be maintained.
The ones on git.freescale.com are still
>>> denzil based for the last SDK release. Ones on git.yoctoproject.org
>>> are newer and include danny and master branches as well.
>>
>> And what are the plans regarding the SDK?
Can we get a statement in the Yocto layers reorg doc on how each SDK
branch will be maintained between SDK releases? As a developer working
to get products out the door, will I view the patched SDK branch
(between releases) as a bug fixed SDK or as an experimental branch for
the next SDK release?
>
> These should be much closer to the same going forward (ideally
> anyways) if not identically esp. for the layers we control, however we
> can't always get all fixes in the oe-core/poky for an SDK release. But
> a lot of times we can get them into the branch for that release and
> eventually a point release.
>
> -M
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
next prev parent reply other threads:[~2013-02-28 14:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 8:15 Please review the proposal of FSL Yocto layers reorg Luo Zhenhua-B19537
2013-02-26 15:05 ` Otavio Salvador
2013-02-26 21:29 ` McClintock Matthew-B29882
2013-02-26 21:43 ` Otavio Salvador
2013-02-26 21:54 ` McClintock Matthew-B29882
2013-02-26 21:21 ` McClintock Matthew-B29882
2013-02-26 21:44 ` Otavio Salvador
2013-02-26 21:57 ` McClintock Matthew-B29882
2013-02-27 6:57 ` Luo Zhenhua-B19537
2013-02-27 12:09 ` Otavio Salvador
2013-02-28 6:16 ` Please review the proposal of FSL Yocto layers reorg - updated version on 28-Feb Luo Zhenhua-B19537
2013-02-28 12:10 ` Otavio Salvador
2013-02-28 19:17 ` McClintock Matthew-B29882
2013-02-28 19:20 ` Otavio Salvador
2013-02-28 19:37 ` McClintock Matthew-B29882
2013-02-28 19:54 ` Otavio Salvador
2013-03-01 3:34 ` Luo Zhenhua-B19537
2013-03-01 15:38 ` Wang Larry-B38019
2013-03-01 16:19 ` Matthew McClintock
2013-03-01 15:30 ` Please review the proposal of FSL Yocto layers reorg Wang Larry-B38019
2013-03-01 16:23 ` Matthew McClintock
2013-03-01 16:43 ` Otavio Salvador
2013-02-26 22:11 ` Fabio Estevam
2013-02-27 20:08 ` Bob Cochran
2013-02-27 20:57 ` McClintock Matthew-B29882
2013-02-27 21:03 ` Otavio Salvador
2013-02-27 21:07 ` McClintock Matthew-B29882
2013-02-28 14:32 ` Bob Cochran [this message]
2013-02-28 15:39 ` McClintock Matthew-B29882
2013-02-28 16:06 ` Eric Bénard
2013-02-28 16:52 ` McClintock Matthew-B29882
2013-02-28 17:18 ` Eric Bénard
2013-02-28 18:59 ` McClintock Matthew-B29882
2013-02-28 22:21 ` Eric Bénard
2013-02-28 22:25 ` McClintock Matthew-B29882
2013-02-28 23:30 ` Bob Cochran
2013-03-01 3:02 ` Luo Zhenhua-B19537
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=512F6A96.8050102@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=B29882@freescale.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
--cc=yocto@linux.freescale.net \
/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.