From: Ralf Baechle <ralf@cobaltmicro.com>
To: miguel@nuclecu.unam.mx (Miguel de Icaza)
Cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: Re: More Linux/SGI status
Date: Tue, 7 Oct 1997 16:28:07 -0700 (PDT) [thread overview]
Message-ID: <199710072328.QAA17826@dull.cobaltmicro.com> (raw)
In-Reply-To: <199710072241.RAA01259@athena.nuclecu.unam.mx> from "Miguel de Icaza" at Oct 7, 97 05:41:38 pm
Hi,
> Ralf's fixes to the dynamic linker fixed the Xt applications. Now,
> only the PAM remains to be fixed.
The PAM problem is also a dynamic linker problem. It's (I hope) one the
last major showstopper class bugs that prevent just building a
Linux/MIPS distribution from 95% unchanged source packages - and
fullfilling all the promises to those loading hardware to me ...
Btw, I stopped the mega load test (Running many compilers and tools in
parallel) I posted recently after some more hours because the machine ran
out of swap, some processes died therefore and load < 100 isn't that
interesting ...
System call latencies were pretty lousy bad for MIPS kernel because
we were using a syscall handler written in C. I rewrote the entire
thing in assembler and now we're as fast as a MMX Pentium accounting
for the different clock rates. Pretty nice, because we actually have
to save/restore many more registers and deal with a more complex
system call convention. Seven nops left to eleminate ...
> So, where do we stand now? So, the only bits missing now are:
>
> 1. me finishing the support for the X server. just a hack
> here and there.
>
> 1.b. Getting the other important bits of the RRM code in the
> kernel.
>
> 2. me fixing the mouse.
>
> 3. Would it be possible to negotiate with SGI management
> the posibility of shipping the IRIX runtime libraries and
> the X server as found on IRIX with a Linux disrtibution?
Bad point in time, it has been pointed out to me that SGI's stock
was doing pretty bad ;-)
> 4. A nice, easy-to use install program. Taking the existing
> Red Hat/Mustand install program and port it should be
> pretty easy.
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@cobaltmicro.com>
To: Miguel de Icaza <miguel@nuclecu.unam.mx>
Cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: Re: More Linux/SGI status
Date: Tue, 7 Oct 1997 16:28:07 -0700 (PDT) [thread overview]
Message-ID: <199710072328.QAA17826@dull.cobaltmicro.com> (raw)
Message-ID: <19971007232807.tudnsE6eaFVgWZgowTmBFvsqBhTFbUYKVczwDZJlqBs@z> (raw)
In-Reply-To: <199710072241.RAA01259@athena.nuclecu.unam.mx> from "Miguel de Icaza" at Oct 7, 97 05:41:38 pm
Hi,
> Ralf's fixes to the dynamic linker fixed the Xt applications. Now,
> only the PAM remains to be fixed.
The PAM problem is also a dynamic linker problem. It's (I hope) one the
last major showstopper class bugs that prevent just building a
Linux/MIPS distribution from 95% unchanged source packages - and
fullfilling all the promises to those loading hardware to me ...
Btw, I stopped the mega load test (Running many compilers and tools in
parallel) I posted recently after some more hours because the machine ran
out of swap, some processes died therefore and load < 100 isn't that
interesting ...
System call latencies were pretty lousy bad for MIPS kernel because
we were using a syscall handler written in C. I rewrote the entire
thing in assembler and now we're as fast as a MMX Pentium accounting
for the different clock rates. Pretty nice, because we actually have
to save/restore many more registers and deal with a more complex
system call convention. Seven nops left to eleminate ...
> So, where do we stand now? So, the only bits missing now are:
>
> 1. me finishing the support for the X server. just a hack
> here and there.
>
> 1.b. Getting the other important bits of the RRM code in the
> kernel.
>
> 2. me fixing the mouse.
>
> 3. Would it be possible to negotiate with SGI management
> the posibility of shipping the IRIX runtime libraries and
> the X server as found on IRIX with a Linux disrtibution?
Bad point in time, it has been pointed out to me that SGI's stock
was doing pretty bad ;-)
> 4. A nice, easy-to use install program. Taking the existing
> Red Hat/Mustand install program and port it should be
> pretty easy.
Ralf
next prev parent reply other threads:[~1997-10-07 23:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-07 22:41 More Linux/SGI status Miguel de Icaza
1997-10-07 23:28 ` Ralf Baechle [this message]
1997-10-07 23:28 ` Ralf Baechle
1997-10-07 23:56 ` Ariel Faigon
1997-10-07 23:56 ` Ariel Faigon
1997-10-08 7:39 ` Alan Cox
1997-10-08 17:46 ` William J. Earl
1997-10-08 17:46 ` William J. Earl
1997-10-08 0:30 ` William J. Earl
1997-10-08 7:32 ` Alan Cox
1997-10-08 7:32 ` Alan Cox
1997-10-16 4:48 ` Ralf Baechle
1997-10-16 13:07 ` Eric Kimminau
1997-10-16 15:39 ` Alex deVries
1997-10-16 19:08 ` Alan Cox
1997-10-16 19:08 ` Alan Cox
1997-10-16 20:16 ` Alex deVries
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=199710072328.QAA17826@dull.cobaltmicro.com \
--to=ralf@cobaltmicro.com \
--cc=linux-mips@fnet.fr \
--cc=linux@cthulhu.engr.sgi.com \
--cc=miguel@nuclecu.unam.mx \
/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