Hello,
Specifically, I'm interested in how the USB keyboard & mouse drivers
publish their nodes. I've been combing through the sources of both
drivers in an attempt to understand a) how they make available the data
from their devices, b) how they publish their device nodes, and c) where
all o
On 2/15/19 7:46 AM, Hans Petter Selasky wrote:
On 2/15/19 2:22 PM, A. D. Sharpe wrote:
On 2/15/2019 3:30 AM, Hans Petter Selasky wrote:
Did you have a look at the code?
sys/dev/usb/input/ums.c and sys/dev/usb/input/ukbd.c
I think I have a decent understanding of USB devices under FreeBSD.
Ho
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 link
On 2/18/19 3:18 PM, Warner Losh wrote:
Yes and no. If the unique prefix has / in it, devfs puts it in a subdir.
If I'm reading the code right, the unique prefix is basically
driver_t::name. Is that correct? If so, I haven't seen a device name (in
the entire tree) that has "/" in it's device n
On 2/18/19 3:37 PM, Ian Lepore wrote:
Not to userland applications so much as to sysadmin-controlled
configuration which is applied from userland during system startup and when new
devices are attached. See the manpage for devfs.conf.
Which does make sense on servers & network infrastructure.
