From dde4feb978ac896b21833e5e2c797d02316a2529 Mon Sep 17 00:00:00 2001 From: Rob Landley Date: Thu, 7 Feb 2008 00:13:32 -0800 Subject: Add table IDs to videobook.tmpl Add table IDs to videobook.tmpl Signed-off-by: Rob Landley Cc: "Randy.Dunlap" Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds --- Documentation/DocBook/videobook.tmpl | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) (limited to 'Documentation') diff --git a/Documentation/DocBook/videobook.tmpl b/Documentation/DocBook/videobook.tmpl index b3d93ee27693..89817795e668 100644 --- a/Documentation/DocBook/videobook.tmpl +++ b/Documentation/DocBook/videobook.tmpl @@ -170,7 +170,7 @@ int __init myradio_init(struct video_init *v) The types available are - Device Types +
Device Types @@ -291,7 +291,7 @@ static int radio_ioctl(struct video_device *dev, unsigned int cmd, void *arg) allows the applications to find out what sort of a card they have found and to figure out what they want to do about it. The fields in the structure are -
struct video_capability fields +
struct video_capability fields @@ -365,7 +365,7 @@ static int radio_ioctl(struct video_device *dev, unsigned int cmd, void *arg) The video_tuner structure has the following fields -
struct video_tuner fields +
struct video_tuner fields @@ -398,7 +398,7 @@ static int radio_ioctl(struct video_device *dev, unsigned int cmd, void *arg)
- struct video_tuner flags +
struct video_tuner flags @@ -421,7 +421,7 @@ static int radio_ioctl(struct video_device *dev, unsigned int cmd, void *arg)
- struct video_tuner modes +
struct video_tuner modes @@ -572,7 +572,7 @@ static int current_volume=0; Then we fill in the video_audio structure. This has the following format -
struct video_audio fields +
struct video_audio fields @@ -607,7 +607,7 @@ static int current_volume=0;
- struct video_audio flags +
struct video_audio flags @@ -625,7 +625,7 @@ static int current_volume=0;
- struct video_audio modes +
struct video_audio modes @@ -775,7 +775,7 @@ module_exit(cleanup); - + Video Capture Devices Video Capture Device Types @@ -855,7 +855,7 @@ static struct video_device my_camera We use the extra video capability flags that did not apply to the radio interface. The video related flags are -
Capture Capabilities +
Capture Capabilities @@ -1195,7 +1195,7 @@ static int camera_ioctl(struct video_device *dev, unsigned int cmd, void *arg) inputs to the video card). Our example card has a single camera input. The fields in the structure are -
struct video_channel fields +
struct video_channel fields @@ -1218,7 +1218,7 @@ static int camera_ioctl(struct video_device *dev, unsigned int cmd, void *arg)
- struct video_channel flags +
struct video_channel flags @@ -1229,7 +1229,7 @@ static int camera_ioctl(struct video_device *dev, unsigned int cmd, void *arg)
- struct video_channel types +
struct video_channel types @@ -1242,7 +1242,7 @@ static int camera_ioctl(struct video_device *dev, unsigned int cmd, void *arg)
- struct video_channel norms +
struct video_channel norms @@ -1328,7 +1328,7 @@ static int camera_ioctl(struct video_device *dev, unsigned int cmd, void *arg) for every other pixel in the image. The other common formats the interface defines are -
Framebuffer Encodings +
Framebuffer Encodings @@ -1466,7 +1466,7 @@ static struct video_buffer capture_fb; display. The video_window structure is used to describe the way the image should be displayed. -
struct video_window fields +
struct video_window fields @@ -1503,7 +1503,7 @@ static struct video_buffer capture_fb; Each clip is a struct video_clip which has the following fields -
video_clip fields +
video_clip fields -- cgit v1.2.3-55-g7522