Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Marc Reilly <marc@cpdesign.com.au>
To: Jan Kobler <eng1@koblersystems.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [pcm043 1/2] New machine pcm043 Phytec phyCORE-i.MX35
Date: Fri, 4 Mar 2011 22:09:44 +1100	[thread overview]
Message-ID: <201103042209.44904.marc@cpdesign.com.au> (raw)
In-Reply-To: <4D70B652.7010706@koblersystems.de>

Hi Jan,


> 1. I have not found a libgles-mx31 either.

Google doesn't say much about it. From memory (1 day ago :| ) the related 
posts were quite old, and it was mainly just wrapping up libs, headers and 
precompiled modules that freescale supplied..

> This seems to provide the binary openGL ES library for the i.MX31, like
> libgles-omap3 for the beagleboard. 

> 3. The i.MX35 has an embedded 2D and vector graphics accelerator
> targeting the OpenVG 1.1 graphics API and feature set. The libgles-mx31
> is for a different GPU. The i.MX35 doesn't need the libgles-mx31.
> 

I was hoping to look at the libgles recipe and do something similar with the 
OpenVG stuff..

> 
> 4. Are you trying to create an image, where libgles-mx31 is missing?

No, but video playback is quite slow, so I was looking for a cheap fix to 
speed it up :)


Cheers
Marc



  reply	other threads:[~2011-03-04 11:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-01 13:01 [pcm043 1/2] New machine pcm043 Phytec phyCORE-i.MX35 Jan Kobler
2011-03-01 13:01 ` [pcm043 2/2] linux-2.6.31 config and patch files for pcm043 Jan Kobler
2011-03-02 22:24 ` [pcm043 1/2] New machine pcm043 Phytec phyCORE-i.MX35 Marc Reilly
2011-03-04  9:52   ` Jan Kobler
2011-03-04 11:09     ` Marc Reilly [this message]
2011-03-04 12:44       ` Jan Kobler
2011-03-04 13:14         ` Eric Benard

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=201103042209.44904.marc@cpdesign.com.au \
    --to=marc@cpdesign.com.au \
    --cc=eng1@koblersystems.de \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox