From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28
Date: Wed, 21 Oct 2015 09:29:42 +0200 [thread overview]
Message-ID: <56273EE6.90307@pseudoterminal.org> (raw)
In-Reply-To: <CAP9ODKqDbBrZWEah6q2tq0WGmErYU+fSfwSCTydW+PtEWhoggw@mail.gmail.com>
I applied the commits aeea3592a13bf12861943e44fc48f1f270941f8d
76ae03828756bac2c1fa2c7eff7485e5f815dbdb
3183696961eda6bef4e848d3ed0b4931de180b2c on the kernel, and it builds now.
However, GPU support is broken. It looks as if the boundary kernel is
incompatible with the newer Vivante firmware. Both G2D and OpenGL ES are
broken.
Am 2015-10-20 um 13:21 schrieb Otavio Salvador:
> On Mon, Oct 19, 2015 at 6:07 PM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> Hm, this doesn't fix it :(
> There are two problems; the patch I sent the link is to fix the kernel
> module build. However the Boundary's kernel are also lacking the
> patches to fix the build for GCC 5.2.
>
next prev parent reply other threads:[~2015-10-21 7:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 19:26 [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28 Carlos Rafael Giani
2015-10-19 19:46 ` Otavio Salvador
2015-10-19 20:07 ` Carlos Rafael Giani
2015-10-19 20:12 ` Gary Thomas
2015-10-19 20:33 ` Carlos Rafael Giani
2015-10-20 11:21 ` Otavio Salvador
2015-10-21 7:29 ` Carlos Rafael Giani [this message]
2015-10-21 7:30 ` Carlos Rafael Giani
2015-10-21 12:31 ` Otavio Salvador
2015-10-21 17:59 ` Carlos Rafael Giani
2015-10-21 18:01 ` Otavio Salvador
2015-10-21 18:02 ` Sundararaj Prabhu
2015-10-21 18:11 ` Carlos Rafael Giani
2015-10-21 18:21 ` Otavio Salvador
2015-10-21 18:25 ` Carlos Rafael Giani
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=56273EE6.90307@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio.salvador@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.