From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id E19A9DDD0B for ; Mon, 7 Jan 2008 18:07:37 +1100 (EST) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JBm57-0003ih-LW for linuxppc-dev@ozlabs.org; Sun, 06 Jan 2008 23:07:33 -0800 Message-ID: <14660018.post@talk.nabble.com> Date: Sun, 6 Jan 2008 23:07:33 -0800 (PST) From: Misbah khan To: linuxppc-dev@ozlabs.org Subject: How to write a device driver in such a fashion .???? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi all .... I need your suggession to write a driver with such requirements :- On Initiation by the application of which key is pressed driver should perform the task accordingly. There are 7 keys so seven different task the driver will perform. 1 . I do not want to use any entry point such as read/write/ioctl. In such a case how to access the driver. 2. We dont want to implement this as a chracrter driver. 3. The driver shall look pretty much like an application where in asscssing the H/W memory map . Hence no entry point and no registeration but an application could be able to communicate .... I need your suggession in this regard ..... -----Misbah -- View this message in context: http://www.nabble.com/How-to-write-a-device-driver-in-such-a-fashion-.-----tp14660018p14660018.html Sent from the linuxppc-dev mailing list archive at Nabble.com.