[PATCH] Documentation fixes in intel810.txt · 9b262144a1 - evie/android_kernel_oneplus_msm8998 - Gay Catgirls Forgejo: gay catgirls having sex

evie/android_kernel_oneplus_msm8998

[PATCH] Documentation fixes in intel810.txt

Signed-off-by: Reiner Herrmann <reiner@reiner-h.de>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Cc: "Antonino A. Daplas" <adaplas@pol.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

This commit is contained in:

Reiner Herrmann

2006-10-03 01:15:08 -07:00

• committed by

Linus Torvalds

parent b98fc9a34b

commit 9b262144a1

1 changed files with 76 additions and 74 deletions

46

Documentation/fb/intel810.txt

View file

 ================================================================
 A. Introduction
 	This is a framebuffer driver for various Intel 810/815 compatible
-graphics devices.  These would include:
+	graphics devices.  These include:
 	Intel 810
 	Intel 810E
 B.  Features
-        - Choice of using Discrete Video Timings, VESA Generalized Timing
+	- Choice of using Discrete Video Timings, VESA Generalized Timing
 	  Formula, or a framebuffer specific database to set the video mode
-	- Supports a variable range of horizontal and vertical resolution, and
+	- Supports a variable range of horizontal and vertical resolution and
 	  vertical refresh rates if the VESA Generalized Timing Formula is
 	  enabled.
-        - Supports color depths of 8, 16, 24 and 32 bits per pixel
+	- Supports color depths of 8, 16, 24 and 32 bits per pixel
 	- Supports pseudocolor, directcolor, or truecolor visuals
-        - Full and optimized hardware acceleration at 8, 16 and 24 bpp
+	- Full and optimized hardware acceleration at 8, 16 and 24 bpp
 	- Robust video state save and restore
-        - MTRR support
+	- MTRR support
 	- Utilizes user-entered monitor specifications to automatically
 	  calculate required video mode parameters.
    g. "hsync1/hsync2:<value>"
 	select the minimum and maximum Horizontal Sync Frequency of the
-	monitor in KHz.  If a using a fixed frequency monitor, hsync1 must
+	monitor in kHz.  If using a fixed frequency monitor, hsync1 must
 	be equal to hsync2. If EDID probing is successful, these will be
 	ignored and values will be taken from the EDID block.
 	Recommendation: check monitor manual for correct values
-	default (29/30)
+	(default = 29/30)
    h. "vsync1/vsync2:<value>"
 	select the minimum and maximum Vertical Sync Frequency of the monitor
 	a 1 unit difference, and vice versa.
    i. "voffset:<value>"
-        select at what offset in MB of the logical memory to allocate the
+	select at what offset in MB of the logical memory to allocate the
 	framebuffer memory.  The intent is to avoid the memory blocks
 	used by standard graphics applications (XFree86).  The default
-        offset (16 MB for a 64MB aperture, 8 MB for a 32MB aperture) will
+	offset (16 MB for a 64 MB aperture, 8 MB for a 32 MB aperture) will
-        avoid XFree86's usage and allows up to 7MB/15MB of framebuffer
+	avoid XFree86's usage and allows up to 7 MB/15 MB of framebuffer
-        memory.  Depending on your usage, adjust the value up or down,
+	memory.  Depending on your usage, adjust the value up or down
 	(0 for maximum usage, 31/63 MB for the least amount).  Note, an
 	arbitrary setting may conflict with XFree86.
 	Recommendation: do not set
 	(default = not set)
    o. <xres>x<yres>[-<bpp>][@<refresh>]
 	The driver will now accept specification of boot mode option.  If this
 	is specified, the options 'xres' and 'yres' will be ignored. See
 E.  Module options
-	The module parameters are essentially similar to the kernel
+The module parameters are essentially similar to the kernel
 parameters. The main difference is that you need to include a Boolean value
 (1 for TRUE, and 0 for FALSE) for those options which don't need a value.
 	make menuconfig/xconfig/config
-	b. Under "Code Maturity Options", enable "Prompt for experimental/
+	b. Under "Code maturity level options" enable "Prompt for development
-	   incomplete code/drivers".
+	   and/or incomplete code/drivers".
  	c. Enable agpgart support for the Intel 810/815 on-board graphics.
-	   This is required.  The option is under "Character Devices"
+	   This is required.  The option is under "Character Devices".
 	d. Under "Graphics Support", select "Intel 810/815" either statically
 	   or as a module.  Choose "use VESA Generalized Timing Formula" if
 	   'use VESA Generalized Timing Formula' to 'y'.
         f. If you want a framebuffer console, enable it under "Console
-	   Drivers"
+	   Drivers".
 	g. Compile your kernel.
-	h. Load the driver as described in section D and E.
+	h. Load the driver as described in sections D and E.
 	i.  Try the DirectFB (http://www.directfb.org) + the i810 gfxdriver
 	    patch to see the chipset in action (or inaction :-).
 G.  Acknowledgment:
 .  Geert Uytterhoeven - his excellent howto and the virtual
-                                 framebuffer driver code made this possible.
+	    framebuffer driver code made this possible.
 .  Jeff Hartmann for his agpgart code.
 	    XFree86 source code.
 .  Intel(c).  For this value-oriented chipset driver and for
-            providing documentation.
+	    providing documentation.
 . Matt Sottek.  His inputs and ideas  helped in making some
-	optimizations possible.
+	   optimizations possible.
 H.  Home Page:
 	A more complete, and probably updated information is provided at
-http://i810fb.sourceforge.net.
+	http://i810fb.sourceforge.net.
 ###########################
 Tony