From: "Kendall Bennett" <KendallB@scitechsoft.com>
To: linux-kernel@vger.kernel.org
Cc: Petr Vandrovec <vandrove@vc.cvut.cz>
Subject: Re: VESA FBconsole driver?
Date: Thu, 13 Mar 2003 15:41:03 -0800 [thread overview]
Message-ID: <3E70A68F.9422.AF1599@localhost> (raw)
In-Reply-To: <20030313221124.GA23719@vana.vc.cvut.cz>
Petr Vandrovec <vandrove@vc.cvut.cz> wrote:
> It was some guy from Finland and I'm under impression that this
> project is dead, because BIOSes were proven to be completely
> unstable in Linux environment.
We have been using the VESA BIOS successfully in user land under Linux
for a long time now, and I would say that the BIOS'es are just as stable
under Linux as under any other platform (you just need to know how to
code around all the screwed up versions out there ;-).
> Try searching linux-fbdev-devel@lists.sourceforge.net archives,
> maybe you'll find something.
Ok, I will look. I tried searching the kernel lists but did not get
anywhere. Don't suppose you recall the name of this project?
> Maybe FreeBSD is too ia32 centric?
Perhaps, but vm86() but it's nature is ia32 specific anyway ;-)
> > Is there any reason why the vm86() services in the Linux kernel cannot be
> > used by other kernel code? Has anyone made an attempt to update the
> > vm86() services to support this?
>
> Why you need it? To run some parts of VGA BIOS? Why you cannot run
> them from userspace task? I think that it is much easier,
> especially now when initramfs is here.
The reason why it would nice is so that the VESA FBconsole driver (and in
fact all the FBconsole drivers that use the real mode BIOS to set an
initial display mode) can restore that mode correctly when an application
exists and restores the console. Right now it is up to the application
program to restore the console, as the kernel has absolutely no way to do
it. If that program has not way to restore it (old SVGALib code for
instance) or the application crashes, you are stuck with a black screen
if you are using a framebuffer console. If the kernel knew how to call
the BIOS to restore the mode, this problem could be completely eliminated
and services could be provided to properly restore the system state when
console graphics programs crash (or the X server for that matter if it
crashes and does not properly clean up).
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! ~
next prev parent reply other threads:[~2003-03-13 23:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 16:07 "Cross" compilation for s390x Pete Zaitcev
2003-03-12 19:07 ` VESA FBconsole driver? Kendall Bennett
2003-03-13 21:31 ` Kendall Bennett
2003-03-13 22:11 ` Petr Vandrovec
2003-03-13 23:41 ` Kendall Bennett [this message]
2003-03-14 10:14 ` Geert Uytterhoeven
2003-03-14 18:25 ` Kendall Bennett
2003-03-14 10:21 ` Helge Hafting
2003-03-13 22:24 ` Gerd Knorr
2003-03-13 23:41 ` Kendall Bennett
2003-03-14 10:15 ` Helge Hafting
2003-03-14 18:25 ` Kendall Bennett
2003-03-15 18:04 ` Helge Hafting
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=3E70A68F.9422.AF1599@localhost \
--to=kendallb@scitechsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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