From: Antonino Daplas <adaplas@pol.net>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: James Simmons <jsimmons@infradead.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Reading the EDID block for x86 machines
Date: 12 Mar 2003 07:02:37 +0800 [thread overview]
Message-ID: <1047423718.1128.160.camel@localhost.localdomain> (raw)
In-Reply-To: <20030311225407.15850.qmail@web14905.mail.yahoo.com>
On Wed, 2003-03-12 at 06:54, Jon Smirl wrote:
> --- Antonino Daplas <adaplas@pol.net> wrote:
> > On Wed, 2003-03-12 at 06:05, Jon Smirl wrote:
> > > If your in messing with the early boot sequence,
> > why
> > > don't you make the kernel initialize all of the
> > video
> > > cards in the system instead of only the primary
> > one.
> >
> > Because I don't know how to :)? It basically just
> > involves a far call
> > no, if we know where the VBIOS code actually starts?
>
> It is more complicated. You need to call the PCI Bios
> to find the video cards by their PCI class. There is
> already code in the kernel that calls PCIBios.
> arch/i386/pci/*
>
> Then you need to one by one map their ROMs (via PCI
> config registers) into C000:0 and call C000:3. But as
> you swap out the other adapters you need to disable
> their VGA emulation as there can only be on VGA device
> per system. By default the VBIOS code will enable VGA
> emulation on all of the adapters and they won't. You
> also need to record the INT vectors and make sure they
> get set back to the primary ones.
>
Yikes! No, it can't be done this way. During the early boot sequence,
the kernel is not yet decompressed and loaded, so all the services the
kernel provides are still unavailable. Unless you want to walk, detect,
enable, etc the PCI subsystem in pure 16-bit assembly...
Tony
-------------------------------------------------------
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 prev parent reply other threads:[~2003-03-11 23:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 12:49 Reading the EDID block for x86 machines Antonino Daplas
2003-03-11 15:49 ` James Simmons
2003-03-11 20:07 ` Antonino Daplas
2003-03-11 21:33 ` Antonino Daplas
2003-03-11 21:47 ` Antonino Daplas
2003-03-11 22:05 ` Jon Smirl
2003-03-11 22:33 ` Antonino Daplas
2003-03-11 22:54 ` Jon Smirl
2003-03-11 23:02 ` Antonino Daplas [this message]
2003-03-11 23:42 ` Jon Smirl
2003-03-12 17:38 ` Antonino Daplas
2003-03-12 18:16 ` Jon Smirl
2003-03-12 22:38 ` Antonino Daplas
2003-03-12 23:36 ` Jon Smirl
2003-03-12 23:47 ` Jon Smirl
2003-03-13 6:50 ` Geert Uytterhoeven
2003-03-13 15:42 ` Jon Smirl
2003-03-16 23:00 ` Antonino Daplas
2003-03-17 4:00 ` Jon Smirl
2003-03-17 7:00 ` Antonino Daplas
2003-03-17 19:33 ` Jon Smirl
2003-03-17 21:38 ` Antonino Daplas
2003-03-17 22:02 ` Jon Smirl
2003-03-17 22:29 ` Antonino Daplas
2003-03-17 23:41 ` Jon Smirl
2003-03-18 9:06 ` Geert Uytterhoeven
2003-03-18 10:00 ` Antonino Daplas
2003-03-18 17:07 ` Jon Smirl
2003-03-19 5:15 ` Antonino Daplas
2003-03-19 6:07 ` Jon Smirl
2003-03-18 0:00 ` Jon Smirl
2003-03-11 23:54 ` Jon Smirl
2003-03-12 12:10 ` Ville Syrjälä
2003-03-12 17:38 ` Antonino Daplas
2003-03-12 18:47 ` Ville Syrjälä
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=1047423718.1128.160.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=jonsmirl@yahoo.com \
--cc=jsimmons@infradead.org \
--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).