From: "Joshua Watt" <JPEWhacker@gmail.com>
To: peter@berginkonsult.se
Cc: Andy Pont <andy.pont@sdcsystems.com>,
meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] OpenGL ES on i.MX8
Date: Mon, 14 Sep 2020 16:54:13 -0500 [thread overview]
Message-ID: <CAJdd5GZqhqNSL5Z-cpSUkXa5vsKSyjUvPndk83fYt1RfY4B7Cg@mail.gmail.com> (raw)
In-Reply-To: <7f60663d-ceef-82cd-bfd3-6f5eaa23548f@berginkonsult.se>
On Mon, Sep 14, 2020 at 3:56 PM Peter Bergin <peter@berginkonsult.se> wrote:
>
> Hi Andy,
>
> On 2020-09-14 13:20, Andy Pont wrote:
> > 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.
>
> this is the statement from NXP
> (https://source.codeaurora.org/external/imx/imx-manifest/tree/README?h=imx-linux-zeus#n53).
> As seen they do not actively support the framebuffer distro for i.Mx8
> targets on their official BSP.
>
> The recipe for vivante user space lib imx-gpu-viv also have a guard for
> mx8 that only builds it when wayland is enabled.
> (https://github.com/Freescale/meta-freescale/blob/e0fa0255795ce584b3b5ad74c330cabeb0caa28d/recipes-graphics/imx-gpu-viv/imx-gpu-viv-6.inc#L60).
>
> I'm also interested in the same question as you are as I'm in a start up
> phase for a i.Mx8 project where we would like to run with OpenGL or
> Vulkan directly against DRM and avoid display manager. Would be great to
> hear someone from NXP give their picture of this. I have tried the NXP
> community but without any info so far.
> (https://community.nxp.com/t5/i-MX-Graphics/vulkan-without-display-server-Wayland-X11/m-p/1134083#M1)
FWIW, standing up a GLES/DRM/KMS application isn't terribly hard. I've
done it on an IMX8 before without too much trouble. kmscube is
probably the best place to start as it is a pretty complete example.
However, I would also highly recommend looking at running your
application under the weston (wayland) fullscreen shell. It's just as
powerful except you don't have to deal with all the twiddly DRM/KMS
APIs, and the "overhead" is pretty much non-existent because you
render directly to a DMA buf which weston presents to the display.
>
> Best regards,
> /Peter
>
>
prev parent reply other threads:[~2020-09-14 21:54 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 ` [meta-freescale] " Prabhu
[not found] ` <637b914a-bd6a-47c0-8365-14440fe7fb43@prabhus-iphone>
2020-09-14 11:33 ` Andy Pont
2020-09-14 12:09 ` Prabhu
2020-09-14 20:56 ` Peter Bergin
2020-09-14 21:54 ` Joshua Watt [this message]
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=CAJdd5GZqhqNSL5Z-cpSUkXa5vsKSyjUvPndk83fYt1RfY4B7Cg@mail.gmail.com \
--to=jpewhacker@gmail.com \
--cc=andy.pont@sdcsystems.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=peter@berginkonsult.se \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).