From: Stefan Berndtsson <stefan@nocrew.org>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: R128 Scaling.
Date: 16 Apr 2002 14:53:10 +0200 [thread overview]
Message-ID: <87wuv7reix.fsf@hades.nocrew.org> (raw)
In-Reply-To: <20020416133220.782c956e.adrian@humboldt.co.uk>
Adrian Cox <adrian@humboldt.co.uk> writes:
> I started looking at that a while ago, but didn't get very far. To get
> much further (and also to tackle the VGA out problems) I probably need
> the chip docs, but I haven't really pursued them. My one email asking to
> become an X developer was ignored, and I don't know of any other way to
> get the docs currently.
>
> The scaling patches I worked on had a problem with display flickering.
> They also needed a general mechanism to get the physical panel size.
I guess I never mentioned it was your patch I messed with. When switching
to 640x480, I get flickering if running 60Hz, but with 85 (which is what
fbset reports for me now), I see no such thing.
> > When running something in DGA (xmame for example), with XF4.1 and UseFBDev,
> > the resolution is changed by MAME, but it seems it still gets the fullsize
> > resolution passed to it, because it draws completely distorted graphics.
> > The area indicates that 1024x768 is passed as resolution even though the
> > display is set to 640x480 using scaling.
>
> I didn't get this one resolved at the time.
Too bad.. I hope it can be fixed :)
/Stefan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-16 12:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 11:49 R128 Scaling Stefan Berndtsson
2002-04-16 12:32 ` Adrian Cox
2002-04-16 12:53 ` Stefan Berndtsson [this message]
2002-04-16 13:12 ` Michel Dänzer
2002-04-16 13:55 ` Adrian Cox
2002-04-16 14:01 ` Geert Uytterhoeven
2002-04-16 14:13 ` Adrian Cox
2002-04-16 13:20 ` Michel Dänzer
2002-04-16 13:30 ` Stefan Berndtsson
2002-04-16 13:40 ` Michel Dänzer
2002-04-16 13:46 ` Stefan Berndtsson
2002-04-17 5:44 ` Ani Joshi
2002-04-17 11:54 ` Michel Dänzer
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=87wuv7reix.fsf@hades.nocrew.org \
--to=stefan@nocrew.org \
--cc=adrian@humboldt.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.