Search results

...ability to import DVDs on-the-fly, and being capable of recording from V4L devices. This example works on [[saa713x devices|saa7134 cards]], using the [[saa7134-alsa]] DMA module under OSS emulation:

==Devices known to be using the TUV1236D== ...option, called "input", that allows the user to select which RF input, on devices possessing a tuner module with dual RF inputs (such as the TUV1236D NIM fou

=== To properly setup your saa7134-based tuner you need === * SAA7134-based tvtuner

In /usr/src/linux/drivers/media/video/saa7134/saa7134-dvb.c, line 873, struct tda1004x_config philips_tiger_config change the ent modprobe saa7134 card=78 gpio_tracking=1

Saa7146 devices are collectively those PCI cards that are based upon the [[Philips SAA7146] ...s for other popular [[PCI interface chipsets]], such as the [[bttv]] and [[saa7134]] kernel driver modules, there is no unified saa7146 driver. Instead, there

[ 45.569809] input: saa7134 IR (Compro Videomate DV as /devices/pci0000:00/0000:00:1e.0/0000:04:03.0/input/input7 [ 45.873425] saa7134 ALSA driver for DMA sound loaded

$sudo modprobe saa7134 card=63 tuner=43 Kernel driver in use: saa7134

...aa7134'' bridge IC ... the AVerMedia 777 is ''card=85'' for saa7134 based devices card driver: saa7134

...s in Russian. If you need english text, look at [[Saa713x devices: Generic SAA7134 Card Installation]] Делаем от пользователя root команду make install. Результат - модули saa7134.ko и так далее должны быть скопированы в /li

Also see the [[Saa7134-alsa redundant]] article; whose info (if it is not redundant) should/will b === How to use alsa or oss with saa7134 ===

saa7134 card=2 tuner=17 oss=1 * The TCL2002MB-3 was first discovered on saa7134 based cards and recently on cx88 based Hauppauge WinTV GO2 models. All use

...rest in using the analogue input signal facilities offered by framegrabber devices. == Hardware Devices supporting Analog TV and/or Framegrabbing facilities==

...ed in its manual. That may seem obvious enough, but a surprising number of devices are available with little or no model identification. Ordinarily, that wou ...arkings printed directly on the board or on IC components. With USB based devices, as they tend to be completely encased, it is difficult, if not impossible,

* [[Philips SAA7134|NXP/Philips SAA7130HL]] (A/V decoder and PCI Interface) ...ces, the relevant output of <code>lspci -vnn</code> or, in the case of USB devices, <code>lsusb -v </code>. We're particularly interested in the subsystem ID'

* Also, this devices doesn't have any external Audio/Video outputs, so the Audio should be softw * Philips [[Philips SAA7134|SAA7135H]] - Philips Video Decoder and Broadcast Audio Decoder /w PCI bridg

...t I had to load '/sbin/modprobe saa7134_dvb' additional to '/sbin/modprobe saa7134', which was running fine. Afterwards the script http://www.fedoralinux.de/c # devices being controlled by this remote: FlyDVB-T Duo (PCI)

* [[Philips SAA7134|NXP/Philips SAA7131E]] (A/V decoder and PCI Interface, compatible with SAA7 Kernel driver in use: saa7134

...<br> Alternatively, several processes can accomplish a digital path. See [[Saa7134-alsa#ALSA_audio_with_other_applications|ALSA audio]]. 3. Edit your /etc/modules file and insert an 'saa7134-dvb' right after the saa7134 entry that should already exist in the file. This will cause the module to

==What devices can receive RDS information?== ...to receive RDS should be self evident - it must be equipped with a [[Radio devices|radio receiver/tuner]]. In addition, it will also require a RDS decoder.

* output - to control or signal other devices attached to the IC and, as such, the pins are configured to be “high” o ==GPIO pins within the context of V4L-DVB devices==