Sponsored Content
Special Forums Hardware ZOTAC NANO AD12...now a paperweight (power prob.) Post 302930354 by DGPickett on Friday 2nd of January 2015 02:19:47 PM
Old 01-02-2015
The conversion of 19vdc down to desired lower and sometimes negative voltages is generaly done on a motherboard using power transistors, diode rectifiers, coils and capacitors. Could be one of the transistors blew, or a cap shorted.
This User Gave Thanks to DGPickett For This Post:
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

nano-2.0.6 HELP!!!!

Hi all, I have this problem. I am running suse linux 10.0 Enterprise. I was able to install nano-2.0.6 and as root I am able to use it. This is where my problem starts. When I exit root and try to use nano, I get this error message. nano: Command not found. but when I type... (3 Replies)
Discussion started by: goku3g
3 Replies

2. Linux

microwindow and nano-X

Dear all I have problem in installing microwindows. What I did 1.I have microwindows-0.90 in home/SHIVA 2.cd microwindows-0.90/src 3.cp configs config 4.make clean; make 5. make 6.now it is giving error :- winevent.c:18: error: static declaration of ‘abs' follows non-static declaration... (0 Replies)
Discussion started by: mishra_sk_in
0 Replies

3. HP-UX

Nano installation for ON HP UX

How to isntall nano on HP UX? Thanks:eek: (1 Reply)
Discussion started by: ldaliosmane
1 Replies

4. UNIX for Dummies Questions & Answers

ZOTAC IONITX-A-U Atom 330 1.6GHz Dual-Core 441 NVI

Has anyone installed on the ZOTAC IONITX-A-U Atom 330 1.6GHz Dual-Core 441 NVIDIA ION Mini ITX platform? If so, what if any, were the challneges that you had? What went smoothly I want to get this board because it looks like a stellar system and perfect for Linux. I'm quite curious about... (2 Replies)
Discussion started by: sarfraz
2 Replies

5. UNIX for Dummies Questions & Answers

using nano x to design GUI

Hi, I am working on a project to develop an embedded device that can transfer files between two usb devices ( pen drives). We are using an NUC950A ARM9 microcontroller and we've put the Linux 2.1 kernel on the development board and it works. Can i use nano -x to design my own GUI so that i can run... (3 Replies)
Discussion started by: dilumcc
3 Replies

6. Shell Programming and Scripting

How to Create files using Nano?

I need to switch files in a directory using Nano thinking i have all the files in the same directory? how would i go about doing that ? (2 Replies)
Discussion started by: JuankyKong
2 Replies

7. Shell Programming and Scripting

Need help with these scripts in nano...

So I am trying to write 3 different scripts using nano. Having some trouble with each. The first one is prompting for the person's information, and I would like to store that information in a new text file. I have most of it complete. The only problem I have here is that I do not know the code... (2 Replies)
Discussion started by: tburns517
2 Replies
power(9E)							Driver Entry Points							 power(9E)

NAME
power - power a device attached to the system SYNOPSIS
#include <sys/ddi.h> #include <sys/sunddi.h> int prefixpower(dev_info_t *dip, int component, int level); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). This entry point is required. If the driver writer does not supply this entry point, the value NULL must be used in the cb_ops(9S) structure instead. PARAMETERS
dip Pointer to the device's dev_info structure. component Component of the driver to be managed. level Desired component power level. DESCRIPTION
The power(9E) function is the device-specific Power Management entry point. This function is called when the system wants the driver to set the power level of component to level. The level argument is the driver-defined power level to which the component needs to be set. Except for power level 0, which is inter- preted by the framework to mean "powered off," the interpretation of level is entirely up to the driver. The component argument is the component of the device to be power-managed. The interpretation of component is entirely up to the driver. When a requested power transition would cause the device to lose state, the driver must save the state of the device in memory. When a requested power transition requires state to be restored, the driver must restore that state. If a requested power transition for one component requires another component to change power state before it can be completed, the driver must call pm_raise_power(9F) to get the other component changed, and the power(9E) entry point must support being re-entered. If the system requests an inappropriate power transition for the device (for example, a request to power down a device which has just become busy), then the power level should not be changed and power should return DDI_FAILURE. RETURN VALUES
The power() function returns: DDI_SUCCESS Successfully set the power to the requested level. DDI_FAILURE Failed to set the power to the requested level. CONTEXT
The power() function is called from user or kernel context only. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
attach(9E), detach(9E), pm_busy_component(9F), pm_idle_component(9F), pm_raise_power(9F), cb_ops(9S) Writing Device Drivers Using Power Management SunOS 5.10 12 Dec 2003 power(9E)
All times are GMT -4. The time now is 06:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy