search for: belkin_subdriver

Browsing through the newhidups.c code, I stumbled across the following: /* master list of avaiable subdrivers */ static subdriver_t *subdriver_list[] = { #ifndef SHUT_MODE &generic_subdriver, #endif &mge_subdriver, #ifndef SHUT_MODE &apc_subdriver, &belkin_subdriver, &tripplite_subdriver, NULL #endif }; Shouldn't the 'NULL' terminator be outside the condition? If SHUT_MODE is defined, the list will not be NULL terminated. Regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57

..."wait", "Wait for AC power and battery level "); /* ... */ } 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_ex...

...not to move things around too much, unless we can get people to test the other models. I realize it is annoying that the subdriver names do not match the brands, but the idea is that the matching happens automatically. > [...] > Right, in usbhid-ups.c, the liebert_subdriver entry is after the belkin_subdriver. OK, i suppose that this issue will be solved when all the liebert devices will be moved in the liebert-hid driver, in the future. >> (3) in the hid report, we have several items with the same name (see attached lsusb dump). >> How it is handled by the lookup table ? Is there any inde...

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...

...e to be NULL if a subdriver does not require > > initialization. > > Am I right in thinking that this is simply a case of doing: > > subdriver_t some_subdriver = { > /* ... */ > some_format_serial, > NULL, > } > > Rather than: > > subdriver_t belkin_subdriver = { > /* ... */ > belkin_format_serial, > belkin_init, > } > in the subdrivers that don't need init()ing? Yes. > >- change the call to: > > > > if (subdriver->init != NULL) { > > subdriver->init(); > > } > > As I'v...

Hi On 10/02/2014 02:39 PM, Charles Lepple wrote:> On Oct 1, 2014, at 9:03 PM, paul.chavent at fnac.net wrote: > >>> It should run as user "nut" in Debian. You may want to reinstall the nut-server package, and check the post-inst error messages to make sure that the "nut" user is created, and that it is in the "nut" group as well. >> >> The

...uot;belkin-hid.h" > @@ -34,6 +35,7 @@ > /* master list of avaiable subdrivers */ > static subdriver_t *subdriver_list[] = { > &generic_subdriver, > + &tripplite_subdriver, > &mge_subdriver, > &apc_subdriver, > &belkin_subdriver, Ah, sorry, I had forgotten these. Good catch. > That made this work with ... > > user=root > [myups] > driver=newhidups > vendorid=09AE > #tripplite=1 > port=/dev/usb/hiddev0 > > And returned.... > > /usr/local/ups/bin/upsc...

Hi I am running FC5 with nut coming from the fc5 extras repositories. I am trying to configure a Gamatronic D-Compact ups. The cable that came with the ups has a serial connector on one end and a usb on the other. cat /proc/bus/usb/devices produces T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: