From owner-freebsd-hackers Mon Dec 7 03:21:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16112 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 03:21:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16097 for ; Mon, 7 Dec 1998 03:21:11 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id MAA24580 for ; Mon, 7 Dec 1998 12:21:31 +0100 (MET) Date: Mon, 7 Dec 1998 12:21:02 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD hackers mailing list Subject: Re: major/minor numbers 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 > Oh, you are right. You mean something like: > > device mse0 at isa? ... # bus mouse > device psm0 at isa? ... # PS/2 mouse > > controller uhci0 > controller usb0 > device ums0 > > pseudo-device mouse 3 # or more, if we like > pseudo-device kbd 2 Why is this? (same for keyboard) We don't need to specify this I believe. Dynamic allocation would do fine I think, especially if you only do a hand-off. But a much better solution would be to create a mouse bus attaching to the root bus, and connect all the mice to that one. Unit numbers will be increasing, so we will only need one major number for that one, one naming scheme, like mouse[0-9]+, in /dev. Sysmouse could integrate with that as well. Dynamic attachment and detachment is straightforward or automatic, implemented in the mouse bus. Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message