Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Alex deVries <adevries@thepuffingroup.com>
To: law@cygnus.com
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
	jason@equator.com, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] booting problems
Date: Sat, 12 Jun 1999 01:10:08 -0400	[thread overview]
Message-ID: <3761EBB0.26A1931C@thepuffingroup.com> (raw)
In-Reply-To: 21640.929159013@upchuck.cygnus.com

Jeffrey A Law wrote:
> 
>   In message <199906120323.XAA29685@hiauly1.hia.nrc.ca>you write:
>   > image.  Finally, the .PARISC.unwind and .PARISC.symext must be
>   > loaded to the correct locations in the LIF image.
> You can throw away the unwind & symext sections.  While one day you might want
> the unwinders in your lif image, you'll never want the symext.
> 
> In the ELF tools, you shouldn't never end up with anything in $CODE$.  If
> you do, that's a bug in either the compiler or the assembler.  It should
> have mapped $CODE$ into .text.

Okay.  So this means there's a problem with the GNU ld code. Jeff, do
you know approximately where within the ld code we should be looking to
fix this?

I confess I'm starting to get a little lost with the segment placings. 
Everything I'm trying is producing nothing at all.  The latest I've
tried is linking with:

parisc-linux-ld -m hppaelf -Ttext 0x1000 -N -s \
     ipl_s.o ipl_c.o rom_interface.o ../../../lib/milli.o -o ipl

You can inspect this kernel, it's at
ftp://puffin.external.hp.com/pub/parisc/binaries/kernels/Image-19990612-1

The IPL starts at 0x1000.

It would be very helpful to get a PIM dump as Kirk had provided earlier.

- Alex

  reply	other threads:[~1999-06-12  5:02 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-11 18:49 [parisc-linux] booting problems 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 [this message]
1999-06-12  5:11           ` Jeffrey A Law
  -- strict thread matches above, loose matches on Subject: below --
2001-08-31 16:06 James Waterhouse
     [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
1999-06-10 21:06 Richard J. Rauenzahn
     [not found] <no.id>
1999-06-10 18:32 ` Stan Sieler
1999-06-10  5:07 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
1999-06-11 18:10         ` Kirk Bresniker

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=3761EBB0.26A1931C@thepuffingroup.com \
    --to=adevries@thepuffingroup.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=jason@equator.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox