Other Parts Discussed in Thread: AM3354, AM3352
Hi,
We want to use AM335x for Touch LCD, which needs only the 2D graphic acceleration.
So I'm now investigating the 2D performance of SGX530. If SGX530 is needless for our application, we want to use AM3352 rather than AM3354.
From the site below, you can find following article.
In the case of Screen Rendering(PVR2D), it says that only 10% reducion is expected in the case of VGA resolution.
Then if we process 320x240 resolution, then 2.5%(=10%/4) in CPU is expected, is it right?
Then, what Mhz will the 2.5% of CPU mean?
In addition, the site says that 2D acceleration with SGX530 has an effect when image resolution is larger than VGA. Then if we use 320x240, the SGX530 has little effect?
S/W acceleration will be good in the case of "small resolution(less than VGA & 2D"?
Using Qt's Powervr backend for display/ 3D acceleration in XgxPerf
If the TI SGX Graphics SDK (see references below for the SDK and Qt integration) is installed, Qt/embedded (not Qt/X11) can be configured to use SGX by invoking
any Qt application in the below manner:
$> ./Qt_app -qws -display powervr
Qt applications can use SGX for 3 kinds of operations.
1. OpenGL ES2.0 applications, that draw 3D objects on screen (application calls 3D APIs directly)
2. Acceleration of Screen Driver (PVR2D in SGX used as a screen driver instead of ARM SW)
In the second case, the screen rendering (2D) operations are accelerated using PVR2D, that uses SGX instead of ARM.
This can result in ~10% reduction in CPU utilisation, for resolutions greater than VGA.
This does not need any changes to the Qt application itself.
The above 2 categories do not need a change in the application itself.
3. In order to use the SGX HW to accelerate even 2D operations, the application has to be rewritten to utilise QGLWidget (rather than QWidget).
QGLWidget is documented in Qt Documentation pages. This results in acceleration typically when screen resolutions are larger than VGA.
Thanks,
Devin
