Re: [linux-dvb] TT Connect S2-3600 (was: Pinnacle PCTV Sat HDTV Pro USB (PCTV452e) and DVB-S2)

2008-02-26 Thread André Weidemann

Dominik Kuhlen wrote:

Hi all,

Manus multiproto HG tree (jusst.de/hg/multiproto) and the attached patch make 
the pctv452e work with DVB-S2 and DVB-S :)


Hi all,
I took Dominiks patch and added support for the TT connect S2-3600.

The S2-3600 is tuning to DVB-S and DVB-S2 but I still got some image 
distortions. I'm quite sure I got the correct firmware for the S2-3600 
but I only did some quick testing last night.

The patch may still have some quirks... so use at your own risk.

If anyone should volunteer to try the attached patch, please make sure 
to apply the patch for the PCTV 452e first!

The firmware for the S2-3600 can be found here:
http://ilpss8.dyndns.org/dvb-usb-tt-connect-s2-3600-01.fw

I will also have a PCTV 452e for testing at the end of the week. So I 
can test both USB boxes with the driver.


 André
diff -Nrubw multiproto-pctv452e/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 
multiproto-s2-3600/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
--- multiproto-pctv452e/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h   
2008-02-26 08:50:03.484626963 +0100
+++ multiproto-s2-3600/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
2008-02-26 09:04:17.757309187 +0100
@@ -40,6 +40,7 @@
 #define USB_VID_MSI0x0db0
 #define USB_VID_OPERA1 0x695c
 #define USB_VID_PINNACLE   0x2304
+#define USB_VID_TECHNOTREND 0x0b48
 #define USB_VID_TERRATEC   0x0ccd
 #define USB_VID_VISIONPLUS 0x13d3
 #define USB_VID_TWINHAN0x1822
@@ -142,6 +143,7 @@
 #define USB_PID_PCTV_400E  0x020f
 #define USB_PID_PCTV_450E  0x0222
 #define USB_PID_PCTV_452E   0x021f
+#define USB_PID_TECHNOTREND_CONNECT_S2_3600 0x3007
 #define USB_PID_NEBULA_DIGITV  0x0201
 #define USB_PID_DVICO_BLUEBIRD_LGDT0xd820
 #define USB_PID_DVICO_BLUEBIRD_LG064F_COLD 0xd500
diff -Nrubw multiproto-pctv452e/linux/drivers/media/dvb/dvb-usb/Kconfig 
multiproto-s2-3600/linux/drivers/media/dvb/dvb-usb/Kconfig
--- multiproto-pctv452e/linux/drivers/media/dvb/dvb-usb/Kconfig 2008-02-26 
08:49:32.034834741 +0100
+++ multiproto-s2-3600/linux/drivers/media/dvb/dvb-usb/Kconfig  2008-02-26 
08:55:36.495604176 +0100
@@ -240,7 +240,7 @@
  Afatech AF9005 based receiver.
 
 config DVB_USB_PCTV452E
-   tristate Pinnacle PCTV HDTV Pro USB device
+   tristate Pinnacle PCTV HDTV Pro USB device/TT Connect S2-3600
depends on DVB_USB
select DVB_LNBP22
select DVB_STB0899
diff -Nrubw multiproto-pctv452e/linux/drivers/media/dvb/dvb-usb/pctv452e.c 
multiproto-s2-3600/linux/drivers/media/dvb/dvb-usb/pctv452e.c
--- multiproto-pctv452e/linux/drivers/media/dvb/dvb-usb/pctv452e.c  
2008-02-26 08:49:32.174842719 +0100
+++ multiproto-s2-3600/linux/drivers/media/dvb/dvb-usb/pctv452e.c   
2008-02-26 08:55:36.943629708 +0100
@@ -370,6 +370,7 @@
 static struct stb0899_config stb0899_config;
 static struct stb6100_config stb6100_config;
 static struct dvb_usb_device_properties pctv452e_properties;
+static struct dvb_usb_device_properties tt_connect_s2_3600_properties;
 
 int pctv452e_frontend_attach(struct dvb_usb_adapter *a) {
 
@@ -395,9 +396,12 @@
return 0;
 }
 
-static int pctv452e_usb_probe(struct usb_interface *intf,
-const struct usb_device_id *id) {
-  return dvb_usb_device_init(intf, pctv452e_properties, THIS_MODULE, NULL);
+static int pctv452e_usb_probe(struct usb_interface *intf,const struct 
usb_device_id *id) {
+   int ret=-ENOMEM;
+if ((ret=dvb_usb_device_init(intf, pctv452e_properties, THIS_MODULE, 
NULL))==0){
+   return ret;
+   }
+return dvb_usb_device_init(intf, 
tt_connect_s2_3600_properties,THIS_MODULE,NULL);
 }
 
 
@@ -423,7 +427,7 @@
 // { STB0899_IRQMSK_3  , 0xff },
 // { STB0899_IRQMSK_4  , 0xff },
{ STB0899_I2CCFG, 0x88 },
-   { STB0899_I2CRPT, 0x5c },
+   { STB0899_I2CRPT, 0x58 },
{ STB0899_GPIO00CFG , 0x82 },
{ STB0899_GPIO01CFG , 0x82 }, /* 0x02 - LED green 0x82 - LED 
orange */
{ STB0899_GPIO02CFG , 0x82 },
@@ -1007,6 +1011,7 @@
 
 static struct usb_device_id pctv452e_usb_table[] = {
{USB_DEVICE(USB_VID_PINNACLE, USB_PID_PCTV_452E)},
+   {USB_DEVICE(USB_VID_TECHNOTREND, USB_PID_TECHNOTREND_CONNECT_S2_3600)},
{}
 };
 MODULE_DEVICE_TABLE(usb, pctv452e_usb_table);
@@ -1066,6 +1071,61 @@
}
 };
 
+static struct dvb_usb_device_properties tt_connect_s2_3600_properties = {
+   .caps = DVB_USB_IS_AN_I2C_ADAPTER, /* more ? */
+   .usb_ctrl = DEVICE_SPECIFIC,
+
+   .size_of_priv = sizeof(struct pctv452e_state),
+
+   .identify_state   = 0, // this is a warm only device
+
+   .power_ctrl   = pctv452e_power_ctrl,
+
+   

Re: [linux-dvb] HVR4000 Update?

2008-02-26 Thread Ian Bonham
Hi Craig,

Thanks for that, after some tinkering about and being able to read that site
I've got DVB-S and DVB-T working on the HVR4000. I've not been able to tune
any DVB-S2, but am working mainly with Myth, so not sure whats required for
S2 with that.

To get DVB-S and DVB-T working in Myth, I had my frontend0 and frontend1
showing in /dev/dvb/adapter0. I created a folder /dev/dvb/adatper1 and
linked frontend0 (and the dvb, net and demux) in that folder into
/dev/dvb/adapter0/frontend1 and so on. That got me around Myth being unable
to handle multifrontends (I'm using Ubuntu feeds, building Myth from source
and patching is a job I'd need a spare weekend for!). I was able to set up
dvb cards and access the types happily that way.

The only thing with Myth that's maybe important to note is you must switch
off EIT scanning. I did not realise this at first and watching DVB-S
channels, every 10 minutes or so Myth would crash. Watching the backend log,
I saw the EIT scan kicking in and trying to access the DVB-T tuner whilst I
was watching the DVB-S channels. Obviously this caused a conflict, so by
turning off EIT scan I've had no problems since.

Hope that helps someone else struggling, and thanks for your pointers Craig,

Ian


On 23/02/2008, Craig Whitmore [EMAIL PROTECTED] wrote:

  Can anyone please make a clear guide on what I should do to get my HVR4k
  going properly with Myth? If I can't get things going 'properly' just
  being able
to help beta stuff would be good. What SVN do I need to check-out?
 What
 patches do I need to apply? What Myth do I need to check out? Then what
  patches does that need?


 If you check
 http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-4000
 there are links how to get:

 - Single Frontend (Either DVB-S or DVB-T)
 - Multi Frontend Going (DVB-S and DVB-T)
 - Multi Proto Going (DVB-S/S2 or DVB-T)
 - Multi Proto with Multi Frontends (DVB-S/S2 and DVB-T)
 ..
 Thanks


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] cx88-input: leadtek tv200xp global

2008-02-26 Thread Frühwald Szabolcs
hi there,

i've a leadtek tv2000xp global pci card
it's running OK (with some errors, but works) with current developement
v4l-dvb branch
i tried to enable it's IR remote control too in cx88-input.c
just copied tv2000xp expert switch entry:

case CX88_BOARD_WINFAST2000XP_EXPERT:
 ir_codes = ir_codes_winfast;
 ir-gpio_addr = MO_GP0_IO;
 ir-mask_keycode = 0x8f8;
 ir-mask_keyup = 0x100;
 ir-polling = 1; /* ms */
 break;

but the result of this was: IR recognized well by kernel, dev/input
device attached
but when i pressed a button on remote, it printed its character, waited
a sec and started to repeat this character forever
so, i pressed '6', out was:
61sec_delay666  etc..
could anybody help me to correct this?
it would be cool if i could paste a patch to the mailing list to enable
this functionality for this card
i figured out the main problem is with ir-mask_keyup=0x100, so maybe
it isn't there... but i didnt find it at 0x60,0x80 too and don't know
where could it be??

ps: I also tried to comment out this line of code (as i saw some other
entrys without this option), the repeats are stopped but when i pressed
a button more than once it's only showed up once. So, i pressed 6,
printed 6 but when i pressed 6 again, it didnt print anything. After i
pressed other button (printed once too), and pressed again 6, prints 6
again).

Thanks for your help...

bye,
Szab



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] help: is ASUS U3000 Mini supported?

2008-02-26 Thread Theng Kiat Ng
Hi all,

Is the above USB tuner (ASUS U3000 Mini) supported under linux? My old
tuners are broken and i need new tuners.

The Wiki says it is supported, but very bare on the details. (e.g. which
kernel module, USB_DIB0700? Where's the firmware? Supported since kernel
version what?)

I've been searching the Internet for hours but can't find anything
definitive.. Tried to download the driver from ASUS support page but no idea
how to install it on my Mandriva64 system.

If this works, does it work well under MythTV? Also can I run 2 tuners on
the same computer?

Would appreciate if somebody (anybody) can offer me some pointers. I'm using
Mandriva 2008.0 (64 bit version) an using stock 2.6.23.16 kernel.
Thanks to anyone who can help me.

Regards
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] help: is ASUS U3000 Mini supported?

2008-02-26 Thread Theng Kiat Ng
On Tue, Feb 26, 2008 at 9:07 PM, Theng Kiat Ng [EMAIL PROTECTED] wrote:

 Hi all,

 Is the above USB tuner (ASUS U3000 Mini) supported under linux? My old
 tuners are broken and i need new tuners.

 The Wiki says it is supported, but very bare on the details. (e.g. which
 kernel module, USB_DIB0700? Where's the firmware? Supported since kernel
 version what?)

I must be very tired today.. Looking further down the Wiki and all my
questions are answered there... :(

Will try to get one tomorrow and hope it'd work. Hopefully somebody in this
list can tell me your  successes/problems stories running two such tuners
under MythTV, esp if ur on a 64bit linux system.


Thanks.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] make errors multiproto

2008-02-26 Thread Michael Curtis
Can anyone help with this please?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Curtis
Sent: 20 February 2008 08:03
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] make errors multiproto

Hi all

The following errors occurred during the 'make all' of the multiproto
install

The mercurial was from the above date

I am using the TT3200 so the stb0899 errors will matter


/home/mythtv/dvb/multiproto/v4l/dvb_frontend.c: In function
'dvb_frontend_thread':
/home/mythtv/dvb/multiproto/v4l/dvb_frontend.c:1123: warning: unused
variable 'status'
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c: In function
'stb0899_diseqc_init':
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:834: warning: unused
variable 'ret_2'
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:833: warning: unused
variable 'ret_1'
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:832: warning: unused
variable 'trial'
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:830: warning: unused
variable 'i'
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:830: warning: unused
variable 'count'
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:826: warning: unused
variable 'rx_data'
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c: In function
'stb0899_sleep':
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:899: warning: unused
variable 'reg'
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c: In function
'stb0899_track':
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:1935: warning: unused
variable 'internal'
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:1932: warning: unused
variable 'lock_lost'
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c: At top level:
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:1727: warning:
'stb0899_track_carrier' defined but not used
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:1744: warning:
'stb0899_get_ifagc' defined but not used
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:1761: warning:
'stb0899_get_s1fec' defined but not used
/home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:1789: warning:
'stb0899_get_modcod' defined but not used
/home/mythtv/dvb/multiproto/v4l/radio-si470x.c: In function
'si470x_get_rds_registers':
/home/mythtv/dvb/multiproto/v4l/radio-si470x.c:562: warning: format '%d'
expects type 'int', but argument 3 has type 'long unsigned int'

Regards

Mike curtis


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

-- 
This message has been scanned for viruses and
dangerous content by IC-MailScanner, and is
believed to be clean.

For queries or information please contact:-

=
Internet Central Technical Support


 http://www.netcentral.co.uk
=


No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.20.9/1294 - Release Date: 22/02/2008 
18:39
 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.21.1/1299 - Release Date: 26/02/2008 
09:08
 

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] multiproto conversion / stb0899_search: Unsupported delivery system

2008-02-26 Thread Florian Lohoff

Hi,
i am trying to convert my little dvb streaming application 1) over to
multiproto and having some issues - I am seeing the DVBFE_SET_PARAMS
ioctl fail with Invalid argument...

The kernel log shows:

stb0899_search: Unsupported delivery system

although i am pretty shure i have set dvbfe_param-delivery to
DVBFE_DELSYS_DVBS2...

Card is a SkyStar HD:

00:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Subsystem: Technotrend Systemtechnik GmbH Unknown device 1019
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR-
Latency: 32 (3750ns min, 9500ns max)
Interrupt: pin A routed to IRQ 20
Region 0: Memory at dfff7e00 (32-bit, non-prefetchable) [size=512]

Modules:

budget_ci  23844  0 
stb089933152  1 
stb6100 7492  1 
firmware_class  9312  1 budget_ci
budget_core10852  1 budget_ci
ttpci_eeprom2464  1 budget_core
ir_common  36228  1 budget_ci
lnbp21  2208  1 
dvb_core   79996  2 budget_ci,budget_core

Kernel log when trying to start my little app stb0899 and stb6100 with verbose 
...:

stb0899_init: Initializing STB0899 ... 
stb0899_init: init device
stb0899_write_regs [0xf000]: 81
stb0899_write_regs [0xf0a0]: 32
stb0899_write_regs [0xf0a1]: 80
stb0899_write_regs [0xf0a4]: 04
stb0899_write_regs [0xf0a5]: 00
stb0899_write_regs [0xf0a6]: 00
stb0899_write_regs [0xf0a7]: 00
stb0899_write_regs [0xf0a8]: 20
stb0899_write_regs [0xf0a9]: 8c
stb0899_write_regs [0xf0aa]: 9a
stb0899_write_regs [0xf110]: 11
stb0899_write_regs [0xf111]: 0a
stb0899_write_regs [0xf112]: 05
stb0899_write_regs [0xf113]: 00
stb0899_write_regs [0xf114]: 00
stb0899_write_regs [0xf11c]: 00
stb0899_write_regs [0xf11d]: 00
stb0899_write_regs [0xf120]: 30
stb0899_write_regs [0xf121]: 00
stb0899_write_regs [0xf122]: 00
stb0899_write_regs [0xf123]: 00
stb0899_write_regs [0xf124]: f3
stb0899_write_regs [0xf125]: fc
stb0899_write_regs [0xf126]: ff
stb0899_write_regs [0xf127]: ff
stb0899_write_regs [0xf128]: 00
stb0899_write_regs [0xf129]: 88
stb0899_write_regs [0xf12a]: 48
stb0899_write_regs [0xf139]: 00
stb0899_write_regs [0xf13a]: 20
stb0899_write_regs [0xf13b]: c9
stb0899_write_regs [0xf13c]: 90
stb0899_write_regs [0xf13d]: 40
stb0899_write_regs [0xf13e]: 00
stb0899_write_regs [0xf140]: 82
stb0899_write_regs [0xf141]: 82
stb0899_write_regs [0xf142]: 82
stb0899_write_regs [0xf143]: 82
stb0899_write_regs [0xf144]: 82
stb0899_write_regs [0xf145]: 82
stb0899_write_regs [0xf146]: 82
stb0899_write_regs [0xf147]: 82
stb0899_write_regs [0xf148]: 82
stb0899_write_regs [0xf149]: 82
stb0899_write_regs [0xf14a]: 82
stb0899_write_regs [0xf14b]: 82
stb0899_write_regs [0xf14c]: 82
stb0899_write_regs [0xf14d]: 82
stb0899_write_regs [0xf14e]: 82
stb0899_write_regs [0xf14f]: 82
stb0899_write_regs [0xf150]: 82
stb0899_write_regs [0xf151]: 82
stb0899_write_regs [0xf152]: 82
stb0899_write_regs [0xf153]: 82
stb0899_write_regs [0xf154]: 82
stb0899_write_regs [0xf155]: b8
stb0899_write_regs [0xf156]: ba
stb0899_write_regs [0xf157]: 1c
stb0899_write_regs [0xf158]: 82
stb0899_write_regs [0xf159]: 91
stb0899_write_regs [0xf15a]: 82
stb0899_write_regs [0xf15b]: 7e
stb0899_write_regs [0xf15c]: 82
stb0899_write_regs [0xf15d]: 82
stb0899_write_regs [0xf15e]: 82
stb0899_write_regs [0xf15f]: 20
stb0899_write_regs [0xf160]: 82
stb0899_write_regs [0xf161]: 82
stb0899_write_regs [0xf162]: 82
stb0899_write_regs [0xf163]: 82
stb0899_write_regs [0xf164]: 82
stb0899_write_regs [0xf165]: 82
stb0899_write_regs [0xf166]: 82
stb0899_write_regs [0xf167]: 82
stb0899_write_regs [0xf1b3]: 15
stb0899_write_regs [0xf1b6]: 02
stb0899_write_regs [0xf1b7]: 00
stb0899_write_regs [0xf1b8]: 00
stb0899_write_regs [0xf1c2]: 20
stb0899_write_regs [0xf1c3]: 00
stb0899_write_regs [0xf200]: 00
_stb0899_read_reg: Reg=[0xf2ff], data=00
stb0899_write_regs [0xf201]: 0a
_stb0899_read_reg: Reg=[0xf2ff], data=00
stb0899_init: init S2 demod
stb0899_write_s2reg Device=[0xf3fc], Base Address=[0x], 
Offset=[0xf300], Data=[0x0103]
stb0899_write_s2reg Device=[0xf3fc], Base Address=[0x], 
Offset=[0xf304], Data=[0x3ed1da56]
stb0899_write_s2reg Device=[0xf3fc], Base Address=[0x], 
Offset=[0xf308], Data=[0x4000]
stb0899_write_s2reg Device=[0xf3fc], Base Address=[0x], 
Offset=[0xf30c], Data=[0x2ade]
stb0899_write_s2reg Device=[0xf3fc], Base Address=[0x], 
Offset=[0xf310], Data=[0x01bc]
stb0899_write_s2reg Device=[0xf3fc], Base Address=[0x], 
Offset=[0xf314], Data=[0x0200]
stb0899_write_s2reg Device=[0xf3fc], Base Address=[0x], 
Offset=[0xf31c], Data=[0x000f]
stb0899_write_s2reg Device=[0xf3fc], Base Address=[0x], 
Offset=[0xf320], Data=[0x03fb4a20]
stb0899_write_s2reg Device=[0xf3fc], Base Address=[0x], 

[linux-dvb] [PATCH] DMX_OUT_TSDEMUX_TAP: record two streams from same mux

2008-02-26 Thread Peter Hartley
Hi there,

Currently (in linux-2.6.24, but linux-dvb hg looks similar), the
dmx_output_t in the dmx_pes_filter_params decides two things: whether
output is sent to demux0 or dvr0 (in dmxdev.c:dvb_dmxdev_ts_callback),
*and* whether to depacketise TS (in dmxdev.c:dvb_dmxdev_filter_start).
As it stands, those two things can't be set independently: output
destined for demux0 is depacketised, output for dvr0 isn't.

This is what you want for capturing multiple audio streams from the same
multiplex simultaneously: open demux0 several times and send
depacketised output there. And capturing a single video stream is fine
too: open dvr0. But for capturing multiple video streams, it's surely
not what you want: you want multi-open (so demux0, not dvr0), but you
want the TS nature preserved (because that's what you want on output, as
you're going to re-multiplex it with the audio).

The attached patch adds a new value for dmx_output_t:
DMX_OUT_TSDEMUX_TAP, which sends TS to the demux0 device. The main
question I have, is, seeing as this was such a simple change, why didn't
it already work like that? Does everyone else who wants to capture
multiple video streams, take the whole multiplex into userspace and
demux it themselves? Or do they take PES from each demux0 device and
re-multiplex that into PS, not TS?

With this patch and a dvb-usb-dib0700 (and UK Freeview from Sandy
Heath), I can successfully capture an audio/video PID pair into a TS
file that mplayer can play back.

Peter

--- include/linux/dvb/dmx.h~	2008-01-24 22:58:37.0 +
+++ include/linux/dvb/dmx.h	2008-02-25 23:01:45.0 +
@@ -39,9 +39,10 @@ typedef enum
 	DMX_OUT_DECODER, /* Streaming directly to decoder. */
 	DMX_OUT_TAP, /* Output going to a memory buffer */
 			 /* (to be retrieved via the read command).*/
-	DMX_OUT_TS_TAP   /* Output multiplexed into a new TS  */
+	DMX_OUT_TS_TAP,  /* Output multiplexed into a new TS  */
 			 /* (to be retrieved by reading from the */
 			 /* logical DVR device). */
+	DMX_OUT_TSDEMUX_TAP /* Like TS_TAP but retrieved from the DMX device */
 } dmx_output_t;
 
 
--- drivers/media/dvb/dvb-core/dmxdev.c~	2008-01-24 22:58:37.0 +
+++ drivers/media/dvb/dvb-core/dmxdev.c	2008-02-25 23:02:29.0 +
@@ -374,7 +374,8 @@ static int dvb_dmxdev_ts_callback(const 
 		return 0;
 	}
 
-	if (dmxdevfilter-params.pes.output == DMX_OUT_TAP)
+	if (dmxdevfilter-params.pes.output == DMX_OUT_TAP
+	|| dmxdevfilter-params.pes.output == DMX_OUT_TSDEMUX_TAP)
 		buffer = dmxdevfilter-buffer;
 	else
 		buffer = dmxdevfilter-dev-dvr_buffer;
@@ -618,7 +619,7 @@ static int dvb_dmxdev_filter_start(struc
 		else
 			ts_type = 0;
 
-		if (otype == DMX_OUT_TS_TAP)
+		if (otype == DMX_OUT_TS_TAP || otype == DMX_OUT_TSDEMUX_TAP)
 			ts_type |= TS_PACKET;
 
 		if (otype == DMX_OUT_TAP)
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Nova-T 500 issues - losing one tuner

2008-02-26 Thread Philip Pemberton
Patrik Hansson wrote:
 Just wanted to say that I´m experiencing the same.
 Using latest rev (the one with patches merged) + unknown remote key patch.
 Ubuntu 7.10
 
 Also having a lot of prebuffer timeout 10 times i the middle of shows.

I think I might have a workaround... On Mythbuntu or one of the many Ubuntu 
variants, this seems to work:

1)  Run:
   lsmod |grep usbcore

2)  If step 1 produced any output that started with 'usbcore', then usbcore is 
loaded as a module. Perform step 3a. Otherwise, step 3b.

3a) Create a text file called /etc/modprobe.d/local-dvb (the name is fairly 
irrelevant). Insert one line of text into it:
   options usbcore autosuspend=-1
 Now go to step 4.

3b) Your kernel has usbcore built in. That means you have to modify the kernel 
command line...
 Edit /boot/grub/menu.lst (you'll need to sudo to do this). Search for 
this line:
# defoptions=quiet splash
 Amend it to read:
# defoptions=quiet splash usbcore.autosuspend=-1
 It's meant to be commented out, so leave the hash at the beginning of the 
line alone... Save and exit, then run ...
sudo update grub
 Ubuntu will regenerate grub.conf, using the new kernel command line. Off 
to step 4 you go!

 If you're using a non-Debian distro (e.g. Fedora), do the same thing but 
edit the 'kernel' line instead. It might read:
kernel  /boot/vmlinuz-2.6.24-8-generic root=LABEL=/ ro quiet splash
 Change it to:
kernel  /boot/vmlinuz-2.6.24-8-generic root=LABEL=/ ro quiet splash 
usbcore.autosuspend=-1

4)  Reboot your PC.

This is a bit long-winded, but saves a kernel recompile, and a ton of messing 
around recompiling kernels when Ubuntu do another release.

I'm working on what I consider to be a better fix, which involves using the 
kernel's Quirks function to disable USB suspend just for the DiBcom 
controllers. That is, the kernel won't try and suspend them at all...

Thanks,
-- 
Phil. |  (\_/)  This is Bunny. Copy and paste Bunny
[EMAIL PROTECTED]   | (='.'=) into your signature to help him gain
http://www.philpem.me.uk/ | ()_() world domination.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Nova-T 500 issues - losing one tuner

2008-02-26 Thread Patrik Hansson
On Tue, Feb 26, 2008 at 8:18 PM, Philip Pemberton [EMAIL PROTECTED] wrote:
 Patrik Hansson wrote:
   Just wanted to say that I´m experiencing the same.
   Using latest rev (the one with patches merged) + unknown remote key patch.
   Ubuntu 7.10
  
   Also having a lot of prebuffer timeout 10 times i the middle of shows.

  I think I might have a workaround... On Mythbuntu or one of the many Ubuntu
  variants, this seems to work:

  1)  Run:
lsmod |grep usbcore

  2)  If step 1 produced any output that started with 'usbcore', then usbcore 
 is
  loaded as a module. Perform step 3a. Otherwise, step 3b.

  3a) Create a text file called /etc/modprobe.d/local-dvb (the name is fairly
  irrelevant). Insert one line of text into it:
options usbcore autosuspend=-1
  Now go to step 4.

  3b) Your kernel has usbcore built in. That means you have to modify the 
 kernel
  command line...
  Edit /boot/grub/menu.lst (you'll need to sudo to do this). Search for
  this line:
  # defoptions=quiet splash
  Amend it to read:
  # defoptions=quiet splash usbcore.autosuspend=-1
  It's meant to be commented out, so leave the hash at the beginning of the
  line alone... Save and exit, then run ...
  sudo update grub
  Ubuntu will regenerate grub.conf, using the new kernel command line. Off
  to step 4 you go!

  If you're using a non-Debian distro (e.g. Fedora), do the same thing but
  edit the 'kernel' line instead. It might read:
  kernel  /boot/vmlinuz-2.6.24-8-generic root=LABEL=/ ro quiet splash
  Change it to:
  kernel  /boot/vmlinuz-2.6.24-8-generic root=LABEL=/ ro quiet splash
  usbcore.autosuspend=-1

  4)  Reboot your PC.

  This is a bit long-winded, but saves a kernel recompile, and a ton of messing
  around recompiling kernels when Ubuntu do another release.

  I'm working on what I consider to be a better fix, which involves using the
  kernel's Quirks function to disable USB suspend just for the DiBcom
  controllers. That is, the kernel won't try and suspend them at all...



  Thanks,
  --
  Phil. |  (\_/)  This is Bunny. Copy and paste Bunny
  [EMAIL PROTECTED]   | (='.'=) into your signature to help him gain
  http://www.philpem.me.uk/ | ()_() world domination.


It was a module and i put the option i /etc/modprobe.d/options next to
options dvb-usb-dib0700 force_lna_activation=1
Running now, will be back with the results.
On a side note:
Could that be the reason debug=15 also might work as a workaround,
there is so much traffic that the usb never suspends ?
Thanks Phil for the fix, hope it stays stable..

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] Fwd: scan file for es-Las_Palmas

2008-02-26 Thread Christoph Pfister
From a kaffeine user ...

Christoph


--  Weitergeleitete Nachricht  --

Betreff: [Kaffeine-user] DVB-t location file
Datum: Sonntag 24 Februar 2008
Von: Gabriel Alemán Rodríguez [EMAIL PROTECTED]
An: [EMAIL PROTECTED]

I send you my DVB-t location from Las Palmas (Spain)

---


es-Las_Palmas
Description: Binary data
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] DVB-T initial tuning data file for lv-Riga

2008-02-26 Thread Christoph Pfister
Hi,

2008/2/18, Raimonds Cicans [EMAIL PROTECTED]:
 # Latvia - Riga (lv-Riga)
 # Generated by Raimonds Cicans

Thanks, added :)

Christoph

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] DVB-T initial scan file for Santander, Spain

2008-02-26 Thread Christoph Pfister
Hi,

2008/2/23, [EMAIL PROTECTED]
[EMAIL PROTECTED]:
  Hello. In the end, I did not need this file, because w_scan with the -X
 option already gave me a channels.conf ready to use with tzap; but since
 it is already created I send it to you.

  I hope this is the right place for this, I have never written to a mailing
 list before.

Yes, it's the correct place.

  Best regards and thanks a lot for your time and work.

Added the file, thanks!

Christoph

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

2008-02-26 Thread Vangelis Nonas
Hello,

Here is the output of hg log|head -n 5 for two different directories 
(multiproto and multiproto_7200)

for multiproto:
changeset:   7205:9bdb997e38b5
tag: tip
user:Manu Abraham [EMAIL PROTECTED]
date:Sun Feb 24 02:10:56 2008 +0400
summary: We can now reduce the debug levels, just need to look at 
errors only.

for multiproto_7200:
changeset:   7200:45eec532cefa
tag: tip
parent:  7095:a577a5dbc93d
parent:  7199:0448e5a6d8a6
user:Manu Abraham [EMAIL PROTECTED]


So I guess I was referring to 7200 and not to 7201.
I am very positive about the results because I have tested it many 
times. It is just that it is 7200 instead of 7201.
So as a concluesion, 7200 behaves better than 7205. My corrected little 
table follows below just for clarification.

Changeset   Verbose  channels

7200 12152
7200 22105
7200 52081
7205 11760
7205 21608
7205 51578


I apologise for the confusion, I may have caused.

Regards
Vagelis




Manu Abraham wrote:
 Vangelis Nonas wrote:
 Hello,

 I have tested again changesets 7201 and 7205 with verbose 5, 2 and 1 
 scanning 101 transponders on Hotbird (I attach my transponders file 
 -- it is taken and adopted from ProgDvb).

 Here are my statistics:

 Changeset   Verbose  channels
 
 7201 12152
 7201 22105
 7201 52081
 7205 11760
 7205 21608
 7205 51578


 Are you really sure that 7201 behaves better than others. I ask 
 this, since
 there was a bug in 7201 which caused many people not to have a LOCK, the
 bugs which was fixed in 7203 and 7204. I am at a loss now, as to
 understanding this strange phenomena, how a lock was achieved with no
 communication to the tuner.

 If it were 7200, i could have still believed, there was a possibility, 
 but 7201
 i am terribly confused.

 Can you please verify whether you didn't get mixed up with the changeset
 numbers or the logs that were produced ?


 Regards,
 Manu


 .



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping

2008-02-26 Thread Manu Abraham
Vangelis Nonas wrote:
 Hello,
 
 Here is the output of hg log|head -n 5 for two different directories 
 (multiproto and multiproto_7200)
 
 for multiproto:
 changeset:   7205:9bdb997e38b5
 tag: tip
 user:Manu Abraham [EMAIL PROTECTED]
 date:Sun Feb 24 02:10:56 2008 +0400
 summary: We can now reduce the debug levels, just need to look at 
 errors only.
 
 for multiproto_7200:
 changeset:   7200:45eec532cefa
 tag: tip
 parent:  7095:a577a5dbc93d
 parent:  7199:0448e5a6d8a6
 user:Manu Abraham [EMAIL PROTECTED]
 
 
 So I guess I was referring to 7200 and not to 7201.
 I am very positive about the results because I have tested it many 
 times. It is just that it is 7200 instead of 7201.
 So as a concluesion, 7200 behaves better than 7205. My corrected little 
 table follows below just for clarification.


Ok, fine this is very much possible. Can other STB0899 users (all of them)
verify this result, such that i can revert back the changes ?


 
 Changeset   Verbose  channels
 
 7200 12152
 7200 22105
 7200 52081
 7205 11760
 7205 21608
 7205 51578
 
 
 I apologise for the confusion, I may have caused.

No worries, don't apologise, this is all a part of the testing phase.


Thanks,
Manu

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Yuan EC372S (STK7700D based device)

2008-02-26 Thread Albert Comerma
Are you really sure it uses the same chips?? because it's really strange
this timeout, when it seems to work in the same model... Which distribution
are you using?

Albert
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Re : My own TT S2-3200 problems ;-)

2008-02-26 Thread manu
On 01/18/2008 10:50:07 AM, David BERCOT wrote:
 Hi,
 
 Like many others, I'm trying to use my TT S2-3200 under Debian. 
 Before
 trying softwares (VDR, etc...), I'd like to install it properly.
 
 Here is my steps (from many tutorials) :
 FIRMWARE
 # mkdir /data/debian/DVB
 # cd /data/debian/DVB
 # wget http://www.linuxtv.org/downloads/firmware/dvb-ttpci-01.fw-2622
 # cd /lib/firmware/
 # cp -a /data/debian/DVB/dvb-ttpci-01.fw-2622 .
 # ln -s dvb-ttpci-01.fw-2622 dvb-ttpci-01.fw
 
 DRIVER
 # cd /data/debian/DVB
 # apt-get install mercurial
 # hg clone http://jusst.de/hg/multiproto
 # cd multiproto
 # make
 # make install
 # modprobe stb6100
 # modprobe stb0899
 # modprobe lnbp21
 # modprobe budget-ci
 
 DMESG
 # dmesg
 saa7146: register extension 'budget_ci dvb'.
 ACPI: PCI Interrupt :05:01.0[A] - GSI 22 (level, low) - IRQ 22
 saa7146: found saa7146 @ mem c20001598c00 (revision 1, irq 22)
 (0x13c2,0x1019).
 saa7146 (0): dma buffer size 192512
 DVB: registering new adapter (TT-Budget S2-3200 PCI)
 adapter has MAC addr = 00:d0:5c:0b:a5:8b
 input: Budget-CI dvb ir receiver saa7146 (0) as /class/input/input9
 budget_ci: CI interface initialised
 stb0899_write_regs [0xf1b6]: 02
 stb0899_write_regs [0xf1c2]: 00
 stb0899_write_regs [0xf1c3]: 00
 _stb0899_read_reg: Reg=[0xf000], data=81
 stb0899_get_dev_id: ID reg=[0x81]
 stb0899_get_dev_id: Device ID=[8], Release=[1]
 _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400],
 Offset=[0xf334], Data=[0x444d4431]
 _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400],
 Offset=[0xf33c], Data=[0x0001] stb0899_get_dev_id: Demodulator
 Core
 ID=[DMD1], Version=[1] _stb0899_read_s2reg Device=[0xfafc], Base
 address=[0x0800], Offset=[0xfa2c], Data=[0x46454331]
 _stb0899_read_s2reg Device=[0xfafc], Base address=[0x0800],
 Offset=[0xfa34], Data=[0x0001] stb0899_get_dev_id: FEC Core
 ID=[FEC1], Version=[1] stb0899_attach: Attaching STB0899
 stb6100_attach: Attaching STB6100 DVB: registering frontend 0 
 (STB0899
 Multistandard)... dvb_ca adaptor 0: PC card did not respond :(
 
 Do you have any clue about this error ?
 
 Thank you very much.


Hi David,
did you manage to test with the cam to get something working?
I would be thrilled to know if someone has ever managed to get the TT 
3200 to work with a CAM (I mean the full monty: lock+good picture ;-)
Bye
Manu


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] hvr1250 messages

2008-02-26 Thread Andy Wettstein
Hi,

I just installed a hauppauge hvr1250 and it seems to be ok, but
there are ton of messages being logged.  I am wondering if these 
messages are something to be concerned about.

uname:
Linux beerme 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686 GNU/Linux


Relevant dmesg output:

cx23885 driver version 0.0.1 loaded
ACPI: PCI Interrupt Link [APC5] enabled at IRQ 16
ACPI: PCI Interrupt :01:00.0[A] - Link [APC5] - GSI 16 (level, low) - 
IRQ 19
CORE cx23885[0]: subsystem: 0070:7911, board: Hauppauge WinTV-HVR1250 
[card=3,autodetected]
cx23885[0]: i2c bus 0 registered
cx23885[0]: i2c bus 1 registered
cx23885[0]: i2c bus 2 registered
tveeprom 0-0050: Encountered bad packet header [ff]. Corrupt or not a Hauppauge 
eeprom.
cx23885[0]: warning: unknown hauppauge model #0
cx23885[0]: hauppauge eeprom: model=0
cx23885[0]: cx23885 based dvb card
MT2131: successfully identified at address 0x61
DVB: registering new adapter (cx23885[0])
DVB: registering frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)...
cx23885[0]/0: found at :01:00.0, rev: 2, irq: 19, latency: 0, mmio: 
0xfd80
PCI: Setting latency timer of device :01:00.0 to 64


lspci:

01:00.0 Multimedia video controller: Conexant Unknown device 8852 (rev 02)
   Subsystem: Hauppauge computer works Inc. Unknown device 7911
   Flags: bus master, fast devsel, latency 0, IRQ 19
   Memory at fd80 (64-bit, non-prefetchable) [size=2M]
   Capabilities: [40] Express Endpoint, MSI 00
   Capabilities: [80] Power Management version 2
   Capabilities: [90] Vital Product Data ?
   Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 
Enable-
   Capabilities: [100] Advanced Error Reporting ?
   Capabilities: [200] Virtual Channel ?
   Kernel driver in use: cx23885
   Kernel modules: cx23885

Once I start watching TV with mythtv I start getting stuff like this:

cx23885[0]: mpeg risc op code error
cx23885[0]: TS2 C - dma channel status dump
cx23885[0]:   cmds: init risc lo   : 0x158ce000
cx23885[0]:   cmds: init risc hi   : 0x
cx23885[0]:   cmds: cdt base   : 0x00010480
cx23885[0]:   cmds: cdt size   : 0x000a
cx23885[0]:   cmds: iq base: 0x00010680
cx23885[0]:   cmds: iq size: 0x0010
cx23885[0]:   cmds: risc pc lo : 0x358a3090
cx23885[0]:   cmds: risc pc hi : 0x
cx23885[0]:   cmds: iq wr ptr  : 0x41a4
cx23885[0]:   cmds: iq rd ptr  : 0x41a8
cx23885[0]:   cmds: cdt current: 0x00010498
cx23885[0]:   cmds: pci target lo  : 0x371aa1a0
cx23885[0]:   cmds: pci target hi  : 0x
cx23885[0]:   cmds: line / byte: 0x0366
cx23885[0]:   risc0: 0x1c0002f0 [ write sol eol count=752 ]
cx23885[0]:   risc1: 0x371aa1a0 [ INVALID eol irq2 irq1 20 19 cnt1 resync 13 
count=416 ]
cx23885[0]:   risc2: 0x [ INVALID count=0 ]
cx23885[0]:   risc3: 0x1c0002f0 [ write sol eol count=752 ]
cx23885[0]:   (0x00010680) iq 0: 0x [ INVALID count=0 ]
cx23885[0]:   (0x00010684) iq 1: 0x180002a0 [ write sol count=672 ]
cx23885[0]:   iq 2: 0x371aad60 [ arg #1 ]
cx23885[0]:   iq 3: 0x [ arg #2 ]
cx23885[0]:   (0x00010690) iq 4: 0x [ INVALID count=0 ]
cx23885[0]:   (0x00010694) iq 5: 0x1c0002f0 [ write sol eol count=752 ]
cx23885[0]:   iq 6: 0x371aa1a0 [ arg #1 ]
cx23885[0]:   iq 7: 0x [ arg #2 ]
cx23885[0]:   (0x000106a0) iq 8: 0x1c0002f0 [ write sol eol count=752 ]
cx23885[0]:   iq 9: 0x371aa490 [ arg #1 ]
cx23885[0]:   iq a: 0x [ arg #2 ]
cx23885[0]:   (0x000106ac) iq b: 0x1c0002f0 [ write sol eol count=752 ]
cx23885[0]:   iq c: 0x371aa780 [ arg #1 ]
cx23885[0]:   iq d: 0x [ arg #2 ]
cx23885[0]:   (0x000106b8) iq e: 0x1c0002f0 [ write sol eol count=752 ]
cx23885[0]:   iq f: 0x371aaa70 [ arg #1 ]
cx23885[0]:   iq 10: 0x92d9c054 [ arg #2 ]
cx23885[0]: fifo: 0x6000 - 0x7000
cx23885[0]: ctrl: 0x00010680 - 0x106e0
cx23885[0]:   ptr1_reg: 0x64b0
cx23885[0]:   ptr2_reg: 0x00010498
cx23885[0]:   cnt1_reg: 0x001c
cx23885[0]:   cnt2_reg: 0x0007


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] [PATCH] DMX_OUT_TSDEMUX_TAP: record two streams from same mux

2008-02-26 Thread Andreas Oberritter
Peter Hartley wrote:
 The attached patch adds a new value for dmx_output_t:
 DMX_OUT_TSDEMUX_TAP, which sends TS to the demux0 device. The main
 question I have, is, seeing as this was such a simple change, why didn't
 it already work like that? Does everyone else who wants to capture
 multiple video streams, take the whole multiplex into userspace and
 demux it themselves? Or do they take PES from each demux0 device and
 re-multiplex that into PS, not TS?

I like your patch and would like to ask Mauro to integrate it if no one
objects, mainly because it serves as a basis for a DMX_ADD_PID ioctl
suggested by Felix Domke some months ago.

Regards,
Andreas

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] New Hauppauge DVB PCIe devices HVR-2200, HVR-1700 and HVR-1200

2008-02-26 Thread Steven Ellis
Been reading up on these as it appears that the HVR-2200 is now available
in Australia. I've updated the Wiki
(http://www.linuxtv.org/wiki/index.php/Hauppauge) with initial pages for
all of these cards, but I don't have any chip or technical details yet.

Most of the information I could find was on their Singapore website -
http://www.hauppauge.com.sg/web-content/pages/prods_hvr.html

Can any of our Hauppauge contacts confirm the chipsets and technical details?

The fact that the HVR-2200 is a dual hybrid tuner with DVB-T and MPEG2
hardware capture makes it a very interesting product.

Steve

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] New Hauppauge DVB PCIe devices HVR-2200, HVR-1700 and HVR-1200

2008-02-26 Thread Craig Whitmore

- Original Message - 
From: Steven Ellis [EMAIL PROTECTED]
To: linux-dvb@linuxtv.org
Sent: Wednesday, February 27, 2008 6:02 PM
Subject: [linux-dvb] New Hauppauge DVB PCIe devices HVR-2200,HVR-1700 and 
HVR-1200


 Been reading up on these as it appears that the HVR-2200 is now available
 in Australia. I've updated the Wiki
 (http://www.linuxtv.org/wiki/index.php/Hauppauge) with initial pages for
 all of these cards, but I don't have any chip or technical details yet.


The wholesalers in NZ have these 3 new cards as well in (but only the 2200 
in stock at the moment). If I read right a while ago no PCI-E cards have any 
drivers yet

Its low profile which is good and from the pictures I've found can't really 
see the chipset its using.

Thanks


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb