The conversion to ReST broke a minor things. Fix them. While here, also make EBUSY constant, just like on other places.
Signed-off-by: Mauro Carvalho Chehab <[email protected]> --- Documentation/linux_tv/media/v4l/dev-osd.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Documentation/linux_tv/media/v4l/dev-osd.rst b/Documentation/linux_tv/media/v4l/dev-osd.rst index 6a6ead6df54d..b9b53fd7eb5d 100644 --- a/Documentation/linux_tv/media/v4l/dev-osd.rst +++ b/Documentation/linux_tv/media/v4l/dev-osd.rst @@ -6,8 +6,8 @@ Video Output Overlay Interface ****************************** - **Also known as On-Screen Display (OSD)** + Some video output devices can overlay a framebuffer image onto the outgoing video signal. Applications can set up such an overlay using this interface, which borrows structures and ioctls of the @@ -48,10 +48,11 @@ the ``linux/fb.h`` header file. The width and height of the framebuffer depends on the current video standard. A V4L2 driver may reject attempts to change the video standard (or any other ioctl which would imply a framebuffer size change) with an -EBUSY error code until all applications closed the framebuffer device. +``EBUSY`` error code until all applications closed the framebuffer device. .. code-block:: c + :caption: Example 4.1. Finding a framebuffer device for OSD #include <linux/fb.h> -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
