All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.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 23:21:03 +0100	[thread overview]
Message-ID: <20130228232103.33c6539f@e6520eb> (raw)
In-Reply-To: <70CC66F5C30A414DADDA6973E4CA391A893C38@039-SN1MPN1-001.039d.mgd.msft.net>

Le Thu, 28 Feb 2013 18:59:41 +0000,
McClintock Matthew-B29882 <B29882@freescale.com> a écrit :

> On Thu, Feb 28, 2013 at 11:18 AM, Eric Bénard <eric@eukrea.com> wrote:
> > Le Thu, 28 Feb 2013 16:52:02 +0000,
> > McClintock Matthew-B29882 <B29882@freescale.com> a écrit :
> >> I think you misinterpreted the intent of my statement, the goal is to
> >> provide the best support we can for the open source versions and get
> >> feedback as well. However, specifically stating what will be done for
> >> each release, branch, layer, etc is not something that is a
> >> deliverable on the open source end and I don't see it happening soon.
> >> That being said, there is no malicious intent and supporting upstream
> >> and making it work as well as possible is the ultimate goal so our SDK
> >> release requires less effort and work.
> >>
> > I may have misinterpreted your statement but it seems you make a
> > difference between the open source version and the SDK release : isn't
> > that roughly the same thing when we talk of meta-fsl-* where the SDK
> > release can be seen as a snapshots of the opensource stable branch at
> > the date of the release ? If not what are the differences ?
> 
> They *should* be the same. But for SDK releases sometimes we skip
> entire Yocto releases (e.g. danny). SDK versions *may* contain
> slightly different versions. This comes into play more with oe-core
> where we don't have official control and we need to include a specific
> fix for the SDK. Layers themselves tend to have less reason to deviate
> from the upstream versions since we control both sides so they
> *should* be the same.
> 
> > Also, do you plan to sync the public accessible git tree only when you
> > do a release or will they get the patches in "realtime" ?
> 
> These should go in real time esp. if we are working on the current
> release (e.g. master branch). Right now we are still using denzil
> until the May release which will be based on what is now master.
> 
understood, thanks for the details.

One last thing while at it : last year, Linaro's FSL team told me they
were about to release an updated kernel for i.MX53 (with updated GPU
closed source libraries & drivers as they had sources for that under
NDA - the userspace binaries are packed into an hwpack named something
like hwpack_linaro-lt-mx5_YYYYMMDD_armel_supported.tar.gz ).
In the end that was never made public but from what I understood they
delivered the sources to Freescale : are there any plan to release
these versions (even if that's not officialy supported by Freescale SDK
and marked as experimental) to meta-fsl-arm so that we can update i.MX53
based designs to more recent kernel than 2.6.35 and still use the GPU ?

Thanks,
Eric


  reply	other threads:[~2013-02-28 22:21 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
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 [this message]
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=20130228232103.33c6539f@e6520eb \
    --to=eric@eukrea.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.