From: Jon Smirl <jonsmirl@yahoo.com>
To: Brad Douglas <brad@neruo.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Rage1128
Date: Tue, 14 Jan 2003 13:59:47 -0800 (PST) [thread overview]
Message-ID: <20030114215947.28884.qmail@web14908.mail.yahoo.com> (raw)
In-Reply-To: <1042579023.20959.14.camel@12-235-123-161.client.attbi.com>
--- Brad Douglas <brad@neruo.com> wrote:
> ATI does not give out initialization information
> about their chipsets.
I got one email from them offering me the Rage128 SDK.
Since then I haven't heard anything. I don't know if
the SDK has the needed info.
I see that the cards can vary in type and amount of
VRAM. But this info must be in the ROM or a register
somewhere. The ROM code needs to read this info from
somewhere at boot time. I was hoping the the
protected mode code could get this info out of the
ROM too.
I found this at Rage Underground:
The simple answer is that you should NOT flash your
Rage128 BIOS! The reason is that there are over 50
revisions of the Rage 128 card.
Do you think ATI can provide the info needs for
writing an init routine that can handle the 50
variations? Has ATI written a unified Rage128 BIOS
that will work in all the cards? I have a hard time
imagining that they are keeping 50 separate source
code projects for the BIOS.
Another solution to this would be to modify the kernel
to initialize secondary video cards via Int10 very
early in the boot process; before it gets so hard to
get into vm86 mode. This would still leave DDC without
a solution. Has anyone tried this approach?
=====
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: Take your first step towards giving
your online business a competitive advantage. Test-drive a Thawte SSL
certificate - our easy online guide will show you how. Click here to get
started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en
prev parent reply other threads:[~2003-01-14 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 19:34 Rage1128 Jon Smirl
2003-01-14 21:17 ` Rage1128 Brad Douglas
2003-01-14 21:59 ` 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=20030114215947.28884.qmail@web14908.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=brad@neruo.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).