From: Jon Smirl <jonsmirl@yahoo.com>
To: Antonino Daplas <adaplas@pol.net>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: real mode entry points for PCI BIOS
Date: Tue, 11 Mar 2003 18:42:24 -0800 (PST) [thread overview]
Message-ID: <20030312024224.82402.qmail@web14908.mail.yahoo.com> (raw)
http://www.delorie.com/djgpp/doc/rbinter/ix/1A/B1.html
The class for video displays is 3
It should be possible to make this work. Do you have a
PCI video card that you can install along with an AGP
one? Future PCI-X allows as many video cards as you
want so we need something along these lines. This
would also solve a lot of problems in framebuffer
development.
The reset program I sent earlier shows how to disable
VGA ports and copy INT vectors, etc. It also shows how
to enable the ROMs (writing to PCI config space).
Video ROMs needs to be copied to RAM before being
executed or they won't run. The BIOS did this to the
primary adapter's ROM for you.
Is it possible to allocate an entire page for DDC
info? At 512 bytes that would support eight video
cards. When the framebuffer driver loads how is it
going to find the page with the DDC info? How does it
know which info goes to which card?
This approach should work crossplatform. The
equivalent code will need to be written for each architecture.
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - establish your business online
http://webhosting.yahoo.com
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
next reply other threads:[~2003-03-12 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 2:42 Jon Smirl [this message]
2003-03-12 3:30 ` Decoding DDC/EDID 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=20030312024224.82402.qmail@web14908.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=adaplas@pol.net \
--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).