In message <20030101232326.0cdde4c4.hscholz@raisdorf.net>, you write: 

-> Hi!
-> 
-> On Wed, 1 Jan 2003 15:03:22 -0600
-> sgimips@mrynet.com (sgimips NetBSD list) wrote:
-> 
-> > > boot -f bootp():/tftpboot/netbsd-ip32
-> > Setting $netaddr to 198.182.227.86 (from server 198.182.227.1)
-> > Obtaining /tftpboot/netbsd-ip32 from server 198.182.227.1
-> > 1832976+156740 entry: 0x80069000
-> >  [ no symbols available ]
-> > CPU clock speed = 180.01Mhz*
-> [...]
-> > cpu0 at mainbus0: MIPS R5000 CPU (0x2321) Rev. 2.1 with built-in FPU
-> 
-> I've got an RM5200 CPU running at 300MHz:
-> cpu0 at mainbus0: QED RM5200 CPU (0x28a0) Rev. 10.0 with built-in FPU
-> 
-> Some call my O2 an O2+ and I would need atleast Irix 6.5.11 to run
-> Irix.
-> 
-> I guess my CPU version is the problem as the Irix stuff works.

Hmm, since it appears that you have a new(ish) O2, I'd guess you may
have a newer version of the CRIME ASIC and hence interrupts may be
routed differently.  If you can boot IRIX, run the following command,
and tell me what IRIX outputs:

	# systune crime_rev

On my O2, I get 0x11, which I assume is CRIME rev. 1.1; rumour (and
Linux sources) have it that CRIME 1.5 maps interrupts differently than
previous versions, which routed all interrupts to CPU INT 1.  Our code,
unfortunately only really knows the difference between CRIME rev. 0
(the "Petty CRIME") and non-rev-0 CRIME ASICs.  Maybe someone should
look at how IRIX tells the different non-pretty versions apart and
tell us 8-)

There's also some interesting comments about post-/and pre-PIO read
delays for the IP32, but the comments don't mention why and when one
would need these delays...

Thanks!
--rafal

----
Rafal Boni                                                     rafal@attbi.com
  We are all worms.  But I do believe I am a glowworm.  -- Winston Churchill