![]() | |||||||||||||
Messages in this thread |
Hi Kay, > > > But userspace should also find out about this change, and this patch > > > prevents that from happening. What about just tearing down the class > > > device and creating a new one? That way userspace knows about the new > > > linkage properly, and any device naming and permission issues can be > > > handled anew? > > > > This won't work for Bluetooth. We create the TTY and its class device > > with tty_register_device() and then the device node is present. Then at > > some point later we open that device and the Bluetooth connection gets > > established. Only when the connection has been established we know the > > device that represents it. So tearing down the class device and creating > > a new one will screw up the application that is using this device node. > > > > Would reissuing the uevent of the class device help here? > > How about KOBJ_ONLINE/OFFLINE? I am not that familiar with the internals of kobject. Can you give me an example on how to do that? Regards Marcel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-07-08 11:33 [from the cache] ©2003-2008 | |||||||||||||