Dmitry Torokhov wrote:
> Yes, I'd consider it a bug. Tearing down and re-creating input device
> generates proper hotplug notifications and userspace needs to respect
> them as capabilities may change even if ids stay the same. For example
> playing with atkbd's scroll attribute will regenerate an input device
> with[out] scroll capabilities but its input_id structure will stay the
> same.
>
So many people said I have some wrongs here ;) it should be truth.
I found our focus is howto or when send notification to userspace.
Intuitional, to reload such device is rather ugly means, it should have
one hotplug message for this case,
and userspace handle it. If only look from design, I will agree with my
argument, however, if also look from compatibility, I think I must agree
your arguments.
At last, you win! :D
I am going to reload.
PS: I found a behavior of usb subsystem, I can not sure whether it is
normal.
After I remove usbhid.ko, the uhci_hcd will reset device repeatly.
usbcore: registered new driver usbhid
/usr/src/redhat/BUILD/linux-2.6.18/drivers/usb/input/hid-core.c:
v2.6:USB HID core driver
usb 5-2: reset low speed USB device using uhci_hcd and address 3
usb 5-2: reset low speed USB device using uhci_hcd and address 3
usb 5-2: reset low speed USB device using uhci_hcd and address 3
usb 5-2: reset low speed USB device using uhci_hcd and address 3
usb 5-2: reset low speed USB device using uhci_hcd and address 3
Goodluck.
-Liyu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
