Hello !
> If you want to confirm, insert this in the beginning of
> vesafb_probe(struct device *device) in drivers/video/vesafb.c:
>
> printk("vesafb: ypan %i, vremap %i", ypan, vram_remap);
>
> And if the above is the cause, you can, temporarily, hardcode
> your preferences in vesafb.c and see at least if it works for you.
In order to hardcode my preferences, I downloaded kernel 2.6.12.5
sources, I tried it before the change in vesafb.c and ... flipping
works with that kernel !
It still using 1800k but the geometry changed, now is 640 480 640 960
24 instead of 640 480 640 480 24.
This is my dmesg with regards to vesafb with kernel 2.6.12.5:
Initializing Cryptographic API
vesafb: framebuffer at 0xd0000000, mapped to 0xe0880000, using 1800k,
total 65536k
vesafb: mode is 640x480x24, linelength=1920, pages=67
vesafb: protected mode interface info at c000:5a83
vesafb: pmi: set display start = c00c5af1, set palette = c00c5b2b
vesafb: pmi: ports = 3010 3016 3054 3038 303c 305c 3000 3004 30b0 30b2 30b4
vesafb: scrolling: ypan using protected mode interface, yres_virtual=960
vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
Console: switching to colour frame buffer device 80x30
fb0: VESA VGA frame buffer device
fb1: Virtual frame buffer device, using 1024K of video memory
isapnp: Scanning for PnP cards...
And this is the reply to a fbset -i:
mode "640x480-73"
# D: 30.720 MHz, H: 36.923 kHz, V: 73.260 Hz
geometry 640 480 640 960 24
timings 32552 80 32 16 4 80 4
rgba 8/16,8/8,8/0,0/0
endmode
Frame buffer device information:
Name : VESA VGA
Address : 0xd0000000
Size : 1843200
Type : PACKED PIXELS
Visual : TRUECOLOR
XPanStep : 0
YPanStep : 1
YWrapStep : 0
LineLength : 1920
Accelerator : No
Thank you all !!
Carlos
_______________________________________________
directfb-dev mailing list
[EMAIL PROTECTED]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
