From: "Steven J. Hill" <sjhill@cotw.com>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: machine types for MIPS in ELF file
Date: Wed, 09 May 2001 07:04:48 -0500 [thread overview]
Message-ID: <3AF93260.A9C63FB3@cotw.com> (raw)
In-Reply-To: 3AF843F7.72BC47F0@mvista.com
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.
>
This has bothered me as well. I would like to see a few machines added
at least something like R5000, R8000, R10000 along with the proper ISA
value being stored in the e_flags field. I would be more than happy to
help make the changes as it is something that IMHO needs to be fixed.
As far as the latest ABI specs go, here are 2 different links for the
same documents. Ralf and I went digging for these a few weeks back.
http://www.sco.com/partners/developer/devspecs/
http://www.linuxbase.org/spec/refspecs/
-Steve
--
Steven J. Hill - Embedded SW Engineer
Public Key: 'http://www.cotw.com/pubkey.txt'
FPR1: E124 6E1C AF8E 7802 A815
FPR2: 7D72 829C 3386 4C4A E17D
next prev parent reply other threads:[~2001-05-09 11:56 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
2001-05-10 2:08 ` Ralf Baechle
2001-05-09 12:04 ` Steven J. Hill [this message]
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=3AF93260.A9C63FB3@cotw.com \
--to=sjhill@cotw.com \
--cc=jsun@mvista.com \
--cc=linux-mips@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