Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ralf@uni-koblenz.de
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	linux@cthulhu.engr.sgi.com
Subject: Re: FYI newport abscon
Date: Sun, 2 Aug 1998 11:52:53 +0200	[thread overview]
Message-ID: <19980802115253.04102@uni-koblenz.de> (raw)
In-Reply-To: <Pine.LNX.3.95.980802003721.4859A-100000@lager.engsoc.carleton.ca>; from Alex deVries on Sun, Aug 02, 1998 at 12:39:37AM -0400

On Sun, Aug 02, 1998 at 12:39:37AM -0400, Alex deVries wrote:

> On Sun, 2 Aug 1998, Thomas Bogendoerfer wrote:
> > 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. 
> 
> This is very, very cool, and much needed to go on with 2.1.x kernel
> development.  
> 
> > 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).
> > 
> 
> Well, this is very cool.  What kind of use is this?  aalib... man, that'll
> be neat.  To hell with X when you have aalib.

Is there MesaGL support for aalib ;-)

Actually aalib is already performing pretty nicely on the old console.
However the ``linux'' driver doesn't work right due to some console bug;
one has to use the slang driver.  So aa is more a test of the correctness
than the performance.

  Ralf

      parent reply	other threads:[~1998-08-02  9:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-02  0:29 FYI newport abscon Thomas Bogendoerfer
1998-08-02  4:39 ` 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 [this message]

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=19980802115253.04102@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=adevries@engsoc.carleton.ca \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=tsbogend@alpha.franken.de \
    /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