From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Tolentino, Matthew E" <matthew.e.tolentino@intel.com>
Cc: Andi Kleen <ak@muc.de>, Greg Stark <gsstark@mit.edu>,
Martin Pool <mbp@sourcefrog.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: KDB in the mainstream 2.4.x kernels?
Date: 28 Aug 2003 21:24:39 +0100 [thread overview]
Message-ID: <1062102278.24978.52.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <D36CE1FCEFD3524B81CA12C6FE5BCAB002FFE662@fmsmsx406.fm.intel.com>
On Iau, 2003-08-28 at 18:08, Tolentino, Matthew E wrote:
> > I've seen workable non forth versions of the proposal yes. It isnt
> > actually that hard to do for most video cards
>
> Interesting. So did the interpreted forth (or other) program then interact with the VGA BIOS or was it more generic?
It consisted simply of a list of in/out values. Thats sufficient for
most cards it turned out. It expected the X server to dump the sequence
of values to the kernel.
A BIOS32/ACPI/whatever is currently trendy service to save/restore video
states would actually be a real help to a lot of things. I guess the
perfect would API would support something like
SaveCurrentMode
SetMode (some properties)
GetLinearFBDetails()
RestoreSavedMode
LoadColor() [for 8bit modes]
ie roughly what vesa bios provides. Given the cost of executing a
virtual machine like ACPI its less clear if cards could describe
basic acceleration this way, at least if it was something like ACPI
or forth which is hard to compile. A bytecode description that can
be turned into native code obviously has different properties.
next prev parent reply other threads:[~2003-08-28 20:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 17:08 KDB in the mainstream 2.4.x kernels? Tolentino, Matthew E
2003-08-28 20:24 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-02 20:40 Tolentino, Matthew E
[not found] <aJIn.3mj.15@gated-at.bofh.it>
2003-07-18 20:43 ` Andi Kleen
2003-07-19 0:31 ` linas
2003-07-19 0:57 ` Andi Kleen
2003-07-20 12:55 ` Keith Owens
2003-07-20 13:31 ` David S. Miller
2003-07-20 22:27 ` Keith Owens
2003-07-21 15:06 ` Andi Kleen
2003-07-29 19:44 ` Robin Holt
2003-08-13 4:40 ` Martin Pool
2003-08-13 11:04 ` Andi Kleen
2003-08-25 12:16 ` Greg Stark
2003-08-25 16:23 ` Andi Kleen
2003-08-26 13:39 ` Greg Stark
2003-08-27 13:49 ` Alan Cox
2003-08-30 10:35 ` Pavel Machek
2003-07-18 20:06 linas
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=1062102278.24978.52.camel@dhcp23.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ak@muc.de \
--cc=gsstark@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=mbp@sourcefrog.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).