PDA

View Full Version : Lifeview Flydvb trio



de12261
December 14th, 2005, 12:27 PM
Hello

this is my first post.
I will buy a Lifeview Flydvb Trio (a new version with analogic tv, dvb-S and dvb-T).

That come with a remote ctrl.

Is there a possibility to use the remote controller with Girder 3.3 or also 4.0?

thank you very much, bye

Promixis
December 14th, 2005, 01:30 PM
product link?

de12261
December 15th, 2005, 01:56 AM
product link?

http://www.lifeview.com.tw/html/products/internal_tv/flydvb_trio.htm

I see that the r.c. is common to other products (also different brand).

thank you. bye

Promixis
December 15th, 2005, 08:48 AM
I cannot tell what chipset the card uses.

de12261
December 15th, 2005, 02:35 PM
I cannot tell what chipset the card uses.

if I find the chipset brand/model, you can help me?

I will try to discover it.

thank you.

PS: I thought that the problem/interesting thing was the R.C. not the chipset...

blubberhoofd
December 15th, 2005, 02:56 PM
hi,

functions like IR signal and tv signal processing, is usually done by the same chip on the card.

if you have the manufacturer and model (main chip is the biggest one on your card I guess) you have to find a compatible plugin, if not present a plugin developer would have to be willing and able to make one for this chipset. :wink:

de12261
December 23rd, 2005, 02:56 PM
I found it!

Philips SAA7130HL

de12261
December 23rd, 2005, 03:02 PM
no! i made a mistake!

i will try to gain this info directly from Lifeview.

Merry christmas to all.

nomentero
March 15th, 2006, 03:35 PM
Hope it can help you:
V4L/DVB (3295): Add analog support for LifeView FlyDVB Trio.

From: Peter Missel <peter.missel@onlinehome.de>

- Add support for LifeView FlyDVB Trio.
- all analog inputs are supported and working, including FM radio
- TO DO: dvb & remote control

Signed-off-by: Peter Missel <peter.missel@onlinehome.de>
Signed-off-by: Michael Krufky <mkrufky@m1k.net>
Signed-off-by: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
---

Documentation/video4linux/CARDLIST.saa7134 | 1 +
drivers/media/video/saa7134/saa7134-cards.c | 41 +++++++++++++++++++++++++++
drivers/media/video/saa7134/saa7134.h | 1 +
3 files changed, 43 insertions(+), 0 deletions(-)

diff --git a/Documentation/video4linux/CARDLIST.saa7134 b/Documentation/video4linux/CARDLIST.saa7134
index 4573e52..cb3a59b 100644
--- a/Documentation/video4linux/CARDLIST.saa7134
+++ b/Documentation/video4linux/CARDLIST.saa7134
@@ -82,3 +82,4 @@
81 -> Philips Tiger reference design [1131:2018]
82 -> MSI TV@Anywhere plus [1462:6231]
83 -> Terratec Cinergy 250 PCI TV [153b:1160]
+ 84 -> LifeView FlyDVB Trio [5168:0319]
diff --git a/drivers/media/video/saa7134/saa7134-cards.c b/drivers/media/video/saa7134/saa7134-cards.c
index 991829e..77e5be9 100644
--- a/drivers/media/video/saa7134/saa7134-cards.c
+++ b/drivers/media/video/saa7134/saa7134-cards.c
@@ -2584,6 +2584,41 @@ struct saa7134_board saa7134_boards[] =
.gpio = 0x0200000,
},
},
+ [SAA7134_BOARD_FLYDVB_TRIO] = {
+ /* LifeView LR319 FlyDVB Trio */
+ /* Peter Missel <peter.missel@onlinehome.de> */
+ .name = "LifeView FlyDVB Trio",
+ .audio_clock = 0x00200000,
+ .tuner_type = TUNER_PHILIPS_TDA8290,
+ .radio_type = UNSET,
+ .tuner_addr = ADDR_UNSET,
+ .radio_addr = ADDR_UNSET,
+ .gpiomask = 0x00200000,
+ .inputs = {{
+ .name = name_tv, /* Analog broadcast/cable TV */
+ .vmux = 1,
+ .amux = TV,
+ .gpio = 0x200000, /* GPIO21=High for TV input */
+ .tv = 1,
+ },{
+ .name = name_svideo, /* S-Video signal on S-Video input */
+ .vmux = 8,
+ .amux = LINE2,
+ },{
+ .name = name_comp1, /* Composite signal on S-Video input */
+ .vmux = 0,
+ .amux = LINE2,
+ },{
+ .name = name_comp2, /* Composite input */
+ .vmux = 3,
+ .amux = LINE2,
+ }},
+ .radio = {
+ .name = name_radio,
+ .amux = TV,
+ .gpio = 0x000000, /* GPIO21=Low for FM radio antenna */
+ },
+ },
};

const unsigned int saa7134_bcount = ARRAY_SIZE(saa7134_boards);
@@ -3043,6 +3078,12 @@ struct pci_device_id saa7134_pci_tbl[] =
.subdevice = 0x1160,
.driver_data = SAA7134_BOARD_CINERGY250PCI,
},{
+ .vendor = PCI_VENDOR_ID_PHILIPS,
+ .device = PCI_DEVICE_ID_PHILIPS_SAA7133, /* SAA 7131E */
+ .subvendor = 0x5168,
+ .subdevice = 0x0319,
+ .driver_data = SAA7134_BOARD_FLYDVB_TRIO,
+ },{
/* --- boards without eeprom + subsystem ID --- */
.vendor = PCI_VENDOR_ID_PHILIPS,
.device = PCI_DEVICE_ID_PHILIPS_SAA7134,
diff --git a/drivers/media/video/saa7134/saa7134.h b/drivers/media/video/saa7134/saa7134.h
index 18978a4..e70eae8 100644
--- a/drivers/media/video/saa7134/saa7134.h
+++ b/drivers/media/video/saa7134/saa7134.h
@@ -209,6 +209,7 @@ struct saa7134_format {
#define SAA7134_BOARD_PHILIPS_TIGER 81
#define SAA7134_BOARD_MSI_TVATANYWHERE_PLUS 82
#define SAA7134_BOARD_CINERGY250PCI 83
+#define SAA7134_BOARD_FLYDVB_TRIO 84

#define SAA7134_MAXBOARDS 8
#define SAA7134_INPUT_MAX 8

BEST REGARDS FRON SPAIN

tobelz
June 19th, 2007, 12:07 PM
Although this Thread is quite old I try to get some support here...

I,too, use this card and it works great, apart from the viewer program that came with the card.
I use DVBViewer instead and I'm facing no problems. But I would like to use the IR shipped with the card. Unfortunately Girder does not seem to support this one.
During the installation of the 'DTV-Program' named viewer program a small tool is installed, named 'Remote Control MFC Application' (RemoteControl.exe). It is shown in the task-bar and allows to start and control the DTV-Program.

Can anyone tell me which possibilities there are to get the IR running with Girder?
What does the text mean 'nomentero' posted?

with best thanks

tobelz