From owner-freebsd-hackers Sat Dec 18 9:15:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id B543614CAA for ; Sat, 18 Dec 1999 09:15:08 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id MAA03024 for ; Sat, 18 Dec 1999 12:15:04 -0500 (EST) Date: Sat, 18 Dec 1999 11:01:42 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Register a KLD module 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 I have looked at the KLD examples and found out that they boils down to a DECLARE_MODULE() macro with the subsystem given as SI_SUB_DRIVERS. Is there any reason for using this particular SI_SUB_DRIVERS? I see another example at http://www.freebsd.org/~abial/ that uses SI_SUB_EXEC. Is this subsystem id really useful for KLDs? KLDs are loaded when we run the kldload command and the subsystem ids are sorted at boot time. Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message