linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@digeo.com>
Cc: James Simmons <jsimmons@infradead.org>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	Linux Fbdev development list 
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] Re: [FBDEV BK] Updates and fixes.
Date: 14 Apr 2003 10:53:31 +0200	[thread overview]
Message-ID: <1050310411.5574.44.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <20030414005814.6719915f.akpm@digeo.com>


> When I enable framebuffer with your latest patch on this machine the display
> screws up - it alternates between blackness and a strange flicker of
> horizontal and vertical grey lines.  No text is visible.
> 
> This machine has:
> 
> ATI Technologies Inc Rage Mobility M3 AGP 2x (rev 02)

This is a r128 based chip, which lacks some of the proper support for
LCD stuff (especially automatic retreival of the EDID from BIOS) that
we have in radeonfb. If you feed the driver with a suitable mode, it
should work

> A second desktop machine has:
> 
> VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX440] (rev a3)
> 
> When fbcon is enabled here the screen is full of random uninitialised gunk
> and no text is readable.

I haven't yet checked which codebase is in there for rivafb, I have
started collecting various patches around & doing my own fixes, I have
a version here that works on PPC with GeForce2 & 4, though I still
have problems with accel on the GeForce4. It's a 2.4 code base right
now, I haven't had time to clean that up and release a patch though.

If 2.5 still has the old codebase, then GeForce4 isn't properly
supported yet.

Note that if you have a flat panel, then the problem of properly
retreiving the EDID to get a suitable default mode is also present
there, unless James added some support for it.

> 	ATI Technologies Inc Radeon VE QY
> 
> it seems to work OK as well.  The penguins started out on a black background.
> I didn't test dual-head mode.

Ok, I've seen that James added various fixes to 2.5 radeonfb, I still
have to port some of my 2.4 ones to 2.5, I except those chips to be
properly supported with fbdev.

Ben.


  reply	other threads:[~2003-04-14  8:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14  4:47 [FBDEV BK] Updates and fixes James Simmons
2003-04-14  7:58 ` Andrew Morton
2003-04-14  8:53   ` Benjamin Herrenschmidt [this message]
2003-04-15 19:25     ` [Linux-fbdev-devel] " James Simmons
2003-04-15 19:21   ` James Simmons
2003-04-15 20:04     ` Andreas Henriksson
2003-04-16  6:20     ` [Linux-fbdev-devel] " Geert Uytterhoeven
2003-04-14 19:15 ` Linus Torvalds
2003-04-15 19:49   ` James Simmons
2003-04-23 16:32 ` Pavel Machek

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=1050310411.5574.44.camel@zion.wanadoo.fr \
    --to=benh@kernel.crashing.org \
    --cc=akpm@digeo.com \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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).