<DocScrutinizer05>
(sorry I can't find a stable link to this, livelogs will point to something else in 22h)
paulk-collins has quit [Read error: Connection reset by peer]
paulk-collins has joined #neo900
goiken has quit [Ping timeout: 260 seconds]
goiken has joined #neo900
tsuggs has joined #neo900
arossdotme has joined #neo900
chomwitt1 has quit [Quit: WeeChat 1.0.1]
illwieckz has joined #neo900
illwieckz has joined #neo900
illwieckz has quit [Changing host]
goiken has quit [Ping timeout: 268 seconds]
goiken has joined #neo900
illwieckz has quit [Ping timeout: 248 seconds]
illwieckz has joined #neo900
illwieckz has joined #neo900
illwieckz has quit [Changing host]
illwieckz has quit [Ping timeout: 268 seconds]
goiken has quit [Ping timeout: 250 seconds]
goiken has joined #neo900
illwieckz has joined #neo900
xman has quit [Quit: Leaving.]
illwieckz has quit [Remote host closed the connection]
Joerg-Neo900 is now known as Guest87112
neo900 has joined #neo900
Guest87112 has quit [Killed (niven.freenode.net (Nickname regained by services))]
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #neo900
goiken has quit [Ping timeout: 248 seconds]
goiken has joined #neo900
SylvieLorxu has joined #neo900
pagurus` has joined #neo900
pagurus has quit [Ping timeout: 252 seconds]
goiken has quit [Ping timeout: 250 seconds]
goiken has joined #neo900
illwieckz has joined #neo900
goiken has quit [Ping timeout: 260 seconds]
goiken has joined #neo900
jonsger has joined #neo900
jonsger has quit [Ping timeout: 250 seconds]
mzki has joined #neo900
goiken has quit [Ping timeout: 260 seconds]
goiken has joined #neo900
<how900>
isn't it part of vdev implementation to bind devices statically? Wouldn't that work?
<DocScrutinizer05>
I thought it should
<DocScrutinizer05>
however paul just told me that kernel is already doing this
<DocScrutinizer05>
[2016-10-14 Fri 08:24:01] <PaulFertser> DocScrutinizer05: the thing is, udev doesn't really probe for devices. If you have a hid keyboard driver already loaded (for real external keyboard) and the modem suddenly changes into being a keyboard too, the kernel will bind the driver right away, without udev's help.
<DocScrutinizer05>
[2016-10-14 Fri 08:24:31] <PaulFertser> DocScrutinizer05: so that's a major requirement you'll have to pass to your kernel hackers. It's not trivial and not out of the box.
<DocScrutinizer05>
[2016-10-14 Fri 08:26:18] <DocScrutinizer05> I thought there's a 2 layer setup: HID/whatever *on top* of a generic USB driver that only handles enum and physical data transfer
<DocScrutinizer05>
[2016-10-14 Fri 08:27:24] <PaulFertser> Yes, there's a kernel usb host controller driver that does enum etc. And usb devices drivers that are in-kernel too. Can be bound without udev.
<DocScrutinizer05>
[2016-10-14 Fri 08:29:39] <DocScrutinizer05> so we need to keep the usb driver (musb-hdrc, ehci, ohci, uhci (?) whatever) but teach whom? kernel? to not bind a device driver on top of that automatically for this one USB port?
<DocScrutinizer05>
[2016-10-14 Fri 08:31:24] <PaulFertser> Yes, that needs to be a new kernel-level option to limit the driver binding for a particular USB port. Not sure if it needs to be HCI-specific or can be implemented in a more generic way to work for any HCI type.