From: Venkatesh Srinivas <me@acm.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] faster vesa driver
Date: Mon, 15 Jun 2009 22:46:42 -0400 [thread overview]
Message-ID: <f75780240906151946p58d740cah13356ff5ba1923fc@mail.gmail.com> (raw)
In-Reply-To: <4102d6887cbcd68b038d15ac44e4e456@quanstro.net>
> mtrrs work on any number of processors. it is plan 9's
> vesa which does not.
Is this just because the driver uses realmode()? Or is there something else?
To solve the realmode() problem, we could link rsc's 8i into the
kernel and use that to execute the vesa bios code, right?
-- vs
next prev parent reply other threads:[~2009-06-16 2:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 21:18 geoff
2009-06-09 21:26 ` erik quanstrom
2009-06-09 23:29 ` Venkatesh Srinivas
2009-06-09 23:36 ` erik quanstrom
2009-06-09 23:54 ` Kenji Arisawa
2009-06-10 0:22 ` Skip Tavakkolian
2009-06-12 9:26 ` Balwinder S Dheeman
2009-06-12 11:33 ` erik quanstrom
2009-06-12 21:42 ` James Tomaschke
2009-06-16 0:20 ` Kenji Arisawa
2009-06-16 2:19 ` erik quanstrom
2009-06-16 2:46 ` Venkatesh Srinivas [this message]
2009-06-16 3:17 ` Ori Bernstein
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=f75780240906151946p58d740cah13356ff5ba1923fc@mail.gmail.com \
--to=me@acm.jhu.edu \
--cc=9fans@9fans.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).