From: Alex deVries <adevries@thepuffingroup.com>
To: Jason Eckhardt <jason@equator.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] booting problems
Date: Fri, 11 Jun 1999 15:37:20 -0400 [thread overview]
Message-ID: <37616570.19DC3853@thepuffingroup.com> (raw)
In-Reply-To: 199906111849.LAA29341@gatekeeper.equator.com
Jason Eckhardt wrote:
>
> > 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.
> >
>
> The bootstrap definately will not work with default data at 0x40000000.
> The HPMC that is occurring is undoubtedly because the data section is there.
Okay, this is the same conclusion I came to. Where should I put both
the data and text sengments?
- Alex
next prev parent reply other threads:[~1999-06-11 19:30 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 [this message]
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
-- 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=37616570.19DC3853@thepuffingroup.com \
--to=adevries@thepuffingroup.com \
--cc=jason@equator.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.