From: Eric Nelson <eric.nelson@boundarydevices.com>
To: "randy.krakora@freescale.com" <randy.krakora@freescale.com>,
Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: gpu-viv-bin-mx6q from 3.10.17 -> 3.5.7?
Date: Wed, 25 Jun 2014 08:50:23 -0700 [thread overview]
Message-ID: <53AAEFBF.20703@boundarydevices.com> (raw)
In-Reply-To: <56468D94-CD63-43A1-A776-E8DB09B3C808@freescale.com>
Hi Randy,
On 06/25/2014 07:44 AM, randy.krakora@freescale.com wrote:
> Yes, unfortunately Eric is right. :)
>
> I need to back port from 3.10.17 to 3.5.7, although I found out
> 3.0.35 has the patches that 3.10.17 does for this as well, so maybe starting
> from there would be better.
>
I suspect that pushing forward to 3.10.17 will be an easier move. Since
both are based on Device Tree, this should be relatively
straightforward.
Regards,
Eric
next prev parent reply other threads:[~2014-06-25 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 15:57 blacklist evbug or remove it from the kernel config Carlos Rafael Giani
2014-06-23 16:03 ` Daiane Angolini
2014-06-23 16:05 ` Carlos Rafael Giani
2014-06-23 16:08 ` Daiane Angolini
2014-06-23 19:32 ` gpu-viv-bin-mx6q from 3.10.17 -> 3.5.7? Ra37740@freescale.comndy
2014-06-24 1:25 ` Daiane.Angolini
2014-06-24 21:06 ` Otavio Salvador
2014-06-24 21:32 ` Eric Nelson
2014-06-25 14:41 ` Otavio Salvador
2014-06-25 14:44 ` randy.krakora
2014-06-25 14:47 ` Otavio Salvador
2014-06-25 15:50 ` Eric Nelson [this message]
2014-06-23 17:27 ` blacklist evbug or remove it from the kernel config Eric Nelson
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=53AAEFBF.20703@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
--cc=randy.krakora@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.