Hi JJim,
I've opened a PR for the driver.list (VFI 3000 TG). I will check the nut-ddl
and open a PR with the data from upsc,etc.
Best Regards,
Strahil Nikolov
В събота, 11 декември 2021 г., 02:26:57 Гринуич+2, Jim Klimov
<[email protected]> написа:
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 <[email protected]> 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<[email protected]> wrote:
_______________________________________________
Nut-upsdev mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
_______________________________________________
Nut-upsdev mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
