From: Rob Landley Add table IDs to videobook.tmpl Signed-off-by: Rob Landley Cc: "Randy.Dunlap" Signed-off-by: Andrew Morton --- Documentation/DocBook/videobook.tmpl | 34 ++++++++++++------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff -puN Documentation/DocBook/videobook.tmpl~add-table-ids-to-videobooktmpl Documentation/DocBook/videobook.tmpl --- a/Documentation/DocBook/videobook.tmpl~add-table-ids-to-videobooktmpl +++ a/Documentation/DocBook/videobook.tmpl @@ -178,7 +178,7 @@ int __init myradio_init(struct video_ini The types available are - Device Types +
Device Types @@ -299,7 +299,7 @@ static int radio_ioctl(struct video_devi 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 @@ -373,7 +373,7 @@ static int radio_ioctl(struct video_devi The video_tuner structure has the following fields -
struct video_tuner fields +
struct video_tuner fields @@ -406,7 +406,7 @@ static int radio_ioctl(struct video_devi
- struct video_tuner flags +
struct video_tuner flags @@ -429,7 +429,7 @@ static int radio_ioctl(struct video_devi
- struct video_tuner modes +
struct video_tuner modes @@ -580,7 +580,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 @@ -615,7 +615,7 @@ static int current_volume=0;
- struct video_audio flags +
struct video_audio flags @@ -633,7 +633,7 @@ static int current_volume=0;
- struct video_audio modes +
struct video_audio modes @@ -783,7 +783,7 @@ module_exit(cleanup); - + Video Capture Devices Video Capture Device Types @@ -864,7 +864,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 @@ -1204,7 +1204,7 @@ static int camera_ioctl(struct video_dev 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 @@ -1227,7 +1227,7 @@ static int camera_ioctl(struct video_dev
- struct video_channel flags +
struct video_channel flags @@ -1238,7 +1238,7 @@ static int camera_ioctl(struct video_dev
- struct video_channel types +
struct video_channel types @@ -1251,7 +1251,7 @@ static int camera_ioctl(struct video_dev
- struct video_channel norms +
struct video_channel norms @@ -1337,7 +1337,7 @@ static int camera_ioctl(struct video_dev for every other pixel in the image. The other common formats the interface defines are -
Framebuffer Encodings +
Framebuffer Encodings @@ -1475,7 +1475,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 @@ -1512,7 +1512,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 _