Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <Matthew.Wilcox@genedata.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
	adevries@thepuffingroup.com, law@cygnus.com,
	parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] booting problems
Date: Sat, 12 Jun 1999 21:36:49 +0200	[thread overview]
Message-ID: <19990612213649.Y31472@mencheca.ch.genedata.com> (raw)
In-Reply-To: <E10sse6-0004NC-00@the-village.bc.nu>; from Alan Cox on Sat, Jun 12, 1999 at 07:36:44PM +0100

On Sat, Jun 12, 1999 at 07:36:44PM +0100, Alan Cox wrote:
> > relocations.  A SOM linker also needs to be stream based.  Thus,
> > it appears difficult (impossible?) to build a SOM linker using the
> > bfd architecture.  On the other hand, the elf32-hppa tools have serious
> > deficiencies and are about to be completely rewritten.  Might it not be
> > better to develop a SOM linker rather than rewrite the elf stuff?
> 
> Writing a linker, especialyl for something complex like SOM is not trivial
> in the slightest.

Yes, if you really want to support SOM properly and follow the spec.
It probably isn't if you want to just deal with what actually exists in
the world.  If you look at page 6-125 of the `32-bit PA-RISC Run-Time
Architecture Document 11.0 Version 1.0', it says that all conforming
executable SOM files must have the `exec auxiliary header (also known as
the HP-UX header with Hewlett-Packard)'.

So in the binfmt_som loader I take this opportunity to ignore the
wonderfully flexible and expressive structure that is contained in the SOM
file format and just map the text, data and bss segments from the file.
I imagine that a SOM linker which did just enough to get a kernel up
and running would not be too hard to write.  On the other hand, I can
think of a dozen more interesting and productive things to do.

-- 
Matthew Wilcox <willy@bofh.ai>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson

  parent reply	other threads:[~1999-06-12 19:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3761F335.ADA76678@thepuffingroup.com>
1999-06-12  6:32 ` [parisc-linux] booting problems 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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
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=19990612213649.Y31472@mencheca.ch.genedata.com \
    --to=matthew.wilcox@genedata.com \
    --cc=adevries@thepuffingroup.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox