All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Andi Kleen <ak@colin2.muc.de>
Cc: Martin Pool <mbp@sourcefrog.net>, Andi Kleen <ak@muc.de>,
	linux-kernel@vger.kernel.org
Subject: Re: KDB in the mainstream 2.4.x kernels?
Date: 25 Aug 2003 08:16:41 -0400	[thread overview]
Message-ID: <87y8xiexue.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <20030813110453.GA26019@colin2.muc.de>


Andi Kleen <ak@colin2.muc.de> writes:

> Only the X server can switch away, because only it knows how 
> to talk to the graphic chipset. And running user space here is 
> far too risky.

There was a proposal a long ways back to allow X to download instructions to
the kernel on how to restore the video mode. The proposal was to code the
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.

-- 
greg


  reply	other threads:[~2003-08-25 12:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <aJIn.3mj.15@gated-at.bofh.it>
2003-07-18 20:43 ` KDB in the mainstream 2.4.x kernels? 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 [this message]
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-09-02 20:40 Tolentino, Matthew E
  -- strict thread matches above, loose matches on Subject: below --
2003-08-28 17:08 Tolentino, Matthew E
2003-08-28 20:24 ` Alan Cox
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=87y8xiexue.fsf@stark.dyndns.tv \
    --to=gsstark@mit.edu \
    --cc=ak@colin2.muc.de \
    --cc=ak@muc.de \
    --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.