similar to: NUT supports new VID/PID

Hello, and thanks for the clarifications. As described, the change does not seem to be too complex on the NUT project's side, the PR posted below took about an hour with some research and this write-up, so I'm not sure I can put a price tag on it :) A donation at https://opencollective.com/networkupstools or https://github.com/sponsors/networkupstools would be welcome though, more so a

Hello Jim, That?s a great help for me. You?re a so kind person ~ Our engineer download the branches f17d9f5 as below and repackage it for test. After testing, The Beta NUT works well with ST VID "0x0483", PID "0xA430. Please tell me how to speed up for merging this to formal version. May I have your predict schedule if possible? Thanks.

On a very few GPUs with the voltage table version 0x50 we have to read out the VIDs out of the entries of the table, where all the other gpus are either PWM based or get a base and a step voltage out of the table header. Currently nouveau tried to autodetect this and actually doesn't parse the entries. This Series adds two things: 1. It parses the entries 2. It decides upon a field in the

Hi, I''m trying to pass an intel video card to a guest via VT-D. I got this to work once so i know my system can do it, but I can''t seem to replicate my success. Not sure if something changed in the bios(vt-d is still enabled there), or elsewhere. When I pass a device with gfx_passthru=0 (using config below), guest boots up and the vid card shows up at an incorrect pci id(ie not

Dear Security Team, Ports/japanese/samba is updated to ja-samba-2.2.12-j1.0beta1, which fixes CAN-2004-1154. Please update the portaudit database. >>>>> In <200505242242.j4OMglSA099193@repoman.freebsd.org> >>>>> Pav Lucistnik <pav@FreeBSD.org> wrote: > pav 2005-05-24 22:42:47 UTC > FreeBSD ports repository > Modified files: >

Programming vids (adding or removing them) still passes guest-endian values in the DMA buffer. That's wrong if guest is big-endian and when virtio 1 is enabled. Note: this is on top of a previous patch: virtio_net: split out ctrl buffer Fixes: 9465a7a6f ("virtio_net: enable v1.0 support") Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/net/virtio_net.c | 6

Programming vids (adding or removing them) still passes guest-endian values in the DMA buffer. That's wrong if guest is big-endian and when virtio 1 is enabled. Note: this is on top of a previous patch: virtio_net: split out ctrl buffer Fixes: 9465a7a6f ("virtio_net: enable v1.0 support") Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/net/virtio_net.c | 6

Hmm...well, after it gets the report descriptor, NUT then gets each of the reports defined in there, so that's good. But after that, there are no more messages (no more reports being requested...the NUT debug info just shows "libusb_get_interrupt: Connection timed out" repeatedly). I put in some enticing values into the report descriptor, like shutdownimminent and discharging and

My company is developing a new UPS, with smarts provided by a PIC32 Microchip micro-controller. The controller comes with a demo for a USBHID-UPS, and after some tweaking, I was able to get NUT to recognize it and start showing some reasonable values. To make this UPS as easy to use as possible for the end-user who chooses Linux, I figured I would just completely implement the official USB HID

Resend the mail. ???: Zhan, Cindy (???) ????: 2015?8?28? 16:19 ???: nut-upsdev at lists.alioth.debian.org<mailto:nut-upsdev at lists.alioth.debian.org> ??: Xie, Maggie(???) ??: Request for ew device<0x2B2D/0xFFFF> listed into NUT Dear NUT Developers: We really appreciate for your great job and accomplishment in NUT. It?s interesting and fabulous. It would be great if

Dear Daniele, I'm trying to create a subdriver for 'nutdrv_qx' instead of modifying the Blazer as you suggested, but i honestly don't understand how to integrate usb-serial devices (some of our UPSs have USB but serial protocol Q1). i understand the serial version but not the USB one. i also checked the "Claim" function, but i can't see drivers that uses the VID

Dear ladies and gentlemen, we are developer and producer of UPS devices. Now we would like to integrate a small UPS via USB connection to NAS systems. We heart from third party that we need a special driver for NAS systems to work fine and to display also the company name and UPS device name in the web page / software of NAS. Currently we have a UPS with USB and our own VID (0x2B2D) and PID

Dear Daniele, i understand perfectly, i'd like to explain you why we choosed to clone the blazer_usb driver: some of our devices uses Voltronic Q1 protocol and we tried the Krauler Subdriver (it was the one with the right "commands", Q1, F, etc.), but the issues were 2: - first: the Krauler Subdriver expects a different number of bytes in answer because in debug i see "Short

I am wondering if there is a way to have Nut Server monitor a Minutemen UPS. https://minutemanups.com/uninterruptible-power-supply/pro-rt2u-line-interactive-uninterruptible-power-supply/ Thanks James -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20231213/254b1111/attachment.htm>

On Mar 6, 2014, at 3:55 PM, Rob Groner wrote: > To make this UPS as easy to use as possible for the end-user who chooses Linux, I figured I would just completely implement the official USB HID UPS spec. That way no subdriver would be needed, or at least very little. At the moment, we use USB VID and PID to select which HID-to-NUT tables to consult (since some vendors have "custom"

My personal experience with a number of UPSes that are monitored via USB cable is that communications errors such as the ones referenced in the issue you linked to below are a result of USB hardware incompatibilities between the USB chipset and the USB port on the motherboard.*? This is NOT specific to the NUT project as it affects both apcupsd and in fact, has been reported as an issue with

Hello I installed CentOS 8 on a clean system.I tested a pl2303 ic with different PID. If i use HP PID 0x4349,i will receive junk data after connecting, but the pl2303 PID 0x2303 work normally. Does someone know about how to fix this situation? thanks Test video link: HP VID/PID - https://www.dropbox.com/s/9hj7im5tr4e1v1u/HP.mp4?dl=0 Prolific VID/PID -

I posted earlier on this list about getting an Arduino Pro Micro using https://github.com/abratchik/HIDPowerDevice in a simple sketch to monitor a DIY UPS I have built. With the changes from that thread (I had a PR merged), I was able to get usbhid-ups to recognize my device and could setup NUT the rest of the way. My intended configuration is to run NUT on a Raspberry Pi, have that device be

Hello NUT ! In order to fill info structure I'm putting in the drivers, I need to gather a lot of information. The information I need, at best, is : - For each USB UPS, the pair VendorID ProductID - For each pair Driver/UPS supported, how was made the driver ? By the manufacturer, by reverse engineering, ... - Who contributed to which driver - Who is the "maintener" of each driver

2015-03-17 0:24 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 16, 2015, at 12:26 PM, cinowell <cinowell at gmail.com> wrote: > >> I've done all the steps. However FSD indication did NOT disappear. So it seems UPS always send the FSD flag. One thing more. Can you launch the driver with a debug level of 3 and then report back the log (gzipped) of the same