linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Simmons <jsimmons@infradead.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Andrew Morton <akpm@digeo.com>,
	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: Tue, 15 Apr 2003 20:25:25 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0304152022550.8236-100000@phoenix.infradead.org> (raw)
In-Reply-To: <1050310411.5574.44.camel@zion.wanadoo.fr>


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

Oh. A Rage 128 chip with a LCD display. Then you are out of luck right 
now.

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

We it sort of is old but yet new. I did port alot of the code from 2.4.X. 
to the latest tree. I haven't ported "thee" latest patches tho.

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

It there but only for PPC platforms. Hopefully with the new fbmon.c code I 
will be able to have this work on ix86 very soon.




  reply	other threads:[~2003-04-15 19:13 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   ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-04-15 19:25     ` James Simmons [this message]
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=Pine.LNX.4.44.0304152022550.8236-100000@phoenix.infradead.org \
    --to=jsimmons@infradead.org \
    --cc=akpm@digeo.com \
    --cc=benh@kernel.crashing.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).