Nut upsuser - Jun 2024 - Powercom BNT USB fix needs testing

Cheers all,

  Per https://github.com/networkupstools/nut/pull/2480 there seems to have
been a byte-order bug in usbhid-ups subdriver for Powercom that precluded
it from shutdowns.

  I am not fully certain if the problem (or the fix) are
endianness-dependent, so would welcome testing of that PR from various
platforms (x86, arm, ...)

  As usual, I hope
https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests
can get you started.

Thanks in advance,
Jim Klimov
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20240616/6fee4e70/attachment.htm>

Gentle bump :)

If there's anyone with a Powercom USB UPS and preferably a non-x86 computer
to build and test a NUT driver on (to confirm the original problem and the
fix), that would be very helpful :)

Jim


On Sun, Jun 16, 2024 at 12:26?PM Jim Klimov <jimklimov at gmail.com>
wrote:
> Cheers all,
>
>   Per https://github.com/networkupstools/nut/pull/2480 there seems to
> have been a byte-order bug in usbhid-ups subdriver for Powercom that
> precluded it from shutdowns.
>
>   I am not fully certain if the problem (or the fix) are
> endianness-dependent, so would welcome testing of that PR from various
> platforms (x86, arm, ...)
>
>   As usual, I hope
>
https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests
> can get you started.
>
> Thanks in advance,
> Jim Klimov
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240702/e017299a/attachment.htm>