From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: check of endianess?
Date: Tue, 24 Jan 2006 20:07:53 -0500 [thread overview]
Message-ID: <43D6CF69.1050204@gentoo.org> (raw)
In-Reply-To: <20060124233846.GA10784@deprecation.cyrius.com>
Martin Michlmayr wrote:
> I just compiled a kernel for SGI IP32 and got some very interesting
> results when booting it: 0 MHz CPU, no RAM... Later I found out that
> I made a copy&paste typo in my build script and used mipsel-linux-cc
> to compile. Shouldn't this be detected earlier on?
That actually booted? I thought SGIs were hardwired specifically for BE, and the
prom should've rejected an LE kernel (Granted, there is a jumper on the IP32
board labelled "Big Endian", so it's anyone's guess).
--Kumba
--
Gentoo/MIPS Team Lead
Gentoo Foundation Board of Trustees
"Such is oft the course of deeds that move the wheels of the world: small hands
do them because they must, while the eyes of the great are elsewhere." --Elrond
next prev parent reply other threads:[~2006-01-25 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 23:38 check of endianess? Martin Michlmayr
2006-01-25 1:07 ` Kumba [this message]
2006-01-25 1:38 ` Martin Michlmayr
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=43D6CF69.1050204@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@linux-mips.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