From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: linuxppc-dev@lists.linuxppc.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Scaling registers on r128
Date: Mon, 12 Nov 2001 22:36:13 +0100 [thread overview]
Message-ID: <3BF040CD.560358DB@iiic.ethz.ch> (raw)
In-Reply-To: 3BEF952D.9000306@humboldt.co.uk
Adrian Cox wrote:
>
> This patch to aty128fb is experimental, and intended for the brave.
>
> The attached patch turns on the panel scaling registers of the R128.
> I've run this on my iBook2, and I've been able to display 640x480 and
> 800x600 modes on the panel successfully.
>
> The panel sizes are currently hardwired on the iBook. This code will
> benefit greatly from a reliable means to find the panel size.
>
> This has revealed problems in the X server: if the XF86Config-4
> specifies 800x600 and the current console is in 1024x768, the display
> is broken.
Does switching resolutions in X fix it again?
> This looks like a generic problem in fbdevhw based Xservers, as
> I saw something similar on 69030.
Yes, I suspect some fbdevHW functions return information about the
current console mode instead of the one the X server wants to set up.
I'm not sure how to fix, you seem to be working a lot with that code
recently so I expect you to find a way. :)
--
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-11-12 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 9:23 Scaling registers on r128 Adrian Cox
2001-11-12 13:16 ` Benjamin Herrenschmidt
2001-11-12 21:36 ` Michel Dänzer [this message]
2001-11-22 1:42 ` 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=3BF040CD.560358DB@iiic.ethz.ch \
--to=michdaen@iiic.ethz.ch \
--cc=adrian@humboldt.co.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).