From owner-freebsd-current Wed Apr 12 12:34:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA21430 for current-outgoing; Wed, 12 Apr 1995 12:34:08 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA21424 for ; Wed, 12 Apr 1995 12:34:06 -0700 Received: by halloran-eldar.lcs.mit.edu; id AA07483; Wed, 12 Apr 1995 15:34:05 -0400 Date: Wed, 12 Apr 1995 15:34:05 -0400 From: Garrett Wollman Message-Id: <9504121934.AA07483@halloran-eldar.lcs.mit.edu> To: current@FreeBSD.org Subject: Attention device-driver writers! Sender: current-owner@FreeBSD.org Precedence: bulk I recently made another apss through all the device drivers in preparation for adding another variable for devconf. (I might also partially re-design the way devconf and sysctl interface; it could use some improvement, but I'm not likely to have the time.) The following drivers are on my devconf $#!+ list, and were not fixed, or were only incompletely fixed, in this round: Support completely missing: cy, gpib, gsc, ix, ze, zp, joy, tw Registration order bad: cx (?), syscons State broken: lots, including el, eg, ep, wd, and the netif part of lpt Not examined: pcvt, sound, matcd, scsi (waiting for Peter) A special raspberry goes to the PCI code, for getting the idea almost completely inside-out. This is supposed to be DRIVER-driven, not generic-bus-code-driven. I don't want to go fiddling fifteen different PCI structures to provide the necessary information next time I add a variable to the devconf interface! -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant