From: Chad Carlin <chad@dallas.sgi.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com,
linux-mips@vger.rutgers.edu
Subject: Re: 2.2.1 MIPS kernel sources plus Indy kernel binaries uploaded
Date: Fri, 05 Mar 1999 18:35:41 -0600 [thread overview]
Message-ID: <36E0785D.1758693B@dallas.sgi.com> (raw)
In-Reply-To: 19990227001617.A4022@alpha.franken.de
Thomas,
Anyone else have trouble with these on an R4400? I tried a couple times. Both
stopped the boot process a the "freeing unused memory" part. Sorry there was no
other info.
Regards,
Chad
Thomas Bogendoerfer wrote:
> After syncing my two source trees with CVS, I've exported a tarball
> and uploaded it to
>
> ftp://ftp.linux.sgi.com/pub/linux/mips/test/linux-2.2.1-990226.tar.gz
>
> I've tested compilation for Indy and Olivetti M700 (MIPS Magnum).
>
> I also uploaded a Indy kernel (map and .config file included):
>
> ftp://ftp.linux.sgi.com/pub/linux/mips/test/vmlinux-indy-2.2.1-990226.tar.gz
>
> Thomas.
>
> --
> This device has completely bogus header. Compaq scores again :-|
> It's a host bridge, but it should be called ghost bridge instead ;^)
> [Martin `MJ' Mares on linux-kernel]
--
-----------------------------------------------------
Chad Carlin Special Systems
Silicon Graphics Inc. 972.205.5911
Pager 888.754.1597 VMail 800.414.7994 X5344
chad@sgi.com http://reality.sgi.com/chad
-----------------------------------------------------
"flying through hyper space ain't like dusting crops, boy"
next prev parent reply other threads:[~1999-03-06 0:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-26 23:16 2.2.1 MIPS kernel sources plus Indy kernel binaries uploaded Thomas Bogendoerfer
1999-02-27 4:30 ` gkm
1999-02-27 11:01 ` Thomas Bogendoerfer
[not found] ` <tsbogend@alpha.franken.de>
1999-02-28 22:16 ` Michael Hill
1999-03-01 23:16 ` Thomas Bogendoerfer
1999-03-13 3:23 ` Ulf Carlsson
1999-03-06 0:35 ` Chad Carlin [this message]
1999-03-06 23:06 ` 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=36E0785D.1758693B@dallas.sgi.com \
--to=chad@dallas.sgi.com \
--cc=chad@sgi.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@vger.rutgers.edu \
--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