linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Reinauer <stepan@suse.de>
To: Jon Smirl <jonsmirl@yahoo.com>,
	fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Rage128 as secondary adapter
Date: Thu, 9 Jan 2003 19:39:21 +0100	[thread overview]
Message-ID: <20030109183921.GB21501@suse.de> (raw)
In-Reply-To: <20030109174706.1471.qmail@web14907.mail.yahoo.com>

* Jon Smirl <jonsmirl@yahoo.com> [030109 18:47]:
> Can someone with access to the Rage128 documentation
> tell me how to do this from protected mode? I have the
> ROM mapped so the code can get to constants stored in
> the ROM. What I need is a piece of C code equal to
> what the ROM initialization does minus the part about
> Int10 vector setup.
 
I'm almost certain that the information you need is only
available when signing an NDA and thus could not be used
in open source drivers. Also a big problem for open source
firmware implementations such as openbios

> The programmers at ATI probably have a piece of code
> available to do this since ATI's Windows driver can do
> it.  I've tried emailing and signing up as a developer
> without response.
 
This is a pretty common experience.

Stefan.

-- 
The use of COBOL cripples the mind; its teaching should, therefore, be
regarded as a criminal offense.                      -- E. W. Dijkstra


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

  reply	other threads:[~2003-01-09 18:39 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 [this message]
2003-01-09 18:56   ` Jon Smirl
2003-01-10 19:31     ` James Simmons
2003-01-10 19:40       ` Jon Smirl

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=20030109183921.GB21501@suse.de \
    --to=stepan@suse.de \
    --cc=jonsmirl@yahoo.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).