From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux@cthulhu.engr.sgi.com
Subject: FYI newport abscon
Date: Sun, 2 Aug 1998 02:29:07 +0200 [thread overview]
Message-ID: <19980802022907.05519@alpha.franken.de> (raw)
Hi,
yesterday I managed to bring up my Indy with the new console code riped
out from 2.1.109. Today I've implemented new scrolling stuff for newport
abscon, which will give us a really fast console. My simple test program,
which does 1000 printf("\n") in a loop, gives me about 62000 lines/second
on a 160x64 sized console. I also tried that program on my Dual P-233
with a Matrox Millenium and got about 260000 lines/s on a 80x25 sized
console (which is less than 1/5 the size of the Indy console).
My next steps are to bring up hardware cursor and palette stuff. So stay
tuned...
Thomas.
--
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
[Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]
next reply other threads:[~1998-08-02 0:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-02 0:29 Thomas Bogendoerfer [this message]
1998-08-02 4:39 ` FYI newport abscon Alex deVries
1998-08-02 9:27 ` Thomas Bogendoerfer
1998-08-02 9:59 ` ralf
1998-08-02 9:59 ` ralf
1998-08-02 9:52 ` ralf
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=19980802022907.05519@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux@cthulhu.engr.sgi.com \
/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