linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: Stefan Berndtsson <stefan@nocrew.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: R128 Scaling.
Date: 16 Apr 2002 15:12:12 +0200	[thread overview]
Message-ID: <1018962733.1590.2316.camel@tibook> (raw)
In-Reply-To: <20020416133220.782c956e.adrian@humboldt.co.uk>


On Tue, 2002-04-16 at 14:32, Adrian Cox wrote:
>
> On 16 Apr 2002 13:49:12 +0200
> Stefan Berndtsson <stefan@nocrew.org> wrote:
>
> > What is the status of the scaling registers for rage128? I saw a patch
> > in the archive, that adds scaling capabilities for the framebuffer,
> > and that seems to work reasonably well.
>
> 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.

You can apply for them with ATI directly, their developer relations
program to be exact.

> The scaling patches I worked on had a problem with display flickering.

I could resolve that problem with custom modes I obtained in a way Kevin
Hendricks posted here.

> They also needed a general mechanism to get the physical panel size.

Shouldn't be hard with Apple machines, and on x86 one can use the BIOS
as seen in the X driver.


--
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/

  parent reply	other threads:[~2002-04-16 13:12 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
2002-04-16 13:12   ` Michel Dänzer [this message]
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=1018962733.1590.2316.camel@tibook \
    --to=michel@daenzer.net \
    --cc=adrian@humboldt.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=stefan@nocrew.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).