From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id A530A67A6C for ; Tue, 8 Mar 2005 18:31:33 +1100 (EST) From: Benjamin Herrenschmidt To: Sven Luther In-Reply-To: <20050308064945.GC27722@pegasos> References: <422C495B.8090805@katalix.com> <20050307125808.6585A200008A@mwinf0308.wanadoo.fr> <20050307225401.GA31041@xyzzy> <20050308064945.GC27722@pegasos> Content-Type: text/plain Date: Tue, 08 Mar 2005 18:27:12 +1100 Message-Id: <1110266832.13607.267.camel@gaston> Mime-Version: 1.0 Cc: linuxppc-dev list , Dale Farnsworth , Nicolas DET Subject: Re: mv643xx_eth SA_SHIRQ support patch List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > Notice that benh is telling me that you should use SA_SHIRQ always and that > SA_INTERRUPT should go away, and that you should contact him online if you > have trouble with that. > > > For the pegasos 2, you'll need the second patch which applies after > > the one I previously sent for chrp_setup.c. > > Ok, will test this anyway, and tell you how it works. GHeh, ok, just picked up the discussion. Yes, there is really no reason to use SA_INTERRUPT here, this is a thing of the past. Ben.