From owner-freebsd-hackers Thu Apr 16 14:01:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00998 for freebsd-hackers-outgoing; Thu, 16 Apr 1998 14:01:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uhf.wireless.net (uhf.wireless.net [209.189.23.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00904 for ; Thu, 16 Apr 1998 21:00:54 GMT (envelope-from bad@shf.wireless.net) Received: from shf.wireless.net (shf [209.189.23.56]) by uhf.wireless.net (8.8.8/8.8.7) with ESMTP id OAA00949; Thu, 16 Apr 1998 14:00:02 -0700 (PDT) Received: from localhost (bad@localhost) by shf.wireless.net (8.8.8/8.8.8) with SMTP id OAA00347; Thu, 16 Apr 1998 14:01:38 -0700 (PDT) (envelope-from bad@shf.wireless.net) Date: Thu, 16 Apr 1998 14:01:38 -0700 (PDT) From: Bernie Doehner To: Mike Smith cc: Bernie Doehner , hackers@FreeBSD.ORG, buaas@wireless.net, bad@ece.WPI.EDU Subject: Re: Documentation of 2.2.5-RELEASE and 3.0 memory protection? In-Reply-To: <199804162026.NAA01011@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [...] > > if_ed driver (some cards use shared memory, but in the ISA hole of > > A0000-100000), to the Digiboard driver (which I thought uses shared > > memory, but BELOW A0000). > > I don't understand you here - drivers are *inside* the kernel, and > behave completely differently to user-mode programs. > Are you writing a driver, or a user-mode program? This is a critical > difference. Using used too loose a definition. Our stuff is ALL user-mode programs currently and it appears to work (with one program using monochrome range for shared-memory, and the other using ISA hole memory) But we'd like to understand the kernel mechanisms better so that we can move/some of it into the kernel and turn it into real device drivers. Bernie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message