Power Management/lang-es: Difference between revisions

From OLPC
Jump to navigation Jump to search
Line 343: Line 343:
* if both are lit, then you know you are a mesh portal for a mesh to the internet.
* if both are lit, then you know you are a mesh portal for a mesh to the internet.
Note that this behavior has not been implemented yet, and will require work in the NetworkManager daemon, as it is probably the best place that knows if connectivity is available. See [http://dev.laptop.org/ticket/1385 bug #1385] to track progress.
Note that this behavior has not been implemented yet, and will require work in the NetworkManager daemon, as it is probably the best place that knows if connectivity is available. See [http://dev.laptop.org/ticket/1385 bug #1385] to track progress.
| display = block }}
| display = none }}


<div id="Power Indicator LED"/>
<div id="Power Indicator LED"/>
Line 377: Line 377:
{{ Translated text |
{{ Translated text |
If the microphone is enabled, the microphone LED is lit. This is a hardware feature than cannot be circumvented.
If the microphone is enabled, the microphone LED is lit. This is a hardware feature than cannot be circumvented.
| display = block }}
| display = none }}


<div id="Camera LED"/>
<div id="Camera LED"/>
Line 385: Line 385:
{{ Translated text |
{{ Translated text |
If the camera is powered on, the camera LED will be lit. This is a hardware feature than cannot be circumvented.
If the camera is powered on, the camera LED will be lit. This is a hardware feature than cannot be circumvented.
| display = block }}
| display = none }}


<div id="Firmware (aka BIOS on conventional PC's)"/>
<div id="Firmware (aka BIOS on conventional PC's)"/>
Line 399: Line 399:
Rather than using a conventional BIOS and boot loader, as of the "C" series of our firmware we are solely using [[Open Firmware]]. We no longer use [http://www.linuxbios.org/Welcome_to_LinuxBIOS LinuxBIOS] for the setup of our systems. Fast path resume from RAM requires setting up the entire system: 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 solely using [[Open Firmware]]. We no longer use [http://www.linuxbios.org/Welcome_to_LinuxBIOS LinuxBIOS] for the setup of our systems. Fast path resume from RAM requires setting up the entire system: 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 we did not have source for it. We did not want an unneeded unmaintainable binary blob in our firmware, and removing VSA and VESA support 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 we did not have source for it. We did not want an unneeded unmaintainable binary blob in our firmware, and removing VSA and VESA support saves space in the flash for other purposes.
| display = block }}
| display = none }}


<div id="Fast Resume"/>
<div id="Fast Resume"/>
Line 408: Line 408:
{{ Translated text |
{{ Translated text |
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 are still determining the minimum resume time, as a 63ms delay we thought was required has a workaround in the Geode. B3 and later systems are probably similar to the GX. 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 are still determining the minimum resume time, as a 63ms delay we thought was required has a workaround in the Geode. B3 and later systems are probably similar to the GX. 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).
| display = block }}
| display = none }}


<div id="System Identification"/>
<div id="System Identification"/>
Line 417: Line 417:
{{ Translated text |
{{ Translated text |
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.
| display = block }}
| display = none }}


<div id="Quiet Boot"/>
<div id="Quiet Boot"/>
Line 647: Line 647:


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

=Seguridad=
=Seguridad=


Revision as of 05:07, 30 May 2007

Administración de Energía

  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

XO-1 Especificación de Software

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