nightmorph 08/03/06 08:58:28 Modified: hb-install-x86+amd64-bootloader.xml Log: switched from vesafb-tng to uvesafb
Revision Changes Path 1.11 xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-bootloader.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-bootloader.xml?rev=1.11&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-bootloader.xml?rev=1.11&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-bootloader.xml?r1=1.10&r2=1.11 Index: hb-install-x86+amd64-bootloader.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-bootloader.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- hb-install-x86+amd64-bootloader.xml 6 Mar 2008 05:59:25 -0000 1.10 +++ hb-install-x86+amd64-bootloader.xml 6 Mar 2008 08:58:28 -0000 1.11 @@ -4,7 +4,7 @@ <!-- The content of this document is licensed under the CC-BY-SA license --> <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-bootloader.xml,v 1.10 2008/03/06 05:59:25 nightmorph Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-bootloader.xml,v 1.11 2008/03/06 08:58:28 nightmorph Exp $ --> <sections> @@ -57,19 +57,13 @@ file. </p> -<p test="func:keyval('arch')='x86'"> +<p> First of all, you need to know what type of framebuffer device you're using. If you use a Gentoo patched kernel tree (such as <c>gentoo-sources</c>) you will -have had the possibility of selecting <c>vesafb-tng</c> as the <e>VESA driver -type</e> (which is default for these kernel sources). If this is the case, you -are using <c>vesafb-tng</c> and <e>do not need</e> to set a <c>vga</c> -statement. Otherwise you are using the <c>vesafb</c> driver and <e>need</e> to -set the <c>vga</c> statement. -</p> - -<p test="contains('AMD64 IA64',func:keyval('arch'))"> -64-bit systems must use the the <c>vesafb</c> driver, and need the <c>vga</c> -statement. +have had the possibility of selecting <c>uvesafb</c> as the <e>VESA driver</e>. +If this is the case, you are using <c>uvesafb</c> and <e>do not need</e> to set +a <c>vga</c> statement. Otherwise you are using the <c>vesafb</c> driver and +<e>need</e> to set the <c>vga</c> statement. </p> <p> @@ -126,9 +120,8 @@ <p> The <c>video</c> statement controls framebuffer display options. It needs to be -given the framebuffer driver (<c>vesafb</c> for 2.6 kernels, or <c>vesa</c> for -2.4 kernels) followed by the control statements you wish to enable. All -variables are listed in +given the framebuffer driver followed by the control statements you wish to +enable. All variables are listed in <path>/usr/src/linux/Documentation/fb/vesafb.txt</path>. The most-used options are: </p> @@ -146,7 +139,7 @@ </ti> </tr> <tr> - <ti>mtrr:n</ti> + <ti>mtrr:<c>n</c></ti> <ti> Setup MTRR registers. <c>n</c> can be:<br/> 0 - disabled<br/> @@ -156,10 +149,10 @@ 4 - write-through </ti> </tr> -<tr test="func:keyval('arch')='x86'"> +<tr> <ti><c>mode</c></ti> <ti> - (<c>vesafb-tng</c> only)<br/> + (<c>uvesafb</c> only)<br/> Set up the resolution, color depth and refresh rate. For instance, <c>[EMAIL PROTECTED]</c> for a resolution of 1024x768, 32 bit color depth and a refresh rate of 85 Hz. @@ -167,16 +160,10 @@ </tr> </table> -<p test="contains('AMD64 IA64',func:keyval('arch'))"> -The result of those two statements could be something like <c>vga=0x318 -video=vesafb:mtrr:3,ywrap</c>. Write this setting down; you will need it -shortly. -</p> - -<p test="func:keyval('arch')='x86'"> +<p> The result of those two statements could be something like <c>vga=0x318 video=vesafb:mtrr:3,ywrap</c> or -<c>video=vesafb:mtrr:3,ywrap,[EMAIL PROTECTED]</c>. Write this setting down; you +<c>video=uvesafb:mtrr:3,ywrap,[EMAIL PROTECTED]</c>. Write this setting down; you will need it shortly. </p> -- [email protected] mailing list
