From: Klaus Naumann <kernel@mgnet.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4 on Cobalt MiPS servers
Date: Thu, 09 Nov 2000 14:52:38 +0100 [thread overview]
Message-ID: <3A0AAC26.3BE421F9@mgnet.de> (raw)
Jason Fayre wrote:
> Hello,
> Does the 2.4 series compile on Cobalt Networks MIPS-based servers? There
> is a cobalt directory under the arch/mips directory.
Hi, I don't think so since the last things I have heard from
this are a while back. You may want to join the linux-mips@oss.sgi.com
mailinglist for further questions.
Also you can take a look at irc.openprojects.net / #mipslinux at
late UTC times :)
HTH, Klaus
--
Klaus Naumann (mailto:kernel@mgnet.de)
http://www.mgnet.de/
Phone: ++49/8761727852
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-09 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 13:52 Klaus Naumann [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-09 1:30 Linux 2.4 on Cobalt MiPS servers Jason Fayre
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=3A0AAC26.3BE421F9@mgnet.de \
--to=kernel@mgnet.de \
--cc=linux-kernel@vger.kernel.org \
/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