425 views
in System Integration by

the folloing URL is my previous question : 

https://ask.embedded-wizard.de/1710/performance-depending-on-whether-arm-neon-function-enabled

In previous question,  the last answer is LCD pixel clock adjustment.

So we modified the pixel clock as following ..

[root@(none) home]# fbset -i

     mode "1280x800-64"
         # D: 74.250 MHz, H: 52.660 kHz, V: 64.376 Hz
         geometry 1280 800 1280 1600 32
         timings 13468 68 60 8 8 2 2
         rgba 8/16,8/8,8/0,8/24
     endmode

     Frame buffer device information:
         Name        : DISP3 BG
         Address     : 0x76700000
         Size        : 8192000
         Type        : PACKED PIXELS
         Visual      : TRUECOLOR
         XPanStep    : 1
         YPanStep    : 1
         YWrapStep   : 1
         LineLength  : 5120
         Accelerator : No

 

1) First step : 

   In original graphic operation example, we change the screen size only. (800,480 -> 1280,800)

   thereupon, It is only partially output on our LCD.

   In this case, the frame rate was normally output to 60.

   

2) Second step

   In original graphic operation example, we change all the components to fit the LCD size. (1280x800)

   In this case, the frame rate was output to 30.

   Why is not 60 frames at 1280x800 resolution?

   

3) Target system specification

     - Embedded Wizard Studio Pro v8.30
     - Embedded Wizard Platform Package for Generic RGBA8888
     - Embedded Wizard Build Environment for Generic RGBA8888
     - Generic RGBA8888 NEON AddOn

     - NXP i.mx6 quad, 2GB RAM and 10.1 TFT LCD (1280x800)

 

4) Compile Flag

###############################################################################
# DEFINES
###############################################################################
CFLAGS  = -O2 -Wall -pipe                                                      \
          -marm                                                                \
          -march=armv7-a                                                       \
          -mcpu=cortex-a9                                                      \
          -mfloat-abi=hard                                                     \
          -DEW_USE_OFFSCREEN_BUFFER                                            \
          -DEW_USE_DOUBLE_BUFFER                                               \
          -mfpu=neon

 

1 Answer

0 votes
by
Hi,

Changing the screen size of the Graphics Accelerator demo from 800x480 to 1280x800 does also imply an increase of the pixels to be updated. Hence the so-called dirty area is now factor 2.6 times bigger than the original set-up. And as everything is still managed entirely by the CPU, the achieved FPS is - from my point of view - not so bad and absolutely ok.

Hope I could shed some lights on this,
best regards,
Manuel

Ask Embedded Wizard

Welcome to the question and answer site for Embedded Wizard users and UI developers.

Ask your question and receive answers from the Embedded Wizard support team or from other members of the community!

Embedded Wizard Website | Privacy Policy | Imprint

...