search for: belkin_claim

I ran into the following issue today and would like some feedback from the group. Setup: I am using a MGE Pulsar Evolution 2200 UPS connected through a Belkin (F5U218-MOB) 4-Port USB Hub. Scenario: The newhidups subdriver_matcher function calls belkin_subdriver->belkin_claim. The belkin_claim function in belkin-hid.c matches the VendorID of the hub to Belkin's VendorID (0x050d), causing the hub to be recognized as a UPS. The newhidups driver (libusb.c) then attempts to claim the device and detatches the kernel driver. When the hub fails to provide a HID descriptor,...

.../* ... */ } The other HID drivers, I guess, could simply have empty functions at the moment. Next, modify the subdriver_t chunk (again, this is shown for the belkin-hid) to be; subdriver_t belkin_subdriver = { BELKIN_HID_VERSION, belkin_claim, belkin_utab, belkin_hid2nut, belkin_shutdown, belkin_format_model, belkin_format_mfr, belkin_format_serial, belkin_extendvartable, }; - In newhidups.c, at the end of upsdrv_make...

...in-hid and liebert-hid drivers. Why not move all liebert related functions in the liebert-hid driver ? (2) i don't understand how the driver selection is done ? if i just add the vendorid/productid to the liebert_usb_device_table, the lookup seems to stop in the belkin driver (perhaps because belkin_claim got "possibly supported" and that the "productid" value is present ?). How do you suggest to implement the addition of this device ? (for my tests, i commented the belkin lookup entry to force the usage of the liebert one). (3) in the hid report, we have several items with th...