All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tolentino, Matthew E" <matthew.e.tolentino@intel.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>, "Andi Kleen" <ak@muc.de>
Cc: "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: Thu, 28 Aug 2003 10:08:50 -0700	[thread overview]
Message-ID: <D36CE1FCEFD3524B81CA12C6FE5BCAB002FFE662@fmsmsx406.fm.intel.com> (raw)

> On Llu, 2003-08-25 at 17:23, Andi Kleen wrote:
> > > instructions as a forth program that frobbed registers 
> appropriately. The
> > > kernel would have a small forth interpretor to run it. 
> Then switching
> > > resolutions could happen safely in the kernel.
> > 
> > Did the proposal come with working code?
> 
> 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? 

matt

             reply	other threads:[~2003-08-28 17:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28 17:08 Tolentino, Matthew E [this message]
2003-08-28 20:24 ` KDB in the mainstream 2.4.x kernels? Alan Cox
  -- 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=D36CE1FCEFD3524B81CA12C6FE5BCAB002FFE662@fmsmsx406.fm.intel.com \
    --to=matthew.e.tolentino@intel.com \
    --cc=ak@muc.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gsstark@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.