From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ovro.ovro.caltech.edu (ovro.ovro.caltech.edu [192.100.16.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.ovro.caltech.edu", Issuer "mail.ovro.caltech.edu" (not verified)) by ozlabs.org (Postfix) with ESMTP id 949BDDDE34 for ; Wed, 8 Aug 2007 02:55:38 +1000 (EST) Message-ID: <46B8A3C9.7060806@ovro.caltech.edu> Date: Tue, 07 Aug 2007 09:54:33 -0700 From: David Hawkins MIME-Version: 1.0 To: Mirek23 Subject: Re: signals handling in the kernel References: <12032525.post@talk.nabble.com> In-Reply-To: <12032525.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Mirek, > I would like to send signals from the interrupt handler > routine (in the kernel) to the user application (in user space). > I have googled on that net and I have found that it could be done with the > function: kill_proc_info. Look in Rubini for the section regarding asynchronous notification, Ch 6. The callback to generate SIGIO is fasync. Cheers Dave