jkt         08/01/21 12:15:56

  Modified:             power-management-guide.xml
  Log:
  whitespace stuff and line wrapping, *no content change*

Revision  Changes    Path
1.34                 xml/htdocs/doc/en/power-management-guide.xml

file : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.34&view=markup
plain: 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?rev=1.34&content-type=text/plain
diff : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/power-management-guide.xml?r1=1.33&r2=1.34

Index: power-management-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- power-management-guide.xml  21 Jan 2008 12:12:12 -0000      1.33
+++ power-management-guide.xml  21 Jan 2008 12:15:56 -0000      1.34
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.33 
2008/01/21 12:12:12 jkt Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/power-management-guide.xml,v 1.34 
2008/01/21 12:15:56 jkt Exp $ -->
 <guide link="/doc/en/power-management-guide.xml">
 <title>Power Management Guide</title>
 
@@ -155,9 +155,8 @@
 <p>
 There are different kernel sources in Portage. I'd recommend using
 <c>gentoo-sources</c> or <c>tuxonice-sources</c>. The latter contains patches
-for TuxOnIce, see the chapter about <uri link="#doc_chap7">sleep
-states</uri> for more details. When configuring the kernel, activate at least
-these options:
+for TuxOnIce, see the chapter about <uri link="#doc_chap7">sleep states</uri>
+for more details. When configuring the kernel, activate at least these options:
 </p>
 
 <pre caption="Minimum kernel setup for Power Management (Kernel 2.6)">
@@ -1406,8 +1405,8 @@
 </pre>
 
 <p>
-The following section discusses the setup of TuxOnIce including fbsplash
-support for a nice graphical progress bar during suspend and resume.
+The following section discusses the setup of TuxOnIce including fbsplash 
support
+for a nice graphical progress bar during suspend and resume.
 </p>
 
 <p>
@@ -1416,8 +1415,8 @@
 config, you have to pass it as a kernel parameter with the
 <c>resume=swap:/dev/SWAP</c> directive. If booting is not possible due to a
 broken image, append the <c>noresume</c> parameter. Additionally, the
-<c>hibernate-cleanup</c> init script invalidates TuxOnIce images during the
-boot process.
+<c>hibernate-cleanup</c> init script invalidates TuxOnIce images during the 
boot
+process.
 </p>
 
 <pre caption="Invalidating TuxOnIce images during the boot process">
@@ -1438,9 +1437,8 @@
 
 <p>
 Please configure <c>fbsplash</c> now if you didn't do already. To enable
-fbsplash support during hibernation, the <c>sys-apps/tuxonice-userui</c>
-package is needed. Additionally, you've got to enable the <c>fbsplash</c> USE
-flag.
+fbsplash support during hibernation, the <c>sys-apps/tuxonice-userui</c> 
package
+is needed. Additionally, you've got to enable the <c>fbsplash</c> USE flag.
 </p>
 
 <pre caption="Installing tuxonice-userui">
@@ -1511,15 +1509,14 @@
 <p>
 <e>A:</e> Make sure your processor supports CPU frequency scaling and you chose
 the right CPUFreq driver for your processor. Here is a list of processors that
-are supported by cpufreq (kernel 2.6.7): ARM Integrator, ARM-SA1100,
-ARM-SA1110, AMD Elan - SC400, SC410, AMD mobile K6-2+, AMD mobile K6-3+, AMD
-mobile Duron, AMD mobile Athlon, AMD Opteron, AMD Athlon 64, Cyrix Media GXm,
-Intel mobile PIII and Intel mobile PIII-M on certain chipsets, Intel Pentium 4,
-Intel Xeon, Intel Pentium M (Centrino), National Semiconductors Geode GX,
-Transmeta Crusoe, VIA Cyrix 3 / C3, UltraSPARC-III, SuperH SH-3, SH-4, several
-"PowerBook" and "iBook2" and various processors on some ACPI 2.0-compatible
-systems (only if "ACPI Processor Performance States" are available to the
-ACPI/BIOS interface).
+are supported by cpufreq (kernel 2.6.7): ARM Integrator, ARM-SA1100, 
ARM-SA1110,
+AMD Elan - SC400, SC410, AMD mobile K6-2+, AMD mobile K6-3+, AMD mobile Duron,
+AMD mobile Athlon, AMD Opteron, AMD Athlon 64, Cyrix Media GXm, Intel mobile
+PIII and Intel mobile PIII-M on certain chipsets, Intel Pentium 4, Intel Xeon,
+Intel Pentium M (Centrino), National Semiconductors Geode GX, Transmeta Crusoe,
+VIA Cyrix 3 / C3, UltraSPARC-III, SuperH SH-3, SH-4, several "PowerBook" and
+"iBook2" and various processors on some ACPI 2.0-compatible systems (only if
+"ACPI Processor Performance States" are available to the ACPI/BIOS interface).
 </p>
 
 <p>
@@ -1542,8 +1539,7 @@
 <e>A:</e> Probably you have activated symmetric multiprocessing support
 (CONFIG_SMP) in your kernel. Deactivate it and it should work. Some older
 kernels had a bug causing this. In that case, run <c>emerge x86info</c>, update
-your kernel as asked and check the current frequency with
-<c>x86info -mhz</c>.
+your kernel as asked and check the current frequency with <c>x86info -mhz</c>.
 </p>
 
 <p>
@@ -1553,11 +1549,11 @@
 
 <p>
 <e>A:</e> You can combine frequency scaling with ACPI throttling to get a lower
-minimum frequency. Notice that throttling doesn't save much energy and is
-mainly used for thermal management (keeping your laptop cool and quiet). You
-can read the current throttling state with <c>cat
-/proc/acpi/processor/CPU/throttling</c> and change it with <c>echo -n "0:x" >
-/proc/acpi/processor/CPU/limit</c>, where x is one of the Tx states listed in
+minimum frequency. Notice that throttling doesn't save much energy and is 
mainly
+used for thermal management (keeping your laptop cool and quiet). You can read
+the current throttling state with <c>cat 
/proc/acpi/processor/CPU/throttling</c>
+and change it with <c>echo -n "0:x" > /proc/acpi/processor/CPU/limit</c>, where
+x is one of the Tx states listed in
 <path>/proc/acpi/processor/CPU/throttling</path>.
 </p>
 
@@ -1633,8 +1629,8 @@
 
 <p>
 <e>A:</e> If there is enough free space on your system, you can use the
-filewriter instead of the swapwriter. The <c>hibernate-script</c> supports it
-as well. More information can be found in
+filewriter instead of the swapwriter. The <c>hibernate-script</c> supports it 
as
+well. More information can be found in
 <path>/usr/src/linux/Documentation/power/tuxonice.txt</path>.
 </p>
 



-- 
[email protected] mailing list

Reply via email to