> Its not the framebuffer memory itself. Can I not write a userland app that
> opens /dev/fb and set the video mode to somthing else. Most low end pci
> cards have two apertures. One for big endian and another for little endian.
> In 8 bit mode the card will most like use the little endian aperture. So
> if you have the X server open /dev/fb and sets the mode via
> FBIOPUT_VSCREENINFO. It then calls FBIOGET_FSCREENINFO and uses that
> data to mmap the framebuffer. Then I use my own fbdev program. It calls
> FBIOPUT_VSCREENINFO to set it to a 16 bpp mode. This means the aperture
> has changed its address this fix->smem_start is invalid. Thus the X
> server will be writing to the wrong memory region.
Does not happen on any of the sbusfb driven cards, in fact PUT_VSCREENINFO
does not work there either.
You just have one chunk of physical memory for smart 32bit aperture, other
chunk of physical memory for dumb 32bit aperture, one for dumb 8bit red
aperture etc. and all these can be mmaped separately.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon May 15 2000 - 21:00:11 EST