From: "Tolentino, Matthew E" <email@example.com>
To: "Pavel Machek" <firstname.lastname@example.org>, "Alan Cox" <email@example.com>
Cc: "Andi Kleen" <firstname.lastname@example.org>, "Greg Stark" <email@example.com>,
"Martin Pool" <firstname.lastname@example.org>,
"Linux Kernel Mailing List" <email@example.com>
Subject: RE: KDB in the mainstream 2.4.x kernels?
Date: Tue, 2 Sep 2003 13:40:31 -0700 [thread overview]
Message-ID: <D36CE1FCEFD3524B81CA12C6FE5BCAB002FFE67A@fmsmsx406.fm.intel.com> (raw)
> > > > 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....
The reason I was asking before was because I've been working on a kernel implementation of the EBC (EFI Byte Code) interpreter so that one could employ the use of the UGA (Universal Graphics Adapter) at OS runtime instead of having to rely on VGA (BIOS or hardware) support. UGA is essentially an EFI driver (aka option ROM) that is intended to be used in pre-OS boot space as well as during OS runtime. When built as an EBC image the driver can be interpreted and thus used on any platform.
The UGA protocols defined in the EFI spec enable the capability to perform the mode switching mentioned above. I hate to keep pointing at ia64, but Tiger systems currently ship with a minimal UGA driver for the embedded ATI controller (this can be seen with the EFI command drivers) and x86 systems with EFI firmware will as well (in addition to traditional VGA support).
Although this doesn't resolve the immediate issue, this might provide the support needed in the future...
next reply other threads:[~2003-09-02 20:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 20:40 Tolentino, Matthew E [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-28 17:08 KDB in the mainstream 2.4.x kernels? Tolentino, Matthew E
2003-08-28 20:24 ` Alan Cox
[not found] <aJIn.firstname.lastname@example.org>
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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.