Date: Mon, 18 Feb 2019 15:03:13 -0600 From: "Apollo D. Sharpe, Sr." <demetrioussharpe@netscape.net> To: Hans Petter Selasky <hps@selasky.org>, freebsd-usb@freebsd.org Subject: Re: Questions about the USB HID device drivers Message-ID: <d792f27e-5e55-e5ca-eb89-b7a8704200e0@netscape.net> In-Reply-To: <0cbc66cd-9007-878e-8bc3-f623364729d4@selasky.org> References: <fd7883c8-604e-e7d7-b135-d1d957938e7c@netscape.net> <9c6a87dd-cf7c-d0eb-82f1-5e904baaf05f@selasky.org> <325834a2-d9f1-a1f4-dff1-7f724aeb4907@netscape.net> <6762c7c9-f9dc-f7d2-0b1f-c2f6e2816cd7@selasky.org> <3724cc29-b682-2395-bd95-cbfa418ad9f2@netscape.net> <0cbc66cd-9007-878e-8bc3-f623364729d4@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/18/19 3:26 AM, Hans Petter Selasky wrote: > Each devicename has a uniq prefix followed by a uniq unit number. So, we just end up dumping ALL device nodes in /dev... > Character device nodes are automatically created. However it is > possible for user-space applications to create symbolic links > afterwards in /dev . ...and leave it to user-space to create the hierarchy within /dev? Is there a technical reason that kernel drivers don't automatically subscribe to a hierarchy, or is this just historic inertia? It seems funny to me that such decisions are left to user-space applications. -- Regards, Apollo D. Sharpe, Sr.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d792f27e-5e55-e5ca-eb89-b7a8704200e0>