From: "Prabhu" <prabhusundar@gmail.com>
To: Andy Pont <andy.pont@sdcsystems.com>
Cc: Meta-Freescale <meta-freescale@lists.yoctoproject.org>
Subject: Re: [meta-freescale] OpenGL ES on i.MX8
Date: Mon, 14 Sep 2020 06:23:07 -0500 [thread overview]
Message-ID: <637b914a-bd6a-47c0-8365-14440fe7fb43@Prabhus-iPhone> (raw)
In-Reply-To: <emb9aa1e1a-0438-4781-b4e1-beb237546cc8@andys-imac.leeshillfarm.local>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
i.MX8 has GBM(DRM) support which is alternative for the lagacy framebuffer.
>
> On Sep 14, 2020 at 6:20 AM, <Andy Pont (mailto:andy.pont@sdcsystems.com)> wrote:
>
>
>
> Hello, This is probably a question for NXP themselves but I thought I would try the collective wisdom of the mailing list first. When I build images for the i.MX6 I can build the OpenGL ES support to use EGL and the Vivante driver to directly access the framebuffer without having to include all of the overhead of X11 or Weston/Wayland. Trying to find an equivalent configuration for the i.MX8m I am unable to find an equivalent method. The Vivante user space libraries don’t seem to exist in a framebuffer or DRM form, instead they all seem to require Wayland or X11. Can someone more knowledgeable than I confirm whether that is the case or whether I am missing something? -Andy.
>
>
[-- Attachment #2: Type: text/html, Size: 1202 bytes --]
next prev parent reply other threads:[~2020-09-14 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 11:20 OpenGL ES on i.MX8 Andy Pont
2020-09-14 11:23 ` Prabhu [this message]
[not found] ` <637b914a-bd6a-47c0-8365-14440fe7fb43@prabhus-iphone>
2020-09-14 11:33 ` [meta-freescale] " Andy Pont
2020-09-14 12:09 ` Prabhu
2020-09-14 20:56 ` Peter Bergin
2020-09-14 21:54 ` Joshua Watt
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=637b914a-bd6a-47c0-8365-14440fe7fb43@Prabhus-iPhone \
--to=prabhusundar@gmail.com \
--cc=andy.pont@sdcsystems.com \
--cc=meta-freescale@lists.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.