From: Jon Smirl <jonsmirl@yahoo.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Stefan Reinauer <stepan@suse.de>,
fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Rage128 as secondary adapter
Date: Fri, 10 Jan 2003 11:40:49 -0800 (PST) [thread overview]
Message-ID: <20030110194049.21039.qmail@web14904.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301101930030.18287-100000@phoenix.infradead.org>
--- James Simmons <jsimmons@infradead.org> wrote:
> So it is a matter of time before they will release
> this info.
>
If you can get me the info, I will do the work. I own
both Rage and Radeon cards so I can do some testing.
I'll also add DDC support if they'll give me that
info.
I spent last night disassembling their ROMs. The reset
procedure is not too difficult. But I would much
rather do it with support from ATI documentation. It
is easy to misinterpret a disassembly.
Do you have a personal contact there? Maybe they can
be convinced to publicly release documentation for
their older products. I'm sure NVidia doesn't care how
the Rage chip works any more. It would make a good PR
release about ATI being a community citizen. It would
also free their developer relations group from
hassling with open source developers on older cards.
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
prev parent reply other threads:[~2003-01-10 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 17:47 Rage128 as secondary adapter Jon Smirl
2003-01-09 18:39 ` Stefan Reinauer
2003-01-09 18:56 ` Jon Smirl
2003-01-10 19:31 ` James Simmons
2003-01-10 19:40 ` Jon Smirl [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=20030110194049.21039.qmail@web14904.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=stepan@suse.de \
/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).