From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: Oddities with CVS Kernels, Memory on Indigo2
Date: Mon, 14 Apr 2003 12:58:42 -0400 [thread overview]
Message-ID: <3E9AE8C2.50409@gentoo.org> (raw)
In-Reply-To: <20030414173510.A2133@ftp.linux-mips.org>
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
next prev parent reply other threads:[~2003-04-14 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-13 5:13 Oddities with CVS Kernels, Memory on Indigo2 Kumba
2003-04-14 14:07 ` Ladislav Michl
2003-04-14 15:53 ` Kumba
2003-04-14 16:00 ` Marc Zyngier
2003-04-14 16:16 ` Kumba
2003-04-14 16:27 ` Marc Zyngier
2003-04-14 16:24 ` Kumba
2003-04-14 16:35 ` Ladislav Michl
2003-04-14 16:58 ` Kumba [this message]
2003-04-15 8:35 ` Kumba
2003-04-15 8:50 ` Ladislav Michl
2003-04-15 9:02 ` Kumba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E9AE8C2.50409@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox