From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Patches to add support for TI Linux Graphics SDK release 04.04.00.02
Date: Wed, 12 Oct 2011 12:57:40 +0200 [thread overview]
Message-ID: <j73rr4$5ar$1@dough.gmane.org> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB038595A16D@dbde02.ent.ti.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 12-10-11 12:42, Srinivas, Prathap schreef:
> Thanks for the comments. Please find my responses inline.
>> diff --git a/recipes/powervr-drivers/libgles-omap3_4.04.00.02.bb
>> b/recipes/powervr-drivers/libgles-omap3_4.04.00.02.bb new file mode
>> 100644 index 0000000..c5062c1 --- /dev/null +++
>> b/recipes/powervr-drivers/libgles-omap3_4.04.00.02.bb @@ -0,0 +1,29 @@
>> +BINLOCATION_omap3 = "${S}/gfx_rel_es3.x" +BINLOCATION_ti816x =
>> "${S}/gfx_rel_es6.x" + +ES2LOCATION = "${S}/gfx_rel_es2.x" +ES3LOCATION
>> = "${S}/gfx_rel_es3.x" +ES5LOCATION = "${S}/gfx_rel_es5.x" +ES6LOCATION
>> = "${S}/gfx_rel_es6.x"
>
> Since the above is being repeated in each recipe, shouldn't it move to
> the .inc? - I am just following in the way of already existing recipes.
> Existing recipes have this. If it still needs to be addressed, let me
> know.
It needs to be addressed, otherwise I wouldn't have mentioned it
>
>> --- /dev/null +++
>> b/recipes/powervr-drivers/omap3-sgx-modules_1.6.16.4117.bb
>
>> +MACHINE_KERNEL_PR_append = "i"
>
> Start at 'a' please, or remove it - I am just following in the way of
> already existing recipes. Existing recipes have this way only. If it
> still needs to be addressed, let me know.
It needs to be addressed, otherwise I wouldn't have mentioned it
>> +TI_PLATFORM_omap3 = "omap3630" +TI_PLATFORM_ti816x = "ti81xx" +
>> +MODULESLOCATION_omap3 = "dc_omapfb3_linux" +MODULESLOCATION_ti816x =
>> "dc_ti81xx_linux"
>
> Move to .inc? - I am just following in the way of already existing
> recipes. Existing recipes have this way only. If it still needs to be
> addressed, let me know.
It needs to be addressed, otherwise I wouldn't have mentioned it
>> diff --git a/recipes/powervr-drivers/libgles-omap3.inc
>> b/recipes/powervr-drivers/libgles-omap3.inc index 36c311d..e605681
>> 100644 --- a/recipes/powervr-drivers/libgles-omap3.inc +++
>> b/recipes/powervr-drivers/libgles-omap3.inc @@ -1,7 +1,7 @@ DESCRIPTION
>> = "libGLES for the omap3" LICENSE = "proprietary-binary"
>
>> -PR = "r15" +PR = "r16"
>
>> COMPATIBLE_MACHINE = "(omap3|ti816x)"
>
>> @@ -35,6 +35,13 @@ do_configure() { for i in $(find ${S} -name "*.h")
>> $(find ${S} -name "*.c") $(find ${S} -name "Make*") ; do chmod 0644 $i
>> done + + for drifile in $(find ${S} -name "libsrv_um_dri.so"); do + if
>> [ "$drifile" != "" ] ; then + dir=$(dirname
>> ${drifile}) + rm -rf ${dir}/libsrv_um_dri.so +
>> fi + done
>
> What does this try to fix exactly? - This fix is for the issue seen with
> opkg install of libgles-omap3_4.04.00.02-r16.6_armv7a.ipk on target. With
> Graphics SDK release 04.04.00.02, there are 2 versions of the library
> libsrv_um.so - one is libsrv_um.so and other is libsrv_um_dri.so (For
> Xorg driver). What we observed was in presence of libsrv_um_dri.so , the
> links created under /usr/lib were all by default linking to
> libsrv_um_dri.so only. Due to this demos used to fail. Now this fix makes
> sure that only 1 appropriate version of the library libsrv_um.so is
> present and hence links created will now be proper.
=
Please put that explanation in both the commit message and as a comment
about the for loop so people won't say "I am just following in the way of
already existing recipes" when this issues has been properly fixed.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFOlXKkMkyGM64RGpERAvROAKCCDqURb233i2eJ2mxdCNU2DoyhEACfXQmr
jB2nZhTMFSiQY0LWiRxYedE=
=1KC2
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-10-12 11:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 9:57 Patches to add support for TI Linux Graphics SDK release 04.04.00.02 Srinivas, Prathap
2011-10-12 10:06 ` Patches to add support for TI Linux Graphics SDK release04.04.00.02 Hauser, Wolfgang (external)
2011-10-12 10:45 ` Srinivas, Prathap
2011-10-12 11:46 ` Patches to add support for TI Linux GraphicsSDK release04.04.00.02 Hauser, Wolfgang (external)
2011-10-13 15:41 ` Hauser, Wolfgang (external)
2011-10-13 18:44 ` Srinivas, Prathap
2011-10-12 10:17 ` Patches to add support for TI Linux Graphics SDK release 04.04.00.02 Koen Kooi
2011-10-12 10:42 ` Srinivas, Prathap
2011-10-12 10:57 ` Koen Kooi [this message]
2011-11-17 10:43 ` Srinivas, Prathap
2011-11-17 14:56 ` Koen Kooi
2011-11-17 16:00 ` Srinivas, Prathap
2011-11-17 23:09 ` Koen Kooi
[not found] ` <C2C4AB609E1BCF4689C1782E8F42E30A027AF8@DBDE01.ent.ti.com>
2011-11-17 16:09 ` Patches to add support for TI Linux Graphics SDK release 04.04.00.02 : Patch1-kernel.bbclass update Srinivas, Prathap
2011-11-17 16:12 ` Patches to add support for TI Linux Graphics SDK release 04.04.00.02 : Patch2-Graphics SDK release 04.04.00.02 build support Srinivas, Prathap
2011-11-17 16:16 ` Patches to add support for TI Linux Graphics SDK release 04.04.00.02 : Patch3-Fix for library linking issue with Graphics SDK Release 04.04.00.02 Srinivas, Prathap
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='j73rr4$5ar$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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