All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex deVries <adevries@thepuffingroup.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: law@cygnus.com, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] booting problems
Date: Fri, 11 Jun 1999 13:19:44 -0400	[thread overview]
Message-ID: <37614530.35570847@thepuffingroup.com> (raw)
In-Reply-To: 199906111406.KAA01206@hiauly1.hia.nrc.ca

John David Anglin wrote:
> 
> >   In message <3760CF80.887DA4C3@thepuffingroup.com>you write:
> >   > Okay, I'm a bit better off now.  I've at least located the problem.  I
> >   > copied the IPL straight out of Jason's binary, rebuilt, and it boots.
> >   > The next task is to figure out why the cross compiled version of ipl is
> >   > broken, and how to fix it.
> > It could well be an endianness problem in the ELF tools if that's what you
> > are using to build stuff.
> 
> While there could be an endianness problem, I think it more likely that
> it is how IPL is being linked and extracted into the LIF image.  

I think you're right.  I'm sure now that the byte order isn't a problem,
because my header and Jason's IPL work fine.

> Jason's
> link options, "-R 0 -N", specified a text origin of 0 and data following
> the text.  I think the default for ELF is to place the text at 0x1000 and
> data at 0x40000000.  The gnu ld equivalent for "-R 0" would appear to
> be "-Ttext 0".  I am not sure there is a direct equivalent for "-N".
> Maybe, you could use "-Tdata" to set the data location.  Maps might be
> useful to sort out what is going on.  

Definitely.  This should be the next step in sorting this out.

> Also, the SOM and ELF headers at the
> beginning of each binary may differ in size.  When I tried "-Ttext 0",
> the size of the ELF header seemed to change in size.  I think there
> is info in the header about its size, etc.

I was thinking that object formats wouldn't really matter in the end; in
the end we're doing straight binary with no loading information.

- Alex

  reply	other threads:[~1999-06-11 17:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-10  5:07 [parisc-linux] booting problems Alex deVries
1999-06-10  6:20 ` Kirk Bresniker
1999-06-10  7:21   ` Alex deVries
1999-06-10 15:26     ` Kirk Bresniker
1999-06-10 17:08       ` Stan Sieler
1999-06-10 17:03     ` Stan Sieler
1999-06-10 21:20 ` John David Anglin
1999-06-11  7:36 ` Alex deVries
1999-06-11  8:57 ` Alex deVries
1999-06-11  9:08   ` Jeffrey A Law
1999-06-11 14:06     ` John David Anglin
1999-06-11 17:19       ` Alex deVries [this message]
1999-06-11 18:10         ` Kirk Bresniker
     [not found] <no.id>
1999-06-10 18:32 ` Stan Sieler
  -- strict thread matches above, loose matches on Subject: below --
1999-06-10 21:06 Richard J. Rauenzahn
1999-06-11 18:49 Jason Eckhardt
1999-06-11 19:37 ` Alex deVries
1999-06-12  0:56   ` John David Anglin
1999-06-12  1:25     ` John David Anglin
1999-06-12  3:23     ` John David Anglin
1999-06-12  3:43       ` Jeffrey A Law
1999-06-12  5:10         ` Alex deVries
1999-06-12  5:11           ` Jeffrey A Law
     [not found] <3761F335.ADA76678@thepuffingroup.com>
1999-06-12  6:32 ` Jeffrey A Law
1999-06-12 11:15   ` Alex deVries
1999-06-12 16:57     ` John David Anglin
1999-06-12 18:36       ` Alan Cox
1999-06-12 18:53         ` Jeffrey A Law
1999-06-12 19:36         ` Matthew Wilcox
1999-06-12 21:15           ` Jeffrey A Law
1999-06-12 21:09     ` Jeffrey A Law
1999-06-13 19:10   ` John David Anglin
1999-06-14  0:17     ` Alex deVries
2001-08-31 16:06 James Waterhouse

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=37614530.35570847@thepuffingroup.com \
    --to=adevries@thepuffingroup.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=law@cygnus.com \
    --cc=parisc-linux@thepuffingroup.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.