From owner-cvs-all Mon Sep 20 14:35:15 1999 Delivered-To: cvs-all@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 62D0514C3D; Mon, 20 Sep 1999 14:35:07 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id XAA25220; Mon, 20 Sep 1999 23:34:54 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: devsw registration (modules/newbus/etc.) In-reply-to: Your message of "Mon, 20 Sep 1999 14:27:04 PDT." Date: Mon, 20 Sep 1999 23:34:54 +0200 Message-ID: <25218.937863294@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk In message , Juli an Elischer writes: >> Why would you want to register a cdevsw until you have found some >> hardware that need it ? > >Because it's part of the driver registration amd not part of the >individual device registration.. Frist remember that cdevsw_add() is destined to be replaced with make_dev() whereever possible, so that DEVFS has something to work with. Second the devsw should not be registered unless some hardware is found, another driver might need to register this slot for compatibilty (ata vs wd driver for instace). Third I simply don't agree that registering your cdevsw is part of the driver registration, in fact, we should move away from that mistake. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message