linux-mips
[Top] [All Lists]

Re: Oddities with CVS Kernels, Memory on Indigo2

To: linux-mips@linux-mips.org
Subject: Re: Oddities with CVS Kernels, Memory on Indigo2
From: Kumba <kumba@gentoo.org>
Date: Mon, 14 Apr 2003 12:58:42 -0400
In-reply-to: <20030414173510.A2133@ftp.linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <3E98F206.5050206@gentoo.org> <20030414140717.GA805@simek> <3E9AD98B.90808@gentoo.org> <wrpbrz9vzkl.fsf@hina.wild-wind.fr.eu.org> <3E9AE0D6.5060401@gentoo.org> <20030414173510.A2133@ftp.linux-mips.org>
Reply-to: kumba@gentoo.org
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
Ladislav Michl wrote:
On Mon, Apr 14, 2003 at 12:24:54PM -0400, Kumba wrote:

Several chips used in Indy (and Indigo2) are used in much complicated machines
(not supported by linux) and SGI always designed its machines with modularity
in mind. local3_irq is another cascade where nothing is hooked on Indy, so you
can't get this irq. and if it happens there is sometning strange with our
system. there are no comments because you need to understand it before coding
and once you read documentation comments are useless ;-)

        ladis

ps. there is driver for built-in parport now by Vincent Stehle
http://vincent.stehle.free.fr/sgi/parport.php3


Ah ha, interesting. I noticed it, because testing both the parallel port and NE2000 ISA card, I had to avoid that IRQ. The parallel port card had physical jumpers I set on it to get around trying to use IRQ3, and the NE2000 Card you *have* to know the IRQ. Can't use the ether=0,0,ethX line on the kernel, because if the kernel attempts to probe for IRQs, it runs into that panic. Enabling it didn't seem to do anything bad either, except that odd message which sounded pretty weird for a kernel.

--Kumba


<Prev in Thread] Current Thread [Next in Thread>