From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Harvard and Von Neumann Architectures and Unix
Date: Sat, 25 Nov 2017 09:24:24 -0500 (EST) [thread overview]
Message-ID: <20171125142424.3518A18C0D9@mercury.lcs.mit.edu> (raw)
> From: Doug McIlroy
> Optimal code for bitblt (raster block transfers) in the Blit
Interesting case. I'm not familiar with BitBLT codes, do they actually modify
the existing program, or rather do they build small custom ones? Only the
former is what I was thinking of.
Noel
next reply other threads:[~2017-11-25 14:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 14:24 Noel Chiappa [this message]
2017-11-25 15:58 ` Lawrence Stewart
2017-11-25 16:10 ` Lars Brinkhoff
2017-11-25 19:59 ` Steve Simon
2017-11-25 21:59 ` Bakul Shah
-- strict thread matches above, loose matches on Subject: below --
2017-11-27 17:11 Noel Chiappa
2017-11-28 0:23 ` Dave Horsfall
2017-11-27 16:11 Noel Chiappa
2017-11-27 16:50 ` Larry McVoy
2017-11-27 17:08 ` Clem Cole
2017-11-27 18:21 ` Lawrence Stewart
2017-11-27 18:30 ` Lars Brinkhoff
2017-11-27 18:14 ` Warner Losh
2017-11-27 18:26 ` Paul Winalski
2017-11-27 17:35 ` Ian Zimmerman
2017-11-28 14:55 ` Tim Bradshaw
2017-11-28 19:45 ` Paul Winalski
2017-11-25 17:34 Doug McIlroy
2017-11-25 3:14 Doug McIlroy
2017-11-25 4:16 ` Jon Steinhart
2017-11-25 5:17 ` ron minnich
2017-11-25 14:23 ` Ralph Corderoy
2017-11-24 21:43 Noel Chiappa
2017-11-24 21:50 ` Jon Steinhart
2017-11-25 21:55 ` William Cheswick
2017-11-25 23:15 ` Dave Horsfall
2017-11-24 22:20 ` Mike Markowski
2017-11-24 22:31 ` Dave Horsfall
2017-11-24 19:25 Will Senn
2017-11-24 19:28 ` Jon Steinhart
2017-11-27 14:50 ` Tony Finch
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=20171125142424.3518A18C0D9@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.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).