From owner-freebsd-current  Wed Nov 18 01:54:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA10114
          for freebsd-current-outgoing; Wed, 18 Nov 1998 01:54:52 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10101
          for <current@FreeBSD.ORG>; Wed, 18 Nov 1998 01:54:45 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA24723;
	Wed, 18 Nov 1998 20:54:15 +1100
Date: Wed, 18 Nov 1998 20:54:15 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811180954.UAA24723@godzilla.zeta.org.au>
To: current@FreeBSD.ORG, winter@jurai.net
Subject: Re: /dev/ioport[bwl]
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>Whats the story on the 
>
>#ifdef notyet
>...
>#endif
>
>Bits around the code implementing /dev/ioport[bwl] in
>src/sys/i386/i386/mem.c?

It should have gone away 6 years ago.

>I'd like to use /dev/io and friends (/dev/ioport[bwl] if they exist) to do
>some PIO routine prototyping for a device driver.

Opening /dev/io gives direct access to i/o instructions.  This is much
easier and just as (in)secure as /dev/ioport would be.  Drivers should
probably be prototyped using modules.

Bruce

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