From owner-freebsd-hackers  Thu Aug 12 14:27: 5 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from p2.acadia.net (p2.acadia.net [205.217.210.2])
	by hub.freebsd.org (Postfix) with ESMTP id 3576D14C97
	for <hackers@freebsd.org>; Thu, 12 Aug 1999 14:26:49 -0700 (PDT)
	(envelope-from tbuswell@acadia.net)
Received: from smpbox.bogus.net (ell74.acadia.net [205.217.218.58])
	by p2.acadia.net (8.9.1/8.9.1) with ESMTP id RAA23246
	for <hackers@freebsd.org>; Thu, 12 Aug 1999 17:26:41 -0400 (EDT)
Received: (from tbuswell@localhost)
	by smpbox.bogus.net (8.9.3/8.9.3) id RAA02152;
	Thu, 12 Aug 1999 17:25:05 -0400 (EDT)
	(envelope-from tbuswell)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 12 Aug 1999 17:25:05 -0400 (EDT)
To: hackers@freebsd.org
Subject: interacting with ISA PnP devices.
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14259.14514.212606.703642@localhost.bogus.net>
From: tbuswell@acadia.net
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Hi,

What is the path of least resistance for getting an unsupported ISA
PnP device to the point where you can do I/O to it (inb,outb)?
Do I need a driver, or is there some general purpose way for
getting the device "up" to the point that you can use /dev/io and a user
space application?  (on -current)  

If I need to write a driver, would a device driver that just maps the
device be considered useful (feasible to implement?)?

This specific device is a "winmodem" which I believe I have enough
hardware documentation to fiddle with, once I get past the ISA PnP
interface.

Thanks,
-Ted
(ISA PnP newbie)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message