[PATCH 19/22] uvesafb: add info about pmipal, yrap and ypan being available only on x86
DORMANTno replies
From: "Antonino A. Daplas" <adaplas@gmail.com>
Date: 2007-08-13 12:51:03
Subsystem:
documentation, framebuffer layer, the rest · Maintainers:
Jonathan Corbet, Helge Deller, Linus Torvalds
From: Michal Januszewski <spock@gentoo.org> Features that use the Protected Mode Interface are available on x86 only. Document this in the uvesafb description. Signed-off-by: Michal Januszewski <spock@gentoo.org> Signed-off-by: Antonino Daplas <adaplas@gmail.com> --- Documentation/fb/uvesafb.txt | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/fb/uvesafb.txt b/Documentation/fb/uvesafb.txt
index cfc4e55..bcfc233 100644
--- a/Documentation/fb/uvesafb.txt
+++ b/Documentation/fb/uvesafb.txt@@ -59,11 +59,12 @@ Accepted options: ypan Enable display panning using the VESA protected mode interface. The visible screen is just a window of the video memory, console scrolling is done by changing the - start of the window. + start of the window. Available on x86 only. ywrap Same as ypan, but assumes your gfx board can wrap-around the video memory (i.e. starts reading from top if it reaches the end of video memory). Faster than ypan. + Available on x86 only. redraw Scroll by redrawing the affected part of the screen, this is the safe (and slow) default.
@@ -75,7 +76,7 @@ vgapal Use the standard VGA registers f pmipal Use the protected mode interface for palette changes. This is the default if the protected mode interface is - available. + available. Available on x86 only. mtrr:n Setup memory type range registers for the framebuffer where n: -------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/