From owner-freebsd-hackers Fri Oct 3 17:00:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA21231 for hackers-outgoing; Fri, 3 Oct 1997 17:00:19 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA21226 for ; Fri, 3 Oct 1997 17:00:18 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA16923; Fri, 3 Oct 1997 16:52:28 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd016921; Fri Oct 3 23:52:21 1997 Message-ID: <343584F8.5656AEC7@whistle.com> Date: Fri, 03 Oct 1997 16:51:20 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: mdean CC: freebsd-hackers@FreeBSD.ORG Subject: Re: devfs / cdevsw References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk mdean wrote: > > When should I use cdevsw, and when should I use devfs, will new systems > have the /devs mountpoint or something? And if your device is named dummy > then how are you supposed to use NDUMMY, and where does it get defined? wow, actually I'm actually doing active development of devfs again after two year's break. NDUMMY is used should you want to statically allocate some resources. New drivers should not do this, but use 'malloc' as a general rule. The use of NDUMMY teneds to make code that is unsuitable for conversion to an LKM and the eventual aim is to have nearly all drivers LKM'able. I run /devs here, but have some problems with disks the answer is a rather large change to the way that disks are handled on FreeBSD, so I've detoured into that for a while before I resume working on DEVFS itself. till then, the example drivers should show you how to do devfs entries. julian