swift       08/05/21 19:29:22

  Modified:             dri-howto.xml
  Log:
  Coding style (trailing whitespace)

Revision  Changes    Path
1.41                 xml/htdocs/doc/en/dri-howto.xml

file : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/dri-howto.xml?rev=1.41&view=markup
plain: 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/dri-howto.xml?rev=1.41&content-type=text/plain
diff : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/dri-howto.xml?r1=1.40&r2=1.41

Index: dri-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/dri-howto.xml,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- dri-howto.xml       23 Aug 2007 22:31:14 -0000      1.40
+++ dri-howto.xml       21 May 2008 19:29:22 -0000      1.41
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/dri-howto.xml,v 1.40 
2007/08/23 22:31:14 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/dri-howto.xml,v 1.41 
2008/05/21 19:29:22 swift Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/dri-howto.xml">
@@ -35,14 +35,14 @@
 <body>
 
 <p>
-With hardware 3D acceleration, three-dimensional rendering uses the graphics 
-processor on your video card instead of taking up valuable CPU resources 
-drawing 3D images. It's also referred to as "hardware acceleration" instead of 
+With hardware 3D acceleration, three-dimensional rendering uses the graphics
+processor on your video card instead of taking up valuable CPU resources
+drawing 3D images. It's also referred to as "hardware acceleration" instead of
 "software acceleration" because without this 3D acceleration your CPU is forced
-to draw everything itself using the Mesa software rendering libraries, which 
+to draw everything itself using the Mesa software rendering libraries, which
 takes up quite a bit of processing power. While Xorg typically supports 2D
-hardware acceleration, it often lacks hardware 3D acceleration. 
-Three-dimensional hardware acceleration is valuable in situations requiring 
+hardware acceleration, it often lacks hardware 3D acceleration.
+Three-dimensional hardware acceleration is valuable in situations requiring
 rendering of 3D objects such as games, 3D CAD and modeling.
 </p>
 
@@ -120,7 +120,7 @@
 <body>
 
 <p>
-With suggestions, questions, etc., e-mail <mail 
+With suggestions, questions, etc., e-mail <mail
 link="[EMAIL PROTECTED]">Donnie Berkholz</mail>.
 </p>
 
@@ -213,7 +213,7 @@
 <body>
 
 <p>
-Open <path>/etc/X11/xorg.conf</path> with your favorite text editor and edit 
+Open <path>/etc/X11/xorg.conf</path> with your favorite text editor and edit
 it to enable DRI and GLX.
 </p>
 
@@ -283,8 +283,8 @@
 direct rendering: Yes
 <comment>(If it says "No", you don't have 3D acceleration.)</comment>
 $ <i>glxgears</i>
-<comment>(Test your frames per second (FPS) at the default size. The number 
should be 
-significantly higher than before configuring DRM. Do this while the CPU is as 
idle as 
+<comment>(Test your frames per second (FPS) at the default size. The number 
should be
+significantly higher than before configuring DRM. Do this while the CPU is as 
idle as
 possible.)</comment>
 </pre>
 
@@ -422,7 +422,7 @@
 <body>
 
 <p>
-That's because you compiled agpgart into the kernel instead of as a module. 
+That's because you compiled agpgart into the kernel instead of as a module.
 Ignore it unless you're having problems.
 </p>
 
@@ -462,7 +462,7 @@
 <body>
 
 <p>
-Edit <path>/etc/X11/xorg.conf</path>. In section "Device" enable ForcePCIMode. 
+Edit <path>/etc/X11/xorg.conf</path>. In section "Device" enable ForcePCIMode.
 </p>
 
 <pre caption="Enabling ForcePCIMode">
@@ -480,11 +480,11 @@
 
 <ol>
   <li>
-    Christopher Webber for suggesting a troubleshooting question about 
changing 
+    Christopher Webber for suggesting a troubleshooting question about changing
     or recompiling kernels
   </li>
   <li>
-    Steve, for suggesting consistency between the cases of dri and DRI in 
+    Steve, for suggesting consistency between the cases of dri and DRI in
     XF86Config
   </li>
 </ol>



-- 
[email protected] mailing list

Reply via email to