From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [rfc] generic testing ACPI module Date: Fri, 12 Mar 2004 20:59:12 +0100 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <20040312195912.GA2153@openzaurus.ucw.cz> References: <1079038411.18351.25.camel@t40> <20040311211005.GM2148@parcelfarce.linux.theplanet.co.uk> <1079041694.5429.58.camel@t40> <20040311225032.GN28592@poupinou.org> <20040312144241.GA1236@openzaurus.ucw.cz> <20040312175724.GP28592@poupinou.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20040312175724.GP28592-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Bruno Ducrot Cc: Pavel Machek , Paul Ionescu , Matthew Wilcox , acpi List-Id: linux-acpi@vger.kernel.org Hi! > > But ioctls are even worse. Why not simply > > open METHOD > > write PARAMETERS > > read RESULTS > > close > > > > Because I'm too stupid to thing of your solution, I guess. Well, instead of doing ioctls on special file, you can simply do write syscall (telling driver parameters for the method) then read syscall on same filedescriptor. That is not racy, and it is less hacky then ioctl() Pavel -- 64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click