media/drivers/zoran.rst

1 .. SPDX-License-Identifier: GPL-2.0
8 website: http://mjpeg.sourceforge.net/driver-zoran/
12 --------------------------
15 ------------------------
28 Drivers to use: videodev, i2c-core, i2c-algo-bit,
31 Inputs/outputs: Composite and S-video
45 Drivers to use: videodev, i2c-core, i2c-algo-bit,
49 	Six physical inputs. 1-6 are composite,
50 	1-2, 3-4, 5-6 doubles as S-video,
51 	1-3 triples as component.
70 Drivers to use: videodev, i2c-core, i2c-algo-bit,
73 Inputs/outputs: Composite and S-video
87 Drivers to use: videodev, i2c-core, i2c-algo-bit,
90 Inputs/outputs: Composite and S-video
104 Drivers to use: videodev, i2c-core, i2c-algo-bit,
107 Inputs/outputs: Composite, S-video and Internal
121 Drivers to use: videodev, i2c-core, i2c-algo-bit,
124 Inputs/outputs: Composite, S-video and Internal
139 Drivers to use: videodev, i2c-core, i2c-algo-bit,
142 Inputs/outputs: Composite, S-video and Internal
157 Drivers to use: videodev, i2c-core, i2c-algo-bit,
160 Inputs/outputs: Composite, S-video and Internal
175 Drivers to use: videodev, i2c-core, i2c-algo-bit,
178 Inputs/outputs: Composite, S-video and Internal
190 ------------------------------------------
205 When you speak about NTSC, you usually mean the standard: CCIR - M using
209 When you talk about PAL, you usually mean: CCIR - B/G using the PAL
212 When you talk about SECAM, you mean: CCIR - L using the SECAM Colorsystem
215 There the other version of SECAM, CCIR - D/K is used in Bulgaria, China,
218 The CCIR - H uses the PAL colorsystem (sometimes SECAM) and is used in
221 The CCIR - I uses the PAL colorsystem, and is used in Great Britain, Hong Kong,
222 Ireland, Nigeria, South Africa.
224 The CCIR - N uses the PAL colorsystem and PAL frame size but the NTSC framerate,
246 - was introduced in 1997, is used in the BUZ and
247 - can handle: PAL B/G/H/I, PAL N, PAL M, NTSC M, NTSC N, NTSC 4.43 and SECAM
252 - was introduced in 1995, is used in the Pinnacle/Miro DC10(new), DC10+ and
253 - can handle: PAL B/G, NTSC M and SECAM
258 - was introduced in 2000, is used in the LML33R10 and
259 - can handle: PAL B/G/D/H/I/N, PAL N, PAL M, NTSC M, NTSC 4.43 and SECAM
264 - was introduced in 1996, and is used in the LML33 and
265 - can handle: PAL B/D/G/H/I, NTSC M
270 - was introduced in 1996, is used in the DC30 and DC30+ and
271 - can handle: PAL B/G/H/I, PAL N, PAL M, NTSC M, NTSC 44, PAL 60, SECAM,NTSC Comb
276 - is used in the AVS6EYES card and
277 - can handle: NTSC-M/N/44, PAL-M/N/B/G/H/I/D/K/L and SECAM
281 --------------------------------------
291 - was introduced in 1996, is used in the BUZ
292 - can generate: PAL B/G, NTSC M
297 - was introduced in 1994, is used in the LML33
298 - can generate: PAL B/D/G/H/I/N, PAL M, NTSC M, PAL-N (Argentina)
303 - was introduced in 2000, is used in the LML300R10
304 - can generate: PAL B/D/G/H/I/N, PAL M, NTSC M, PAL 60
309 - was introduced in 1996, is used in the DC10, DC10+, DC10 old, DC30, DC30+
310 - can generate: PAL B/D/G/H/I/N, PAL M, NTSC M
315 - was introduced in 1991, is used in the DC10 old
316 - can generate: PAL , NTSC , SECAM
321 - is used in AVS6EYES, and
322 - can generate: NTSC/PAL, PAL-M, PAL-N
329 ------------------------------------
338 alias char-major-81-0 zr36067
344 XF86Config-4 when you use X by default, or to run 'v4l-conf -c <device>' in
349 ---------------------------------------------------------
355 than users with a DC10+/LML33. Also, it tells us that people owning a VIA-
361 - VIA MVP3
362 	- Forget it. Pointless. Doesn't work.
363 - Intel 430FX (Pentium 200)
364 	- LML33 perfect, Buz tolerable (3 or 4 frames dropped per movie)
365 - Intel 440BX (early stepping)
366 	- LML33 tolerable. Buz starting to get annoying (6-10 frames/hour)
367 - Intel 440BX (late stepping)
368 	- Buz tolerable, LML3 almost perfect (occasional single frame drops)
369 - SiS735
370 	- LML33 perfect, Buz tolerable.
371 - VIA KT133(*)
372 	- LML33 starting to get annoying, Buz poor enough that I have up.
374 - Both 440BX boards were dual CPU versions.
378 - AMD 751
379 	- Buz perfect-tolerable
380 - AMD 760
381 	- Buz perfect-tolerable
384 if you have a VIA-based motherboard. They may be cheap, but sometimes, you'd
398 ---------------------
404 the MJPEG-tools (http://mjpeg.sf.net/).
417 ------------
447 --------------------------------------------------
459 fields are 720x288x16/2 bits/field (2 fields/frame) = 207360 bytes/field x 2 =
466 --
469 > -q 50 -b 128 : 24.283.332 Bytes
470 > -q 50 -b 256 : 48.442.368
471 > -q 25 -b 128 : 24.655.992
472 > -q 25 -b 256 : 25.859.820
480 704x288 pixels, one field, is 202752 pixels. Divided by 64 pixels per block;
481 3168 blocks per field. Each pixel consist of two bytes; 128 bytes per block;
487 becomes 811008 bits; 101376 bytes per field. We're talking raw bits and bytes
488 here, so we don't need to do any fancy corrections for bits-per-pixel or such
489 things. 101376 bytes per field.
494 But wait a second! -b128 gives 128kB buffers! It's not possible to cram
501 leaves 65536 bytes for each field. Using 3168 blocks per field, we get
503 request for 256 bits per block when there's only 165 bits available! The -q50
504 option is silently overridden, and the -b128 option takes precedence, leaving
505 us with the equivalence of -q32.
508 to 65340 bytes per field, out of the allowed 65536. The current driver has
509 another level of rate limiting; it won't accept -q values that fill more than
511 a safe bet. Personally, I think I would have lowered requested-bits-per-block
514 per block, the equivalence of -q24. With 128kB buffers, you can't use greater
515 than -q24 at -d1. (And PAL, and 704 pixels width...)
517 The third example is limited to -q24 through the same process. The second
518 example, using very similar calculations, is limited to -q48. The only
519 example that actually grab at the specified -q value is the last one, which
521 --
532 ---------------------------------------
550 ----------------------
553 - Laurent Pinchart <laurent.pinchart@skynet.be>
554 - Ronald Bultje rbultje@ronald.bitfreak.net
555 - Serguei Miridonov <mirsev@cicese.mx>
556 - Wolfgang Scherr <scherr@net4you.net>
557 - Dave Perks <dperks@ibm.net>
558 - Rainer Johanni <Rainer@Johanni.de>
561 ----------------