From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: FYI newport abscon
Date: Sun, 2 Aug 1998 11:27:12 +0200 [thread overview]
Message-ID: <19980802112712.38261@alpha.franken.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.
yes, and that's my primary goal. The closer we get to the current 2.1.x
kernel, the better we can merge our changes into Linus tree. And this is
the best thing to let people see, that the MIPS port is still alive.
> 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.
:-) As I only speeded up scrolling time, it won't make any difference for
aalib. But sitting in front of a fast console you get the impression, that
the machine flys:-)
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 prev parent reply other threads:[~1998-08-02 9:36 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 [this message]
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=19980802112712.38261@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=adevries@engsoc.carleton.ca \
--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