From owner-freebsd-hackers Thu Sep 25 03:54:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA10879 for hackers-outgoing; Thu, 25 Sep 1997 03:54:05 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA10871 for ; Thu, 25 Sep 1997 03:53:49 -0700 (PDT) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by Campino.Informatik.RWTH-Aachen.DE (8.8.7/RBI-Z13) with ESMTP id MAA27115 for ; Thu, 25 Sep 1997 12:53:45 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id NAA00834 for freebsd-hackers@freefall.cdrom.com; Thu, 25 Sep 1997 13:00:23 +0200 (MEST) Date: Thu, 25 Sep 1997 13:00:23 +0200 (MEST) From: Christoph Kukulies Message-Id: <199709251100.NAA00834@gil.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: mapping physical (ISA) memory Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Being new to device driver writing I'd like to obtain a few short hints on how to proceed mapping the physical region of a device into the driver's address space. Does the isa_device structure do this for me already? My device has a 16 K block at 0xc8000 (for example) and I want to read some location to verify that the device is there and second to download some data into that memory region. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de