From: Paul Furber <paulf@ga...> - 2002-06-07 02:03:15
Perhaps someone can enlighten me. I've been ploughing through the vesafb
source and various other bits (video.S in boot as well) and I see that
the vesa driver supports changing the virtual y resolution but not the
virtual x. I suspect there is a really good reason for this - possibly
the real mode nature of BIOS calls or perhaps something to do with
bytes_per_line and the console driver - but I am not sure. Would it be
possible to allow virtual x resolutions to be set at startup? If not
then can the authors please fix the rivafb driver for GeForce2 Go chips?
:) I really need hardware x panning - it's for a demo that will boot and
run off a floppy.
many thanks - and hoping to be able to contribute,