600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
your Linux-MIPS system is more than likely little endian. So no, no way at all.
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
nyef wrote: Have you considered the flipside question: What would it take to get NetBSD running on this hardware?
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
TeamBlackFox wrote: Uhh I don't know what you're on, but NetBSD does have Fibrechannel and gigabit ethernet drivers for common chipsets. That being said, sounds like you're having an excuse to avoid BSD - which is your own business, but I doubt you'll have the patience and skill to adapt the NetBSD binary emulation layer for GNU/Linux. Maybe ask one of the Linux/MIPS guys like Kumba or ivelegacy, but beyond that, you're SOL, my friend. ...
bplaa.yai wrote: If I believe this post and this linux kernel commit it looks like that irix binary compatibility support did exist at some point in time.
It seems it was pretty buggy and limited to the O32 ABI.
But it may give you some inspiration...
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
bplaa.yai wrote:mia wrote: I have, don't set your hopes too high, some static binaries will work.
Interesting. Would you elaborate on this ?
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
jan-jaap wrote: No, it doesn't. I tried once but the build system was sufficiently Linuxified that I lost interest.
While it does have a MIPS code generator these days, it's not from MIPSpro.
The IRIX/MIPSpro compiler works like this:
* Front end: licensed from 3rd party, the Edinburgh Compiler Group (EDG). Many other commerial UNIX vendors used this front end, including the DEC/Compaq compilers for Tru64, and I'm pretty sure the Intel Compilers use it.
* Intermediate (optimizer): built by SGI
* Back end (code generator for MIPS CPUs): built by SGI.
Later, SGI built a new back end for IA64 CPUs, and open sourced the compiler as Open64. They couldn't open source parts they didn't own (EDG) so they replaced it with bits from GCC. The MIPS back end code was not open sourced.
Later on, other people implemented new back ends from scratch for x86-64, and MIPS.
). I have
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
ivelegacy wrote:cybercow wrote: neko-qcad
...
edit:
it seems to me there are two open sources choices
- gEAD
- KiCad
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
nyef wrote: It should be possible to implement IRIX binary compatibility for Linux purely from user mode.
Yes, it would be slow in execution. But you would have the improved cycle time of not needing to deal with a full kernel build (or even "just" the dance for a loadable module), you can bring a normal debugger to bear, and so on. And once it's all running reasonably well, then you can consider building it as a kernel module. And until then, well, now you don't have to worry nearly as much about keeping it in sync with the Linux kernel because the ABI doesn't change incompatibly all that often.
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
ivelegacy wrote: maybe (in the next life) I will find a way to home-build pretty (cheap) PCI fpga dev boards (they are already existing, but too expensive), in this case we could domesticate the SGI_PCI, and It should be nice to add new hw and sw features without all the troubles we have now because the SGI_PCI is not INTEL_PCI compliant.
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
ivelegacy wrote:rwengerter wrote: The "5I25 Superport FPGA based PCI Anything I/O card" from Mesa Electronics
is a Spartan-6 based PCI-card that is not expensive. It costs 89 US$.
See:
http://www.mesanet.com/fpgacardinfo.html
The manual is here:
http://www.mesanet.com/pdf/parallel/5i25man.pdf
I have bought a pair of those boards. They are on their way.
plans: to develop something cool by the end of the next year.
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
pentium wrote: It's cold outside. We're all running our machines as long as we can while the air conditioning is free.
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz
foetz wrote: shouldn't thisbe LD_LIBRARYN32_PATH ?Code: Select all
LD_LIBRARY_PATH="$HDSO:$LD_LIBRARY_PATH"
600 MHz, 2 GB RAM, 72 GB 15k RPM HD
180 MHz