From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: Vivante GPU on i.MX6solo
Date: Tue, 25 Mar 2014 05:03:21 -0600 [thread overview]
Message-ID: <53316279.3060608@mlbassoc.com> (raw)
In-Reply-To: <CAP9ODKo3O_LK1ueCrvvP=nixky=mPS6DEJmggwovDJAYODi4UQ@mail.gmail.com>
On 2014-03-24 20:07, Otavio Salvador wrote:
> Hello Gary,
>
> On Mon, Mar 24, 2014 at 12:13 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> I have a board which uses the i.MX6solo chip. This CPU (SOC) has
>> a different GPU than its cousins i.MX6Q and i.MX6dual. When I try
>> to run anything using the accelerated graphics, e.g. X server using
>> the Vivante libraries, it crashes hard.
>>
>> I know that my SOC has a Vivante GC880 whereas the i.MX6Q uses the
>> Vivante GC2000.
>>
>> Is there any way to get Vivante GPU support for my board/SOC?
>
> Well, it is lacking a lot of information so it is quite hard to guess.
> My guess is that you have an old BSP kernel and without the 4.6.9p13
> patches. When those things happen you see a segfault in Xorg
> initialization using the Vivante drivers.
This well could be - I use the linux-boundary recipe for 3.0.35+
(my board is nearly identical to a SabreLite from Boundary Devices)
I'm a bit confused by the '4.6.9p13' reference. Is that part of
a GPU recipe version? or a kernel version?
Can you point me to any discussion of this, or the kernel (which tree)
revision that made this change, etc?
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-03-25 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 15:13 Vivante GPU on i.MX6solo Gary Thomas
2014-03-25 2:07 ` Otavio Salvador
2014-03-25 11:03 ` Gary Thomas [this message]
2014-03-25 11:40 ` Otavio Salvador
2014-03-25 12:03 ` Gary Thomas
2014-03-25 12:08 ` Otavio Salvador
2014-03-26 10:19 ` Gary Thomas
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=53316279.3060608@mlbassoc.com \
--to=gary@mlbassoc.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.