Hi, I again looking into getting my old SGI Indy and my newer Origin 300 system to actually do sth. useful ;) I got both hooked up into my rack and serial console attached to it, dhcp and tftp so that the boxes can potentially boot via network.
Some information about my Origin 3000 I have collected here: https://www.l00-bugdead-prods.de/origin.html Regarding the old Indy, I was already asking over 2 years ago: http://www.mail-archive.com/m...@openbsd.org/msg50839.html Joel sent me a link to an ecoff kernel that time that I tried to boot, but unfortunately that I do not have anymore, and also the link doesn't work anymore. I tried to boot an actual NetBSD ecoff kernel on that machine, but that also did not went that far as I anticipated, and ended with an exception. The actual IRIX on the disks is still booting, so the box should be OK: I know an older NetBSD version was running on the machine some point in time, I still need to find the harddisk where I have the installation on it. I know both are not (yet ;) supported by OpenBSD as the sgi.html states. However, IIRC, on older versions of the page it stated for the Origin that it may be supported, but that was still untested. Now it states that the Origin 300 is not supported yet. I guess someone tested this meanwhile and it was not working? reading the INSTALL.sgi, for the IP35 based systems I should boot the IP27 bsd.rd. Trying this on the Origin 3000 ends up here: >> bootp(): Setting $netaddr to 10.0.0.32 (from server ) Obtaining from server 5389376+728816 entry: 0xa800000000040000 ARCS64 Firmware Version 64.0 Found SGI-IP35, setting up. Machine is in M mode. And then it hangs here forever. I wonder whether that is actually expected at that early stage? Or is it just because the serial port is not supported for that machine? The Indy should be supposed to work with Linux or NetBSD as far as I know, but the Origin 3000 doesn't even seem to be supported by neither of those. Therefore now to the cross compiling, the actual topic of the mail. Unfortunately I do not own a SGI that is able to run OpenBSD, therefore I just got a little stuck to get the cross compilation stuff changing. I found this interesting paper from Rainer regarding porting openbsd to mips32: http://www.openbsd.org/papers/mips32-openbsd.pdf My system that I have now is a OpenBSD i386 4.6 box. There I compiled the cross compilation tools for the target sgi: TARGET=sgi TARGET_ARCH=mips64 as explained in the pdf from Rainer. I have a lot of stuff now in /usr/cross, but I did not found out yet, how to use it to create a mips64 binary/kernel. Any hint on how to use that stuff would be great, should I chroot into that directory and then just compile it? I downloaded the barebone.tar.gz mentioned in the slides from Rainer. In the accompanying README, it states that the CPU needs the CP0 register, so must be R4k compatible. Still need to take a look into the makefile because it only seems to be able to create elf binaries, not ecoff. I was searching for information about the R12k processor, whether this also has that register, and found some PDFs where it was mentioned. So I guess that the Origin also should be able to execute that code, when I get it cross compiled? Could someone prove me wrong/right here please. For the Indy, I also still need to find out how to enable the ECOFF targets, any hint on this one would be great too. I'm also still looking at the linux-mips porting howto that was also mentioned in the slides from Rainer. Any pointers what I should enable when I get to the stage to try to build a kernel for the Origin or the Indy to get the most output at all when it crashes? DEBUG, KGDB or DDB, what else? So sorry for the lenghty mail, hope its not too confusted. Any pointers to more documentation and/or hints on start to get me going are appreciated. cheers, Sebastian
