Hello and welcome!
It really depends on what it really means to "add support":
If the needed abilities are already present in an existing driver and its
sub-driver (`usbhid-ups` as you say, if this uses a HID protocol, or
`nutdrv_qx` likely otherwise), and the issue is just about adding the IDs
to the suitable handler so it "knows" it is compatible during device
detection, then it is trivial. In fact, if you go to NUT GitHub Wiki page
to look for "Building in-place" instructions, you can experiment
locally
and post a pull request with a checked-working change set.
If this issue is however about adding a new (or extending an old)
(sub-)driver, then I really hope some of the list members can help with the
investigation and coding.
Hope this helps,
Jim Klimov
On Wed, Feb 7, 2024, 07:50 abeyoungh--- via Nut-upsdev <
nut-upsdev at alioth-lists.debian.net> wrote:
> Hi all,
>
>
>
> I am looking for someone who help me request NUT to supports power
> device which has unregistered VID/PID. I will pay you for your service.
>
>
>
> Detail requirement
>
> 1. New VID "0x0483", PID "0xA430"
> 2. Corresponding driver "usbhid-ups"
> 3. Manufacture "CyberEnergy"
>
>
>
> I have no idea to handle this. If need more information, please let me
> know, thanks.
> _______________________________________________
> 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/20240207/0f2808b9/attachment.htm>