linux-mips
[Top] [All Lists]

Re: EISA support

To: "William J. Earl" <wje@fir.engr.sgi.com>
Subject: Re: EISA support
From: Ralf Baechle <ralf@uni-koblenz.de>
Date: Tue, 3 Aug 1999 01:17:20 +0200
Cc: "Andrew R. Baker" <andrewb@uab.edu>, Linux SGI <linux@cthulhu.engr.sgi.com>
In-reply-to: <14246.7994.461082.434930@fir.engr.sgi.com>; from William J. Earl on Mon, Aug 02, 1999 at 03:44:10PM -0700
References: <14246.1339.269402.396117@fir.engr.sgi.com> <Pine.LNX.3.96.990803003314.15805B-100000@mdk187.tucc.uab.edu> <14246.7994.461082.434930@fir.engr.sgi.com>
Sender: owner-linux@cthulhu.engr.sgi.com
On Mon, Aug 02, 1999 at 03:44:10PM -0700, William J. Earl wrote:

>        I see that some drivers use NR_IRQS to form an IRQ_ports[] array,
> to map from IRQ to board object, as in serial.c, whereas others, such as
> riscom8.c, wire in 16 as the limit.   Still, you could make
> probe_irq_on() and probe_irq_off() actually work for an Indy and Indigo2,
> and simply declare broken any drives which do not use NR_IRQS and probe
> using the probe_irq_* routines.  The biggest problem with that approach
> is that NR_IRQS is 64 on mips, which means that probe_irq_on() and 
> probe_irq_off()
> would need a different interface (long long instead of int, to allow 64-bit
> IRQ bit maps on 32-bit kernel).  

probe_irq_{on,off} are being used for interrupt probing only and that's
an art only practiced for ISA.  So we don't even want to support these
functions for interupts >= 16, that is non (E)ISA interrupts.

  Ralf

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