search for: microvolts

Playing a bit with todays linux-next on my jetson, it seems this patch is still required for enabling the GPU. Is there anything blocking it (firmware not available yet in liux-firmware?) On Mon, May 19, 2014 at 06:24:10PM +0900, Alexandre Courbot wrote: > Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> > --- > arch/arm/boot/dts/tegra124-jetson-tk1.dts | 8 +++++++- >

On 09/25/2014 07:27 AM, Sjoerd Simons wrote: > Playing a bit with todays linux-next on my jetson, it seems this patch is > still required for enabling the GPU. Is there anything blocking it (firmware > not available yet in liux-firmware?) I think initially I was waiting for the DRM patch "drm/nouvea: support for probing platform devices" to be applied, but it looks like

Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> --- arch/arm/boot/dts/tegra124-jetson-tk1.dts | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/tegra124-jetson-tk1.dts b/arch/arm/boot/dts/tegra124-jetson-tk1.dts index e31fb61a81d3..15a194d1277f 100644 --- a/arch/arm/boot/dts/tegra124-jetson-tk1.dts +++

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

On Mar 28, 2014, at 9:08 AM, Bill S wrote: > 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.

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 can...

...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 wit...

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 can...