[Prism54-users] /proc/interrupts conflict with the prism driver/firmware - Luis, could you help please?

[Herbert Valerio Riedel]

On Sat, Dec 06, 2003 at 08:47:27PM +0100, Aurelien wrote:
> I think mcgrof was thinking about the following change : 
> line 189 in islpci_hotplug.c, replace : 
> 
> SA_SHIRQ, ndev->name, priv);
> 
> with :
> 
> SA_INTERRUPT | SA_SHIRQ, ndev->name, priv);
> 
> But I don't think it will help.

indeed; it was actually yours truly who removed the SA_INTERRUPT
symbol from the source some weeks ago; reason: see

from <asm/signal.h>:

/*
 * SA_FLAGS values:
 *
 * SA_ONSTACK indicates that a registered stack_t will be used.
 * SA_INTERRUPT is a no-op, but left due to historical reasons. Use the
 * SA_RESTART flag to get restarting signals (which were the default long ago)
 * SA_NOCLDSTOP flag to turn off SIGCHLD when children stop.
 * SA_RESETHAND clears the handler when the signal is delivered.
 * SA_NOCLDWAIT flag on SIGCHLD to inhibit zombies.
 * SA_NODEFER prevents the current signal from being masked in the handler.
 *
 * SA_ONESHOT and SA_NOMASK are the historical Linux names for the Single
 * Unix names RESETHAND and NODEFER respectively.
 */


regards,
-- 
Herbert Valerio Riedel       /    Phone: (EUROPE) +43-1-58801-18840
Email: hvr@hvrlab.org       /    Finger hvr@gnu.org for GnuPG Public Key
GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748  5F65 4981 E064 883F 4142