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

On Sun, Aug 02, 1998 at 11:27:12AM +0200, Thomas Bogendoerfer wrote:

> 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.

>From the next week on I'll spend allmost all my time again on Linux, so
if there it is possible to convince Linux to accept our patches, then we
can make it.

> > 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:-)

How true.  Also the old console is very buggy.  When using the driver for
the Linux console aa plain doesn't work.

(And who says one needs stinking X for c0o/_ D3m0z ;-)

  Ralf

WARNING: multiple messages have this Message-ID (diff)
From: ralf@uni-koblenz.de
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Alex deVries <adevries@engsoc.carleton.ca>, linux@cthulhu.engr.sgi.com
Subject: Re: FYI newport abscon
Date: Sun, 2 Aug 1998 11:59:05 +0200	[thread overview]
Message-ID: <19980802115905.12081@uni-koblenz.de> (raw)
Message-ID: <19980802095905._Qz7ts6GhHA8R9QMA-ogWG-ingIK-oSdN0sG_bKfgwc@z> (raw)
In-Reply-To: <19980802112712.38261@alpha.franken.de>; from Thomas Bogendoerfer on Sun, Aug 02, 1998 at 11:27:12AM +0200

On Sun, Aug 02, 1998 at 11:27:12AM +0200, Thomas Bogendoerfer wrote:

> 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.

From the next week on I'll spend allmost all my time again on Linux, so
if there it is possible to convince Linux to accept our patches, then we
can make it.

> > 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:-)

How true.  Also the old console is very buggy.  When using the driver for
the Linux console aa plain doesn't work.

(And who says one needs stinking X for c0o/_ D3m0z ;-)

  Ralf

  reply	other threads:[~1998-08-02  9:59 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 [this message]
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=19980802115905.12081@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