[Nut-upsdev] R: [HCL] <EPYC> <UPS> supported by <usbhid-ups -Cyber Power>

[Jim Klimov]

For DDL (Device data dump library) it is relatively simple: outputs of upsc
(or better more tools, scripts available to automate) a dir/file with
standardized naming should be PRed to nut-ddl repo. This covers much of the
backlog where people thankfully posted such info on mailing lists and
github issues and some PR comments. Needs lots of time and focus, but is
not "hard".

Then there's also HCL and/or drivers.list file in main codebase, I did not
fully figure out criteria for its maintenance, was too busy with code and
CI.

And possibly, like in this case and some more posted, adding USB VID/PID
combos to driver sources (and testing them, and regenerating udev rules and
similar data) so that devices are handled out of the box. This is somewhat
straightforward when a subdriver exists, so no new code is needed. But
lately there were too many collisions with same USB interface chips used by
unrelated incompatible devices, and/or with chips using some bogus
(unregistered) IDs like 0xffff, 0x0000, 0x1111 or 0x0001 and hoping to be
unique.

On Wed, Dec 8, 2021, 06:09 Strahil Nikolov <hunter86_bg at yahoo.com> wrote:

> Hi Jim,
>
>
> I didn't see any guidance how to proceed with PRs. Maybe you can shed some
> light and I can propose the change for my Powerwalker VFI 3000.
>
> Best Regards,
> Strahil Nikolov
>
> On Wed, Dec 8, 2021 at 1:25, Jim Klimov via Nut-upsdev
> <nut-upsdev at alioth-lists.debian.net> wrote:
> _______________________________________________
> Nut-upsdev mailing list
> Nut-upsdev at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20211211/230e912f/attachment.htm>