home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.prime
- Path: sparky!uunet!think.com!spool.mu.edu!yale.edu!jvnc.net!primerd.prime.com!j.cook
- From: j.cook@primerd.prime.com (C. James Cook)
- Subject: Re: X Windows on 50-Series
- Message-ID: <1992Dec27.144848@primerd.Prime.COM>
- Organization: Prime Computer R&D
- References: <1hgcfmINN496@werple.apana.org.au>
- Date: Sun, 27 Dec 1992 19:53:38 GMT
- Lines: 27
-
- markd@werple.apana.org.au (Mark Delany) writes:
- > j.cook@primerd.prime.com (C. James Cook) writes:
- > >markd@werple.apana.org.au (Mark Delany) writes:
- > I vaguely recall that at one stage (and for reasons I don't know) that
- > SPL could not be used for ring0 code.
-
- The proper SPL runtime library routines had to be determined and added to
- Primos before SPL could be used for ring 0 coding. This has been done.
- So long as you obey good coding rules to avoid compiler generated calls
- to P$ANY2, etc., things are fine.
-
-
- > >If you are a 50-series instruction set guru, you will notice the three word
- > >pointer format first defined with the P400 in the 70's has the capability to
- > >address down to the bit level.
- >
- > I'm not, but I remember. Practically, I think the subsequent
- > overloading of this extension bit as a character address for IX was a
- > better choice since prior to this there was no real character
- > addressing available.
-
- Not true. Setting the extension bit and adding the third word to indicate an
- eight bit offset gave you character addressing. It worked just fine. IX-mode
- chose to redefine the extension bit as indicating an odd byte address without
- the need for the third word.
-
- Jim
-