From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Rage128 support for resolutions less than panel resolution?
Date: 05 Dec 2001 00:47:45 +0100 [thread overview]
Message-ID: <1007509665.21511.38.camel@pismo> (raw)
In-Reply-To: <20011204175547.WVJL16262.tomts14-srv.bellnexxia.net@there>
On Tue, 2001-12-04 at 18:58, Kevin B. Hendricks wrote:
> However if you have the correct timing info, you should be able to write a
> mode to use and then use fbset to set rage128 frame buffer to that mode.
>
> This should work to change your resolution to whatever you want as long as
> the "scaling register code" patch I saw fly by recently (a couple of weeks
> ago) actually made it into the aty128fb.c code yet.
>
> If it did you should be in luck. Just take the timing from the the full
> native resolution and just change the x and y resolution and leave all of
> the rest untouched. The scaling registers code should figure out the rest.
> as long as the real native panel resolution is known by the driver.
Thanks for these instructions Kevin! I'm now able to use 800x600 and
640x480 on my Pismo without any flickering and artifacts.
One thing I noticed is that when I use the timings from 1024x768-60 for
640x480, the vertical refresh is shown as 130 Hz. That doesn't harm the
panel?
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-04 23:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 17:22 Rage128 support for resolutions less than panel resolution? Derrik Pates
2001-12-04 17:58 ` Kevin B. Hendricks
2001-12-04 18:15 ` Derrik Pates
2001-12-04 20:06 ` Derrik Pates
2001-12-04 23:47 ` Michel Dänzer [this message]
2001-12-05 0:25 ` Kevin B. Hendricks
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=1007509665.21511.38.camel@pismo \
--to=michdaen@iiic.ethz.ch \
--cc=kevin.hendricks@sympatico.ca \
--cc=linuxppc-dev@lists.linuxppc.org \
/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