> >> A player then does XSync, so that I can actually see the picture appear >> on screen, > >This could be where X uses all the CPU. While waiting for the CCE to go >idle, it can't do much but busy loop. (The DRM uses a loop with udelay() >actually; see r128_do_cce_idle() in r128_cce.c)
Can't the kernel block and wait for an interrupt ? >> and calling another X function until it's finished causes X to "hang" >> and this "eats" CPU time. > >It might be a good idea to test if XSync alone causes the same >behaviour. _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
