Search results

Jump to navigation Jump to search

Page title matches

Page text matches

  • modprobe saa7134 card=60 tuner=63 modprobe saa7134-dvb
    269 bytes (41 words) - 19:24, 4 May 2009
  • It is supported under Linux by the [[saa713x devices|saa7134]] and associated kernel driver modules. ==Devices==
    840 bytes (122 words) - 22:10, 12 May 2009
  • ...th programs like tvtime. However, the process of moving the data from the saa7134 chip to your sound card will add a delay. Unfortunately, software can not ...parameters (execept the device). The parameters will be determined by the saa7134 signal source (analog NTSC, broadcast, cable, etc?).
    1 KB (191 words) - 19:28, 25 December 2008
  • options saa7134 card=55 oss=55 rmmod saa7134
    1 KB (183 words) - 22:34, 4 May 2009
  • A [[DVB-T]] [[DVB-T PCMCIA Devices|PCMCIA (CardBus) device]] from [[MSI]]. *saa7134
    1 KB (160 words) - 22:20, 4 May 2009
  • * SAA7134 chipset See [[Saa713x devices: Generic SAA7134 Card Installation]].
    3 KB (444 words) - 11:22, 6 May 2009
  • ...In recent 2.6.11 kernels there is this line in drivers/media/video/saa7134/saa7134.h: but the corresponding entry in saa7134-cards.c didn't work for me, I couldn't tune in any channel.
    5 KB (682 words) - 22:32, 6 May 2009
  • ...iver (in the case of TV tuner devices) and A/V inputs (in the case of some devices) and the host computer's PCI bus. Some examples of PCI interface chipsets | [[Philips SAA7134|SAA7134]]
    2 KB (204 words) - 21:56, 3 October 2009
  • ...ardlist (see [[Saa713x devices#Supported saa713x devices|Supported saa713x devices]]): ...ally, using something like this (on Debian, this goes into /etc/modprobe.d/saa7134):
    4 KB (615 words) - 15:17, 7 May 2009
  • ==Analog Devices== | VA1000 POWER || saa7133/saa7134
    818 bytes (109 words) - 02:49, 24 June 2010
  • ...4(FM)' product lines, indicating the use respective use of the SAA7130 and SAA7134 chips. The card needs the saa7134 driver, which should be built as a module in the kernel. When the module is
    6 KB (977 words) - 15:16, 7 May 2009
  • By default my Linux box loads saa7134 driver with UNKNOWN/GENERIC board and no tuner detected. To make it work I use "modprobe saa7134 card=81 tuner=54", here is snapshot from dmesg:
    6 KB (918 words) - 23:11, 4 May 2009
  • After inserting the card, lsmod should tell you that saa7134, tuner, and options saa7134 oss=1 dsp_nr=1 mixer_nr=1 oss_rate=32000 i2c_debug=1
    5 KB (798 words) - 11:29, 6 May 2009
  • Kernel driver in use: saa7134 Kernel modules: saa7134
    2 KB (310 words) - 21:48, 3 May 2009
  • * Philips [[Philips SAA7134|SAA7134]] [[Category:DVB-T CardBus Devices]]
    1 KB (169 words) - 07:33, 24 December 2016
  • Kernel driver in use: saa7134 Kernel modules: saa7134
    3 KB (530 words) - 10:11, 23 May 2009
  • ...logue video framegrabbers, tv-cards, and A/V editing boards (see [[Saa7146 devices]]). ...plemented in the SAA7146 chipset's direct successor, the [[Philips SAA7134|SAA7134]], as the later IC has a dedicated digital stream interface.
    2 KB (322 words) - 20:14, 18 April 2010
  • <td>saa7134</td> <td>Most cards need only the saa7134 driver, but a few need the ir-kbd-i2c helper. Boards known to require ir-kb
    10 KB (1,657 words) - 01:44, 3 May 2009
  • Добавить опцию загрузки модуля saa7134: options saa7134 card=46 tuner=12
    12 KB (1,297 words) - 22:33, 6 May 2009
  • ...hilips SAA7134|SAA713x]] chips, and which are supported under Linux by the saa7134 and associated kernel driver modules. ==saa7134 and associated kernel driver modules==
    8 KB (1,165 words) - 00:30, 4 December 2016
  • ...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:
    3 KB (469 words) - 10:54, 12 April 2010
  • ==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
    4 KB (691 words) - 20:47, 29 May 2009
  • === To properly setup your saa7134-based tuner you need === * SAA7134-based tvtuner
    9 KB (1,465 words) - 19:10, 11 June 2010
  • 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
    10 KB (1,330 words) - 08:36, 28 January 2017
  • 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
    2 KB (263 words) - 20:05, 20 September 2009
  • [ 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
    18 KB (1,927 words) - 00:07, 17 May 2009
  • $sudo modprobe saa7134 card=63 tuner=43 Kernel driver in use: saa7134
    6 KB (755 words) - 23:53, 3 March 2011
  • ...aa7134'' bridge IC ... the AVerMedia 777 is ''card=85'' for saa7134 based devices card driver: saa7134
    12 KB (1,937 words) - 07:42, 5 December 2016
  • ...s in Russian. If you need english text, look at [[Saa713x devices: Generic SAA7134 Card Installation]] Делаем от пользователя root команду make install. Результат - модули saa7134.ko и так далее должны быть скопированы в /li
    14 KB (660 words) - 03:22, 27 February 2009
  • 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 ===
    16 KB (2,509 words) - 01:38, 4 January 2013
  • 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
    4 KB (675 words) - 03:14, 2 June 2009
  • ...rest in using the analogue input signal facilities offered by framegrabber devices. == Hardware Devices supporting Analog TV and/or Framegrabbing facilities==
    7 KB (974 words) - 19:48, 18 August 2016
  • ...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,
    8 KB (1,298 words) - 13:47, 2 March 2014
  • * [[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'
    7 KB (1,149 words) - 21:02, 14 August 2012
  • * 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
    6 KB (912 words) - 00:29, 4 December 2016
  • ...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)
    11 KB (1,629 words) - 22:09, 6 May 2009
  • * [[Philips SAA7134|NXP/Philips SAA7131E]] (A/V decoder and PCI Interface, compatible with SAA7 Kernel driver in use: saa7134
    8 KB (1,135 words) - 17:14, 17 December 2009
  • ...<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
    11 KB (1,858 words) - 08:36, 28 January 2017
  • ==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.
    5 KB (771 words) - 22:54, 11 October 2011
  • * 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==
    12 KB (2,054 words) - 19:57, 18 April 2010
  • ==Analogue Devices Usable With Text== ===bt8x8 devices===
    14 KB (2,259 words) - 23:35, 17 October 2011
  • ...TV project. AVerMedia, themselves, do not provide direct support for their devices under Linux but for one exception (which itself is a case that is quite lim ==Analog devices==
    10 KB (1,438 words) - 18:02, 9 June 2022
  • ...ilitates the creation on the basis of this inexpensive chip PCI-functional devices. ...connectors - is Phone Jack 3.5mm. When connecting to a TV tuner, external devices require specific cable or adapter for the sound. In principle, such a purch
    5 KB (781 words) - 11:09, 20 February 2014
  • The CVT boards are not supported under Linux although many of the individual devices are. ...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'
    9 KB (1,359 words) - 21:36, 28 July 2009
  • '''For PCI/PCIe devices''' - use the command: '''For USB based devices''' - use the command:
    10 KB (1,654 words) - 17:56, 8 October 2012
  • * Philips [[Philips SAA7134|SAA7134]] * Philips [[Philips SAA7134|SAA7134]]
    50 KB (7,139 words) - 11:26, 19 October 2018
  • ...atest set of Linux kernel driver modules for [[What is V4L or DVB?|V4L-DVB devices]]. This page contains information to help an "end user" install these devic ...dev]] will "automagically" create appropriate [[Device nodes and character devices|device nodes]] on ''/dev''''': <br>
    24 KB (4,043 words) - 19:27, 7 November 2018
  • ...Digital Video Broadcasting Devices ---> < > Philips SAA7134 support
    7 KB (850 words) - 22:44, 20 September 2010
  • Currently, most analog and digital devices have an Infrared input for a remote control. Each manufacturer has their ow ...dy other similar devices. For an example, please see: [[add IR support for saa7134]].
    10 KB (1,633 words) - 07:10, 18 December 2016
  • [ 64.121124] input: saa7134 IR (AVerMedia Hybrid TV as /devices/pci0000:00/0000:00:14.4/0000:03:07.0/input/input6
    7 KB (961 words) - 06:48, 4 January 2010
  • Remember: on ubuntu you need to delete the "original" modules for cx88 and saa7134 # rm -rf /lib/modules/`uname -r`/ubuntu/media/saa7134
    15 KB (2,214 words) - 08:42, 15 October 2010
  • Kernel driver in use: saa7134 Kernel modules: saa7134
    7 KB (1,142 words) - 08:37, 28 January 2017
  • * [[Philips SAA7134|NXP/Philips SAA7135HS/203]] -- A/V decoder and PCI Interface (IC1) Kernel driver in use: saa7134
    26 KB (3,977 words) - 01:07, 24 November 2011
  • A sample MPlayer command line that will play TV for Europe, channel E2, for devices that use analog audio wired from the TV card audio output into the aux or c ...here are more useful information about audio setups with alsa modules on [[Saa7134-alsa]].
    11 KB (1,843 words) - 15:48, 18 May 2014
  • Devices: 2 x LifeView TV Walker Twin ** saa7134
    9 KB (1,344 words) - 00:35, 18 May 2014