* Re: omap5: 3d graphics hardware acceleration build
2013-09-24 6:27 ` Leonid Iziumtsev
@ 2013-09-24 8:22 ` Leonid Iziumtsev
0 siblings, 0 replies; 4+ messages in thread
From: Leonid Iziumtsev @ 2013-09-24 8:22 UTC (permalink / raw)
To: Denys Dmytriyenko; +Cc: meta-ti
[-- Attachment #1.1: Type: text/plain, Size: 3368 bytes --]
Denys, all,
I also found that TI provide OMAP5 GLSDK and according to this guide -
http://processors.wiki.ti.com/index.php/OMAP5_GLSDK_Software_Developers_Guide
I should be able to build "arago-glsdk-multimedia-image" target that I
believe contain all support for SGX and Ducati *(please correct me if I'm
wrong).
*
Unfortunately I could not find GLSDK6.02. The latest version that is
available here -
http://software-dl.ti.com/dsps/dsps_public_sw/glsdk/latest/index_FDS.htmlis
6.01
*(please give me the link to 6.02 if you know where to get it)*.
I followed procedure (described in GLSDK guide ) using GLSDK6.01 but get
such error:
*ERROR: Nothing PROVIDES 'arago-glsdk-multimedia-image'*
Looking into "yocto-layers"directory (root folder for git://
arago-project.org/git/projects/oe-layersetup) I couldn't find recipe for
this target. *Can you please suggest what is the problem? Could it be
related to old GLSDK6.01 that I'm using?*
Also "arago-glsdk-multimedia-image" wasn't present in list of available
targets. That only targets that I got are :
core-image-minimal
core-image-sato
meta-toolchain
meta-toolchain-sdk
adt-installer
meta-ide-support
The output of "oe-layertool-setup.sh" script looks a bit strange to me
(please find full log in attachment).
I complain to such lines:
Fetching arago
fatal: git checkout: updating paths is incompatible with switching branches.
Did you intend to checkout 'origin/danny' which can not be resolved as
commit?
fatal: 'origin/danny' does not point to a commit
Note: checking out 'af9632689392ea03fd14879ca33b3c6c6ed2e347'.
not sure if it is right behaviour.
Thank you again for helping me. Looking forward for you reply!
Regards,
Leonid
On Tue, Sep 24, 2013 at 9:27 AM, Leonid Iziumtsev <
leonid.iziumtsev@globallogic.com> wrote:
> Hi Denys,
>
> Thank you for fast reply and clarification!
>
>
> On Mon, Sep 23, 2013 at 4:23 PM, Denys Dmytriyenko <denys@ti.com> wrote:
>
>> On Mon, Sep 23, 2013 at 01:15:11PM +0300, Leonid Iziumtsev wrote:
>> > Hi all,
>> >
>> > Pardon me if this list is not the right place to ask the questions and
>> if
>> > so, please poing me to the right one.
>> >
>> > I'm developer in Panasonic Inc. Currently working with OAMP5 (pandaboard
>> > uevm) I'm trying to get build with 3D graphics hardware acceleration
>> using
>> > DirectFB (no X support recurred). In future hopefully going run some Qt
>> > based UI.
>> > In search I came across "meta-ti" layer.
>> >
>> > I'm new in yocto based build system so don't
>> > completely understand: is it what I was looking for? Will it allow me to
>> > get build with proper graphic support?
>>
>> Leonid,
>>
>> Yes, this is the correct layer for OMAP5 uEVM support. But 3D Graphics is
>> not
>> yet available - there were some patches being developed, but they haven't
>> been
>> finalized yet.
>>
>> --
>> Denys
>>
>
>
>
> --
>
> Name | Title
> GlobalLogic
> P +x.xxx.xxx.xxxx M +x.xxx.xxx.xxxx S skype
> www.globallogic.com
> <http://www.globallogic.com/>
> http://www.globallogic.com/email_disclaimer.txt
>
--
Name | Title
GlobalLogic
P +x.xxx.xxx.xxxx M +x.xxx.xxx.xxxx S skype
www.globallogic.com
<http://www.globallogic.com/>
http://www.globallogic.com/email_disclaimer.txt
[-- Attachment #1.2: Type: text/html, Size: 8268 bytes --]
[-- Attachment #2: oe-layertool-setup.output --]
[-- Type: application/octet-stream, Size: 6484 bytes --]
liziumtsev@kbp1-dhp-f24222:~/ti-glsdk_omap5-uevm_6_01_00_01/yocto-layers$ ./oe-layertool-setup.sh -f configs/glsdk/glsdk-06.01.00-config.txt
/home/liziumtsev/ti-glsdk_omap5-uevm_6_01_00_01/yocto-layers
cloning repo bitbake
Fetching oe
fatal: git checkout: updating paths is incompatible with switching branches.
Did you intend to checkout 'origin/master' which can not be resolved as commit?
fatal: 'origin/master' does not point to a commit
Note: checking out '1.17.0'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at cc7fdbd... Update version to 1.17.0
cloning repo meta-arago
Fetching arago
fatal: git checkout: updating paths is incompatible with switching branches.
Did you intend to checkout 'origin/master' which can not be resolved as commit?
fatal: 'origin/master' does not point to a commit
Note: checking out 'd08f424bd078d9a0c88a94ac92f859c8efaf06d4'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at d08f424... images: Add new arago-glsdk-console-image
cloning repo meta-openembedded
Fetching oe
fatal: git checkout: updating paths is incompatible with switching branches.
Did you intend to checkout 'origin/danny' which can not be resolved as commit?
fatal: 'origin/danny' does not point to a commit
Note: checking out 'f00028caf257e386c0f3ae46bd4b3ba53dd0729d'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at f00028c... cifs-utils: Add runtime recommendation to CIFS kernel module
cloning repo meta-ti
Fetching arago
fatal: git checkout: updating paths is incompatible with switching branches.
Did you intend to checkout 'origin/danny' which can not be resolved as commit?
fatal: 'origin/danny' does not point to a commit
Note: checking out 'af9632689392ea03fd14879ca33b3c6c6ed2e347'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at af96326... abefw: Firmware for OMAP5 ABE
cloning repo meta-linaro
Fetching linaro
fatal: git checkout: updating paths is incompatible with switching branches.
Did you intend to checkout 'origin/danny' which can not be resolved as commit?
fatal: 'origin/danny' does not point to a commit
Note: checking out 'd0558fa4304592622423582f8b464e1c22cfe6f1'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at d0558fa... netbase: remove bbappend
cloning repo oe-core
Fetching oe
fatal: git checkout: updating paths is incompatible with switching branches.
Did you intend to checkout 'origin/danny' which can not be resolved as commit?
fatal: 'origin/danny' does not point to a commit
Note: checking out '0785489d558c34cacf5cb349949a15e27084efbf'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at 0785489... grub-efi-native: fix build on modern distributions without gets()
################################################################################
The bblayers.conf configuration file has been created for you with some
default values. Please verify the contents of your conf/bblayers.conf
file for correctness.
NOTE: Any additional entries to this file will be lost if the ./oe-layertool-setup.sh
script is run again. To add entries permanently to this file
please add them to the config file used and rerun the
./oe-layertool-setup.sh script.
################################################################################
The local.conf configuration file has been created for you with some
default values. Please verify the contents of your conf/local.conf
file for correctness.
By default the number of threads used by the build is set to the number
of CPUs found on your system.
NOTE: You will probably want to change the default MACHINE setting in the
local.conf file to the machine you are trying to build.
################################################################################
A setenv file has been created for you in the conf directory. Please verify
The contents of this file. Once you have verified the contents please source
this file to configure your environment for building:
. conf/setenv
You can then start building using the bitbake command. You will likely want
to set the MACHINE option if you have not done so in your local.conf file.
For example:
MACHINE=xxxxx bitbake <target>
Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-toolchain-sdk
adt-installer
meta-ide-support
^ permalink raw reply [flat|nested] 4+ messages in thread