Sorry my friends,have checked the wrong folder(i.e /usr/libs instead of /usr/lib or vice versa ) for the list of libraries. somebody else should do it,also:
Tutorial for finding the extensions supported by SGX driver: A quick check of the extensions supported by the SGX driver can be done using "eglinfo" utility. A sample first few lines of this output are shown below.

EGL config number: 0
EGL vendor string: Imagination Technologies
EGL version string: 1.4 build 1.5.15.3130
EGL extensions: EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_vg_parent_image EGL
EGL client APIs are: OpenGL_ES OpenVG

EGL config Attributes:
EGL_CONFIG_ID = 0x1
EGL_BUFFER_SIZE = 0x10
EGL_RED_SIZE = 0x5
EGL_GREEN_SIZE = 0x6

...Extension (and other) information can be obtained at run-time with the eglQueryString() api. See the example C code below:

// The display needs to be set according to your platform
// EGLDisplay display;
char* extensions;
extensions = eglQueryString(display, EGL_EXTENSIONS);
printf("%s\n", extensions);
Testing the support for ARGB8888 in Frame Buffer Driver(For OMAP35xx only) as the TI said : (Maybe for OMAP 34xx?)
The bootargs need to be changed as given below.

OMAP3EVM # setenv bootargs 'console=ttyS0,115200n8=noinitrd=rw ip=dhcp
root=/dev/nfs nfsroot=<your nfs_path>,nolock, mem=128M omapfb.vram="4M"
omapfb.video_mode="640x480MR-24@60" omap-dss.def_disp="dvi"'Use fbset to configure ARGB8888 mode for framebuffer memory

target $fbset -rgba 8/16,8/8,8/0,8/24 Note that if you are switching to ARGB8888 mode after bootup it is mandatory to reload omaplfb.ko kernel module


For technical support please post your questions at http://e2e.ti.com.