public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sven Vermeulen <swift@stork.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: dri-howto.xml
Date: Wed, 21 May 2008 19:29:22 +0000	[thread overview]
Message-ID: <E1Jyu02-0000D1-I0@stork.gentoo.org> (raw)

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="dberkholz@gentoo.org">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>



-- 
gentoo-doc-cvs@lists.gentoo.org mailing list



             reply	other threads:[~2008-05-21 19:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 19:29 Sven Vermeulen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-06  9:42 [gentoo-doc-cvs] cvs commit: dri-howto.xml Joshua Saddler
2008-09-10 21:20 Joshua Saddler
2007-04-26  3:45 Josh Saddler
2007-02-18 23:44 Josh Saddler
2006-10-10  9:36 Xavier Neys
2006-10-10  9:35 Xavier Neys
2006-10-09 13:43 Josh Saddler
2006-10-09 13:41 Josh Saddler
2006-07-31 19:37 Jan Kundrat
2006-05-12 19:32 Josh Saddler
2006-05-07 12:39 Josh Saddler
2006-02-01 11:58 Xavier Neys
2005-12-16  7:30 Shyam Mani
2005-10-11  3:46 swift
2005-07-30 21:48 Xavier Neys
2005-07-30  9:47 Xavier Neys
2005-07-27 12:45 Shyam Mani
2005-07-13 12:57 Sven Vermeulen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1Jyu02-0000D1-I0@stork.gentoo.org \
    --to=swift@stork.gentoo.org \
    --cc=docs-team@lists.gentoo.org \
    --cc=gentoo-doc-cvs@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox