• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 101 subscribers
  • Views 1168 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP35x_Graphics_SDK_3_01_00_07 compilation issue on OMAP3515

Francis LE HOANG LONG
Prodigy 50 points

Dear all,

I would like to compiler power sgx driver for my card with 3515 processor, unfortunately some errors that I can't fix its. Somebody can help me.

I have used a kernel version 2.6.33.7 with somme driver modify and uImage run.

Thank you for your reponse

Regards,

Francis LE

 

$ make OMAPES=3.x BUILD=release


building the sgx kernel modules...
make[1]: Entering directory `/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM'
make -C /home/flehoanglong/OMAP3D/kernel M=`pwd` clean
make[2]: Entering directory `/home/flehoanglong/OMAP3D/kernel'
  CLEAN   /home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/.tmp_versions
make[2]: Leaving directory `/home/flehoanglong/OMAP3D/kernel'
make[1]: Leaving directory `/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM'
make[1]: Entering directory `/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM'
make -C /home/flehoanglong/OMAP3D/kernel M=`pwd`
make[2]: Entering directory `/home/flehoanglong/OMAP3D/kernel'
  LD      /home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/built-in.o
  CC [M]  /home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/bc_cat.o
  LD [M]  /home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/bufferclass_ti.o
  LD      /home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux/built-in.o
  CC [M]  /home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux/omaplfb_displayclass.o
  CC [M]  /home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux/omaplfb_linux.o
/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux/omaplfb_linux.c:57:50: error: expected declaration specifiers or '...' before 'IMG_UINT32'
/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux/omaplfb_linux.c: In function 'OMAPLFBEnableVSyncInterrupt':
/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux/omaplfb_linux.c:104:6: error: 'pOMAPLFBVSyncISRHandle' undeclared (first use in this function)
/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux/omaplfb_linux.c:104:6: note: each undeclared identifier is reported only once for each function it appears in
/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux/omaplfb_linux.c: In function 'OMAPLFBDisableVSyncInterrupt':
/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux/omaplfb_linux.c:110:6: error: 'pOMAPLFBVSyncISRHandle' undeclared (first use in this function)
/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux/omaplfb_linux.c: In function 'OMAPLFBFlip':
/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux/omaplfb_linux.c:195:2: error: too many arguments to function 'omap_dispc_set_plane_base'
/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux/omaplfb_linux.c:57:13: note: declared here
make[4]: *** [/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux/omaplfb_linux.o] Error 1
make[3]: *** [/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux] Error 2
make[2]: *** [_module_/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM] Error 2
make[2]: Leaving directory `/home/flehoanglong/OMAP3D/kernel'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/flehoanglong/OMAP3D/graphics/OMAP35x_Graphics_SDK_3_01_00_07/GFX_Linux_KM'
make: *** [buildkernel] Error 2

 

  • 0
    TI__Expert 6580 points

    Is CONFIG_OMAP2_DSS enabled in your kernel ? Looks like it is not.

    Please refer to kernel requirements below:

    http://processors.wiki.ti.com/index.php/RN_4_03_00_02

    Also the rebuild procedure here:

    http://processors.wiki.ti.com/index.php/GSG:_AM35x_and_OMAP35x_Rebuilding_the_Software#Rebuilding_the_Graphics_SGX_Kernel_Modules

     

    There are some patches (untested by TI), if you do not have CONFIG_OMAP2_DSS enabled in kernel. Example,

    http://repository.timesys.com/buildsources/o/omap35x-graphics-sdk/omap35x-graphics-sdk-3_00_00_09/no-dss-support.patch