> > As mentioned earlier, Ultrix on RISC means that it is a MIPS processor.
> > Any hints for Alexander on how to do it *if* it is a MIPS processor?
> Not sure. The only info I see in s_lock.h is in the "SGI" section:
> * This stuff may be supplemented in the future with Masato Kataoka's MIPS-II
> * assembly from his NECEWS SVR4 port, but we probably ought to retain this
> * for the R3000 chips out there.
> That name doesn't ring a bell with me --- anyone remember what code is
> being referred to here, or where we might find Masato Kataoka?
I'm not remembering either...
> MIPS-II code may or may not be compatible with Alexander's machine
> anyway, but it's the only starting point I see.
The Ultrix machine is more likely to be a 2000- or 3000-series (older)
processor.
> Anyway, the last CVS update to port/ultrix.h that appears to have come
> from someone actually using Ultrix was rev 1.2 on 7-May-97, which
> predates the very existence of s_lock.h as a separate file. So I'd
> definitely advise Alexander to find a tarball from that era and look at
> how Ultrix was handled then.
> I dunno if we even have tarballs from that far back on-line ... I
> suppose another possibility is a date-based pull from the CVS server.
What can we help with Alex?
- Thomas
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
