From patchwork Mon Dec 28 12:57:23 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Wilk X-Patchwork-Id: 7926001 Return-Path: X-Original-To: patchwork-linux-fbdev@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork2.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.136]) by patchwork2.web.kernel.org (Postfix) with ESMTP id 84831BEEE5 for ; Mon, 28 Dec 2015 13:03:35 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id 7BA4020173 for ; Mon, 28 Dec 2015 13:03:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9CCF820160 for ; Mon, 28 Dec 2015 13:03:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752081AbbL1NDc (ORCPT ); Mon, 28 Dec 2015 08:03:32 -0500 Received: from 5.mo2.mail-out.ovh.net ([87.98.181.248]:53510 "EHLO 5.mo2.mail-out.ovh.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752027AbbL1NDb (ORCPT ); Mon, 28 Dec 2015 08:03:31 -0500 X-Greylist: delayed 364 seconds by postgrey-1.27 at vger.kernel.org; Mon, 28 Dec 2015 08:03:31 EST Received: from mail157.ha.ovh.net (b9.ovh.net [213.186.33.59]) by mo2.mail-out.ovh.net (Postfix) with SMTP id DE2BA1000736 for ; Mon, 28 Dec 2015 13:57:25 +0100 (CET) Received: from localhost (HELO queueout) (127.0.0.1) by localhost with SMTP; 28 Dec 2015 14:57:25 +0200 Received: from ip-5-172-247-251.free.aero2.net.pl (HELO jwilk.net) (jwilk%jwilk.net@5.172.247.251) by ns0.ovh.net with SMTP; 28 Dec 2015 14:57:24 +0200 From: Jakub Wilk To: linux-fbdev@vger.kernel.org Subject: [PATCH] Documentation/fb: Fix typos Date: Mon, 28 Dec 2015 13:57:23 +0100 Message-Id: <1451307443-1481-1-git-send-email-jwilk@jwilk.net> X-Mailer: git-send-email 2.6.4 X-Ovh-Tracer-Id: 3581487605312313118 X-Ovh-Remote: 5.172.247.251 (ip-5-172-247-251.free.aero2.net.pl) X-Ovh-Local: 213.186.33.20 (ns0.ovh.net) X-OVH-SPAMSTATE: OK X-OVH-SPAMSCORE: 0 X-OVH-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeekiedrheeiucetufdoteggodftvfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecu X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeekiedrheeigdeghecutefuodetggdotffvucfrrhhofhhilhgvmecuqfggjfenuceurghilhhouhhtmecufedttdenuc Sender: linux-fbdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fbdev@vger.kernel.org X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_HI, RCVD_IN_SBL_CSS, RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Signed-off-by: Jakub Wilk --- Documentation/fb/fbcon.txt | 2 +- Documentation/fb/sh7760fb.txt | 2 +- Documentation/fb/sm712fb.txt | 2 +- Documentation/fb/sstfb.txt | 2 +- Documentation/fb/udlfb.txt | 6 +++--- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/Documentation/fb/fbcon.txt b/Documentation/fb/fbcon.txt index 4a9739a..5bc41ca 100644 --- a/Documentation/fb/fbcon.txt +++ b/Documentation/fb/fbcon.txt @@ -144,7 +144,7 @@ C. Boot options Support is compiled in your kernel. NOTE: This is purely console rotation. Any other applications that - use the framebuffer will remain at their 'normal'orientation. + use the framebuffer will remain at their 'normal' orientation. Actually, the underlying fb driver is totally ignorant of console rotation. diff --git a/Documentation/fb/sh7760fb.txt b/Documentation/fb/sh7760fb.txt index b994c3b..280c849 100644 --- a/Documentation/fb/sh7760fb.txt +++ b/Documentation/fb/sh7760fb.txt @@ -20,7 +20,7 @@ Caveats: a) if you're using 15/16bit color modes at >= 640x480 px resolutions, b) during PCMCIA (or any other slow bus) activity. -* Rotation works only 90degress clockwise, and only if horizontal +* Rotation works only 90 degrees clockwise, and only if horizontal resolution is <= 320 pixels. files: drivers/video/sh7760fb.c diff --git a/Documentation/fb/sm712fb.txt b/Documentation/fb/sm712fb.txt index c388442..438a2bf 100644 --- a/Documentation/fb/sm712fb.txt +++ b/Documentation/fb/sm712fb.txt @@ -27,5 +27,5 @@ Missing Features ================ (alias TODO list) - * 2D acceleratrion + * 2D acceleration * dual-head support diff --git a/Documentation/fb/sstfb.txt b/Documentation/fb/sstfb.txt index 13db107..8cd3547 100644 --- a/Documentation/fb/sstfb.txt +++ b/Documentation/fb/sstfb.txt @@ -116,7 +116,7 @@ Tools These tools are mostly for debugging purposes, but you can find some of these interesting : - - con2fb , maps a tty to a fbramebuffer . + - con2fb , maps a tty to a framebuffer . con2fb /dev/fb1 /dev/tty5 - sst_dbg_vgapass , changes vga passthrou. You have to recompile the driver with SST_DEBUG and SST_DEBUG_IOCTL set to 1 diff --git a/Documentation/fb/udlfb.txt b/Documentation/fb/udlfb.txt index 57d2f29..c985cb6 100644 --- a/Documentation/fb/udlfb.txt +++ b/Documentation/fb/udlfb.txt @@ -9,7 +9,7 @@ pairing that with a hardware framebuffer (16MB) on the other end of the USB wire. That hardware framebuffer is able to drive the VGA, DVI, or HDMI monitor with no CPU involvement until a pixel has to change. -The CPU or other local resource does all the rendering; optinally compares the +The CPU or other local resource does all the rendering; optionally compares the result with a local shadow of the remote hardware framebuffer to identify the minimal set of pixels that have changed; and compresses and sends those pixels line-by-line via USB bulk transfers. @@ -66,10 +66,10 @@ means that from a hardware and fbdev software perspective, everything is good. At that point, a /dev/fb? interface will be present for user-mode applications to open and begin writing to the framebuffer of the DisplayLink device using standard fbdev calls. Note that if mmap() is used, by default the user mode -application must send down damage notifcations to trigger repaints of the +application must send down damage notifications to trigger repaints of the changed regions. Alternatively, udlfb can be recompiled with experimental defio support enabled, to support a page-fault based detection mechanism -that can work without explicit notifcation. +that can work without explicit notification. The most common client of udlfb is xf86-video-displaylink or a modified xf86-video-fbdev X server. These servers have no real DisplayLink specific