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

I think having this logic buried within libhid/libusb (libusb:libusb_open(), line 179 to 206) is ultimately a mistake, albeit one that I am probably responsible for. Would it make sense to confine libhid to low-level operations, and leave the decision of trying to reopen vs. retrying to open to the high-level driver, in this case usbhid-ups? I envision that the code in usbhid-ups:reconnect_ups()

Hi Alexander, thanks for your good work on the megatec_usb driver. I have made a few more (cosmetic) changes. Is the driver now working stably for your device? In particular, do the instant commands (and particularly "upsdrvctl -k") work properly? In this case, we could hopefully mark the device as "supported" and merge the driver to the main branch. There is still the

Hi All, I've finally found solutions for my previous problems. But since this includes changes in the shared files, I'd like to discuss them here. 1. Driver restart problem. When I start the driver for the first time, everything is ok. But when I want to restart it, problems begin. The driver fails to read Report descriptor for the second time (libusb_open is used to open the device).

> Author: aquette > Date: Thu Jun 21 07:43:46 2007 > New Revision: 971 > > Log: > fix communication lost status handling > > Modified: > trunk/ChangeLog > trunk/drivers/usbhid-ups.c > > Modified: trunk/ChangeLog > ============================================================================== > --- trunk/ChangeLog (original) > +++ trunk/ChangeLog

> ---------- Forwarded message ---------- > From: Arjen de Korte > To: nut-commits at lists.alioth.debian.org > Date: Mon, 27 Aug 2007 18:33:00 +0000 > Subject: svn commit r1076 - in trunk: . drivers > Author: adkorte-guest > Date: Mon Aug 27 18:33:00 2007 > New Revision: 1076 > > Log: > * drivers/libhid.[ch],libshut.[ch],libusb.[ch]: > - Cut the libshut and

I get the following error on r809 (but it looks like the code change happened here). Does HIDDevice_t need to be defined/changed in one of the headers? if gcc -DHAVE_CONFIG_H -I. -I../../drivers -I../include -I../../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -DINET6 -O2 -D_REENTRANT -DNETSNMP_USE_INLINE -Wall -Dlinux -I.

Hello, I've already written to the list before about my non-standard hid Unitek UPS. I've tried to use hiddev to access my UPS as its USB HID interface is the same as the energizerups. Nevertheless, the protocols are different and I didn't manage to communicate with my UPS through hiddev. Moreover, the problem described in this page http://www.vttoth.com/ER-OF800.htm about the Linux

Related to the following question on Stackoverflow: https://stackoverflow.com/questions/44723690/unexpected-behavior-of-sys-setlocale#44723690 It appears as if Sys.setlocale() does not update LC_TIME correctly for use in date formatting. Although R reports that LC_TIME is changed to the new setting after use of Sys.setlocale(), as.Date() still uses the old settings. The only way to update this is

* I committed into CVS the gendb patch that I sent to the mailing list on September 12. Arnaud, I hope you approve of this patch; it is more reliable than the previous method in tracking the correct dependencies. * This, together with some other minor recent changes on the Development branch, is between the "before_PSE_3" and "after_PSE_3" tags. Arnaud: if you

On 1/23/07, Henning Brauer <hb-nut@bsws.de> wrote: > good new first: the megatec driverin 2.0.5 now works with the Online > Xanto S3000R here - well, for the very basics. > > the UPS has NO way ofidentifying itself. It also does not respond to > the power ratings query ("F"). I previously used a hacked up fentonups > driver. This means the driver cannot figure out

Arnaud, you changed the "if" part, perhaps you'd like to change the "else" part, too? Changing the output format of HIDDumpTree() has the potential to break the functionality of scripts/subdriver/path-to-subdriver.sh; I don't think it does in this instance, but I have not checked it. Perhaps it would be good to add a comment in the source code as a caution. -- Peter

2007/3/8, Charles Lepple <clepple-guest@alioth.debian.org>: > Author: clepple-guest > Date: Thu Mar 8 04:15:51 2007 > New Revision: 848 > > Modified: > branches/tl_usb_fbsd/drivers/Makefile.am > branches/tl_usb_fbsd/drivers/libhid-uhid.c > Log: > Work-in-progress... maybe I need to look at how the SHUT subdriver works. > ... simply use the same interface

Just a little tiny detail : ============================================================================== > --- trunk/scripts/hotplug/libhid.usermap (original) > +++ trunk/scripts/hotplug/libhid.usermap Fri Aug 25 19:18:19 2006 > @@ -21,5 +21,7 @@ > libhidups 0x0003 0x09ae 0x1003 0x0000 0x0000 0x00 0x00 0x00 0x00

Full_Name: Mike Ulrich Version: 2.9 OS: Mac OSX Submission from: (NULL) (69.169.178.34) The help documentation for loadings() lists more then one parameter. The function call only expects one parameter. The digits, cutoff, and sort parameters are not used in the function. ## S3 method for class 'loadings': print(x, digits = 3, cutoff = 0.1, sort = FALSE, ...) ## S3 method for class

Arnaud, this commit refers to files called libshut.c and libshut.h, yet no such file has been added to SVN. Perhaps take this opportunity to run "svn status" and check for other files that might be missing from SVN. -- Peter > ---------- Forwarded message ---------- > From: Arnaud Quette > To: nut-commits@lists.alioth.debian.org > Date: Fri, 16 Jun 2006 13:40:59 +0000

2010/12/22 Arjen de Korte <adkorte-guest at alioth.debian.org> > Author: adkorte-guest > Date: Wed Dec 22 20:31:42 2010 > New Revision: 2777 > URL: http://trac.networkupstools.org/projects/nut/changeset/2777 > > Log: > Don't version generated files > > Deleted: > trunk/scripts/hal/ups-nut-device.fdi.in > trunk/scripts/hotplug/libhid.usermap >

Citeren Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Thu Jan 15 20:02:22 2009 > New Revision: 1734 > > Log: > Freshly generated USB helper files > > Modified: > trunk/scripts/hal/ups-nut-device.fdi.in > trunk/scripts/hotplug/libhid.usermap > trunk/scripts/udev/nut-usbups.rules.in Questions is, should we try

Citeren Kjell Claesson <keyson-guest op alioth.debian.org>: > Author: keyson-guest > Date: Mon Mar 23 17:37:37 2009 > New Revision: 1817 > > Log: > data/driver.list, add Eaton Powerware 9130 compatibility with bcmxcp > and usbhid-ups. 1) Is this really true? I would have expected that this device would be supported through bcmxcp (serial) and bcmxcp_usb (USB), like

Hello, all. Some time ago I bought myself a UPS which was advertised as USB-HID. It was a surprise to learn that while it definitely is recognized as USB device, the HID descriptor has no UPS pages at all. The only software it came with was a windows program written in visual basic. Trying to research this topic I found a reference to energizer USB ups driver and learned about variety of

was: Re: [Nut-upsdev] usbhid-ups.h: hid_info_t structure On 8/2/07, Peter Selinger <selinger at mathstat.dal.ca> wrote: > All this needs to be replaced by a re-designed, cleaned-up data > structure. It's on my to-do list, but nothing on that list will get > done by me anytime soon. As nothing is technically broken, and the > changes are prone to introducing subtle bugs, this