linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: <ajoshi@unixbox.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH]: Make radeonfb work alot better with new powerbooks
Date: Thu, 8 Nov 2001 11:22:37 +0100	[thread overview]
Message-ID: <20011108102237.11596@smtp.adsl.oleane.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111072026090.30759-100000@www.cgsoftware.com>


>
>This patch makes the radeonfb work a lot better on the rev b powerbooks.
>It's against benh's latest, as of last night.

Heh, Great ! I ordered a new TiPb but didn't get it yet :)

Could you send me a tarball of /proc/device-tree ?

>Fixed/added:
>1. Any other mode besides 640x480 was absurdly slow. Unusable, in fact.
>It now is pretty darn quick, and completely usable.
>2. It would default to 640x480, rather than 1152x768, on rev b powerbooks.
>3. It would also determine that we had no monitor, and no display panel,
>because it couldn't read the video bios that doesn't exist in the
>powerbooks.
>In reality, the LCD is on the DVI port.
>So for rev b powerbooks, we go ahead and say so, and let it detect
>the flat panel size/stretching/etc.

We need to fix this for DVI LCDs as well, for both radeon and aty128fb.

"Mac" radeons will put the monitor EDID in the device-tree, so we could
probably just parse that, but r128's firmware won't. I'd rather implement
the proper i2c code for reading that and add a generic fbdev ioctl for
retreiveing it (as it's not card specific) so userland tools can use it
to generate proper XF86Config as well.

>4. It would assume blanking meant blanking the crt. It will now turn off
>the lcd as well.
>5. It now supports the backlevel lighting control. It's the same on the
>rage128 and the radeon, so i copied and renamed the routines from
>aty128fb.c

Beware with blanking of the CRT/LCD. The current code I have for r128
seem to have problems. I've user reports on r128 of "burned" lines after
keeping the LCD off a long timech fortunately disappeared, but only after
several hours of normal use. I suspect a different shutdown sequence should
be used to properly turn off the LVDS and the panel itself, but I don't know
what for sure, the docs I have from ATI aren't very precise.

I want to remove part of that code and let only LVDS_DIS and backlight off.

>It *shouldn't* have any problems on a normal radeon powermac, but i don't
>have one to try it out on.

I'll try it on the radeon AGP card I have at work, if it still works, I'll
include it in my tree and bk _devel.

>Hopefully, this is useful for someone besides me.

Yup ;)

Regards,
Ben./


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-11-08 10:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08  2:15 [PATCH]: Make radeonfb work alot better with new powerbooks Daniel Berlin
2001-11-08 10:22 ` Benjamin Herrenschmidt [this message]
2001-11-08 15:04   ` Daniel Berlin
2001-11-08 16:38     ` Benjamin Herrenschmidt
2001-11-08 17:05       ` Daniel Berlin
2001-11-08 17:07       ` Adrian Cox
2001-11-08 17:11         ` Benjamin Herrenschmidt

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=20011108102237.11596@smtp.adsl.oleane.com \
    --to=benh@kernel.crashing.org \
    --cc=ajoshi@unixbox.com \
    --cc=dan@cgsoftware.com \
    --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).