From owner-freebsd-hardware Tue Nov 3 09:02:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05024 for freebsd-hardware-outgoing; Tue, 3 Nov 1998 09:02:47 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05018 for ; Tue, 3 Nov 1998 09:02:44 -0800 (PST) (envelope-from pb@ludd.luth.se) Received: from father.ludd.luth.se (pb@father.ludd.luth.se [130.240.16.18]) by zed.ludd.luth.se (8.8.5/8.8.5) with ESMTP id SAA28054 for ; Tue, 3 Nov 1998 18:02:34 +0100 From: Peter Brevik Received: (pb@localhost) by father.ludd.luth.se (8.6.11/8.6.11) id SAA09424 for freebsd-hardware@FreeBSD.ORG; Tue, 3 Nov 1998 18:02:33 +0100 Message-Id: <199811031702.SAA09424@father.ludd.luth.se> Subject: Generic DMA driver? To: freebsd-hardware@FreeBSD.ORG Date: Tue, 3 Nov 1998 18:02:33 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I been thinking on creating a driver that allows one to launch dma transfers with arbitrary channel. From user space so that one could use this in combination with /dev/io to experiment when writting new drivers. Is this a good idea..? ,or does it "re-invent" the wheel even? Most drivers seem to consist of in() + out() + dma transfer.. /Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message