From owner-freebsd-hackers Thu Oct 23 07:31:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA29646 for hackers-outgoing; Thu, 23 Oct 1997 07:31:02 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA29632 for ; Thu, 23 Oct 1997 07:30:29 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id XAA00457; Thu, 23 Oct 1997 23:56:23 +0930 (CST) Message-Id: <199710231426.XAA00457@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Christoph Kukulies cc: freebsd-hackers@freefall.FreeBSD.org Subject: Re: need help in ISA memory mapping In-reply-to: Your message of "Thu, 23 Oct 1997 09:46:58 +0200." <199710230746.JAA13974@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Oct 1997 23:56:07 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > A user program should be able to directly read/write into these memory > locations via a pointer (byte or word). Is there a way tp 'map' > this into a user address space? Is it possible at all? Yup. You just need to mmap() a friendly driver or memory extent. > I can use the isa_dev structure in the kernel driver (I have written > a minimum driver that probes the card) but this only works in kernel > mode. You could extend the driver trivially to offer mmap() facilities; this would be ideal as it would allow you to detect the correct location for the card & disallow the mapping if the card did not exist. Have a look at the mapping stuff in syscons for an example. mike