Re: EM28188 and TDA18271HDC2

2011-06-06 Thread Magnus Alm
Hi!

Doesn't Sundtek make their own closed drivers?

2011/6/6 Kristoffer Edwardsson :
> HI
>
> I Noticed the em28xx driver in kernel but the EM28188 is not supported.
>
> I dont know if it can be supported but here is some info about the device.
> Its a DVB-CT hybrid device without analog from Sundtek.
>
>
> Device Descriptor:
>  bLength                18
>  bDescriptorType         1
>  bcdUSB               2.00
>  bDeviceClass            0 (Defined at Interface level)
>  bDeviceSubClass         0
>  bDeviceProtocol         0
>  bMaxPacketSize0        64
>  idVendor           0xeb1a eMPIA Technology, Inc.
>  idProduct          0x51b2
>  bcdDevice            1.00
>  iManufacturer           0
>  iProduct                1 USB 28185 Device
>  iSerial                 2 ODVBTB
>  bNumConfigurations      1
>  Configuration Descriptor:
>
> //Kristoffer
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: For those that uses Pinnacle PCTV 340e

2010-11-20 Thread Magnus Alm
2010/11/15 Mohammad Bahathir Hashim :
> On 2010-11-14, Magnus Alm  wrote:
>> --00504502b04953b108049503ec60
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> Hi!
>>
>> I've merged the code for the 340e, that Devin Heitmueller made over at
>> Kernellabs, with the latest HG tree and tested it on Ubuntu 10.10
>> today (2.6.35-22-generic).
>>
>> I lack the knowledge on how to add the new files (xc4000.c and
>> xc4000.h) to a patch, so the script added in the tar ball just copies
>> it to the right place, the firmware has to be manually copied too.
>>
>> /Magnus
>
> Just want to share an alternatives, patches to vanilla kernel 2.6.35;
> by me, which I sent to Istvan Varga.
>
> http://istvanv.users.sourceforge.net/v4l/xc4000.html
>
>
> I am using PCTV 340e with GNU/Linux since Devin Heitmueller's
> "Christmas present" in kernellabs.com last year. I did few portings to
> make the driver workable with vanilla 2.6.34 and later.
>
> Beside's Devin's xc4000.[ch], I also use the files (xc4000.[ch] and
> firmware) from Istvan page. It works very well and the dongle feels
> much cooler when idling. because the PCTV 340e's power management is
> working.
>
> Since there are several devices using xc4000 driver; I really hope
> that it can included in main v4l stream; at least in the staging
> directory.
>
> Also really like to see analog support (S-video capture, analog TV and
> FM radio) for PCTV 340e too :). I was told that the dib0700 driver
> does not has the analog tuning yet.
>
> Thank you
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Tried "your" code today and it works slightly better since the tuner
still works after a reboot.
The remote stops working tho. I get this in dmesg: "dib0700: rc submit
urb failed".

Can't say I notice any difference on how warm it becomes tho.

/Magnus Alm
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [em28xx] No sound in Leadtek WinFast TV USB II (not Deluxe)

2010-05-06 Thread Magnus Alm
2010/5/7 Владимир Чернышев :
> Hello.
>
> I try to plug  Leadtek WinFast TV USB II (LR6021 Rev. C) to my Ubuntu
> 10.04 (2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010
> i686 GNU/Linux with all latest security and updates ). First I try
> card=8 - no results, then I try card=28 (because in Windows it seems
> like Leadtek WinFast TV USB II Deluxe) - TV works fine, tvtime scans
> all available channels, but no sound in any audio standards
> (/dev/mixer:line1 is ok with other sources). If I start tuner in
> Windows, make hard reset, boot Ubuntu and start tvtime then audio
> works fine at all channels while tuner is powered on. So I think
> em28xx doesn't execute some initializing sequence for turn on audio.
>
> With latest version from http://linuxtv.org/hg/v4l-dvb my tuner works
> only if i change SAA7115_COMPOSITE4 to SAA7115_COMPOSITE2 in
> EM28XX_VMUX_TELEVISION section for Leadtek WinFast TV USB II Deluxe in
> em28xx-cards.c and only video too. /dev/radio detected but not work
> too.
>
> Any tips, recommendations? I don't want use Windows to tuner init only :)
>
> The peace of dmesg when I don't set card:
>
> em28xx #0: found i2c device @ 0x30 [???]
> em28xx #0: found i2c device @ 0x3e [???]
> em28xx #0: found i2c device @ 0x4a [saa7113h]
> em28xx #0: found i2c device @ 0x86 [tda9887]
> em28xx #0: found i2c device @ 0xb0 [tda9874]
> em28xx #0: found i2c device @ 0xc2 [tuner (analog)]
> em28xx #0: Board i2c devicelist hash is 0x81bb00dc
>
> dmesg with "original" (srcversion: AC6C6B6C3CB530BED33DFD3) em28xx
>
> em28xx: New device @ 480 Mbps (eb1a:2820, interface 0, class 0)
> em28xx #0: chip ID is em2820 (or em2710)
> em28xx #0: board has no eeprom
> em28xx #0: Identified as Leadtek Winfast USB II Deluxe (card=28)
> em28xx #0:
> em28xx #0: The support for this board weren't valid yet.
> em28xx #0: Please send a report of having this working
> em28xx #0: not to V4L mailing list (and/or to other addresses)
> saa7115 2-0025: saa7113 found (1f7113d0e10) @ 0x4a (em28xx #0)
> tuner 2-0043: chip found @ 0x86 (em28xx #0)
> tda9887 2-0043: creating new instance
> tda9887 2-0043: tda988[5/6/7] found
> tuner 2-0061: chip found @ 0xc2 (em28xx #0)
> tuner-simple 2-0061: creating new instance
> tuner-simple 2-0061: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3))
> em28xx #0: Config register raw data: 0x00
> em28xx #0: v4l2 driver version 0.1.2
> em28xx #0: V4L2 video device registered as /dev/video0
> usbcore: registered new interface driver em28xx
> em28xx driver loaded
>
> dmesg with latest (srcversion: 7B6A05D4D518CB79FF69F9D) em28xx (with
> minor change sad above).
>
> em28xx: New device @ 480 Mbps (eb1a:2820, interface 0, class 0)
> em28xx #0: chip ID is em2820 (or em2710)
> em28xx #0: board has no eeprom
> input: i2c IR (i2c IR (EM2820 Winfast  as /devices/virtual/irrcv/irrcv0/input7
> irrcv0: i2c IR (i2c IR (EM2820 Winfast  as /devices/virtual/irrcv/irrcv0
> ir-kbd-i2c: i2c IR (i2c IR (EM2820 Winfast  detected at
> i2c-2/2-001f/ir0 [em28xx #0]
> em28xx #0: Identified as Leadtek Winfast USB II Deluxe (card=28)
> em28xx #0:
> em28xx #0: The support for this board weren't valid yet.
> em28xx #0: Please send a report of having this working
> em28xx #0: not to V4L mailing list (and/or to other addresses)
> saa7115 2-0025: saa7113 found (1f7113d0e10) @ 0x4a (em28xx #0)
> tvaudio 2-0058: found tda9874a.
> tvaudio 2-0058: tda9874h/a found @ 0xb0 (em28xx #0)
> tuner 2-: chip found @ 0x0 (em28xx #0)
> tuner 2-0043: chip found @ 0x86 (em28xx #0)
> tda9887 2-0043: creating new instance
> tda9887 2-0043: tda988[5/6/7] found
> tuner 2-0061: chip found @ 0xc2 (em28xx #0)
> tuner-simple 2-: unable to probe Alps TSBE1, proceeding anyway.
> tuner-simple 2-: creating new instance
> tuner-simple 2-: type set to 10 (Alps TSBE1)
> tuner-simple 2-0061: creating new instance
> tuner-simple 2-0061: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3))
> em28xx #0: Config register raw data: 0x00
> em28xx #0: v4l2 driver version 0.1.2
> em28xx #0: Registered radio device as radio0
> em28xx #0: V4L2 video device registered as video0
> usbcore: registered new interface driver em28xx
> em28xx driver loaded
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Hi, the main problem (I think) is that your box doesn't support audio
over usb. So when you use the "card=28" option, it doesn't turn on the
audio output connector. Your box has a Em2800 chip, where the "Deluxe"
version uses a Em2820.

I'll take a look at the code when I comes home, maybe I can figure
something out. Your box is supposed to be supported but maybe some
regression in the codes has happend.

/Magnus
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majord

I found I bug in tvtime, where do I report it?

2009-11-13 Thread Magnus Alm
Hi!

If this is the right place, I can as well try to describe it now.
(And I hope I makes sense.)

The bug is about the "Enable/Disable signal detection".

As it is now in  videoinput.c:

int videoinput_check_for_signal( videoinput_t *vidin, int check_freq_present )
{
if(  videoinput_freq_present( vidin ) || !check_freq_present ) {
switch( vidin->cur_tuner_state ) {
case TUNER_STATE_NO_SIGNAL:


Should be:

int videoinput_check_for_signal( videoinput_t *vidin, int check_freq_present )
{
if( !check_freq_present || videoinput_freq_present( vidin )) {
switch( vidin->cur_tuner_state ) {
case TUNER_STATE_NO_SIGNAL:

So just switch place for "videoinput_freq_present( vidin )" and
"!check_freq_present" so it actually cares if you disable signal
detection.

With this change, disabling signal detection will remove the frame
drops I have in tvtime.


Cheers, have a nice weekend.
Magnus Alm
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[PATCH] em28xx: fix for "Leadtek winfast tv usbii deluxe"

2009-11-13 Thread Magnus Alm
em28xx: fix for "Leadtek winfast tv usbii deluxe"

From: Magnus Alm 

This patch adds working:
Video and Sound for Television, Svideo and Composite.
Radio.
Stereo.
Also ir-remote for kernel 2.6.30 and higher.

Priority: high

diff -r 19c0469c02c3 linux/drivers/media/common/ir-keymaps.c
--- a/linux/drivers/media/common/ir-keymaps.c   Sat Nov 07 15:51:01 2009 -0200
+++ b/linux/drivers/media/common/ir-keymaps.c   Fri Nov 13 09:40:40 2009 +0100
@@ -3303,3 +3303,51 @@
.size = ARRAY_SIZE(ir_codes_gadmei_rm008z),
 };
 EXPORT_SYMBOL_GPL(ir_codes_gadmei_rm008z_table);
+
+/* Leadtek Winfast TV USB II Deluxe remote
+   Magnus Alm 
+ */
+static struct ir_scancode ir_codes_winfast_usbii_deluxe[] = {
+   { 0x62, KEY_0},
+   { 0x75, KEY_1},
+   { 0x76, KEY_2},
+   { 0x77, KEY_3},
+   { 0x79, KEY_4},
+   { 0x7a, KEY_5},
+   { 0x7b, KEY_6},
+   { 0x7d, KEY_7},
+   { 0x7e, KEY_8},
+   { 0x7f, KEY_9},
+
+   { 0x38, KEY_CAMERA},/* SNAPSHOT */
+   { 0x37, KEY_RECORD},/* RECORD */
+   { 0x35, KEY_TIME},  /* TIMESHIFT */
+
+   { 0x74, KEY_VOLUMEUP},  /* VOLUMEUP */
+   { 0x78, KEY_VOLUMEDOWN},/* VOLUMEDOWN */
+   { 0x64, KEY_MUTE},  /* MUTE */
+
+   { 0x21, KEY_CHANNEL},   /* SURF */
+   { 0x7c, KEY_CHANNELUP}, /* CHANNELUP */
+   { 0x60, KEY_CHANNELDOWN},   /* CHANNELDOWN */
+   { 0x61, KEY_LAST},  /* LAST CHANNEL (RECALL) */
+
+   { 0x72, KEY_VIDEO}, /* INPUT MODES (TV/FM) */
+
+   { 0x70, KEY_POWER2},/* TV ON/OFF */
+
+   { 0x39, KEY_CYCLEWINDOWS},  /* MINIMIZE (BOSS) */
+   { 0x3a, KEY_NEW},   /* PIP */
+   { 0x73, KEY_ZOOM},  /* FULLSECREEN */
+
+   { 0x66, KEY_INFO},  /* OSD (DISPLAY) */ 
+
+   { 0x31, KEY_DOT},   /* '.' */
+   { 0x63, KEY_ENTER}, /* ENTER */
+
+};
+struct ir_scancode_table ir_codes_winfast_usbii_deluxe_table = {
+   .scan = ir_codes_winfast_usbii_deluxe,
+   .size = ARRAY_SIZE(ir_codes_winfast_usbii_deluxe),
+};
+EXPORT_SYMBOL_GPL(ir_codes_winfast_usbii_deluxe_table);
diff -r 19c0469c02c3 linux/drivers/media/video/em28xx/em28xx-cards.c
--- a/linux/drivers/media/video/em28xx/em28xx-cards.c   Sat Nov 07
15:51:01 2009 -0200
+++ b/linux/drivers/media/video/em28xx/em28xx-cards.c   Fri Nov 13
09:40:40 2009 +0100
@@ -466,21 +466,30 @@
.name = "Leadtek Winfast USB II Deluxe",
.valid= EM28XX_BOARD_NOT_VALIDATED,
.tuner_type   = TUNER_PHILIPS_FM1216ME_MK3,
-   .tda9887_conf = TDA9887_PRESENT,
+   .has_ir_i2c   = 1,
+   .tvaudio_addr = 0x58,
+   .tda9887_conf = TDA9887_PRESENT |
+   TDA9887_PORT2_ACTIVE |
+   TDA9887_QSS,
.decoder  = EM28XX_SAA711X,
+   .adecoder = EM28XX_TVAUDIO,
.input= { {
.type = EM28XX_VMUX_TELEVISION,
-   .vmux = SAA7115_COMPOSITE2,
-   .amux = EM28XX_AMUX_VIDEO,
+   .vmux = SAA7115_COMPOSITE4,
+   .amux = EM28XX_AMUX_AUX,
}, {
.type = EM28XX_VMUX_COMPOSITE1,
-   .vmux = SAA7115_COMPOSITE0,
+   .vmux = SAA7115_COMPOSITE5,
.amux = EM28XX_AMUX_LINE_IN,
}, {
.type = EM28XX_VMUX_SVIDEO,
-   .vmux = SAA7115_COMPOSITE0,
+   .vmux = SAA7115_SVIDEO3,
.amux = EM28XX_AMUX_LINE_IN,
} },
+   .radio= {
+   .type = EM28XX_RADIO,
+   .amux = EM28XX_AMUX_AUX,
+   }
},
[EM2820_BOARD_VIDEOLOGY_20K14XUSB] = {
.name = "Videology 20K14XUSB USB2.0",
@@ -2309,9 +2318,12 @@
return;
}
 #else
+   /* Leadtek winfast tv USBII deluxe can find a non working IR-device */
+   /* at address 0x18, so if that address is needed for another board in */
+   /* the future, please put it after 0x1f. */
struct i2c_board_info info;
const unsigned short addr_list[] = {
-0x30, 0x47, I2C_CLIENT_END
+0x1f, 0x30, 0x47, I2C_CLIENT_END   
};

if (disable_ir)
@@ -2361,6 +2373,18 @@
dev->init_data.name = "i2c IR (EM2840 Hauppauge)";
 #endif
break;
+   case EM2820_BOARD_LEADTEK_WINFAST_USBII_DELUXE:
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 30)
+   ir->ir_codes = &ir_codes_winfast_usbii

Re: em28xx based USB Hybrid (Analog & DVB-T) TV Tuner not supported

2009-11-07 Thread Magnus Alm
I think your stick has more in common with
EM2881_BOARD_DNT_DA2_HYBRID, dvb support hasn't been enabled for that
tuner yet tho, only analog..

If you look at pdf for the  utvhyl3 (seems like they removed the
utvhyl2) http://idream.com.hk/consulter.php?pid=120&tab=6
And compares it with the DNT DA2 ,
http://www.dnt.de/neu/data/download/files/110/Prospekt%20-%20DA2%20Hybrid.pdf
 (only avalible in german tho)
They even seem to have the same remote (doesn't mean they are identical tho.)

/Magnus Alm

2009/11/7 Magnus Alm :
> Well, maybe you where more right than me...
>
> From em28xx-dvb.c
>
>        case EM2880_BOARD_TERRATEC_HYBRID_XS:
>        case EM2881_BOARD_PINNACLE_HYBRID_PRO:
>                dvb->frontend = dvb_attach(zl10353_attach,
>                                           &em28xx_zl10353_xc3028_no_i2c_gate,
>                                           &dev->i2c_adap);
>                if (dvb->frontend == NULL) {
>                        /* This board could have either a zl10353 or a mt352.
>                           If the chip id isn't for zl10353, try mt352 */
>                        dvb->frontend = dvb_attach(mt352_attach,
>                                                   &terratec_xs_mt352_cfg,
>                                                   &dev->i2c_adap);
>                }
>
>
> 2009/11/7 Magnus Alm :
>> Hi
>>
>> I read some where that trying different card types for a DVB tuner can
>> potentially cause damage to them.
>>
>> You are probably right about the firmare.
>> Do you have a link to the manufacture of your stick?
>> I tried to google the name of it but couldn't found an exact match.
>>
>> The EM2881_BOARD_PINNACLE_HYBRID_PRO uses it's XC3028 to getter with a
>> ZARLINK456
>> as you can see from the following line in em28xx-cards.c
>>
>> case EM2881_BOARD_PINNACLE_HYBRID_PRO:
>>                ctl->demod = XC3028_FE_ZARLINK456;
>>                break;
>>
>> It is probably not compliant with your  Zarlink MT352.
>>
>> There is a mt352 module tho, but I guess it doesn't get loaded when
>> you plug your stick in.
>>
>> I'll pooke around a bit.
>>
>> PS
>> Use the "reply all", so others can see your mails, since I'm probably
>> one of the least competent guys/gals on this mailing list.
>> DS
>>
>>
>>
>> 2009/11/7 Johan Mutsaerts :
>>> Hi Magnus,
>>>
>>> Thanks for a quick reply. Here is some more detailed information:
>>>
>>> My USB device ID is 0xeb1a:0x2881 it is eMPIA based.
>>>
>>> These are the components inside
>>> - Empia EM2880
>>> - Texas Instruments 5150AM1
>>> - XCeive XC3028
>>> - Empia EMP202
>>> - Zarlink MT352
>>>
>>> Difficult for me to get to the windows stuff
>>>
>>> No /dev/dvb/ is generated ? Could it have something to do with no 
>>> Firmware ?
>>>
>>> I found my device to be quite similar to the Pinnacle Hybrid Pro so I tried
>>> sudo rmmod em28xx-dvb
>>> sudo rmmod em28xx-alsa
>>> sudo rmmod em28xx
>>> sudo modprobe em28xx card=53 and card=56
>>> sudo modprobe em28xx-alsa
>>> sudo modprobe em28xx-dvb
>>> However with not much success.
>>> Card=53 cased MeTV to see a tuner but no channels could be found
>>>
>>> TIA for any assistance you can provide.
>>>
>>> Best Regards,
>>> Johan
>>>
>>> 2009/11/7 Magnus Alm :
>>>> Hi!
>>>>
>>>> The dmesg didn't reveal what tuner your stick/card has, it's probably
>>>> a XC2028/XC3028 or something like that.
>>>> Easiest way to find out would be if you could open the cover and have
>>>> a look inside.
>>>>
>>>> If you have access to windows and the pvr program that came with the
>>>> tuner you could do a usb-sniff.
>>>>
>>>> http://www.pcausa.com/Utilities/UsbSnoop/
>>>> or
>>>> http://benoit.papillault.free.fr/usbsnoop/
>>>>
>>>> Switch between different inputs while doing the log, like "dvb",
>>>> "analog" and if it has "svideo"/"composite" input.
>>>>
>>>> copy the windows log to unix and parse the output with parser.pl (I've
>>>> added is as an attachment.)
>>>> I think there is a new parser somewhere, but I forgot the name of it.
>>>>
>>>> I'm a

Re: em28xx based USB Hybrid (Analog & DVB-T) TV Tuner not supported

2009-11-07 Thread Magnus Alm
Well, maybe you where more right than me...

>From em28xx-dvb.c

case EM2880_BOARD_TERRATEC_HYBRID_XS:
case EM2881_BOARD_PINNACLE_HYBRID_PRO:
dvb->frontend = dvb_attach(zl10353_attach,
   &em28xx_zl10353_xc3028_no_i2c_gate,
   &dev->i2c_adap);
if (dvb->frontend == NULL) {
/* This board could have either a zl10353 or a mt352.
   If the chip id isn't for zl10353, try mt352 */
dvb->frontend = dvb_attach(mt352_attach,
   &terratec_xs_mt352_cfg,
   &dev->i2c_adap);
    }


2009/11/7 Magnus Alm :
> Hi
>
> I read some where that trying different card types for a DVB tuner can
> potentially cause damage to them.
>
> You are probably right about the firmare.
> Do you have a link to the manufacture of your stick?
> I tried to google the name of it but couldn't found an exact match.
>
> The EM2881_BOARD_PINNACLE_HYBRID_PRO uses it's XC3028 to getter with a
> ZARLINK456
> as you can see from the following line in em28xx-cards.c
>
> case EM2881_BOARD_PINNACLE_HYBRID_PRO:
>                ctl->demod = XC3028_FE_ZARLINK456;
>                break;
>
> It is probably not compliant with your  Zarlink MT352.
>
> There is a mt352 module tho, but I guess it doesn't get loaded when
> you plug your stick in.
>
> I'll pooke around a bit.
>
> PS
> Use the "reply all", so others can see your mails, since I'm probably
> one of the least competent guys/gals on this mailing list.
> DS
>
>
>
> 2009/11/7 Johan Mutsaerts :
>> Hi Magnus,
>>
>> Thanks for a quick reply. Here is some more detailed information:
>>
>> My USB device ID is 0xeb1a:0x2881 it is eMPIA based.
>>
>> These are the components inside
>> - Empia EM2880
>> - Texas Instruments 5150AM1
>> - XCeive XC3028
>> - Empia EMP202
>> - Zarlink MT352
>>
>> Difficult for me to get to the windows stuff
>>
>> No /dev/dvb/ is generated ? Could it have something to do with no 
>> Firmware ?
>>
>> I found my device to be quite similar to the Pinnacle Hybrid Pro so I tried
>> sudo rmmod em28xx-dvb
>> sudo rmmod em28xx-alsa
>> sudo rmmod em28xx
>> sudo modprobe em28xx card=53 and card=56
>> sudo modprobe em28xx-alsa
>> sudo modprobe em28xx-dvb
>> However with not much success.
>> Card=53 cased MeTV to see a tuner but no channels could be found
>>
>> TIA for any assistance you can provide.
>>
>> Best Regards,
>> Johan
>>
>> 2009/11/7 Magnus Alm :
>>> Hi!
>>>
>>> The dmesg didn't reveal what tuner your stick/card has, it's probably
>>> a XC2028/XC3028 or something like that.
>>> Easiest way to find out would be if you could open the cover and have
>>> a look inside.
>>>
>>> If you have access to windows and the pvr program that came with the
>>> tuner you could do a usb-sniff.
>>>
>>> http://www.pcausa.com/Utilities/UsbSnoop/
>>> or
>>> http://benoit.papillault.free.fr/usbsnoop/
>>>
>>> Switch between different inputs while doing the log, like "dvb",
>>> "analog" and if it has "svideo"/"composite" input.
>>>
>>> copy the windows log to unix and parse the output with parser.pl (I've
>>> added is as an attachment.)
>>> I think there is a new parser somewhere, but I forgot the name of it.
>>>
>>> I'm also not sure how I used it, but I think it was like this: perl
>>> parser.pl < "your_windows_log" > "parsed_log"
>>> That log is needed to  find out what "gpio" your tuner needs for
>>> different settings.
>>>
>>> Don't be scared of the size of the windows log, it gets large, often a
>>> few hundred MB.
>>> The parsed log is much smaller,  a few hundred KB.
>>>
>>> That is all I can think about atm.
>>>
>>> /Magnus Alm
>>>
>>>
>>> 2009/11/6 Johan Mutsaerts :
>>>> Hi,
>>>>
>>>> I have an iDream UTVHYL2 USB TV Tuner (with IR remote control) that I
>>>> cannot get to work with Ubuntu (9.04, 2.6.28-16). I have successfully
>>>> compiled and installed the em28xx-new driver from linuxtv.org. No
>>>> /dev/dvb/adapter... is created and that is where it ends for me know.
>>>> MyTV claims no adapter is detected.
>>>>
>>>> I have attached the output of lsusb and dmesg as requested...
>>>>
>>>> Please let me know what more I can do and what exactly it is you can do ?
>>>>
>>>> Thanks in advance and
>>>> Best Regards,
>>>> Johan (Belgium)
>>>>
>>>
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: em28xx based USB Hybrid (Analog & DVB-T) TV Tuner not supported

2009-11-07 Thread Magnus Alm
Hi

I read some where that trying different card types for a DVB tuner can
potentially cause damage to them.

You are probably right about the firmare.
Do you have a link to the manufacture of your stick?
I tried to google the name of it but couldn't found an exact match.

The EM2881_BOARD_PINNACLE_HYBRID_PRO uses it's XC3028 to getter with a
ZARLINK456
as you can see from the following line in em28xx-cards.c

case EM2881_BOARD_PINNACLE_HYBRID_PRO:
ctl->demod = XC3028_FE_ZARLINK456;
break;

It is probably not compliant with your  Zarlink MT352.

There is a mt352 module tho, but I guess it doesn't get loaded when
you plug your stick in.

I'll pooke around a bit.

PS
Use the "reply all", so others can see your mails, since I'm probably
one of the least competent guys/gals on this mailing list.
DS



2009/11/7 Johan Mutsaerts :
> Hi Magnus,
>
> Thanks for a quick reply. Here is some more detailed information:
>
> My USB device ID is 0xeb1a:0x2881 it is eMPIA based.
>
> These are the components inside
> - Empia EM2880
> - Texas Instruments 5150AM1
> - XCeive XC3028
> - Empia EMP202
> - Zarlink MT352
>
> Difficult for me to get to the windows stuff
>
> No /dev/dvb/ is generated ? Could it have something to do with no 
> Firmware ?
>
> I found my device to be quite similar to the Pinnacle Hybrid Pro so I tried
> sudo rmmod em28xx-dvb
> sudo rmmod em28xx-alsa
> sudo rmmod em28xx
> sudo modprobe em28xx card=53 and card=56
> sudo modprobe em28xx-alsa
> sudo modprobe em28xx-dvb
> However with not much success.
> Card=53 cased MeTV to see a tuner but no channels could be found
>
> TIA for any assistance you can provide.
>
> Best Regards,
> Johan
>
> 2009/11/7 Magnus Alm :
>> Hi!
>>
>> The dmesg didn't reveal what tuner your stick/card has, it's probably
>> a XC2028/XC3028 or something like that.
>> Easiest way to find out would be if you could open the cover and have
>> a look inside.
>>
>> If you have access to windows and the pvr program that came with the
>> tuner you could do a usb-sniff.
>>
>> http://www.pcausa.com/Utilities/UsbSnoop/
>> or
>> http://benoit.papillault.free.fr/usbsnoop/
>>
>> Switch between different inputs while doing the log, like "dvb",
>> "analog" and if it has "svideo"/"composite" input.
>>
>> copy the windows log to unix and parse the output with parser.pl (I've
>> added is as an attachment.)
>> I think there is a new parser somewhere, but I forgot the name of it.
>>
>> I'm also not sure how I used it, but I think it was like this: perl
>> parser.pl < "your_windows_log" > "parsed_log"
>> That log is needed to  find out what "gpio" your tuner needs for
>> different settings.
>>
>> Don't be scared of the size of the windows log, it gets large, often a
>> few hundred MB.
>> The parsed log is much smaller,  a few hundred KB.
>>
>> That is all I can think about atm.
>>
>> /Magnus Alm
>>
>>
>> 2009/11/6 Johan Mutsaerts :
>>> Hi,
>>>
>>> I have an iDream UTVHYL2 USB TV Tuner (with IR remote control) that I
>>> cannot get to work with Ubuntu (9.04, 2.6.28-16). I have successfully
>>> compiled and installed the em28xx-new driver from linuxtv.org. No
>>> /dev/dvb/adapter... is created and that is where it ends for me know.
>>> MyTV claims no adapter is detected.
>>>
>>> I have attached the output of lsusb and dmesg as requested...
>>>
>>> Please let me know what more I can do and what exactly it is you can do ?
>>>
>>> Thanks in advance and
>>> Best Regards,
>>> Johan (Belgium)
>>>
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Patch for "Leadtek Winfast TV USB II Deluxe" (with IR)

2009-10-29 Thread Magnus Alm
Hi!

I managed to get the remote working now in both in Ubuntu 9.04 (kernel
2.6.28-16) and Ubuntu 9.10 (kernel 2.6.31-14).

There is one difference tho, in the 2.6.28-16 kernel the remote
doesn't do anything without configuring lirc.
In 2.6.31-14 I can for example adjust volume in X and use the numeric
keys to change channels in tvtime without lirc.
Don't know why, it just works like that.

I've added 3 different examples for a patch as attachment, since the
remote can be enabled different ways.
(They also changes the basic config for my board.)

ex1.patch only works for kernel 2.6.31.

ex2.patch works for both 2.6.31 and 2.6.28 but can in the future cause
problems for boards that would like to use adress 0x1f (0x3e) for IR.
(Because of the "case 0x1f" for my board.)

ex3.patch is a combination of ex1 and ex2. where it is depending on if
kernel version is higher or lower than 2.6.30.

Dunno which one that would be most suitable.

Another thing is that my board finds an IR device at 0x18 (0x30), but
ir-polling doesn't work at that address, so if any board in the future
needs that added
0x1f needs to stand before 0x18.
This is for the funtion in em28xx-cards if kernel higher than 2.6.30:

const unsigned short addr_list[] = {
 0x1f, 0x30, 0x47, I2C_CLIENT_END   
};

or in  ir-kbd-i2c for kernel lower than 2.6.30:

static const int probe_em28XX[] = { 0x1f, 0x30, 0x47, -1 };


I guess you also might have objections in how I'm naming stuff like
"get_key_lwtu2d", maybe it's a bit obscure...


/Magnus Alm
--- org/v4l-dvb/linux/include/media/ir-common.h	2009-10-29 13:03:42.515061680 +0100
+++ ex1/v4l-dvb/linux/include/media/ir-common.h	2009-10-26 12:00:00.0 +0100
@@ -179,4 +179,5 @@
 extern struct ir_scancode_table ir_codes_terratec_cinergy_xs_table;
 extern struct ir_scancode_table ir_codes_videomate_s350_table;
 extern struct ir_scancode_table ir_codes_gadmei_rm008z_table;
+extern struct ir_scancode_table ir_codes_lwtu2d_table;
 #endif
--- org/v4l-dvb/linux/drivers/media/common/ir-keymaps.c	2009-10-29 13:03:41.525062396 +0100
+++ ex1/v4l-dvb/linux/drivers/media/common/ir-keymaps.c	2009-10-27 16:51:08.267566000 +0100
@@ -3302,3 +3302,42 @@
 	.size = ARRAY_SIZE(ir_codes_gadmei_rm008z),
 };
 EXPORT_SYMBOL_GPL(ir_codes_gadmei_rm008z_table);
+
+static struct ir_scancode ir_codes_lwtu2d[] = {
+	{ 0x70, KEY_POWER2},		/* POWER OFF*/
+	{ 0x72, KEY_MODE}, 		/* TV/FM */
+	{ 0x21, KEY_CHANNEL},		/* CHANNEL SURF */
+	{ 0x73, KEY_ZOOM},		/* FULLSECREEN */
+	{ 0x39, KEY_CLOSE},		/* MINIMIZE */
+	{ 0x66, KEY_INFO},		/* DISPLAY */
+	{ 0x61, KEY_PREVIOUS},		/* RECALL */
+	{ 0x64, KEY_MUTE},		/* MUTE */
+	
+	{ 0x75, KEY_1},
+	{ 0x76, KEY_2},
+	{ 0x77, KEY_3},
+	{ 0x79, KEY_4},
+	{ 0x7a, KEY_5},
+	{ 0x7b, KEY_6},
+	{ 0x7d, KEY_7},
+	{ 0x7e, KEY_8},
+	{ 0x7f, KEY_9},
+	{ 0x62, KEY_0},
+	{ 0x31, KEY_DOT},		/* '.' */
+	{ 0x63, KEY_ENTER},		/* ENTER */
+
+	{ 0x35, KEY_TIME},		/* TIMESHIFT */
+	{ 0x38, KEY_CAMERA},		/* SNAPSHOT */
+	{ 0x37, KEY_RECORD},		/* RECORD */
+	{ 0x3a, KEY_TV2},		/* PIP */
+
+	{ 0x74, KEY_VOLUMEUP},		/* VOLUMEUP */
+	{ 0x78, KEY_VOLUMEDOWN},	/* VOLUMEDOWN */
+	{ 0x7c, KEY_CHANNELUP},		/* CHANNELUP */
+	{ 0x60, KEY_CHANNELDOWN},	/* CHANNELDOWN */
+};
+struct ir_scancode_table ir_codes_lwtu2d_table = {
+	.scan = ir_codes_lwtu2d,
+	.size = ARRAY_SIZE(ir_codes_lwtu2d),
+};
+EXPORT_SYMBOL_GPL(ir_codes_lwtu2d_table);
--- org/v4l-dvb/linux/drivers/media/video/ir-kbd-i2c.c	2009-10-29 13:03:42.155062472 +0100
+++ ex1/v4l-dvb/linux/drivers/media/video/ir-kbd-i2c.c	2009-10-29 13:28:02.705063253 +0100
@@ -416,6 +416,7 @@
 		ir_codes= &ir_codes_pv951_table;
 		break;
 	case 0x18:
+	case 0x1f:
 	case 0x1a:
 		name= "Hauppauge";
 		ir->get_key = get_key_haup;
--- org/v4l-dvb/linux/drivers/media/video/em28xx/em28xx-cards.c	2009-10-29 13:03:42.045061311 +0100
+++ ex1/v4l-dvb/linux/drivers/media/video/em28xx/em28xx-cards.c	2009-10-29 13:48:43.285519588 +0100
@@ -466,22 +466,31 @@
 		.name = "Leadtek Winfast USB II Deluxe",
 		.valid= EM28XX_BOARD_NOT_VALIDATED,
 		.tuner_type   = TUNER_PHILIPS_FM1216ME_MK3,
-		.tda9887_conf = TDA9887_PRESENT,
+		.has_ir_i2c   = 1,
+		.tvaudio_addr = 0x58,	
+		.tda9887_conf = TDA9887_PRESENT |
+TDA9887_PORT2_ACTIVE |
+TDA9887_QSS,
 		.decoder  = EM28XX_SAA711X,
-		.input= { {
+		.adecoder = EM28XX_TVAUDIO,
+  		.input= { {
 			.type = EM28XX_VMUX_TELEVISION,
-			.vmux = SAA7115_COMPOSITE2,
-			.amux = EM28XX_AMUX_VIDEO,
-		}, {
+			.vmux = SAA7115_COMPOSITE4,
+			.amux = EM28XX_AMUX_AUX,
+  		}, {
 			.type = EM28XX_VMUX_COMPOSITE1,
-			.vmux = SAA7115_COMPOSITE0,
+			.vmux = SAA7115_COMPOSITE5,
 			.amux = EM28XX_AMUX_LINE_IN,
-		}, {
+  		}, {
 			.type = EM28XX_VMUX_SVIDEO,
-			.vmux = SAA7115_COMPOSITE0,
+			.vmux = SAA7

Re: Almost got remote working with my "Winfast tv usb II Deluxe" box

2009-10-25 Thread Magnus Alm
Hm, it works better with the 64bit AMD version.

2009/10/25 Magnus Alm :
> Hi!
>
> This is on Ubuntu 9.04, kernel 2.6.28-16.
> I get the following in dmesg when pressing channel down on my remote:
>
> [ 3517.984559] : unknown key: key=0x90 raw=0x90 down=1
> [ 3518.096558] : unknown key: key=0x90 raw=0x90 down=0
>
> That should correspond with the following row in my keytable in ir-keymaps:
>
>        { 0x90, KEY_CHANNELDOWN},       /* CHANNELDOWN */
>
>
> Do I need to configure lirc also?
> But since something responds (ir-common ?) to my pressing on the
> remote I thought it shouldn't be necessary.
>
> /Magnus
>
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Almost got remote working with my "Winfast tv usb II Deluxe" box

2009-10-25 Thread Magnus Alm
Hi!

This is on Ubuntu 9.04, kernel 2.6.28-16.
I get the following in dmesg when pressing channel down on my remote:

[ 3517.984559] : unknown key: key=0x90 raw=0x90 down=1
[ 3518.096558] : unknown key: key=0x90 raw=0x90 down=0

That should correspond with the following row in my keytable in ir-keymaps:

{ 0x90, KEY_CHANNELDOWN},   /* CHANNELDOWN */


Do I need to configure lirc also?
But since something responds (ir-common ?) to my pressing on the
remote I thought it shouldn't be necessary.

/Magnus
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: More about "Winfast TV USB Deluxe"

2009-10-20 Thread Magnus Alm
I tested the same config on my laptop instead, Ubuntu 9.04 (kernel
2.6.28-15-generic).
On the other PC I have Ubuntu 9.10 (kernel 2.6.31.xx  -generic can't
remember the last two digits.), where no scan happens.

On the laptop, ir-kbd-i2c at least scanned for ir devices.

[ 2362.20] ir-kbd-i2c: probe 0x30 @ em28xx #0: no
[ 2362.446045] ir-kbd-i2c: probe 0x3e @ em28xx #0: no
[ 2362.446416] ir-kbd-i2c: probe 0x47 @ em28xx #0: no

I went back to windows and ran some more usb sniffs.

When the tuner is just plugged in, I get the output you can view in
the attached file "plugged_in.txt"
It looks as if the box runs a initialization sequence internally, I
don't know if this is initialized by the windows driver or by the box
itself.

When I start the winfast pvr program the first things that appears
after the initialization is this.

000236:  OUT: 00 ms 107655 ms c0 00 00 00 08 00 01 00 <<<  ff
000237:  OUT: 00 ms 107655 ms c0 00 00 00 09 00 01 00 <<<  af
000238:  OUT: 01 ms 107655 ms 40 00 00 00 08 00 01 00 >>>  af
000239:  OUT: 00 ms 107656 ms 40 02 00 00 3e 00 02 00 >>>  02 00
000240:  OUT: 00 ms 107656 ms c0 00 00 00 05 00 01 00 <<<  00
000241:  OUT: 00 ms 107656 ms 40 02 00 00 3e 00 02 00 >>>  04 00
000242:  OUT: 01 ms 107656 ms c0 00 00 00 05 00 01 00 <<<  00
000243:  OUT: 00 ms 107657 ms 40 02 00 00 3e 00 02 00 >>>  03 ff
000244:  OUT: 00 ms 107657 ms c0 00 00 00 05 00 01 00 <<<  00
000245:  OUT: 01 ms 107657 ms 40 03 00 00 3e 00 01 00 >>>  10
<- Looks as IR polling to me.
000246:  OUT: 00 ms 107658 ms c0 00 00 00 05 00 01 00 <<<  00<-
000247:  OUT: 00 ms 107658 ms c0 02 00 00 3e 00 01 00 <<<  00<-
000248:  OUT: 01 ms 107658 ms c0 00 00 00 05 00 01 00 <<<  00<-
000249:  OUT: 00 ms 107659 ms 40 02 00 00 86 00 04 00 >>>  00 6a 90 20
000250:  OUT: 000961 ms 107659 ms c0 00 00 00 05 00 01 00 <<<  00
000251:  OUT: 00 ms 108620 ms 40 03 00 00 3e 00 01 00 >>>  10
000252:  OUT: 00 ms 108620 ms c0 00 00 00 05 00 01 00 <<<  00
000253:  OUT: 00 ms 108620 ms c0 02 00 00 3e 00 01 00 <<<  00
000254:  OUT: 005580 ms 108620 ms c0 00 00 00 05 00 01 00 <<<  00
000255:  OUT: 01 ms 114200 ms 40 03 00 00 3e 00 01 00 >>>  10
000256:  OUT: 00 ms 114201 ms c0 00 00 00 05 00 01 00 <<<  00
000257:  OUT: 00 ms 114201 ms c0 02 00 00 3e 00 01 00 <<<  00
000258:  OUT: 000176 ms 114201 ms c0 00 00 00 05 00 01 00 <<<  00
000259:  OUT: 00 ms 114377 ms 40 03 00 00 3e 00 01 00 >>>  10
000260:  OUT: 01 ms 114377 ms c0 00 00 00 05 00 01 00 <<<  00
000261:  OUT: 00 ms 114378 ms c0 02 00 00 3e 00 01 00 <<<  00
000262:  OUT: 000251 ms 114378 ms c0 00 00 00 05 00 01 00 <<<  00
And so on


When pressing a button on my remote, rows like this appears in pairs:

007268:  OUT: 01 ms 416915 ms c0 02 00 00 3e 00 01 00 <<<  80
007272:  OUT: 00 ms 416920 ms c0 02 00 00 3e 00 01 00 <<<  88


I have a theory that Leadtek took another approach for the remote
handling on my box.
There is a em78p153 micro processor (with a rom), I think it's that
that shows up as an eeprom in dmesg when the em28xx module is loaded.

So my theory is that the em78p153 is handling all input from the
remote internally after the polling is started by the pvr program with
this sequence:

000239:  OUT: 00 ms 107656 ms 40 02 00 00 3e 00 02 00 >>>  02 00
000241:  OUT: 00 ms 107656 ms 40 02 00 00 3e 00 02 00 >>>  04 00
000243:  OUT: 00 ms 107657 ms 40 02 00 00 3e 00 02 00 >>>  03 ff

Or maybe the pvr program handles the polling too.

I could be wrong...

Now I just need to figure out how too test this somehow...
(hints on how to are appreciated.)

/Magnus

2009/10/18 Magnus Alm :
> Hi again.
>
> Started to look at getting the remote to work also.
> I used "Terratec Cinergy 250 USB" as template and added the needed
> information in:
>
> em28xx-cards.c
> em28xx.h
> em28xx-input.c
> ir-common.h
> ir-keymaps.c
>
> Compiled it with: make, make install and rebooted.
>
> But it seems that I've missed something since ir-kbd-i2c loads, but it
> doesn't seem to look for any ir devices.
> Tried loading ir-kbd-i2c with debug=1, but not even an error message
> shows up in dmesg, it looks just as before.
>
> What I've added in the files is in a text file attachment.
>
> The keymap I added is just garabage and the polling structure in
> em28xx is probably wrong too.
> But I have to start somewhere.
>
> /Magnus
>
>
>
> 2009/10/15 Magnus Alm :
>> yay
>>
>> [ 2478.224015] tda9887 4-0043: configure for: Radio Stereo
>

Re: More about "Winfast TV USB Deluxe"

2009-10-18 Thread Magnus Alm
Hi again.

Started to look at getting the remote to work also.
I used "Terratec Cinergy 250 USB" as template and added the needed
information in:

em28xx-cards.c
em28xx.h
em28xx-input.c
ir-common.h
ir-keymaps.c

Compiled it with: make, make install and rebooted.

But it seems that I've missed something since ir-kbd-i2c loads, but it
doesn't seem to look for any ir devices.
Tried loading ir-kbd-i2c with debug=1, but not even an error message
shows up in dmesg, it looks just as before.

What I've added in the files is in a text file attachment.

The keymap I added is just garabage and the polling structure in
em28xx is probably wrong too.
But I have to start somewhere.

/Magnus



2009/10/15 Magnus Alm :
> yay
>
> [ 2478.224015] tda9887 4-0043: configure for: Radio Stereo
> [ 2478.224017] tda9887 4-0043: writing: b=0xcc c=0x90 e=0x3d
>
> /Magnus
>
> 2009/10/15 Magnus Alm :
>> Strange, but changeing the tvaudio_addr = 0xb0 to 88, (half of the
>> decimal value of b0) made tvaudio find my tda9874.
>>
>> [ 1186.725140] tvaudio: TV audio decoder + audio/video mux driver
>> [ 1186.725142] tvaudio: known chips: tda9840, tda9873h, tda9874h/a/ah,
>> tda9875, tda9850, tda9855, tea6300, tea6320, tea6420, tda8425,
>> pic16c54 (PV951), ta8874z
>> [ 1186.725151] tvaudio 4-0058: chip found @ 0xb0
>> [ 1186.736444] tvaudio 4-0058: chip_read2: reg254=0x11
>> [ 1186.749704] tvaudio 4-0058: chip_read2: reg255=0x2
>> [ 1186.749708] tvaudio 4-0058: tda9874a_checkit(): DIC=0x11, SIC=0x2.
>> [ 1186.749710] tvaudio 4-0058: found tda9874a.
>> [ 1186.749712] tvaudio 4-0058: tda9874h/a/ah found @ 0xb0 (em28xx #0)
>> [ 1186.749714] tvaudio 4-0058: matches:.
>> [ 1186.749716] tvaudio 4-0058: chip_write: reg0=0x0
>> [ 1186.760012] tvaudio 4-0058: chip_write: reg1=0xc0
>> [ 1186.772014] tvaudio 4-0058: chip_write: reg2=0x2
>> [ 1186.784013] tvaudio 4-0058: chip_write: reg11=0x80
>> [ 1186.796010] tvaudio 4-0058: chip_write: reg12=0x0
>> [ 1186.808013] tvaudio 4-0058: chip_write: reg13=0x0
>> [ 1186.820012] tvaudio 4-0058: chip_write: reg14=0x1
>> [ 1186.832015] tvaudio 4-0058: chip_write: reg15=0x0
>> [ 1186.844012] tvaudio 4-0058: chip_write: reg16=0x14
>> [ 1186.856018] tvaudio 4-0058: chip_write: reg17=0x50
>> [ 1186.868011] tvaudio 4-0058: chip_write: reg18=0xf9
>> [ 1186.880745] tvaudio 4-0058: chip_write: reg19=0x80
>> [ 1186.892347] tvaudio 4-0058: chip_write: reg20=0x80
>> [ 1186.904015] tvaudio 4-0058: chip_write: reg24=0x80
>> [ 1186.916011] tvaudio 4-0058: chip_write: reg255=0x0
>> [ 1186.928021] tvaudio 4-0058: tda9874a_setup(): A2, B/G [0x00].
>> [ 1186.928091] tvaudio 4-0058: thread started
>>
>> Now I probably need to set some gpio's too
>>
>> /Magnus
>>
>> 2009/10/14 Magnus Alm :
>>> Loaded em28xx with i2c_scan and i2c_debug and tvaudio with tda9874a
>>> option and debug.
>>>
>>> sudo modprobe -v em28xx i2c_scan=1 i2c_debug=1
>>> sudo modprobe -v tvaudio tda9874a=1 debug=1
>>>
>>> And got this ouput:
>>>
>>> [91083.588182] em28xx #0: found i2c device @ 0x30 [???]
>>> [91083.590179] em28xx #0: found i2c device @ 0x3e [???]
>>> [91083.590804] em28xx #0: found i2c device @ 0x42 [???]
>>> [91083.600308] em28xx #0: found i2c device @ 0x86 [tda9887]
>>> [91083.603805] em28xx #0: found i2c device @ 0xa0 [eeprom]
>>> [91083.606183] em28xx #0: found i2c device @ 0xb0 [tda9874]
>>> [91083.608808] em28xx #0: found i2c device @ 0xc2 [tuner (analog)]
>>> [91083.617682] em28xx #0: Identified as Leadtek Winfast USB II Deluxe 
>>> (card=28)
>>> [91083.617684] em28xx #0:
>>> [91083.617684]
>>> [91083.617687] em28xx #0: The support for this board weren't valid yet.
>>> [91083.617688] em28xx #0: Please send a report of having this working
>>> [91083.617690] em28xx #0: not to V4L mailing list (and/or to other 
>>> addresses)
>>> [91083.617691]
>>> [91083.980702] saa7115 4-0021: saa7114 found (1f7114d0e00) @ 0x42
>>> (em28xx #0)
>>> [91086.173114] tvaudio: TV audio decoder + audio/video mux driver
>>> [91086.173116] tvaudio: known chips: tda9840, tda9873h, tda9874h/a/ah,
>>> tda9875, tda9850, tda9855, tea6300, tea6320, tea6420, tda8425,
>>> pic16c54 (PV951), ta8874z
>>> [91086.173125] tvaudio 4-00b0: chip found @ 0x160
>>> [91086.173127] tvaudio 4-00b0: no matching chip description found
>>> [91086.173131] tvaudio: probe of 4-00b0 failed with error -5
>>>
>>>
>>> It seems to be a tda9874 there -> em28xx #0: found i2c device @ 0

Re: More about "Winfast TV USB Deluxe"

2009-10-15 Thread Magnus Alm
yay

[ 2478.224015] tda9887 4-0043: configure for: Radio Stereo
[ 2478.224017] tda9887 4-0043: writing: b=0xcc c=0x90 e=0x3d

/Magnus

2009/10/15 Magnus Alm :
> Strange, but changeing the tvaudio_addr = 0xb0 to 88, (half of the
> decimal value of b0) made tvaudio find my tda9874.
>
> [ 1186.725140] tvaudio: TV audio decoder + audio/video mux driver
> [ 1186.725142] tvaudio: known chips: tda9840, tda9873h, tda9874h/a/ah,
> tda9875, tda9850, tda9855, tea6300, tea6320, tea6420, tda8425,
> pic16c54 (PV951), ta8874z
> [ 1186.725151] tvaudio 4-0058: chip found @ 0xb0
> [ 1186.736444] tvaudio 4-0058: chip_read2: reg254=0x11
> [ 1186.749704] tvaudio 4-0058: chip_read2: reg255=0x2
> [ 1186.749708] tvaudio 4-0058: tda9874a_checkit(): DIC=0x11, SIC=0x2.
> [ 1186.749710] tvaudio 4-0058: found tda9874a.
> [ 1186.749712] tvaudio 4-0058: tda9874h/a/ah found @ 0xb0 (em28xx #0)
> [ 1186.749714] tvaudio 4-0058: matches:.
> [ 1186.749716] tvaudio 4-0058: chip_write: reg0=0x0
> [ 1186.760012] tvaudio 4-0058: chip_write: reg1=0xc0
> [ 1186.772014] tvaudio 4-0058: chip_write: reg2=0x2
> [ 1186.784013] tvaudio 4-0058: chip_write: reg11=0x80
> [ 1186.796010] tvaudio 4-0058: chip_write: reg12=0x0
> [ 1186.808013] tvaudio 4-0058: chip_write: reg13=0x0
> [ 1186.820012] tvaudio 4-0058: chip_write: reg14=0x1
> [ 1186.832015] tvaudio 4-0058: chip_write: reg15=0x0
> [ 1186.844012] tvaudio 4-0058: chip_write: reg16=0x14
> [ 1186.856018] tvaudio 4-0058: chip_write: reg17=0x50
> [ 1186.868011] tvaudio 4-0058: chip_write: reg18=0xf9
> [ 1186.880745] tvaudio 4-0058: chip_write: reg19=0x80
> [ 1186.892347] tvaudio 4-0058: chip_write: reg20=0x80
> [ 1186.904015] tvaudio 4-0058: chip_write: reg24=0x80
> [ 1186.916011] tvaudio 4-0058: chip_write: reg255=0x0
> [ 1186.928021] tvaudio 4-0058: tda9874a_setup(): A2, B/G [0x00].
> [ 1186.928091] tvaudio 4-0058: thread started
>
> Now I probably need to set some gpio's too
>
> /Magnus
>
> 2009/10/14 Magnus Alm :
>> Loaded em28xx with i2c_scan and i2c_debug and tvaudio with tda9874a
>> option and debug.
>>
>> sudo modprobe -v em28xx i2c_scan=1 i2c_debug=1
>> sudo modprobe -v tvaudio tda9874a=1 debug=1
>>
>> And got this ouput:
>>
>> [91083.588182] em28xx #0: found i2c device @ 0x30 [???]
>> [91083.590179] em28xx #0: found i2c device @ 0x3e [???]
>> [91083.590804] em28xx #0: found i2c device @ 0x42 [???]
>> [91083.600308] em28xx #0: found i2c device @ 0x86 [tda9887]
>> [91083.603805] em28xx #0: found i2c device @ 0xa0 [eeprom]
>> [91083.606183] em28xx #0: found i2c device @ 0xb0 [tda9874]
>> [91083.608808] em28xx #0: found i2c device @ 0xc2 [tuner (analog)]
>> [91083.617682] em28xx #0: Identified as Leadtek Winfast USB II Deluxe 
>> (card=28)
>> [91083.617684] em28xx #0:
>> [91083.617684]
>> [91083.617687] em28xx #0: The support for this board weren't valid yet.
>> [91083.617688] em28xx #0: Please send a report of having this working
>> [91083.617690] em28xx #0: not to V4L mailing list (and/or to other addresses)
>> [91083.617691]
>> [91083.980702] saa7115 4-0021: saa7114 found (1f7114d0e00) @ 0x42
>> (em28xx #0)
>> [91086.173114] tvaudio: TV audio decoder + audio/video mux driver
>> [91086.173116] tvaudio: known chips: tda9840, tda9873h, tda9874h/a/ah,
>> tda9875, tda9850, tda9855, tea6300, tea6320, tea6420, tda8425,
>> pic16c54 (PV951), ta8874z
>> [91086.173125] tvaudio 4-00b0: chip found @ 0x160
>> [91086.173127] tvaudio 4-00b0: no matching chip description found
>> [91086.173131] tvaudio: probe of 4-00b0 failed with error -5
>>
>>
>> It seems to be a tda9874 there -> em28xx #0: found i2c device @ 0xb0 
>> [tda9874]
>>
>> But does tvaudio stop @ 0x160 (decimal value of 0xa0 rigth? ) and
>> doesn't look further?
>> I mean does tvaudio find my boards eeprom, cant talk to it and gives up?
>>
>>
>> /Magnus
>>
>>
>> 2009/10/13 Magnus Alm :
>>> Hi!
>>>
>>> Thanks to Devin's moral support I  now have sound in television. ;-)
>>>
>>> Thanks!!
>>>
>>> I pooked around some more managed to get radio to function with these 
>>> settings:
>>>
>>> [EM2820_BOARD_LEADTEK_WINFAST_USBII_DELUXE] = {
>>>                .name         = "Leadtek Winfast USB II Deluxe",
>>>                .valid        = EM28XX_BOARD_NOT_VALIDATED,
>>>                .tuner_type   = TUNER_PHILIPS_FM1216ME_MK3,
>>>                .tda9887_conf = TDA9887_PRESENT |
>>>                                TDA9887_PORT1_ACTIVE,
>>>                .decoder      = EM28XX_SAA71

Re: More about "Winfast TV USB Deluxe"

2009-10-14 Thread Magnus Alm
Strange, but changeing the tvaudio_addr = 0xb0 to 88, (half of the
decimal value of b0) made tvaudio find my tda9874.

[ 1186.725140] tvaudio: TV audio decoder + audio/video mux driver
[ 1186.725142] tvaudio: known chips: tda9840, tda9873h, tda9874h/a/ah,
tda9875, tda9850, tda9855, tea6300, tea6320, tea6420, tda8425,
pic16c54 (PV951), ta8874z
[ 1186.725151] tvaudio 4-0058: chip found @ 0xb0
[ 1186.736444] tvaudio 4-0058: chip_read2: reg254=0x11
[ 1186.749704] tvaudio 4-0058: chip_read2: reg255=0x2
[ 1186.749708] tvaudio 4-0058: tda9874a_checkit(): DIC=0x11, SIC=0x2.
[ 1186.749710] tvaudio 4-0058: found tda9874a.
[ 1186.749712] tvaudio 4-0058: tda9874h/a/ah found @ 0xb0 (em28xx #0)
[ 1186.749714] tvaudio 4-0058: matches:.
[ 1186.749716] tvaudio 4-0058: chip_write: reg0=0x0
[ 1186.760012] tvaudio 4-0058: chip_write: reg1=0xc0
[ 1186.772014] tvaudio 4-0058: chip_write: reg2=0x2
[ 1186.784013] tvaudio 4-0058: chip_write: reg11=0x80
[ 1186.796010] tvaudio 4-0058: chip_write: reg12=0x0
[ 1186.808013] tvaudio 4-0058: chip_write: reg13=0x0
[ 1186.820012] tvaudio 4-0058: chip_write: reg14=0x1
[ 1186.832015] tvaudio 4-0058: chip_write: reg15=0x0
[ 1186.844012] tvaudio 4-0058: chip_write: reg16=0x14
[ 1186.856018] tvaudio 4-0058: chip_write: reg17=0x50
[ 1186.868011] tvaudio 4-0058: chip_write: reg18=0xf9
[ 1186.880745] tvaudio 4-0058: chip_write: reg19=0x80
[ 1186.892347] tvaudio 4-0058: chip_write: reg20=0x80
[ 1186.904015] tvaudio 4-0058: chip_write: reg24=0x80
[ 1186.916011] tvaudio 4-0058: chip_write: reg255=0x0
[ 1186.928021] tvaudio 4-0058: tda9874a_setup(): A2, B/G [0x00].
[ 1186.928091] tvaudio 4-0058: thread started

Now I probably need to set some gpio's too

/Magnus

2009/10/14 Magnus Alm :
> Loaded em28xx with i2c_scan and i2c_debug and tvaudio with tda9874a
> option and debug.
>
> sudo modprobe -v em28xx i2c_scan=1 i2c_debug=1
> sudo modprobe -v tvaudio tda9874a=1 debug=1
>
> And got this ouput:
>
> [91083.588182] em28xx #0: found i2c device @ 0x30 [???]
> [91083.590179] em28xx #0: found i2c device @ 0x3e [???]
> [91083.590804] em28xx #0: found i2c device @ 0x42 [???]
> [91083.600308] em28xx #0: found i2c device @ 0x86 [tda9887]
> [91083.603805] em28xx #0: found i2c device @ 0xa0 [eeprom]
> [91083.606183] em28xx #0: found i2c device @ 0xb0 [tda9874]
> [91083.608808] em28xx #0: found i2c device @ 0xc2 [tuner (analog)]
> [91083.617682] em28xx #0: Identified as Leadtek Winfast USB II Deluxe 
> (card=28)
> [91083.617684] em28xx #0:
> [91083.617684]
> [91083.617687] em28xx #0: The support for this board weren't valid yet.
> [91083.617688] em28xx #0: Please send a report of having this working
> [91083.617690] em28xx #0: not to V4L mailing list (and/or to other addresses)
> [91083.617691]
> [91083.980702] saa7115 4-0021: saa7114 found (1f7114d0e00) @ 0x42
> (em28xx #0)
> [91086.173114] tvaudio: TV audio decoder + audio/video mux driver
> [91086.173116] tvaudio: known chips: tda9840, tda9873h, tda9874h/a/ah,
> tda9875, tda9850, tda9855, tea6300, tea6320, tea6420, tda8425,
> pic16c54 (PV951), ta8874z
> [91086.173125] tvaudio 4-00b0: chip found @ 0x160
> [91086.173127] tvaudio 4-00b0: no matching chip description found
> [91086.173131] tvaudio: probe of 4-00b0 failed with error -5
>
>
> It seems to be a tda9874 there -> em28xx #0: found i2c device @ 0xb0 [tda9874]
>
> But does tvaudio stop @ 0x160 (decimal value of 0xa0 rigth? ) and
> doesn't look further?
> I mean does tvaudio find my boards eeprom, cant talk to it and gives up?
>
>
> /Magnus
>
>
> 2009/10/13 Magnus Alm :
>> Hi!
>>
>> Thanks to Devin's moral support I  now have sound in television. ;-)
>>
>> Thanks!!
>>
>> I pooked around some more managed to get radio to function with these 
>> settings:
>>
>> [EM2820_BOARD_LEADTEK_WINFAST_USBII_DELUXE] = {
>>                .name         = "Leadtek Winfast USB II Deluxe",
>>                .valid        = EM28XX_BOARD_NOT_VALIDATED,
>>                .tuner_type   = TUNER_PHILIPS_FM1216ME_MK3,
>>                .tda9887_conf = TDA9887_PRESENT |
>>                                TDA9887_PORT1_ACTIVE,
>>                .decoder      = EM28XX_SAA711X,
>>                .input        = { {
>>                        .type     = EM28XX_VMUX_TELEVISION,
>>                        .vmux     = SAA7115_COMPOSITE4,
>>                        .amux     = EM28XX_AMUX_AUX,
>>                }, {
>>                        .type     = EM28XX_VMUX_COMPOSITE1,
>>                        .vmux     = SAA7115_COMPOSITE5,
>>                        .amux     = EM28XX_AMUX_LINE_IN,
>>                }, {
>>                        .type     = EM28XX_VMUX_SVIDEO,
>>                        .vmux     = SA

Re: More about "Winfast TV USB Deluxe"

2009-10-14 Thread Magnus Alm
Loaded em28xx with i2c_scan and i2c_debug and tvaudio with tda9874a
option and debug.

sudo modprobe -v em28xx i2c_scan=1 i2c_debug=1
sudo modprobe -v tvaudio tda9874a=1 debug=1

And got this ouput:

[91083.588182] em28xx #0: found i2c device @ 0x30 [???]
[91083.590179] em28xx #0: found i2c device @ 0x3e [???]
[91083.590804] em28xx #0: found i2c device @ 0x42 [???]
[91083.600308] em28xx #0: found i2c device @ 0x86 [tda9887]
[91083.603805] em28xx #0: found i2c device @ 0xa0 [eeprom]
[91083.606183] em28xx #0: found i2c device @ 0xb0 [tda9874]
[91083.608808] em28xx #0: found i2c device @ 0xc2 [tuner (analog)]
[91083.617682] em28xx #0: Identified as Leadtek Winfast USB II Deluxe (card=28)
[91083.617684] em28xx #0:
[91083.617684]
[91083.617687] em28xx #0: The support for this board weren't valid yet.
[91083.617688] em28xx #0: Please send a report of having this working
[91083.617690] em28xx #0: not to V4L mailing list (and/or to other addresses)
[91083.617691]
[91083.980702] saa7115 4-0021: saa7114 found (1f7114d0e00) @ 0x42
(em28xx #0)
[91086.173114] tvaudio: TV audio decoder + audio/video mux driver
[91086.173116] tvaudio: known chips: tda9840, tda9873h, tda9874h/a/ah,
tda9875, tda9850, tda9855, tea6300, tea6320, tea6420, tda8425,
pic16c54 (PV951), ta8874z
[91086.173125] tvaudio 4-00b0: chip found @ 0x160
[91086.173127] tvaudio 4-00b0: no matching chip description found
[91086.173131] tvaudio: probe of 4-00b0 failed with error -5


It seems to be a tda9874 there -> em28xx #0: found i2c device @ 0xb0 [tda9874]

But does tvaudio stop @ 0x160 (decimal value of 0xa0 rigth? ) and
doesn't look further?
I mean does tvaudio find my boards eeprom, cant talk to it and gives up?


/Magnus


2009/10/13 Magnus Alm :
> Hi!
>
> Thanks to Devin's moral support I  now have sound in television. ;-)
>
> Thanks!!
>
> I pooked around some more managed to get radio to function with these 
> settings:
>
> [EM2820_BOARD_LEADTEK_WINFAST_USBII_DELUXE] = {
>                .name         = "Leadtek Winfast USB II Deluxe",
>                .valid        = EM28XX_BOARD_NOT_VALIDATED,
>                .tuner_type   = TUNER_PHILIPS_FM1216ME_MK3,
>                .tda9887_conf = TDA9887_PRESENT |
>                                TDA9887_PORT1_ACTIVE,
>                .decoder      = EM28XX_SAA711X,
>                .input        = { {
>                        .type     = EM28XX_VMUX_TELEVISION,
>                        .vmux     = SAA7115_COMPOSITE4,
>                        .amux     = EM28XX_AMUX_AUX,
>                }, {
>                        .type     = EM28XX_VMUX_COMPOSITE1,
>                        .vmux     = SAA7115_COMPOSITE5,
>                        .amux     = EM28XX_AMUX_LINE_IN,
>                }, {
>                        .type     = EM28XX_VMUX_SVIDEO,
>                        .vmux     = SAA7115_SVIDEO3,
>                        .amux     = EM28XX_AMUX_LINE_IN,
>                } },
>                        .radio    = {
>                        .type     = EM28XX_RADIO,
>                        .amux     = EM28XX_AMUX_AUX,
>                }
>        },
>
> I tested with different settings on tda9887 and modprobe "tda9887
> port1=1" seemed to work be best.
>
> One odd thing when the modules is load is this:
>
> [15680.459343] tuner 4-: chip found @ 0x0 (em28xx #0)
> [15680.473017] tuner 4-0043: chip found @ 0x86 (em28xx #0)
> [15680.473089] tda9887 4-0043: creating new instance
> [15680.473091] tda9887 4-0043: tda988[5/6/7] found
> [15680.485719] tuner 4-0061: chip found @ 0xc2 (em28xx #0)
> [15680.486169] tuner-simple 4-: unable to probe Alps TSBE1,
> proceeding anyway.                            <-- What is that?
> [15680.486171] tuner-simple 4-: creating new instance
>                                                       <--
> [15680.486174] tuner-simple 4-: type set to 10 (Alps TSBE1)
>                                                    <--
> [15680.496562] tuner-simple 4-0061: creating new instance
> [15680.496566] tuner-simple 4-0061: type set to 38 (Philips PAL/SECAM
> multi (FM1216ME MK3))
>
>
> Another question, my box has a tda9874ah chip and if  understand the
> data sheet it gives support for stereo (even Nicam if that is still
> used anymore.).
> So I tried to configure my box the same way as
> [EM2820_BOARD_COMPRO_VIDEOMATE_FORYOU] by adding these lines:
>
> .tvaudio_addr = 0xb0,                             < address of
> tda9874 according to ic2-addr.h
> .adecoder     = EM28XX_TVAUDIO,
>
> But it didnt work, got the following message when I plugged it in:
>
> [15677.928972] em28xx #0: Please send a report of having this working
> [15677.928974] em28xx #0: not to V4L mailing list (and/or to other addresses)
> [15677

More about "Winfast TV USB Deluxe"

2009-10-13 Thread Magnus Alm
Hi!

Thanks to Devin's moral support I  now have sound in television. ;-)

Thanks!!

I pooked around some more managed to get radio to function with these settings:

[EM2820_BOARD_LEADTEK_WINFAST_USBII_DELUXE] = {
.name = "Leadtek Winfast USB II Deluxe",
.valid= EM28XX_BOARD_NOT_VALIDATED,
.tuner_type   = TUNER_PHILIPS_FM1216ME_MK3,
.tda9887_conf = TDA9887_PRESENT |
TDA9887_PORT1_ACTIVE,
.decoder  = EM28XX_SAA711X,
.input= { {
.type = EM28XX_VMUX_TELEVISION,
.vmux = SAA7115_COMPOSITE4,
.amux = EM28XX_AMUX_AUX,
}, {
.type = EM28XX_VMUX_COMPOSITE1,
.vmux = SAA7115_COMPOSITE5,
.amux = EM28XX_AMUX_LINE_IN,
}, {
.type = EM28XX_VMUX_SVIDEO,
.vmux = SAA7115_SVIDEO3,
.amux = EM28XX_AMUX_LINE_IN,
} },
.radio= {
.type = EM28XX_RADIO,
.amux = EM28XX_AMUX_AUX,
}
},

I tested with different settings on tda9887 and modprobe "tda9887
port1=1" seemed to work be best.

One odd thing when the modules is load is this:

[15680.459343] tuner 4-: chip found @ 0x0 (em28xx #0)
[15680.473017] tuner 4-0043: chip found @ 0x86 (em28xx #0)
[15680.473089] tda9887 4-0043: creating new instance
[15680.473091] tda9887 4-0043: tda988[5/6/7] found
[15680.485719] tuner 4-0061: chip found @ 0xc2 (em28xx #0)
[15680.486169] tuner-simple 4-: unable to probe Alps TSBE1,
proceeding anyway.<-- What is that?
[15680.486171] tuner-simple 4-: creating new instance
   <--
[15680.486174] tuner-simple 4-: type set to 10 (Alps TSBE1)
<--
[15680.496562] tuner-simple 4-0061: creating new instance
[15680.496566] tuner-simple 4-0061: type set to 38 (Philips PAL/SECAM
multi (FM1216ME MK3))


Another question, my box has a tda9874ah chip and if  understand the
data sheet it gives support for stereo (even Nicam if that is still
used anymore.).
So I tried to configure my box the same way as
[EM2820_BOARD_COMPRO_VIDEOMATE_FORYOU] by adding these lines:

.tvaudio_addr = 0xb0, < address of
tda9874 according to ic2-addr.h
.adecoder = EM28XX_TVAUDIO,

But it didnt work, got the following message when I plugged it in:

[15677.928972] em28xx #0: Please send a report of having this working
[15677.928974] em28xx #0: not to V4L mailing list (and/or to other addresses)
[15677.928975]
[15678.288360] saa7115 4-0021: saa7114 found (1f7114d0e00) @ 0x42
(em28xx #0)
[15680.457094] tvaudio: TV audio decoder + audio/video mux driver
[15680.457097] tvaudio: known chips: tda9840, tda9873h, tda9874h/a/ah,
tda9875, tda9850, tda9855, tea6300, tea6320, tea6420, tda8425,
pic16c54 (PV951), ta8874z
[15680.457105] tvaudio 4-00b0: chip found @ 0x160
[15680.457107] tvaudio 4-00b0: no matching chip description found
[15680.457111] tvaudio: probe of 4-00b0 failed with error -5
[15680.459343] tuner 4-: chip found @ 0x0 (em28xx #0)
[15680.473017] tuner 4-0043: chip found @ 0x86 (em28xx #0)
[15680.473089] tda9887 4-0043: creating new instance


It might be so that my box is not wired to fully utilize the chip or I
did something wrong.


/Magnus
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html