9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Stack initialisation
Date: Wed, 30 Aug 2000 07:19:44 +0200	[thread overview]
Message-ID: <20000830071943.A2949@cackle.proxima.alt.za> (raw)
In-Reply-To: <200008292210.SAA09540@cse.psu.edu>; from forsyth@vitanuova.com on Tue, Aug 29, 2000 at 11:08:51PM +0000

On Tue, Aug 29, 2000 at 11:08:51PM +0000, forsyth@vitanuova.com wrote:
> 
> >>	Ptab    = 0xbfff5000,    /* Private stack */
> >>	Execstk = 0xbf001000,    /* Exec stack linkage area */
> 
> the values are related to those of USTKTOP and USTKSIZE
> in the  2nd edition kernel, both of which differ in the 3rd edition
> kernel, since the arrangement of virtual memory has changed slightly
> (on the PC at least).

Well, to reveal the truth, the new values (that work, that is, I think
I can tweak them further) are

	Ptab     = 0x7fff5000,  (could possibly be 0x7fffe000)
	Execstk  = 0x7f001000,	(not sure about this one)

(thank you, Charles, you put me on the right track), and now I have
a version of Alef for 3rd Edition Plan 9 that (apparently) compiles
and executes programs on my i386 PC.  Anyone got something easier than
the test/ programs.  I tried sieve, pstest and tstbio with seeming
success, I'm not sure what test should produce and I have not tried
anything else.

I haven't yet tackled the graphic libraries (libg.a and libframe.a), I
suspect I won't get that right alone, but I'll give it a good try.
Only too happy to feed back the changed sources to Bell Labs, and do
whatever necessary to keep them current.

I have no idea what other changes to the 2ed libraries I may have
neglected, and so on; feel free to push me in the right direction.

++L


  reply	other threads:[~2000-08-30  5:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-29 22:08 forsyth
2000-08-30  5:19 ` Lucio De Re [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-08-31 10:25 lucio
2000-08-31  0:25 okamoto
2000-08-30 16:45 forsyth
2000-08-30 16:55 ` Boyd Roberts
2000-08-30 15:26 lucio
2000-08-30 14:35 forsyth
2000-08-30 14:17 lucio
2000-08-30 15:36 ` ozan s. yigit
2000-08-30 16:12   ` Lucio De Re
2000-08-30 16:32     ` Boyd Roberts
2000-08-30 16:44       ` Lucio De Re
2000-08-30 16:59         ` Boyd Roberts
2000-08-30 17:06           ` Lucio De Re
2000-08-31  9:26         ` Elliott Hughes
2000-08-30 13:45 rob pike
2000-08-30 13:44 rob pike
2000-08-30  6:14 okamoto
2000-08-30  6:23 ` Lucio De Re
2000-08-30  5:44 okamoto
2000-08-30  6:00 ` Lucio De Re
2000-08-29 16:45 rob pike
2000-08-29 16:58 ` Lucio De Re
2000-08-29 16:45 rob pike
2000-08-29 14:30 Lucio De Re

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=20000830071943.A2949@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).