Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Williams, Eric A" <eawilliams@howard.edu>
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: DHCP/TFTP PROM error (F_magic 0x5330)
Date: Fri, 5 Mar 2004 15:41:58 +0100	[thread overview]
Message-ID: <20040305144158.GA20641@linux-mips.org> (raw)
In-Reply-To: <012CF7B248DA774B8F93F0F6DBC4AB112B0362@davis.howard.edu>

On Thu, Mar 04, 2004 at 12:02:58PM -0500, Williams, Eric A wrote:

> Anyone can give me insight as to what the error means.
> 
> Illegal F_magic number 0x5330, expected MIPSELMAGIC or MIPSEBMAGIC

You're feeding ELF to a machine that is expecting ECOFF binaries.  That's
a very old Indy firmware it seems.

  Ralf

  reply	other threads:[~2004-03-05 14:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04 17:02 DHCP/TFTP PROM error (F_magic 0x5330) Williams, Eric A
2004-03-05 14:41 ` Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-05 18:39 Williams, Eric A

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=20040305144158.GA20641@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=eawilliams@howard.edu \
    --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