Linked by Thom Holwerda on Tue 9th May 2006 21:25 UTC
Thread beginning with comment 123002
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
[Most of the kernel code is SysV (with a touch of BSD for network code). There are the additions SGI made (NUMA, xfs, etc) but there doesn't seem to be anything "for MIPS" about them (i.e. assembly code, etc). ]
Actually, you are only partially right. You are right in the fact that it is based off of SysV and BSD, but there are MIPS specific stuff in IRIX.
There are pieces that are written in assembly for performance issues. Furthermore, there are MIPS specific stuff related to addressing and paging. Consequently, any port of IRIX would be quite complicated.




Member since:
2006-02-03
Also Irix is written from the ground up for MIPS and has been tested for years on MIPS hardware. Porting would be a massive undertaking requiring re-writing large parts and thus introducing plenty of new bugs.
When was Irix written from the ground up, let alone "for MIPS" ? Most of the kernel code is SysV (with a touch of BSD for network code). There are the additions SGI made (NUMA, xfs, etc) but there doesn't seem to be anything "for MIPS" about them (i.e. assembly code, etc).
So, would you care to enlighten me about these two points ("written from the ground up", and "written for MIPS")?