From: Ralf Baechle <ralf@conectiva.com.br>
To: Dax Kelson <dax@gurulabs.com>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.19-pre2 on Cobalt Qube 2?
Date: Fri, 1 Mar 2002 05:32:38 +0100 [thread overview]
Message-ID: <20020301053238.A32004@dea.linux-mips.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0202281742250.2182-100000@freak.distro.conectiva> <Pine.LNX.4.44.0202282112130.14732-100000@mooru.gurulabs.com>
In-Reply-To: <Pine.LNX.4.44.0202282112130.14732-100000@mooru.gurulabs.com>; from dax@gurulabs.com on Thu, Feb 28, 2002 at 09:18:30PM -0700
On Thu, Feb 28, 2002 at 09:18:30PM -0700, Dax Kelson wrote:
> > Here is 2.4.19-pre2: A very big patch (around 13MB uncompressed) due to
> > the architecture (MIPS and IA64 mainly) updates.
>
> Does this MIPS merge mean that the 2.4.19-pre2 kernel would work on a MIPS
> based Cobalt Qube 2? It that's the case, then I just need a working
> userland.
>
> The official Linux kernel from Cobalt is 2.0 vintage. I'm currently
> running NetBSD 1.5.2 to have something a little more modern, but I would
> like to come back to Linux if possible.
The MIPS merge still isn't complete, this was just the bulk part. So such
I haven't even tried to build let alone test Marcelo's -pre2 kernel. If
you want a 2.4.18 kernel for a Qube, get it via anonymous CVS. See the
MIPS HOWTO at http://oss.sgi.com/mips/mips-howto.html.
Ralf
--
"Embrace, Enhance, Eliminate" - it worked for the pope, it'll work for Bill.
next prev parent reply other threads:[~2002-03-01 4:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 20:50 Linux 2.4.19-pre2 Marcelo Tosatti
2002-02-28 23:19 ` Eyal Lebedinsky
2002-03-01 11:04 ` Jens Axboe
2002-03-01 4:18 ` Linux 2.4.19-pre2 on Cobalt Qube 2? Dax Kelson
2002-03-01 4:32 ` Ralf Baechle [this message]
2002-03-02 2:18 ` Mr. James W. Laferriere
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=20020301053238.A32004@dea.linux-mips.net \
--to=ralf@conectiva.com.br \
--cc=dax@gurulabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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