search for: subdriver_t

...;Wait for AC power "); addvar(VAR_VALUE,"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,...

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

j T wrote: > >- allow the value 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. > >-...

...+ (unsigned int)0x37E, + (unsigned int)0x38C, + (unsigned int)0x399, + (unsigned int)0x3A5, + (unsigned int)0x3AF, + (unsigned int)0x3B7, + (unsigned int)0x3BF, + (unsigned int)0x3C6, + (unsigned int)0x3CC +}; + +static unsigned int therm_tbl_size = sizeof(therm_tbl)/sizeof(therm_tbl[0]); + +extern subdriver_t openups_subdriver; + +#endif /* OPENUPS_HID_H */ Index: drivers/usbhid-ups.c =================================================================== --- drivers/usbhid-ups.c (revision 3782) +++ drivers/usbhid-ups.c (working copy) @@ -37,6 +37,7 @@ /* include all known subdrivers */ #include "m...

...bdrivers: - 'protocols', which are communication-type-agnostic (i.e. they do not fiddle with serial or USB operations, and are not restrained by them), only map the protocol used by the device to the protocol used by NUT, and are implemented in their own files using (and exposing only) the `subdriver_t` format (for more info on this type, see the chapter of the developer guide I mentioned before, 'nutdrv_qx.h' or the various 'nutdrv_qx_<name-of-the-protocol>.c' files), - 'USB subdrivers', which only deal with USB I/O operations, and, conversely, are implemented entir...

Dear Daniele, I'm trying to create a subdriver for 'nutdrv_qx' instead of modifying the Blazer as you suggested, but i honestly don't understand how to integrate usb-serial devices (some of our UPSs have USB but serial protocol Q1). i understand the serial version but not the USB one. i also checked the "Claim" function, but i can't see drivers that uses the VID

...r perhaps not yet)\n" "supported by newhidups. Try running the driver with the '-x productid=%04x'\n" "option. Please report your results to the NUT developer's mailing list.\n", hd->VendorID, hd->ProductID, hd->ProductID); return 0; } } } subdriver_t powercom_subdriver = { POWERCOM_HID_VERSION, powercom_claim, powercom_utab, powercom_hid2nut, powercom_shutdown, powercom_format_model, powercom_format_mfr, powercom_format_serial, };

...nown subdrivers */ > #include "generic-hid.h" > +#include "tripplite-hid.h" > #include "mge-hid.h" > #include "apc-hid.h" > #include "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...

...bdrivers: - 'protocols', which are communication-type-agnostic (i.e. they do not fiddle with serial or USB operations, and are not restrained by them), only map the protocol used by the device to the protocol used by NUT, and are implemented in their own files using (and exposing only) the `subdriver_t` format (for more info on this type, see the chapter of the developer guide I mentioned before, 'nutdrv_qx.h' or the various 'nutdrv_qx_<name-of-the-protocol>.c' files), - 'USB subdrivers', which only deal with USB I/O operations, and, conversely, are implemented entir...

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:

...r perhaps not yet)\n" "supported by newhidups. Try running the driver with the '-x productid=%04x'\n" "option. Please report your results to the NUT developer's mailing list.\n", hd->VendorID, hd->ProductID, hd->ProductID); return 0; } } } subdriver_t dynex_subdriver = { DYNEX_HID_VERSION, dynex_claim, dynex_utab, dynex_hid2nut, dynex_shutdown, dynex_format_model, dynex_format_mfr, dynex_format_serial, }; <<EOF>> # lsusb Bus 005 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus...