Thanks Paul!
On 22 December 2011 10:11, Ying-Chun Liu (PaulLiu) paul.liu@linaro.org wrote:
Hi Zach,
First, you need to register for http://www.freescale.com/ On the right-top side.
And then go to this link
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB
In Downloads Tab -> i.MX53 Software and Development Tool Resources And the following links (for Debian/Ubuntu): i.MX53 Linux Source Code - 2D/3D binaries. i.MX53 Linux Multimedia Codecs Source Code - Multimedia codec binaries.
They are big tarballs which contains a lot of small tarballs. Most of the things are open source and are already in Ubuntu and we don't need that. We just need the binary stuff.
Here's the list in Ubuntu (we package the things base on the above small tarballs, most of them are only binaries: amd-gpu-x11-bin-mx51 - OpenGLES, OpenVG.. just those 3D stuff (z430) firmware-imx - firmware for kernel fsl-mm-codeclib - multimedia codecs imx-lib - LGPL licensed wrapper for IPU/VPU libz160-bin - 2D accel lib (2D GPU z160)
And there are Android stuff for download. I didn't download that before but I think the content should be similar.
Yours Sincerely, Paul
-- z160 is g12 and z430 is yamato.
On 11-12-22 03:33 PM, Zach Pfeffer wrote:
Thanks Paul!
On 22 December 2011 10:11, Ying-Chun Liu (PaulLiu)paul.liu@linaro.org wrote:
Hi Zach,
First, you need to register for http://www.freescale.com/ On the right-top side.
And then go to this link
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB
In Downloads Tab -> i.MX53 Software and Development Tool Resources And the following links (for Debian/Ubuntu): i.MX53 Linux Source Code - 2D/3D binaries. i.MX53 Linux Multimedia Codecs Source Code - Multimedia codec binaries.
They are big tarballs which contains a lot of small tarballs. Most of the things are open source and are already in Ubuntu and we don't need that. We just need the binary stuff.
Here's the list in Ubuntu (we package the things base on the above small tarballs, most of them are only binaries: amd-gpu-x11-bin-mx51 - OpenGLES, OpenVG.. just those 3D stuff (z430) firmware-imx - firmware for kernel fsl-mm-codeclib - multimedia codecs imx-lib - LGPL licensed wrapper for IPU/VPU libz160-bin - 2D accel lib (2D GPU z160)
And there are Android stuff for download. I didn't download that before but I think the content should be similar.
Yours Sincerely, Paul
-- z160 is g12 and z430 is yamato.
FYI, there isn't much of interest here for Android, and it seems awfully old (2.6.35 based). I'm currently downloading the latest Android (r10.2.1) release for iMX53 from Freescale's compass site. Send you a link to it when I can.
Scott
On 22 December 2011 19:43, Scott Bambrough scott.bambrough@linaro.org wrote:
On 11-12-22 03:33 PM, Zach Pfeffer wrote:
Thanks Paul!
On 22 December 2011 10:11, Ying-Chun Liu (PaulLiu)paul.liu@linaro.org wrote:
Hi Zach,
First, you need to register for http://www.freescale.com/ On the right-top side.
And then go to this link
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB
In Downloads Tab -> i.MX53 Software and Development Tool Resources And the following links (for Debian/Ubuntu): i.MX53 Linux Source Code - 2D/3D binaries. i.MX53 Linux Multimedia Codecs Source Code - Multimedia codec binaries.
They are big tarballs which contains a lot of small tarballs. Most of the things are open source and are already in Ubuntu and we don't need that. We just need the binary stuff.
Here's the list in Ubuntu (we package the things base on the above small tarballs, most of them are only binaries: amd-gpu-x11-bin-mx51 - OpenGLES, OpenVG.. just those 3D stuff (z430) firmware-imx - firmware for kernel fsl-mm-codeclib - multimedia codecs imx-lib - LGPL licensed wrapper for IPU/VPU libz160-bin - 2D accel lib (2D GPU z160)
And there are Android stuff for download. I didn't download that before but I think the content should be similar.
Yours Sincerely, Paul
-- z160 is g12 and z430 is yamato.
FYI, there isn't much of interest here for Android, and it seems awfully old (2.6.35 based). I'm currently downloading the latest Android (r10.2.1) release for iMX53 from Freescale's compass site. Send you a link to it when I can.
I disagree. I've spoken with many who would like to base products off of this. At the end of the day the kernel doesn't actually have much of a difference - in fact newer kernels have tended to slow things down and make things less stable. What does make a difference is running our 4.6 toolchain and shipping libjpeg-turbo and libpng-turbo. So an accelerated ICS on 2.6.35 would be quite a good treat for many people.
Scott
On 22 December 2011 18:42, Zach Pfeffer zach.pfeffer@linaro.org wrote:
I disagree. I've spoken with many who would like to base products off of this. At the end of the day the kernel doesn't actually have much of a difference - in fact newer kernels have tended to slow things down and make things less stable.
I don't think that's the new kernels' fault - it's more likely because we've been enabling more debug features.
Gator needs tracing and profiling enabled, and that stuff - while useful for development - hurts performance.
At some point we should probably have a development build w/ all this stuff enabled and a show-off build w/ everything unnecessary disabled.
ttyl bero
2011/12/23 Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org:
On 22 December 2011 18:42, Zach Pfeffer zach.pfeffer@linaro.org wrote:
I disagree. I've spoken with many who would like to base products off of this. At the end of the day the kernel doesn't actually have much of a difference - in fact newer kernels have tended to slow things down and make things less stable.
I don't think that's the new kernels' fault - it's more likely because we've been enabling more debug features.
That's true. We haven't done a thorough breakdown of the impacts of each modification we've made, apart from the monthly benchmarks. My main point was that the kernel is only one component of many in Android and that upgrades to it may have either positive or negative effects on the user, but those effects tend to be less pronounced than compiler improvements, hardware acceleration, etc. Even on the PM front. You can try to do as much as you want in the kernel, but your LCD still eats 50% of your battery, WiFI and 3G eat 25% - so you're working to optimize the rest of the 25%.
Gator needs tracing and profiling enabled, and that stuff - while useful for development - hurts performance.
At some point we should probably have a development build w/ all this stuff enabled and a show-off build w/ everything unnecessary disabled.
Yeah. I think if we can get back to one manifest and do better tree maintenance we can get there.
ttyl bero
On 12/28/2011 12:03 PM, Somebody in the thread at some point said:
2011/12/23 Bernhard Rosenkränzerbernhard.rosenkranzer@linaro.org:
On 22 December 2011 18:42, Zach Pfefferzach.pfeffer@linaro.org wrote:
I disagree. I've spoken with many who would like to base products off of this. At the end of the day the kernel doesn't actually have much of a difference - in fact newer kernels have tended to slow things down and make things less stable.
I don't think that's the new kernels' fault - it's more likely because we've been enabling more debug features.
That's true. We haven't done a thorough breakdown of the impacts of each modification we've made, apart from the monthly benchmarks. My main point was that the kernel is only one component of many in Android and that upgrades to it may have either positive or negative effects on the user, but those effects tend to be less pronounced than compiler improvements, hardware acceleration, etc. Even on the PM front. You can try to do as much as you want in the kernel, but your LCD still eats 50% of your battery, WiFI and 3G eat 25% - so you're working to optimize the rest of the 25%.
That's assuming kernel pm is already there and doing its job. If dvfs and the other major kernel pm elements are absent, in fact your CPU is pulling more power than the rest of a typical offhook smartphone put together all the time.
So it's more accurate to look at it that kernel pm is reducing the cpu power share from 125% to 25%... highly critical for battery case.
-Andy
linaro-android@lists.linaro.org