From: Jun Sun <jsun@mvista.com>
To: Ralf Baechle <ralf@oss.sgi.com>, macro@ds2.pg.gda.pl
Cc: linux-mips@oss.sgi.com
Subject: Re: machine types for MIPS in ELF file
Date: Tue, 08 May 2001 14:20:06 -0700 [thread overview]
Message-ID: <3AF86306.343F53D0@mvista.com> (raw)
In-Reply-To: 20010508164846.A1471@bacchus.dhis.org
Ralf Baechle wrote:
>
> On Tue, May 08, 2001 at 12:07:35PM -0700, Jun Sun wrote:
>
> > The e_machine field in ELF file standard defines two values for MIPS:
> >
> > 8 - MIPS RS3000 BE
> > 10 - MIPS RS4000 BE
> >
> > Naturally the question is: what about LE binaries? And what about other
> > CPUs? Is there any effort to clean up this thing?
> >
> > All the tools that I know of are using 8, pretty much for all CPUs and both
> > endians. No real harm has been observed, but it causes some anonying "invalid
> > byte order" complains if you do "file" on a MIPS LE binary. Of course, it
> > will also invariably reports "R3000" cpu as well.
>
> EM_MIPS_RS4_BE was apparently only in use for a short time; EM_MIPS is
> being used for both byte order. The byteorder is nowadays identified by
> EI_DATA.
>
That makes a lot of sense.
BTW, where is the latest ELF spec that says so? Maciej, which spec are you
referring to?
Jun
next prev parent reply other threads:[~2001-05-08 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 19:07 machine types for MIPS in ELF file Jun Sun
2001-05-08 19:34 ` Maciej W. Rozycki
2001-05-08 19:48 ` Ralf Baechle
2001-05-08 21:20 ` Jun Sun [this message]
2001-05-10 2:08 ` Ralf Baechle
2001-05-09 12:04 ` Steven J. Hill
2001-05-09 13:54 ` Maciej W. Rozycki
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=3AF86306.343F53D0@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
--cc=ralf@oss.sgi.com \
/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