From owner-freebsd-arch Tue Nov 27 14:45:25 2001 Delivered-To: freebsd-arch@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 6FC9337B417 for ; Tue, 27 Nov 2001 14:45:22 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fARMjLa07839; Tue, 27 Nov 2001 15:45:21 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fARMjKM17357; Tue, 27 Nov 2001 15:45:20 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200111272245.fARMjKM17357@harmony.village.org> Subject: Re: Anybody working on devd? To: Dima Dorfman , arch@FreeBSD.ORG In-reply-to: Your message of "Tue, 27 Nov 2001 15:43:37 MST." <200111272243.fARMhbM17326@harmony.village.org> References: <200111272243.fARMhbM17326@harmony.village.org> <20011127223854.78E853EF3@bazooka.trit.org> Date: Tue, 27 Nov 2001 15:45:20 -0700 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200111272243.fARMhbM17326@harmony.village.org> Warner Losh writes: : But pccard doesn't deal in terms of dev_t, but rather device_t. The : pccard bus system has no earthly clue what you just added to the : system. Plus, unless jlemon has been busy, the network drivers do not : add dev_t's. : : : The advantages of this approach is that it's very simple, doesn't : : strictly depend on devfs, can probably be used to replace pccardd and : : usbd (although I haven't looked at the latter much), and if we stick a : : call to the hypothetical notify_userland() function in make_dev(), it : : can somewhat be used to control permissions in /dev, although not : : satisfactorily. : : I dislike this approach because it depends on dev_t rather than : device_t. And there's no way to notify userland that "The bus says : the plug and play info is XYZ, but no driver attached." so that the : daemon can load the right driver. I'd also point out that devfsd, in my world view, dealt with dev_t, while devd dealt with device_t. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message