All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Martin Michlmayr <tbm@cyrius.com>,
	linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: [patch] swarm-cs4297a: Support little-endian configuration
Date: Mon, 5 Apr 2004 10:55:35 -0700	[thread overview]
Message-ID: <20040405105535.D13322@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.55.0404051457010.31851@jurand.ds.pg.gda.pl>; from macro@ds2.pg.gda.pl on Mon, Apr 05, 2004 at 03:01:19PM +0200

On Mon, Apr 05, 2004 at 03:01:19PM +0200, Maciej W. Rozycki wrote:
> On Mon, 5 Apr 2004, Martin Michlmayr wrote:
> 
> > Are you using their boot loader (sibyl), and did you notice it has
> > problems in little-endian?  (IF so, do you have patches?  ;-)  Also,
> > have you been able to compile sibyl against a normal e2fslibs rather
> > than their custom version?
> 
>  I boot kernels directly (a bit dissatisfied with no ELF64 support in CFE,
> but that can be fixed, I suppose) over the network, so I can't help you
> with your problems, sorry.
>

I have been using objcopy to convert ELF64 to ELF32 and then boot through 
CFE (suggested by Drow).  This seems to be working fine.

I have also used a LE version sibyl before and did not notice any problem.
I think that version is a binary from broadcom.

Jun

  reply	other threads:[~2004-04-05 17:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05 11:09 [patch] swarm-cs4297a: Support little-endian configuration Maciej W. Rozycki
2004-04-05 12:54 ` Martin Michlmayr
2004-04-05 13:01   ` Maciej W. Rozycki
2004-04-05 17:55     ` Jun Sun [this message]
2004-04-05 18:12       ` Maciej W. Rozycki
2004-04-05 18:28         ` Mitch Lichtenberg
2004-04-06 13:15           ` 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=20040405105535.D13322@mvista.com \
    --to=jsun@mvista.com \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=tbm@cyrius.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.