similar to: [nut-commits] svn commit r1578 - in trunk: . drivers

Arnaud, I have a question regarding the below structure you've added: > typedef struct usb_device_id_t { > int vendorID; > int productID; > void*(*fun)(); /* handler for specific processing */ > } usb_device_id; I don't understand the last element in this structure. While there can be plenty of reasons for functions returning (void *), I can't figure out what

Thanks to the great help here, I now have a UPS spitting out something resembling a report descriptor. So since I seem destined to have to create a new USB HID subdriver, I figured I'd get started on the path. I followed all of the directions on the web....I used the script to generate the usbhid subdriver, feeding it the output of the usbhid-ups driver from reading my UPS. All that worked

On Wed, 2011-09-14 at 12:25 +0000, Charles Lepple wrote: > Author: clepple-guest > Date: Wed Sep 14 12:25:03 2011 > New Revision: 3226 > URL: http://trac.networkupstools.org/projects/nut/changeset/3226 > > Log: > Include <string.h> for nut-scanner > > Modified: > trunk/tools/nut-scanner/scan_snmp.c > trunk/tools/nut-scanner/scan_usb.c > >

Hi Arnaud, hi developers, attach there is the patch for riello drivers. Can you tell me if there is other to change in order to accomplish your rules and if the steps I have followed to create the patch are all rights? Cheers, Elio Parisi. Elio Parisi Centro Ricerche RPS SpA Viale Europa, 7 37045 Legnago VR Tel. +39 0442 635811 Fax. +39 0442 635934 Skype Id: - Voip: E-mail: E.Parisi

Hi all, I attached a driver for MiniBox openUPS device ( http://www.mini-box.com/OpenUPS) and a dump of the hid usages. I had the possibility to make a few adjustments to the device firmware for HID usages, and although I haven't managed to produce a good structure many issues from previous firmware were at least fixed and new information added. ATM the driver only shows pertaining