From: Paul Furber <paulf@gam.co.za>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: vesafb and xres_virtual
Date: Fri, 07 Jun 2002 04:02:02 +0200 [thread overview]
Message-ID: <3D00141A.2090308@gam.co.za> (raw)
Hi all,
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,
Paul.
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
reply other threads:[~2002-06-07 2:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D00141A.2090308@gam.co.za \
--to=paulf@gam.co.za \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).