SGI O2 Netboot Kernel

	ip32-r5k-20050530.img - Boots SGI O2 R5000
	ip32-rm5k2-20050530.img - Boots SGI O2 RM5200

	Kernel Version: 2.6.12-rc5
	Kernel Build Date: 30 May 2005
	Kernel CVS Date: 29 May 2005

	Features (Not a Full List):
		Loopback
		Networking
		Serial Console
		SCSI Disk/Tape/CD
		Graphics BackEnd (GBEFB) [4MB]
		RAID 0/1/4/5/6/0+1/Linear
		USB 1.1/2.0 (UHCI, OHCI, or EHCI; Works best w/ ALi Cards)

	Supported Filesystems:
		EFS
		Ext2
		Ext3
		ISO9660
		JFS
		NFS
		ReiserFS
		shmfs/tmpfs
		SMB
		UDF
		XFS

	Root Image:
		Embedded into Kernel Image


>>> How to boot (On Serial Console):
	bootp(): root=/dev/ram0 console=ttyS0,<baud rate>
		where <baud rate> is usually 9600 for most machines, unless changed by
		editing the 'dbaud' parameter in the PROM Monitor.  38400 is a good,
		safe value.

>>> How to boot (On Framebuffer (gbefb Console)):
	bootp(): root=/dev/ram0 console=tty0


RM7000 based O2 systems are not known to boot entirely in Linux.  Due to the rarity of these
systems, it is unknown if they will ever be fully supported.  The primary problems currently
exist in support for the Tertiary cache (L3) support on the CPU board.

R10000/R12000 based systems may never be supported, however, this could change.  With the
success of the Linux port to the SGI IP28 (Indigo2 Impact R10000), some of the code
and/or theories may be applicable on O2.  Especially the modifications to the gcc compiler
used to build the kernel.  Anyone wishing to assist in this porting effort is advised to:

	1) Read the R10000 Manual.  Available on google if you search the right
	   terms or on NEC's website under the moniker of VR10000-<something>.

	2) Look over the changes done to gcc and the IP28 patches to get an idea of what was
	   done.

	3) Have lots of caffeine, pizza, and other essential survival gear, and be prepared
	   to spend several nights staring at nothing but unglorified kernel code.