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 1BBD3DDE0C for ; Fri, 31 Aug 2007 01:57:45 +1000 (EST) Message-ID: <46D6E8DA.9090308@ovro.caltech.edu> Date: Thu, 30 Aug 2007 08:57:14 -0700 From: David Hawkins MIME-Version: 1.0 To: Mirek23 Subject: Re: signals handling in the kernel References: <12032525.post@talk.nabble.com> <46B8A3C9.7060806@ovro.caltech.edu> <46B8BA93.8020909@ovro.caltech.edu> <12048448.post@talk.nabble.com> <46B9FB23.8040903@ovro.caltech.edu> <12409543.post@talk.nabble.com> In-Reply-To: <12409543.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 went throught the Rubini book about device drivers > and I see that you are absolutly right about > the way how to handle interrupts in the user space. Great, glad to hear you are convinced :) > When I find a bit of time I will try your first > suggestion with read() which blocks in the user space > and waits for ISR to write data to the buffer. Look at the example drivers I wrote. Its all in there, just copy whatever you want. > Many thanks for all your suggestions No problem! Its the open-source way ;) Cheers, Dave