On Tue, 2002-11-05 at 06:39, Henric Andersson wrote: > > > Problem is that I got used to the way the vesa framebuffer worked, > > > so I based my designs on it :( > > > if you had carefully read the README that comes with DirectFB you > > would probably have configured your vesa frame buffer device as > > suggested there: > > > ----8< cut >8---- > > > > a vesa frame buffer device configured in such a way should flip by > > switching pointers. > > Unfortunatly not mine.... trust me... I ran with these options for like, 1 > month now or so. I saw some errors "unable to pan" but I never figured it > had anything todo with flip:ing since everything "worked", so I figured it > must be normal. I usually "RTFM" so to speak ;) since it's easy to overlook > something. > > But I know better now :) > What does 'dmesg' show about vesafb? Does it say, scrolling: ypan, ywrap or redraw. If it is redraw, then yes, panning is not supported. If it says ypan or ywrap, then vesafb should be able to pan the display. And if your app doesn't, then it's probably a bug.
Note: the fb_var_screeninfo structure passed during the pan_display ioctl call must have var->yres_virtual greater than var->yoffset and xoffset = 0 in order for pan_display to exit without an error. You may want to debug src/core/fbdev/fbdev.c just to see the actual values in var. If xoffset != 0, use the ypan option, else use ywrap in lilo.conf. Tony Tony -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
