From: Pavel Machek <pavel@ucw.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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: Sat, 30 Aug 2003 12:35:23 +0200 [thread overview]
Message-ID: <20030830103523.GA386@elf.ucw.cz> (raw)
In-Reply-To: <1061992194.22739.18.camel@dhcp23.swansea.linux.org.uk>
Hi!
> > > 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
We could make them use code for ACPI interpretter, that's already in
and has advantage that graphics people might eventually ship it in
card roms....
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-08-30 10:45 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
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 [this message]
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=20030830103523.GA386@elf.ucw.cz \
--to=pavel@ucw.cz \
--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.