From: Steve Longerbeam <stevel@mvista.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Steven Newbury <steven.newbury1@ntlworld.com>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: atyfb and radeonfb
Date: Wed, 20 Nov 2002 16:56:16 -0800 [thread overview]
Message-ID: <3DDC2F30.6040709@mvista.com> (raw)
In-Reply-To: Pine.GSO.4.21.0211141209250.8876-100000@vervain.sonytel.be
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
Geert Uytterhoeven wrote:
>On 13 Nov 2002, Benjamin Herrenschmidt wrote:
>
>
>>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 ;)
>>
>>
>
>Erhm, not really...
>
>For RAGE XL support, you want to contact Steve Longerbeam <stevel@mvista.com>.
>
I reverse-engineered ATI's video BIOS on the Xpert98 PCI card (RageXL) using
a PCI bus analyzer. Got atyfb to work on embedded platforms and PC's
that way.
It could work with other RageXL-based cards with some tweaking. I'll
give you the
source if you're interested.
--
Steve Longerbeam
MontaVista Software, Inc.
office:408-328-9008, fax:408-328-3875
http://www.mvista.com
[-- Attachment #2: Type: text/html, Size: 1730 bytes --]
prev parent reply other threads:[~2002-11-21 0:56 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
2002-11-14 11:09 ` Geert Uytterhoeven
2002-11-21 0:56 ` Steve Longerbeam [this message]
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=3DDC2F30.6040709@mvista.com \
--to=stevel@mvista.com \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.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).