From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net,
James Simmons <jsimmons@infradead.org>
Subject: Re: atyfb in 2.5.51
Date: 11 Dec 2002 00:11:10 +0100 [thread overview]
Message-ID: <1039561870.538.28.camel@zion> (raw)
In-Reply-To: <15862.27438.787187.93003@argo.ozlabs.ibm.com>
On Tue, 2002-12-10 at 23:31, Paul Mackerras wrote:
> I tried 2.5.51 on my G3 powerbook (laptop), which has a Rage LT Pro
> video chip (ID 0x4c49 or LI). With the patch below, atyfb compiles
> and seems to mostly work. However, I didn't see any penguin on boot.
> Instead the top inch or so of the screen was just black.
>
> X seems to be running just fine. I have 'Option "UseFBDev"' in my
> /etc/X11/XF86Config-4.
AFAIK, the X "mach64" driver in XF 4.* doesn't care about UseFBDev.
Marc Aurele La France (maintainer of this driver) is basically allergic
to kernel fbdev support.
> What doesn't work is changing VTs from X to a
> text console. If I press ctrl-alt-F1, for instance, the colormap
> changes but I don't see anything get redrawn. The screen looks just
> like what I had in X but with the altered colormap. If I then press
> alt-F7, it switches back to X and X redraws the screen properly and
> restores its colormap.
I don't know if happened with earlier fbdev versions for you, but one
possibility is that X reconfigures the display base, and possibly more
bits of the card's internal memory map. Either fbdev should restore
that, or adapt to what X set. On R128's and radeon's, this is things
like DISPLAY_BASE_ADDR.
> The patch below also takes out the CONFIG_NVRAM stuff since it doesn't
> work and I don't believe anyone has ever used it.
Yup, it's some wacky old pmac stuff that should be killed.
> I have also tried aty128fb with some local patches to get it to
> compile for my G4 powerbook. It also doesn't draw the penguin, and it
> oopses when X starts, for some reason.
Hrm... I'll have to test radeonfb... It worked yesteday in console (I
don't remember about the penguin) but I didn't try X.
next prev parent reply other threads:[~2002-12-10 23:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 22:31 atyfb in 2.5.51 Paul Mackerras
2002-12-10 23:11 ` Benjamin Herrenschmidt [this message]
2002-12-11 6:18 ` James Simmons
2002-12-11 8:42 ` David S. Miller
2002-12-11 15:16 ` James Simmons
2002-12-11 20:43 ` David S. Miller
2002-12-11 21:35 ` Alan Cox
2002-12-12 20:23 ` Pavel Machek
2002-12-13 8:53 ` Geert Uytterhoeven
2002-12-13 10:26 ` Alan Cox
2002-12-22 13:40 ` Geert Uytterhoeven
2002-12-11 21:06 ` Paul Mackerras
2002-12-15 11:45 ` Stefan Reinauer
2002-12-13 8:49 ` Geert Uytterhoeven
2002-12-11 12:49 ` [Linux-fbdev-devel] " Antonino Daplas
2002-12-11 15:46 ` James Simmons
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=1039561870.538.28.camel@zion \
--to=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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.