From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Steven Newbury <steven.newbury1@ntlworld.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: atyfb and radeonfb
Date: 13 Nov 2002 00:09:44 +0100 [thread overview]
Message-ID: <1037142584.2774.230.camel@zion> (raw)
In-Reply-To: <3DCBD804.8050109@ntlworld.com>
On Fri, 2002-11-08 at 16:28, Steven Newbury wrote:
> Is atyfb in 2.4 known to work with recent Mach64 chips like Rage XL?
> When I install the driver it detects the chip but results in just a
> black screen. I also noticed that it detects WRAM, whereas I am certain
> it should be SGRAM. The XFree86 driver detects everything ok and just
> works.
Well, I don't know if Geert still have much time to maintain
this driver, any help implementing the missing features would
be nice ;)
> I have also noticed that the radeonfb driver lacks support for
> initialising the card if the BIOS hasn't already done it. I have
> recently changed from a matrox setup where the matroxfb driver would
> initialise any matrox cards found irrespective of whether the BIOS
> decided to do it unless it was told not to. Is there any chance that
> this functionality is going to be added to the radeonfb driver? In
> 2.5/6 perhaps?
If you can get ATI to provide POST code for every single ASIC
rev. out there, that may be a good start.
Ben.
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
next prev parent reply other threads:[~2002-11-12 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 15:28 atyfb and radeonfb Steven Newbury
2002-11-11 9:16 ` Meelis Roos
2002-11-12 23:09 ` Benjamin Herrenschmidt [this message]
2002-11-14 11:09 ` Geert Uytterhoeven
2002-11-21 0:56 ` Steve Longerbeam
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=1037142584.2774.230.camel@zion \
--to=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=steven.newbury1@ntlworld.com \
/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).