All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Rumpf <Philipp.H.Rumpf@mathe.stud.uni-erlangen.de>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Cary Coutant <cary@cup.hp.com>,
	Philipp Heinrich Rumpf
	<Philipp.H.Rumpf@mathe.stud.uni-erlangen.de>,
	law@cygnus.com, bame@debian.fc.hp.com,
	parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Today's boot experience on a 735
Date: Mon, 22 Nov 1999 10:40:54 +0100	[thread overview]
Message-ID: <19991122104054.D1310@mathe.stud.uni-erlangen.de> (raw)
In-Reply-To: <199911201840.NAA01911@hiauly1.hia.nrc.ca>

> > You should be able to use "_edata" and "_end" to figure out how much 
> > memory to initialize to zero at startup, or you could have the boot 
> > loader do that for you -- the information is in the a.out aux header.
> 
> I haven't verified this myself but I believe others have determined
> that the kernel needs to clear unitialized data itself because of the
> various different way it is loaded.

The problem is we need to know where free memory starts for our memory
allocator - who does the BSS clearing is another issue.

> > By the way, the SOM linker does support "scripts" of a sort. They're 
> > called k-files (because you use the -k option to specify them), and they 
> > allow you to control the placement of your spaces and subspaces within 
> > the address space.
> 
> That's good to know and it might provide a better way for the kernel to
> determine its end.

Is anyone reasonably fluent in whatever language ld uses ?

	Philipp Rumpf

  reply	other threads:[~1999-11-22  9:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-20  0:57 [parisc-linux] Today's boot experience on a 735 Cary Coutant
1999-11-20 18:40 ` John David Anglin
1999-11-22  9:40   ` Philipp Rumpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-11-16 19:58 John David Anglin
1999-11-16 20:18 ` Paul Bame
1999-11-16 20:52   ` John David Anglin
1999-11-16 22:56     ` John David Anglin
1999-11-17  2:04       ` John David Anglin
1999-11-17  2:22         ` Jeffrey A Law
1999-11-17  2:48           ` John David Anglin
1999-11-17  3:35             ` Jeffrey A Law
1999-11-17  6:34               ` Philipp Rumpf
1999-11-17 18:12                 ` John David Anglin
1999-11-17 20:54                   ` Philipp Rumpf
1999-11-17 17:34               ` John David Anglin

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=19991122104054.D1310@mathe.stud.uni-erlangen.de \
    --to=philipp.h.rumpf@mathe.stud.uni-erlangen.de \
    --cc=bame@debian.fc.hp.com \
    --cc=cary@cup.hp.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.