tiomap-dev team mailing list archive

[Alexandros Frantzis <alf82@xxxxxxxxxxx>]

Public bug reported:

With the latest drivers on an SDP 4430 board calling eglInitialize takes
extremely long. Running the example program (attached) on an completely
idle system produces the following results:

# time ./eglinit       
real	0m5.797s
user	0m0.008s
sys	0m1.055s

# time ./eglinit
real	0m10.523s
user	0m0.008s
sys	0m1.047s

# time ./eglinit
real	0m30.459s
user	0m0.008s
sys	0m1.055s

# time ./eglinit
real	0m5.638s
user	0m0.008s
sys	0m1.055s

# time ./eglinit
real	0m10.088s
user	0m0.008s
sys	0m1.047s

I have attached an strace capture of a sample run that shows that the
delay is happening in an ioctl() around line 10000.

The trace also shows that the driver wastes a lot of time trying out
/dev/dri/* devices, but that is another subject :)

** Affects: ubuntu-omap4-extras-graphics
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of TI OMAP
Developers, which is subscribed to ubuntu-omap4-extras-graphics.
https://bugs.launchpad.net/bugs/690821

Title:
  Calling eglInitialize() takes too long

Status in Ubuntu OMAP4 graphics addons:
  New

Bug description:
  With the latest drivers on an SDP 4430 board calling eglInitialize takes extremely long. Running the example program (attached) on an completely idle system produces the following results:

# time ./eglinit       
real	0m5.797s
user	0m0.008s
sys	0m1.055s

# time ./eglinit
real	0m10.523s
user	0m0.008s
sys	0m1.047s

# time ./eglinit
real	0m30.459s
user	0m0.008s
sys	0m1.055s

# time ./eglinit
real	0m5.638s
user	0m0.008s
sys	0m1.055s

# time ./eglinit
real	0m10.088s
user	0m0.008s
sys	0m1.047s

I have attached an strace capture of a sample run that shows that the delay is happening in an ioctl() around line 10000.

The trace also shows that the driver wastes a lot of time trying out /dev/dri/* devices, but that is another subject :)