From: Eric Nelson <eric.nelson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt5 and gpu-viv-bin-mx6q problem
Date: Thu, 27 Feb 2014 17:11:00 -0700 [thread overview]
Message-ID: <530FD414.10003@boundarydevices.com> (raw)
In-Reply-To: <CACP2RPYKf_dVKkiHVsqM4vA-Ox69h0C_Nvt33Q-e5uGP6xDorA@mail.gmail.com>
Hi Massimiliano,
On 02/27/2014 02:40 PM, Massimiliano Marretta wrote:
> Can I use the gpu-viv-bin-mx6q-3.5.7-1.0.0-hfp.bin with the kernel
> version 3.0.35 ?
>
Unfortunately, saying "3.0.35" isn't specific enough. The first
few releases (what Freescale referred to as 1.0.0, 1.1.0, and 4.0.0)
won't support the badly-named 3.5.7-1.0.0 GPU binaries.
For that, you need the updates that came with the 3.0.35_4.1.0
release.
Clear, huh?
If you have a commit id in your source tree for the last Freescale
update we (or you) can likely pin-point it with "git branch --contains".
If you started with one of the older branches, it's likely that
your patches will forward-port pretty easily. None of the 3.0.35
releases from Freescale had any major re-structuring.
Regards,
Eric
next prev parent reply other threads:[~2014-02-28 0:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 21:40 [Buildroot] Qt5 and gpu-viv-bin-mx6q problem Massimiliano Marretta
2014-02-28 0:11 ` Eric Nelson [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-28 9:12 Massimiliano Marretta
2014-02-27 8:22 Massimiliano Marretta
2014-02-27 20:16 ` Arnout Vandecappelle
2014-02-27 20:42 ` Eric Nelson
2014-02-27 20:43 ` Arnout Vandecappelle
2014-02-27 23:50 ` 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=530FD414.10003@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox