Power Management/lang-es: Difference between revisions

From OLPC
Jump to navigation Jump to search
(inicial draft)
(+ anchors + categorization)
Line 1: Line 1:
{{OLPC}}{{Translation | lang = es | source = Power Management | version = 36691}}{{__TOCright__}}{{Ongoing Translation}}
=Administración de potencia=
<div id="Power Management"/>
<big>Administración de potencia</big>

<div id="Introduction and Related Material"/>
==Introducción y material relacionado==
==Introducción y material relacionado==

Careful stewardship of battery power is critical.
Careful stewardship of battery power is critical.


Line 12: Line 17:
Ademas de manejar efectivamente la potencia que hay en la batería también la pagina [[Battery and power]] discute muchas fuentes alternas de potencia que pueden ser usadas para complementar el actual cargador.
Ademas de manejar efectivamente la potencia que hay en la batería también la pagina [[Battery and power]] discute muchas fuentes alternas de potencia que pueden ser usadas para complementar el actual cargador.


<div id="Linux's Approach to Power Control"/>
==Enfoque de Linux al control de potencia==
==Enfoque de Linux al control de potencia==

Linux is highly cross platform, running on just about all significant architectures, including many that are used for battery powered embedded systems. The infrastructure for power management has therefore become quite sophisticated over the last years, though it is still maturing. This means that the facilities are general, and not tied to any particular architecture. The generation one OLPC system, being from the x86 part of the world, is therefore similar '''and''' fundamentally different from other x86 based systems, for reasons that will become clear in the discussion below.
Linux is highly cross platform, running on just about all significant architectures, including many that are used for battery powered embedded systems. The infrastructure for power management has therefore become quite sophisticated over the last years, though it is still maturing. This means that the facilities are general, and not tied to any particular architecture. The generation one OLPC system, being from the x86 part of the world, is therefore similar '''and''' fundamentally different from other x86 based systems, for reasons that will become clear in the discussion below.


Linux is not dependent on ACPI or the older APM power management systems, which are x86 specific. As such, Linux's design has always done its power control in the operating system, and ACPI and the like are considered "platform dependent".
Linux is not dependent on ACPI or the older APM power management systems, which are x86 specific. As such, Linux's design has always done its power control in the operating system, and ACPI and the like are considered "platform dependent".


<div id="OLPC's Innovations"/>
==Innovaciones de OLPC==
==Innovaciones de OLPC==

The DCON chip lets us take over refresh of our very low power flat panel
The DCON chip lets us take over refresh of our very low power flat panel
and therefore completely power off the processor board. Given our flat panel is usable in gray scale mode at .1 watt, you can see that the leakage
and therefore completely power off the processor board. Given our flat panel is usable in gray scale mode at .1 watt, you can see that the leakage
Line 24: Line 33:
We are also able to leave the Marvell wireless module to operate independently, forwarding packets in the mesh while possibly
We are also able to leave the Marvell wireless module to operate independently, forwarding packets in the mesh while possibly
everything else is powered down.
everything else is powered down.

<div id="Firmware (aka BIOS on conventional PC's)"/>
==Firmware (BIOS en PC's convencionales)==
==Firmware (BIOS en PC's convencionales)==

<div id="Use of Open Firmware"/>
===Uso del Open Firmware===
===Uso del Open Firmware===

Rather than using a conventional BIOS and boot loader, as of the "C" series of our firmware we are using [[Open Firmware]]. We no longer use [http://www.linuxbios.org/Welcome_to_LinuxBIOS LinuxBIOS] for the setup of our systems. This is a result of having implemented fast past resume from RAM; once you have implemented this, setup of the system initially is almost identical.
Rather than using a conventional BIOS and boot loader, as of the "C" series of our firmware we are using [[Open Firmware]]. We no longer use [http://www.linuxbios.org/Welcome_to_LinuxBIOS LinuxBIOS] for the setup of our systems. This is a result of having implemented fast past resume from RAM; once you have implemented this, setup of the system initially is almost identical.


We have also removed VSA and VESA support (the Geode Virtual Systems Support) from our firmware. Since our PCI bus is fixed, we have no need for PCI configuration registers. Similarly, using the fbdev driver on Linux, we have no need for VESA emulation; while the PCI bus emulation was free software (AMD had generously made it available), the VESA emulation was the one part of VSA that they did not own, and so we did not have source for it. We did not want an unmaintainable binary blob in our firmware that we did not need anyway, and saves space in the flash for other purposes.
We have also removed VSA and VESA support (the Geode Virtual Systems Support) from our firmware. Since our PCI bus is fixed, we have no need for PCI configuration registers. Similarly, using the fbdev driver on Linux, we have no need for VESA emulation; while the PCI bus emulation was free software (AMD had generously made it available), the VESA emulation was the one part of VSA that they did not own, and so we did not have source for it. We did not want an unmaintainable binary blob in our firmware that we did not need anyway, and saves space in the flash for other purposes.

<div id="Fast Resume"/>
===Fast Resume===
===Fast Resume===

Resume on our system is extremely fast: even without any serious attempt to optimize resume, we can resume from RAM in 160 milliseconds (mid-April). We believe the hardware limitations for resume are about 63 milliseconds on the B2 and before systems; B3 and later are probably similar. We will work in the future to further speed resume. Note that for most uses, 100ms is considered at the edge of human perception (e.g. typing).
Resume on our system is extremely fast: even without any serious attempt to optimize resume, we can resume from RAM in 160 milliseconds (mid-April). We believe the hardware limitations for resume are about 63 milliseconds on the B2 and before systems; B3 and later are probably similar. We will work in the future to further speed resume. Note that for most uses, 100ms is considered at the edge of human perception (e.g. typing).

<div id="System Identification"/>
===Identificación del sistema===
===Identificación del sistema===

The [[Manufacturing Data]] page documents the Model ID string, part number, localization information, factory, BIOS version, and many other pieces of data.
The [[Manufacturing Data]] page documents the Model ID string, part number, localization information, factory, BIOS version, and many other pieces of data.


<div id="Quiet Boot"/>
===Quiet Boot===
===Quiet Boot===

Boot is not "quiet" at this time. Linux has facilities to make a splash screen at boot overlay the boot messages, but OLPC has not implemented this as yet. [http://dev.laptop.org/ticket/1394 Bug #1394] tracks this issue for eventual resolution.
Boot is not "quiet" at this time. Linux has facilities to make a splash screen at boot overlay the boot messages, but OLPC has not implemented this as yet. [http://dev.laptop.org/ticket/1394 Bug #1394] tracks this issue for eventual resolution.

<div id="POST Message"/>
===POST Message===
===POST Message===

At this moment (prior to Q2C10, at a minimum), if any key is pressed during the initial countdown after the initial message, the boot sequence is stopped and OFW's command interpreter invoked. OFW gives a cheery "ok" message to indicate it is ready for a command.
At this moment (prior to Q2C10, at a minimum), if any key is pressed during the initial countdown after the initial message, the boot sequence is stopped and OFW's command interpreter invoked. OFW gives a cheery "ok" message to indicate it is ready for a command.

<div id="Open Firmware Command Prompt"/>
===Open Firmware Command Prompt===
===Open Firmware Command Prompt===

The [[OFW FAQ]] answers some of the most common questions of how to interact with the OLPC OFW firmware.
The [[OFW FAQ]] answers some of the most common questions of how to interact with the OLPC OFW firmware.

<div id="Power Management Support"/>
==Power Management Support==
==Power Management Support==

As discussed above, Linux does not depend on ACPI. To meet our fast resume goals and transparency into the firmware, we do not use ACPI, which would significantly slow our resume from suspend while adding no benefit. In this regard, we differ significantly from other x86 systems. This is the normal case for Linux on other architectures, so should not be regarded as unusual for Linux overall.
As discussed above, Linux does not depend on ACPI. To meet our fast resume goals and transparency into the firmware, we do not use ACPI, which would significantly slow our resume from suspend while adding no benefit. In this regard, we differ significantly from other x86 systems. This is the normal case for Linux on other architectures, so should not be regarded as unusual for Linux overall.

<div id="Power Button"/>
===Botón de Prendido/Apagado===
===Botón de Prendido/Apagado===

The power button on OLPC serves as a power button.
The power button on OLPC serves as a power button.

<div id="Momentary Button Push"/>
====Momentary Button Push====
====Momentary Button Push====

The system will suspend to RAM after the button is pressed momentarily. Wireless will be left operational when suspended this way.
The system will suspend to RAM after the button is pressed momentarily. Wireless will be left operational when suspended this way.
(Prior to deployment of suspend/resume, this button currently performs a clean Linux shutdown). See [http://dev.laptop.org/ticket/1396 bug #1396] for more information.
(Prior to deployment of suspend/resume, this button currently performs a clean Linux shutdown). See [http://dev.laptop.org/ticket/1396 bug #1396] for more information.

<div id="Four Second Button Push"/>
====Four Second Button Push====
====Four Second Button Push====

Pressing the power button for four seconds does a hard reset of the system and all state is lost.
Pressing the power button for four seconds does a hard reset of the system and all state is lost.

<div id="Power Management States"/>
===Estados de Administración de Potencia===
===Estados de Administración de Potencia===

The following are the major operating states of the system. For simplicity's sake in using commonly understood terminology, see [http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface Wikipedia's ACPI article].
The following are the major operating states of the system. For simplicity's sake in using commonly understood terminology, see [http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface Wikipedia's ACPI article].

<div id="Powered Down"/>
====Powered Down====
====Powered Down====

In this state, (G3 is this state in ACPI). Everything is off and the battery can be swapped. The operating system will have to be booted to start operation; the RAM is not preserved. On our hardware, if power is available, the EC will be powered up and potentially charging the battery.
In this state, (G3 is this state in ACPI). Everything is off and the battery can be swapped. The operating system will have to be booted to start operation; the RAM is not preserved. On our hardware, if power is available, the EC will be powered up and potentially charging the battery.

<div id="Suspended, with Mesh Active, No screen"/>
====Suspended, with Mesh Active, No screen====
====Suspended, with Mesh Active, No screen====

A common mode of use will be the system not being used, but still active forwarding in the mesh network on behalf of others in the mesh, but otherwise unused. This differs from our powered down state by the fact the Marvell wireless will be powered up, and active. In ACPI terminology, the closest match is G1/S3. The processor is suspended to RAM (in self-refresh).
A common mode of use will be the system not being used, but still active forwarding in the mesh network on behalf of others in the mesh, but otherwise unused. This differs from our powered down state by the fact the Marvell wireless will be powered up, and active. In ACPI terminology, the closest match is G1/S3. The processor is suspended to RAM (in self-refresh).

<div id="Suspended, with Mesh Active, Screen Enabled"/>
====Suspended, with Mesh Active, Screen Enabled====
====Suspended, with Mesh Active, Screen Enabled====

Another common mode of use is sometimes called "ebook mode". Both the screen and the Marvell wireless are left operational: the screen by use of the DCON chip. This differs from our powered down state by the fact the Marvell wireless will be powered up, and active along with the display. In ACPI terminology, the closest match is G1/S3. The processor is suspended to RAM (in self-refresh). Note that the DCON has facilities to implement a "screen saver" where it can disable itself and the backlight after a preset time without requiring the system to be resumed from RAM.
Another common mode of use is sometimes called "ebook mode". Both the screen and the Marvell wireless are left operational: the screen by use of the DCON chip. This differs from our powered down state by the fact the Marvell wireless will be powered up, and active along with the display. In ACPI terminology, the closest match is G1/S3. The processor is suspended to RAM (in self-refresh). Note that the DCON has facilities to implement a "screen saver" where it can disable itself and the backlight after a preset time without requiring the system to be resumed from RAM.

<div id="System fully operational"/>
====System fully operational====
====System fully operational====

In this state, the system is available for normal use. The ACPI processor states that this corresponds to are C0 and C1 (note that C1 is not useful on a GX, but does save power on the LX). Linux is working very hard to remove "ticks"; as of this writing, the kernel is now "tickless" and this is operational on OLPC, meaning that it no longer uses a periodic timer clock interrupt to drive the scheduling of processes (which had caused 250 interrupts and transitions from C1 to C0 per second). The OLPC has been observed at 40 per second. Work is underway in user space to abolish polling of hardware that might force wakeups, and private communications are that a full Gnome environment has been seen as low as only a few wakeups/second.
In this state, the system is available for normal use. The ACPI processor states that this corresponds to are C0 and C1 (note that C1 is not useful on a GX, but does save power on the LX). Linux is working very hard to remove "ticks"; as of this writing, the kernel is now "tickless" and this is operational on OLPC, meaning that it no longer uses a periodic timer clock interrupt to drive the scheduling of processes (which had caused 250 interrupts and transitions from C1 to C0 per second). The OLPC has been observed at 40 per second. Work is underway in user space to abolish polling of hardware that might force wakeups, and private communications are that a full Gnome environment has been seen as low as only a few wakeups/second.


Note that in this state, Linux may have many parts of the system powered down: e.g. audio, GPU, etc. as described in detail below.
Note that in this state, Linux may have many parts of the system powered down: e.g. audio, GPU, etc. as described in detail below.

<div id="Switches"/>
==Switches==
==Switches==

<div id="Lid Close Switch"/>
===Lid Close Switch===
===Lid Close Switch===

<div id="Ebook Sense Switch"/>
===Ebook Sense Switch===
===Ebook Sense Switch===

<div id="Rotation Switch"/>
===Rotation Switch===
===Rotation Switch===

<div id="Thermal Management"/>
==Thermal Management==
==Thermal Management==

<div id="Configuration"/>
==Configuración==
==Configuración==

<div id="Boot Configuration"/>
===Configuración del Boot===
===Configuración del Boot===

<div id="Device Tree"/>
===Device Tree===
===Device Tree===

<div id="Video RAM"/>
===Video RAM===
===Video RAM===

<div id="System Resources"/>
===Recursos del sistema===
===Recursos del sistema===

<div id="IRQ Map"/>
===Mapa IRQ ===
===Mapa IRQ ===

<div id="DMA Map"/>
===Mapa DMA ===
===Mapa DMA ===

<div id="Status Indicators"/>
==Indicadores de Estado==
==Indicadores de Estado==

<div id="Wireless Lights"/>
===Wireless Lights===
===Wireless Lights===

<div id="Battery LED"/>
====LED de la Bateria====
====LED de la Bateria====

<div id="Microphone LED"/>
====LED del Microfono====
====LED del Microfono====

<div id="Camera LED"/>
====LED de la Camara====
====LED de la Camara====

<div id="Security"/>
==Seguridad==
==Seguridad==

<div id="Firmware Recovery"/>
===Firmware Recovery===
===Firmware Recovery===

<div id="Special Function Keys"/>
==Special Function Keys==
==Special Function Keys==

<div id="Video"/>
===Video===
===Video===

<div id="Wireless"/>
===Wireless===
===Wireless===

<div id="System Management BIOS Interface"/>
===System Management BIOS Interface===
===System Management BIOS Interface===

Not Supported
Not Supported

<div id="Battery Subsystem"/>
===Subsistema de la Batería===
===Subsistema de la Batería===

<div id="Hardware Power Management"/>
==Hardware Power Management==
==Hardware Power Management==

<div id="Device Tree Support"/>
===Device Tree Support===
===Device Tree Support===

<div id="Power Management"/>
===Power Management===
===Power Management===

<div id="Device Power Down"/>
====Device Power Down====
====Device Power Down====

<div id="Sleeping States"/>
====Sleeping States====
====Sleeping States====

<div id="Thermal Management"/>
====Thermal Management====
====Thermal Management====

<div id="Lid Close"/>
====Lid Close====
====Lid Close====

<div id="PCI Subsystem ID's"/>
===PCI Subsystem ID's===
===PCI Subsystem ID's===

<div id="Keyboard Languages Support"/>
===Keyboard Languages Support===
===Keyboard Languages Support===

<div id="CPU Support"/>
===CPU Support===
===CPU Support===

<div id="Memory Module Support"/>
===Memory Module Support===
===Memory Module Support===

<div id="Wireless Devices"/>
===Wireless Devices===
===Wireless Devices===

<div id="One Touch Buttons"/>
===One Touch Buttons===
===One Touch Buttons===

<div id="Platform Software"/>
==Platform Software==
==Platform Software==

<div id="Screen"/>
===Screen===
===Screen===

<div id="DCON mode"/>
====DCON mode====
====DCON mode====

<div id="Refresh Rate"/>
====Refresh Rate====
====Refresh Rate====

<div id="GPU Powered Up"/>
====GPU Powered Up====
====GPU Powered Up====

<div id="Audio"/>
===Audio===
===Audio===

<div id="USB"/>
===USB===
===USB===

<div id="Keyboard/Touchpad"/>
===Keyboard/Touchpad===
===Keyboard/Touchpad===


[[Category:Hardware]]
[[Category:Battery & Power]]

Revision as of 13:35, 4 May 2007

  Esta página está supervisada por el equipo de OLPC.
  Traducción de Power Management original  
  english | español | 日本語 | 한국어   +/- cambios  
This is an on-going translation

Administración de potencia

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Power_Management/lang-es&oldid=36692"