X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=Documentation%2FDocBook%2Fvideobook.tmpl;h=89817795e668d438d3ea64f9dd37cfa9d0e55785;hb=529a41e36673b518c9e091f3a8d932b6b9e3c461;hp=b629da33951d3945f619bf900862c163c43e849e;hpb=f82bc1762e0e74b7e0040a4d83be06d32c37fc2e;p=firefly-linux-kernel-4.4.55.git
diff --git a/Documentation/DocBook/videobook.tmpl b/Documentation/DocBook/videobook.tmpl
index b629da33951d..89817795e668 100644
--- a/Documentation/DocBook/videobook.tmpl
+++ b/Documentation/DocBook/videobook.tmpl
@@ -96,7 +96,6 @@ static struct video_device my_radio
{
"My radio",
VID_TYPE_TUNER,
- VID_HARDWARE_MYRADIO,
radio_open.
radio_close,
NULL, /* no read */
@@ -118,13 +117,6 @@ static struct video_device my_radio
indicates that the device can be tuned. Clearly our radio is going to have some
way to change channel so it is tuneable.
-
- The VID_HARDWARE_ types are unique to each device. Numbers are assigned by
- alan@redhat.com when device drivers are going to be released. Until then you
- can pull a suitably large number out of your hat and use it. 10000 should be
- safe for a very long time even allowing for the huge number of vendors
- making new and different radio cards at the moment.
-
We declare an open and close routine, but we do not need read or write,
which are used to read and write video data to or from the card itself. As
@@ -178,7 +170,7 @@ int __init myradio_init(struct video_init *v)
The types available are
- Device Types
+ Device Types
@@ -299,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
@@ -373,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
@@ -406,7 +398,7 @@ static int radio_ioctl(struct video_device *dev, unsigned int cmd, void *arg)
- struct video_tuner flags
+ struct video_tuner flags
@@ -429,7 +421,7 @@ static int radio_ioctl(struct video_device *dev, unsigned int cmd, void *arg)
- struct video_tuner modes
+ struct video_tuner modes
@@ -580,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
@@ -615,7 +607,7 @@ static int current_volume=0;
- struct video_audio flags
+ struct video_audio flags
@@ -633,7 +625,7 @@ static int current_volume=0;
- struct video_audio modes
+ struct video_audio modes
@@ -783,7 +775,7 @@ module_exit(cleanup);
-
+
Video Capture Devices
Video Capture Device Types
@@ -844,7 +836,6 @@ static struct video_device my_camera
"My Camera",
VID_TYPE_OVERLAY|VID_TYPE_SCALES|\
VID_TYPE_CAPTURE|VID_TYPE_CHROMAKEY,
- VID_HARDWARE_MYCAMERA,
camera_open.
camera_close,
camera_read, /* no read */
@@ -864,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
@@ -1204,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
@@ -1227,7 +1218,7 @@ static int camera_ioctl(struct video_device *dev, unsigned int cmd, void *arg)
- struct video_channel flags
+ struct video_channel flags
@@ -1238,7 +1229,7 @@ static int camera_ioctl(struct video_device *dev, unsigned int cmd, void *arg)
- struct video_channel types
+ struct video_channel types
@@ -1251,7 +1242,7 @@ static int camera_ioctl(struct video_device *dev, unsigned int cmd, void *arg)
- struct video_channel norms
+ struct video_channel norms
@@ -1337,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
@@ -1475,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
@@ -1512,7 +1503,7 @@ static struct video_buffer capture_fb;
Each clip is a struct video_clip which has the following fields
-