Re: [Nut-upsuser] suse linux and nut

2006-08-30 Thread Arnaud Quette
Hi 2006/8/27, Peter Selinger [EMAIL PROTECTED]: ... What's to do here for the NUT developers is: first, improve support for interrupt transfers in newhidups. right, as we still rely on the (very) early code I first wrote. moreover, the big nested if in update is not clean and too heavy.

Re: [Nut-upsuser] suse linux and nut

2006-08-30 Thread Peter Selinger
Arnaud Quette wrote: Hi 2006/8/27, Peter Selinger [EMAIL PROTECTED]: ... What's to do here for the NUT developers is: first, improve support for interrupt transfers in newhidups. right, as we still rely on the (very) early code I first wrote. moreover, the big nested if in update

Re: [Nut-upsuser] suse linux and nut

2006-08-30 Thread Arnaud Quette
2006/8/30, Peter Selinger [EMAIL PROTECTED]: Arnaud Quette wrote: Hi 2006/8/27, Peter Selinger [EMAIL PROTECTED]: ... What's to do here for the NUT developers is: first, improve support for interrupt transfers in newhidups. right, as we still rely on the (very) early code I first

Re: [Nut-upsuser] suse linux and nut

2006-08-30 Thread Peter Selinger
Arnaud Quette wrote: 2006/8/30, Peter Selinger [EMAIL PROTECTED]: Arnaud Quette wrote: Hi 2006/8/27, Peter Selinger [EMAIL PROTECTED]: ... What's to do here for the NUT developers is: first, improve support for interrupt transfers in newhidups. right, as we still

Re: [Nut-upsuser] suse linux and nut

2006-08-27 Thread Marc Collin
Le dimanche 27 ao=3DFBt 2006 12:38, Peter Selinger a =3DE9crit=3DA0: Yes, that's actually useful. It shows that the Windows driver exclusively uses interrupt transfers, something that newhidups is not yet very good at. Decoding the transmitted values by hand, I get the following. The values

Re: [Nut-upsuser] suse linux and nut

2006-08-26 Thread Marc Collin
Le samedi 26 août 2006 09:13, Peter Selinger a écrit : You did make install, right? (Else upsdrvctl might be trying to start an older version of the driver). ./configure --with-user=ups make make usb make install make install-usb mkdir -p /var/state/ups chmod 0700 /var/state/ups chown

Re: [Nut-upsuser] suse linux and nut

2006-08-26 Thread Peter Selinger
Marc Collin wrote: linux64:/home/collinm/Download/trunk # /usr/local/ups/bin/upsc [EMAIL PROTECTED] driver.name: newhidups driver.parameter.port: /dev/hiddev0 driver.version: 2.1.0 driver.version.data: PowerCom HID 0.1 driver.version.internal: 0.30 powercom.coll2.feature3: 1

Re: [Nut-upsuser] suse linux and nut

2006-08-26 Thread Marc Collin
Le samedi 26 août 2006 19:45, Peter Selinger a écrit : Marc Collin wrote: linux64:/home/collinm/Download/trunk # /usr/local/ups/bin/upsc [EMAIL PROTECTED] driver.name: newhidups driver.parameter.port: /dev/hiddev0 driver.version: 2.1.0 driver.version.data: PowerCom HID 0.1

Re: [Nut-upsuser] suse linux and nut

2006-08-25 Thread Peter Selinger
Dear Marc, first, the 'powercom' driver is a serial driver, so it will not work for USB. Second, newhidups does not currently support Powercom. The reason is simple: this is (as far as I remember) the first time we are seeing a Powercom USB device. It might not be too difficult to add support

Re: [Nut-upsuser] suse linux and nut

2006-08-25 Thread Peter Selinger
Marc Collin wrote: Le vendredi 25 ao=C3=BBt 2006 21:51, vous avez =C3=A9crit=C2=A0: Marc, interesting, actually, we have seen this device before; see the posts by Barry Fawthrop around August 1. It is a HID device, but it does not follow the USB HID standard for power devices. So