From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GFWr3-0003ZF-9J for garchives@archives.gentoo.org; Tue, 22 Aug 2006 14:03:45 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k7ME2sDp012264; Tue, 22 Aug 2006 14:02:54 GMT Received: from mail47.e.nsc.no (mail47.e.nsc.no [193.213.115.47]) by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k7ME2rqq023670 for ; Tue, 22 Aug 2006 14:02:54 GMT Received: from mail.nor.wtbts.org ([213.234.126.131]) by mail47.nsc.no (8.13.7/8.13.5) with ESMTP id k7ME2rw7019196 for ; Tue, 22 Aug 2006 16:02:53 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.nor.wtbts.org (Postfix) with ESMTP id 319633FA49 for ; Tue, 22 Aug 2006 16:02:53 +0200 (CEST) Received: from mail.nor.wtbts.org ([127.0.0.1]) by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04645-09 for ; Tue, 22 Aug 2006 16:02:52 +0200 (CEST) Received: from nc.nor.wtbts.org (unknown [192.168.65.211]) by mail.nor.wtbts.org (Postfix) with ESMTP id DBFF53FA30 for ; Tue, 22 Aug 2006 16:02:52 +0200 (CEST) Subject: Re: [gentoo-embedded] writing device drivers howto From: Natanael Copa To: gentoo-embedded@lists.gentoo.org In-Reply-To: References: Content-Type: text/plain Date: Tue, 22 Aug 2006 16:02:52 +0200 Message-Id: <1156255372.17633.43.camel@localhost> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-embedded@gentoo.org Reply-to: gentoo-embedded@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at wtbts.no X-Archives-Salt: 5f506a64-8efb-4b04-8203-f60c965c90d4 X-Archives-Hash: f73ff03f806db3f43cb945d0cbb950ad On Tue, 2006-08-22 at 15:37 +0200, andreas.sumper@cnsystems.at wrote: > > Hi list! > > This is some sort of offtopic, but I guess this is the best point to > ask. > I have an embedded system running linux. I need to access some special > registers (e.g. containing the clock cycles, ...) So I managed to > write a very simple module, which is able to access the registers. But > what makes me worrying now, is the way, I have to get the data into my > user-space application. Is there some documentation, concerning > writing device drivers and accessing them from the user space > anywhere? I found some documentation, but either I did not understand > the part about getting data from kernel space into user space, or it > was just simply missing. > > Maybe anyone here can help me out! > > Thanks in advance and kind regards! > I don't have much experience with kernel development but I think you need a device in /dev that you can control with ioctl to communicate with the module. I looked into how to access the md5/sha1/sha256 kernel modules and I concluded that a /dev/crypto was needed. Someone had made a patch for it but it doesn look like it will go into main kernel so I gave it up. You can look how he did. google for cryptodev. > Bye, > Andy -- Natanael Copa -- gentoo-embedded@gentoo.org mailing list