From: Jan Kobler <eng1@koblersystems.de>
To: Marc Reilly <marc@cpdesign.com.au>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [pcm043 1/2] New machine pcm043 Phytec phyCORE-i.MX35
Date: Fri, 04 Mar 2011 10:52:18 +0100 [thread overview]
Message-ID: <4D70B652.7010706@koblersystems.de> (raw)
In-Reply-To: <201103030924.09980.marc@cpdesign.com.au>
Hi Marc,
1. I have not found a libgles-mx31 either.
This seems to provide the binary openGL ES library for the i.MX31, like
libgles-omap3 for the beagleboard.
I have derived the BSP for the pcm043 from the BSP of mx31ads and I
copied these definitions too. This seems to be also a problem of mx31ads.
The i.MX31 has a MBX R-S 3D Graphics Core.
2. Before I have released the patch, I have built with bitbake the
minimal-image, opie-image, x11-gpe-image and the xfce46-image for the
pcm043 machine and tested it on the board for a short time.
It is described here:
http://en.gentoo-wiki.com/wiki/Phytec_phyCORE-iMX35/Openembedded
All these images don't use the libgles-mx31. Only when I try to build
the illume-image, bitbake reports a missing libgles-mx31.
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 have already tried a new patch, where libgles-mx31 is not used, but I
could not build illume-image successfully. It got stuck somewhere else.
I would like to be able to prove that a patch is working on my board,
before I release it.
4. Are you trying to create an image, where libgles-mx31 is missing?
Best regards
Jan
next prev parent reply other threads:[~2011-03-04 10:33 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 [this message]
2011-03-04 11:09 ` Marc Reilly
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=4D70B652.7010706@koblersystems.de \
--to=eng1@koblersystems.de \
--cc=marc@cpdesign.com.au \
--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 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.