This is getting stranger still... It seems that the FlipBuffer function in the savage driver isn't used. Instead, it falls back to the generic framebuffer thingy. Whats more, savagefb has primary and a secondary layer ?? And only the primary layer is used (it seems) and that would explain some of the strange behaviour. But not all... far from it. The secondary layer seems to "lock" the user into 640x480 display? Go figure....
Does someone know what all this means? The source isn't exactly filled with comments :( How do you people who use matrox cards write programs for DirectFB? Do you need to copy the entire screen between bufferflips? /Henric -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
