All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: Lauren Post <Lauren.Post@freescale.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: i.MX 3.10.31-1.1.0_beta release - community feedback requested
Date: Tue, 19 Aug 2014 17:00:23 -0300	[thread overview]
Message-ID: <CAP9ODKr+eOkAmfbd43gKSQkZ4LDTcZ664u1GQzyUJ2wCdM4vPA@mail.gmail.com> (raw)
In-Reply-To: <3310df336e324285a7539c861de00e93@DM2PR0301MB0701.namprd03.prod.outlook.com>

Hello folks,

On Tue, Aug 19, 2014 at 4:23 PM, Lauren Post <Lauren.Post@freescale.com> wrote:
...
> - Soon 3.10.17 and 3.10.31 graphics will be  independent from kernel and would be able to be mixed with each kernel  meaning you could use 3.10.31 kernel with v4 graphics (3.10.17)

This is a great step in the right direction. So this alleviate part of
the trouble we have across vendors. So is it going to be done for the
3.10.31 GA? or still for the Beta?

What about the VPU? Is 3.10.31 VPU packages compatible with 3.10.17?

> - Eric's point about upgraded proprietary packages is a good one in that our next chance to update them will only be the 3.10.31 GA release so bugs reported earlier help us get these fixed for GA.

Eric concern, in my understanding, is about the ABI between the binary
blobs and the compatibility against kernel releases.

What has changed? What is needed to backport?

> - There is a higher chance of getting bugs fixed NOW for GA then after GA. Please submit bugs via bugzilla and forward me so I can forward to the teams to investigate.

Please subscribe to the Bugzilla so I can assign the current issues to
your account. This easy tracking of reported issues.

> - Everything for 3.10.31-1.1.0_beta is public on our external git - http://git.freescale.com/ and you can  build using our release layer on top of daisy http://git.freescale.com/git/cgit.cgi/imx/fsl-arm-yocto-bsp.git/tree/README?h=imx-3.10.31-1.1.0_beta  Try it before making a final decision.   Our patches will not be upstreamed until after our field trial concludes this week.

So folks, one question remain open:

Considering we go with option 2, as seem most people prefer, what to
do regarding the non-updated boards in meta-fsl-arm-extra?

-- 
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-08-19 20:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b82299f1e1374ceea2a54dc92a7edc83@DM2PR0301MB0701.namprd03.prod.outlook.com>
     [not found] ` <8f1e8166115a4a4381ded78a5536c001@BY2PR03MB379.namprd03.prod.outlook.com>
2014-08-18 15:32   ` i.MX 3.10.31-1.1.0_beta release - community feedback requested Lauren Post
2014-08-18 15:54     ` Alfonso Tamés
2014-08-18 17:28       ` Eric Nelson
2014-08-18 19:35       ` Carlos Rafael Giani
2014-08-18 21:14         ` John Weber
2014-08-19  0:34         ` Alfonso Tamés
2014-08-19  2:32     ` Sébastien Taylor
2014-08-19  6:56       ` Carlos Rafael Giani
2014-08-19 13:59     ` Otavio Salvador
2014-08-19 15:55       ` Eric Nelson
2014-08-19 16:01         ` Carlos Rafael Giani
2014-08-19 16:22           ` Eric Nelson
2014-08-19 17:21             ` Otavio Salvador
2014-08-19 18:25               ` Eric Nelson
2014-08-19 17:24         ` Otavio Salvador
2014-08-19 18:44           ` Eric Nelson
2014-08-19 19:23             ` Lauren Post
2014-08-19 20:00               ` Otavio Salvador [this message]
2014-08-19 20:13                 ` Eric Bénard
2014-08-19 20:20                 ` John Weber
2014-08-20 13:31                   ` Daiane Angolini
2014-08-20 17:32                 ` Sébastien Taylor
2014-08-20 22:53     ` Alexander Holler
2014-08-20 23:04       ` Lauren Post
2014-08-20 23:29         ` Alexander Holler
2014-08-20 18:12 xxiao8
2014-08-20 19:41 ` Otavio Salvador
2014-08-20 23:11   ` xxiao8

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=CAP9ODKr+eOkAmfbd43gKSQkZ4LDTcZ664u1GQzyUJ2wCdM4vPA@mail.gmail.com \
    --to=otavio@ossystems.com.br \
    --cc=Lauren.Post@freescale.com \
    --cc=meta-freescale@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.