Displaying 3 results from an estimated 3 matches for "r1210".
Did you mean:
1210
2008 Jan 11
1
usbhid-ups bug
Hi all,
greetings and a happy new year! I am writing as a user, rather than as
an ex-developer. Usbhid-ups contains a fatal bug that was apparently
introduced in r1210 (I did a binary search to find the exact
revision). Arjen, you wrote "correct me if I'm wrong", so it seems
that's what I am doing.
------------------------------------------------------------------------
r1210 | adkorte-guest | 2008-01-02 16:34:26 -0400 (Wed, 02 Jan 2008) | 3 l...
2008 Jan 02
2
[nut-commits] svn commit r1210 - in trunk: . drivers
On Jan 2, 2008 3:34 PM, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote:
> Author: adkorte-guest
> Date: Wed Jan 2 20:34:26 2008
> New Revision: 1210
>
> Log:
> Parsing continues if the HID path for a report ends in 0x00000000 (these will not be made available). Commonly used as placeholders.
>
> It looks like (but correct me if I'm wrong) that reports
2008 Feb 26
0
[nut-commits] svn commit r1334 - in trunk: . drivers
...34
>
> Log:
> Allocate twice the maximum number of reports we expect (MAX_REPORTS), to
> allow for bogus/duplicate reports.
Retrospectively, this is gross hack at best and probably only good to fix
the problem temporarily. I think I have a better solution available (in a
similar way as r1210, that was broken in another aspect), but that needs a
little more testing. I wrote a parser for the debug output from
'usbhid-ups -DDD -a <upsname>', so that it is easier to see if the old and
new version will be compatible. We probably have sufficient debug logs
available in the arch...