similar to: drivers/Doxyfile

Displaying 20 results from an estimated 3000 matches similar to: "drivers/Doxyfile"

2005 Sep 12
1
Re: Status of the PSE NUT patches (was: NUT patches)
[I'm switching my dev address to @gmail.com instead of @mgeups... please, update your bookmark] Peter Selinger wrote: > > Arnaud Quette wrote: > > > > Here is the status of PSE (Peter Selinger) NUT patches > > for newhidups (hidparser, apc support, ...). > > > > - nut-cvs-patch-REOPEN-2005-08-24: > > approved and applied on Development tree > >
2009 Mar 23
1
[nut-commits] svn commit r1817 - in trunk: . data
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
2005 Nov 08
1
adding libusb CFLAGS to generic-hid.c rule
Peter, attached is a proposed patch to fix compilation of generic-hid.c when libusb's usb.h is not in /usr/include (but the -I flag is provided by "libusb-config --cflags"). It fixes the build under OS X, where Fink installs libusb with --prefix=/sw. I changed "usb.h" to <usb.h> so that 'make depend' wouldn't generate a dependency on 'usb.h' with
2006 Oct 16
1
doxygen (was: Re: NUT and Automake)
On 10/15/06, Peter Selinger <selinger@mathstat.dal.ca> wrote: > I have converted NUT's build system to Automake/Libtool. Right now, > the new build system is contained in the "automake" branch, at: Wow... this is really nice. Thanks for taking the time to do the conversion. > drivers/Doxyfile - this seems to belong to Charles. Perhaps >
2007 May 20
1
Sweex 1000VA UPS (was: powermust usb)
--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the
2007 May 20
1
Sweex 1000VA UPS (was: powermust usb)
--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the
2009 Jun 05
3
Tripplite Smart1500
Hello, We have a Tripplite SMART1500RMXL2U and nut-2.2.0-6.el5 installed on Centos 5.3. I've been unsuccessful on getting upsmon to work. usdrvctl seems to start despite some warnings/errors: # upsdrvctl start smart1500 Network UPS Tools - UPS driver controller 2.2.0- Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11.1 (2.2.0-) Warning: This is an experimental driver. Some
2015 Mar 09
2
Install problems (group permissions) with nut 2.7.2
Ok, I tried this from scratch on a fresh 2.7.2 directory. I followed the web instructions, specifically: + I generated the new subdriver for my UPS (rtd-hid.*) based on PATH info. + I put them in the drivers subdir + I added the include line (#include rtd-hid.h) in usbhid-ups.c (specifically in the #ifndef SHUT_MODE section) + I added &rtd_subdriver, to the subdriver_list in usbhid-ups.c
2014 Nov 09
0
Emerson/Liebert GXT3
On Nov 9, 2014, at 8:13 AM, Marcelo Fernandez <marcelo.fidel.fernandez at gmail.com> wrote: > 2014-11-09 9:59 GMT-03:00 Charles Lepple <clepple at gmail.com>: >> >> Strange, I would have thought that the "Value: 0" would show the actual number. Does it look like drivers/libhid.o got rebuilt? > > Yes, at first I thought the same (that I did something
2014 Nov 09
2
Emerson/Liebert GXT3
2014-11-09 9:59 GMT-03:00 Charles Lepple <clepple at gmail.com>: > On Nov 9, 2014, at 6:58 AM, Marcelo Fernandez <marcelo.fidel.fernandez at gmail.com> wrote: > >> I'm attaching a new debug log with this modification, just in case, >> but I'm still seeing the lines you've pointed at: >> >> 0.062308 Path: UPS.PowerSummary.Voltage, Type:
2007 Aug 23
1
[nut-commits] svn commit r1073 - 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()
2007 Aug 28
0
[nut-commits] svn commit r1076 - in trunk: . drivers
> ---------- 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
2005 Aug 25
3
Tr : NUT patches
Hi Peter, I've forwarded your mail to upsdev as it will be of interest for several people that are working on it. As I'm also on vacation (again) for a week and 1/2 as of this evening, I don't think I'll have the time for it before I get back.... I've not yet audited the patches, but these are queued on the Alioth tracker:
2009 Jan 15
1
[nut-commits] svn commit r1734 - in trunk/scripts: hal hotplug udev
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
2005 Nov 08
0
gcc4 noise
Is anyone besides me using gcc 4.*.*? I noticed that NUT generates an enormous amount of warning noise with that compiler, mostly due to implicit casts between signed/unsigned pointer types. Any volunteers to de-noise the code a bit? The easy way is to insert typecasts; the better way is to actually take care about signedness. -- Peter gcc -I../include -O -Wall -Wsign-compare -c -o everups.o
2017 Jan 28
2
make check error (opus 1.1.4)
Hi I am not sure if this issue has been resolved, but on the latest opus 1.1.4, * I downloaded the tarball, * ran ./configure followed by * make and then * make check Can you please help? Thank you make[3]: Entering directory `/prj/avspw/karthikr/Development/BFamily/Broadcast/SDM845/Opus/opus-1.1.4/doc' doxygen Warning: ignoring unsupported tag
2008 Aug 16
1
[nut-commits] svn commit r1520 - in trunk: . drivers
Charles Lepple wrote: > Author: clepple-guest > Date: Fri Aug 15 23:49:44 2008 > New Revision: 1520 > > Log: > drivers/tripplite_usb.c: Increase send retries to 10 (as needed by some > protocol 2001 units) Would you mind if I made an attempt to re-engineer the reconnection and USB error handling code of this driver? Best regards, Arjen
2010 Dec 23
1
[nut-commits] svn commit r2777 - in trunk: data docs/man drivers scripts/hal scripts/hotplug scripts/udev
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 >
2007 Oct 03
2
[nut-commits] svn commit r1136 - in trunk: . drivers
> Author: agordeev-guest > Date: Wed Oct 3 00:09:21 2007 > New Revision: 1136 > > Log: > - drivers/megatec_usb.c: added ability to do subdriver-specific > initialization, and moved some shared code to agiler init function > since krauler doesn't need it. [...] I'm not very thrilled about this patch: 1) Down at the subdriver level, one shouldn't use
2006 Oct 16
5
NUT and Automake
Dear NUT developers, I have converted NUT's build system to Automake/Libtool. Right now, the new build system is contained in the "automake" branch, at: ssh://svn.debian.org/svn/nut/branches/automake I plan to merge this into the main branch after a period of testing, if there are no objections. Here are some highlights: * automatic dependency tracking: no more need to do this