Carlos Ojea Castro wrote:
2.6.11 should be fine. Post your dmesg with regards to vesafb.

vesafb: framebuffer at 0xd0000000, mapped to 0xe0880000, using 1800k,
total 65472k
vesafb: mode is 640x480x24, linelength=1920, pages=67
vesafb: protected mode interface info at c000:5a83
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
fb0: VESA VGA frame buffer device
Console: switching to colour frame buffer device 80x30

most important would be the the availability of the "Protected Mode
Interface" in the BIOS. If this is not available, than panning will be
disabled by vesafb.

line about protected mode is  "vesafb: protected mode interface info
at c000:5a83", does it mean the protected mode is avaliable?

Yes.



Also, if you think that your Video BIOS is incorrect about the amount
of video RAM you have, you can use the option vtotal and vremap.
(vtotal is the total amount of RAM in MB, and vremap for the amount
of RAM you want to use.  See Documentation/fb/vesafb.txt).

I put this options: kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda6 ro acpi=off
video=vesafb:ypan,mtrr,vtotal:64,vremap:32 vga=786

The related message in /var/log/dmesg :
vesafb: framebuffer at 0xd0000000, mapped to 0xe0880000, using 1800k,
total 65472k
It seems to find all video memory, but it still uses only 1800k
instead of 32000k as I put in the vremap option, and my program still
crashes when I try to use page flipping. Do you know why? Is there
something wrong with my options?

I think something is wrong with how your bootloader is passing your
options to the kernel.  If you enable ypan, you should get an additional
line in your dmesg that is something like this:

vesafb: pmi: set display start = xxxx, set palette = xxxx

Since you don't have this message, I guess the "ypan" option and
the "vremap" option was not passed at all.

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.

Tony

_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev

Reply via email to