From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/src/^(9 boot)^/pc/memory.c
Date: Tue, 17 Sep 2002 18:56:39 -0400 [thread overview]
Message-ID: <61e4f3c55b0993e14dde2692d5b527f3@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 243 bytes --]
Because the code was hideous (the mouse is hideous enough as is) and
because almost all VGAs in use have hardware support.
The mouse needs its Nth complete rethink, given the advent of USB mice.
It's someone else's turn, though.
-rob
[-- Attachment #2: Type: message/rfc822, Size: 1484 bytes --]
From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/src/^(9 boot)^/pc/memory.c
Date: Tue, 17 Sep 2002 18:08:06 -0400
Message-ID: <20020917220806.3872.qmail@g.bio.cse.psu.edu>
| page that it allocates for the hardware cursor.
Can someone remind me why we can't use software cursors in 4e?
next reply other threads:[~2002-09-17 22:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 22:56 rob pike, esq. [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-18 16:46 Charles Forsyth
2002-09-18 11:38 Russ Cox
2002-09-18 23:21 ` paurea
2002-09-18 4:49 Russ Cox
2002-09-18 5:02 ` Lucio De Re
2002-09-18 1:26 Russ Cox
2002-09-18 5:31 ` paurea
2002-09-17 23:13 rob pike, esq.
2002-09-18 4:18 ` Lucio De Re
2002-09-18 16:42 ` rob pike, esq.
2002-09-18 12:08 ` Lucio De Re
2002-09-17 22:58 Russ Cox
2002-09-17 23:41 ` paurea
[not found] <dhog@plan9.bell-labs.com>
2002-09-17 22:04 ` David Gordon Hogan
2002-09-17 22:08 ` Scott Schwartz
2002-09-17 7:57 Charles Forsyth
2002-09-17 15:13 ` Axel Belinfante
2002-09-17 20:08 ` Axel Belinfante
2002-09-17 20:37 ` Axel Belinfante
2002-09-17 4:19 YAMANASHI Takeshi
2002-09-17 2:58 Russ Cox
2002-09-17 2:40 YAMANASHI Takeshi
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=61e4f3c55b0993e14dde2692d5b527f3@plan9.bell-labs.com \
--to=rob@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).