All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sébastien Taylor" <me@staylor.ca>
To: Otavio Salvador <otavio@ossystems.com.br>
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: Wed, 20 Aug 2014 11:32:27 -0600	[thread overview]
Message-ID: <03FB412A-820F-4142-9EFD-94A81C19C780@staylor.ca> (raw)
In-Reply-To: <CAP9ODKr+eOkAmfbd43gKSQkZ4LDTcZ664u1GQzyUJ2wCdM4vPA@mail.gmail.com>


On Aug 19, 2014, at 2:00 PM, Otavio Salvador <otavio@ossystems.com.br> wrote:

> 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?
> 

To me this is the biggest push for 3.10.31.  GPU driver/library updates are few and far between, and are badly needed.  Keeping the two separate would make it easier to pull in GPU updates without having to do the full kernel updates.

As a bonus, RELEASE NOTES for GPU driver/library updates would be greatly appreciated.




  parent reply	other threads:[~2014-08-20 17:32 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
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 [this message]
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=03FB412A-820F-4142-9EFD-94A81C19C780@staylor.ca \
    --to=me@staylor.ca \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.