search for: microvolt

...000868 { > pinctrl-names = "default"; > pinctrl-0 = <&state_default>; > @@ -1505,7 +1511,7 @@ > regulator-always-on; > }; > > - sd6 { > + vdd_gpu: sd6 { > regulator-name = "+VDD_GPU_AP"; > regulator-min-microvolt = <650000>; > regulator-max-microvolt = <1200000>; -- If you put it off long enough, it might go away.

...default"; >> pinctrl-0 = <&state_default>; >> @@ -1505,7 +1511,7 @@ >> regulator-always-on; >> }; >> >> - sd6 { >> + vdd_gpu: sd6 { >> regulator-name = "+VDD_GPU_AP"; >> regulator-min-microvolt = <650000>; >> regulator-max-microvolt = <1200000>; >

...;&vdd_gpu>; + }; + pinmux: pinmux at 0,70000868 { pinctrl-names = "default"; pinctrl-0 = <&state_default>; @@ -1505,7 +1511,7 @@ regulator-always-on; }; - sd6 { + vdd_gpu: sd6 { regulator-name = "+VDD_GPU_AP"; regulator-min-microvolt = <650000>; regulator-max-microvolt = <1200000>; -- 1.9.2

This patch series is the final (?) step towards the initial support of GK20A, allowing it to be probed and used (currently at a very slow speed, and for offscreen rendering only) on the Jetson TK1 and Venice 2 boards. The main piece if the first patch which adds platform devices probing support to Nouveau. There are probably lots of things that need to be discussed about it, e.g.: * The way the

...uot;24.0" is slightly optimistic on my part ;-) but the value "f0" is hex for 240, so the UPS is capable of reporting increments of 0.1V. We used to print the floating point values with "%.6f" or similar, which is IMHO slightly more misleading since nobody is measuring with microvolt resolution. That's been on my list to fix for some time now. ConfigVoltage (battery.voltage.nominal) is often an even multiple of 12V, but you're right, the actual voltage should be higher for fully-charged batteries. That voltage may be hiding somewhere else in the report. If there is a...

On Fri, Mar 28, 2014 at 8:12 AM, Charles Lepple <clepple at gmail.com> wrote: <<Snip>> > > I'll be honest, I haven't really done much with the CGI scripts lately. For debugging values, it is probably better to be closer to the driver. I'd recommend using "upsc" or the driver logs. > > To that end, the .ac.txt and .bat.txt files both show 24.0 V:

...Also, we occasionally run across cosmetic errors in the output data: http://thread.gmane.org/gmane.comp.monitoring.nut.devel/6482 While this shouldn't affect the shutdown sequence, we do try to correct the returned measurements if we can identify a good algorithm. If all of the voltages are in microvolts (including the config voltages), we can apply a multiplier across the board. But if only some of the exponents are wrong, it is harder to write a general rule that won't break when the HID descriptor in the firmware is fixed. If there is a firmware revision that we can compare against, that ca...

...her random USB devices besides UPSes, so we don't just do a wildcard entry for everything with Tripp Lite's VendorID. Also, many Tripp Lite devices have what I would consider to be bugs in the HID descriptor, and so many values end up being reported in the wrong units (Hz*100 for frequency, microvolts for voltage measurements, etc.). When we add a product ID to the table, we also try to correct for the obvious typos. If this doesn't work, please save the logs and let us know what failed. > So, looking around and after spending some time looking at things that had > nothing to do wi...

Hello, My name is Eric Cobb and I am a Product Specialist with Tripp Lite. We have tested your latest NUT distributions against our HID USB compatible UPS systems and would like to know what is needed and/or who is needed to contact in order to updated the listing of compatible Tripp Lite UPS systems in your HCL list? Best Regards, Eric K. Cobb Product Management Specialist [Tripp Lite] 1111

I have a user running centos 6.8 with a brand new Tripplite HID (protocol 4016) UPS. So I installed nut 6.5 from EPEL and it sometimes worked, and it sometimes didn't, and it seemed to be very inconsistent about loading the device driver. So, looking around and after spending some time looking at things that had nothing to do with the real problem, I instead wiped the full install,

...Also, we occasionally run across cosmetic errors in the output data: http://thread.gmane.org/gmane.comp.monitoring.nut.devel/6482 While this shouldn't affect the shutdown sequence, we do try to correct the returned measurements if we can identify a good algorithm. If all of the voltages are in microvolts (including the config voltages), we can apply a multiplier across the board. But if only some of the exponents are wrong, it is harder to write a general rule that won't break when the HID descriptor in the firmware is fixed. If there is a firmware revision that we can compare against, that ca...