From: "Devon H. O'Dell" <dodell@sitetronics.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] VBE 1.2/2.0+ functions for Plan9
Date: Tue, 30 Nov 2004 11:40:03 +0100 [thread overview]
Message-ID: <41AC4E03.7010004@sitetronics.com> (raw)
In-Reply-To: <74f32320e9b5042e0d79f57b4c38aeca@vitanuova.com>
rog@vitanuova.com wrote:
>>I got some tips to look in Inferno code, since Roger Peppe had
>>implemented a VESA driver there. After looking through the Inferno
>>source, it appears that any VESA code has been left out of the public
>>source.
>
> [snip]
> life would have been much easier if i had been able to figure
> a way of invoking 16-bit BIOS calls from 32-bit real mode,
> but i failed. anyone know how? other systems seem to manage it.
>
> my memory is very rusty, but email me if you want help figuring
> out my crappy code!
>
> cheers,
> rog.
Well, I must admit, I'm not the best assembly developer out there. I've
been taking a look at how DragonFly BSD [1] and NetBSD [2] are doing it
[executing real mode code under protected mode], and I'm having a bit of
trouble understanding how it works.
If somebody with more assembler experience might be able to help me go
through this code to understand what's happening, or would be able to
work on implementing it with me, this would be highly appreciated.
Specifically, I can follow the flow of the code (I'm not completely
hopeless ;)), but I don't understand why certain values and registers
are used in their context.
When this is done, implementing the VBE 1.2/2.0/3.0 functions will be
quite a snap. So, anybody who can give me a hand, I invite you to please
do so! I'm pretty easy to contact for live discussion on most chat
media; see http://www.the-bofh.org/contact.html for a pretty
comprehensive list. Of course, email works too :). Don't be shy!
Kind regards,
Devon H. O'Dell
[1]
http://dragonfly.the-bofh.org/cgi-bin/cvsweb.cgi/src/sys/i386/i386/vm86bios.s?rev=1.12&content-type=text/x-cvsweb-markup
[2]
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/i386/i386/kvm86call.S?rev=1.4&content-type=text/x-cvsweb-markup
next prev parent reply other threads:[~2004-11-30 10:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 16:44 Devon H. O'Dell
2004-11-25 17:13 ` rog
2004-11-25 18:57 ` Devon H. O'Dell
2004-11-29 20:21 ` Jack Johnson
2004-11-30 12:51 ` rog
2004-11-30 10:40 ` Devon H. O'Dell [this message]
2004-11-30 11:08 ` Tiit Lankots
2004-11-30 11:21 ` Devon H. O'Dell
2004-11-30 11:28 ` Tiit Lankots
2004-11-30 11:37 ` Devon H. O'Dell
2004-11-26 3:03 Fwd: " Bob Hartley
2004-11-26 3:04 ` boyd, rounin
2004-11-26 3:08 ` Russ Cox
2004-11-26 4:19 ` Bob Hartley
2004-11-26 5:52 ` Devon H. O'Dell
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=41AC4E03.7010004@sitetronics.com \
--to=dodell@sitetronics.com \
--cc=9fans@cse.psu.edu \
/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).