From owner-freebsd-current Sun Oct 10 12:40: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id AD65114FDC; Sun, 10 Oct 1999 12:39:50 -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 VAA16203; Sun, 10 Oct 1999 21:32:43 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Assar Westerlund Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Heads up! In-reply-to: Your message of "10 Oct 1999 21:21:24 +0200." <5loge7uimj.fsf@assaris.sics.se> Date: Sun, 10 Oct 1999 21:32:42 +0200 Message-ID: <16201.939583962@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5loge7uimj.fsf@assaris.sics.se>, Assar Westerlund writes: >Poul-Henning Kamp writes: >> We have now come so far that we can start to kill cdevsw_add() >> calls and rely on make_dev() for most of the device drivers. > >So how is this supposed to work for device kld's? Currently, >cdevsw_add() gets called from the glue generated by DEV_MODULE. The same as for any other driver, once you find your hardware you call make_dev() for it. Use the variant of MODULE macro which doesn't take a cdevsw agument. -- 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 freebsd-current" in the body of the message