From: "Kendall Bennett" <KendallB@scitechsoft.com>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Finding Aki M Laukkanen's VESAFBD project?
Date: Mon, 17 Mar 2003 10:22:35 -0800 [thread overview]
Message-ID: <3E75A1EB.8118.1424F41D@localhost> (raw)
In-Reply-To: <1047855538.1251.77.camel@localhost.localdomain>
Antonino Daplas <adaplas@pol.net> wrote:
> > A long time ago in early 2000, Aki M Laukkanen was a guy working on a
> > VESA framebuffer console daemon for Linux. This driver was structured as
> > a as a user land daemon that the kernel vesafb console driver would call
> > back into once the system was up, allowing the userland VESA driver to
> > use the vm86() service to change modes, program the palette and other
> > useful things that can't be done by the basic VESA driver that uses a
> > mode set previously by LILO or GRUB.
>
> That is a very neat project :-) It can also be expanded to
> something not just the VESA driver will use, but as a general
> interface whenever the BIOS services are to be needed.
Yes, it could. It also doesn't need to be used just for VESA/BIOS
services, but could be used to implement real mode fbconsole drivers
using existing driver modules from XFree86 if desired.
> BTW: I want to initialize multiple VGA adapters during the early
> boot sequence. The machine will be in real mode, so there's no
> such thing as copy-on-write. I'm pretty sure it's not possible,
> but do you know of a way to disable the BIOS write protection of
> the C000:0000 segment?
I don't think it is possible to do this because the BIOS is in ROM on the
graphics card. If the system BIOS is shadowing it (quite likely) then it
would be possible, but you would need to know how to disable the write
protection in the system chipset which is probably different for each
motherboard.
The other option is to use the x86emu BIOS emulator project. Then you
don't need to do any of this stuff and instead can warm boot all the
graphics controllers using the BIOS from the card (see the sample
'warmboot' program included in the source code archives). The code is
presently 32-bit specific I believe, so you would have two choices for
running this from real mode - port the code to a 16-bit C compiler or
port it to run in 32-bit real mode. I assume you are probably thinking of
during the boot phase of GRUB or LILO, so at that point you will have
full control and should be able to execute 32-bit real mode code. You may
even be able to put the machine into protected mode and run the code as
32-bit protected mode code also if needed (but you would need to then
write your own protected mode kernel).
The BIOS emulator code is available from:
ftp://ftp.scitechsoft.com/devel/x86emu
I think...
Regards,
---
Kendall Bennett
Chief Executive Officer
SciTech Software, Inc.
Phone: (530) 894 8400
http://www.scitechsoft.com
~ SciTech SNAP - The future of device driver technology! ~
-------------------------------------------------------
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-17 18:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 18:37 Finding Aki M Laukkanen's VESAFBD project? Kendall Bennett
2003-03-14 18:56 ` Jon Smirl
2003-03-14 19:42 ` Kendall Bennett
2003-03-14 20:11 ` Jon Smirl
2003-03-14 22:57 ` Kendall Bennett
2003-03-14 23:22 ` Jon Smirl
2003-03-15 9:52 ` Geert Uytterhoeven
2003-03-17 18:22 ` Kendall Bennett
2003-03-16 23:00 ` Antonino Daplas
2003-03-17 18:22 ` Kendall Bennett [this message]
2003-03-17 21:39 ` Antonino Daplas
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=3E75A1EB.8118.1424F41D@localhost \
--to=kendallb@scitechsoft.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).