* Re: DVB support for MSI DigiVox A/D II and KWorld 320U [not found] <31497292.9391255416643929.JavaMail.root@mail> @ 2009-10-13 6:54 ` Lauri Laanmets 2009-11-13 8:37 ` Fwd: " Lauri Laanmets 0 siblings, 1 reply; 4+ messages in thread From: Lauri Laanmets @ 2009-10-13 6:54 UTC (permalink / raw) To: Devin Heitmueller; +Cc: linux-media Hello > Check the dvb_gpio setting in the board profile. On some of those > boards you need to take put one of the GPO pins high to take the demod > out of reset. The KWorld 315u and 330u are both like that. Absolutely true. Using the same pin setting as KWorld 330U made the I2C communication work correctly and the device is found. Now the trouble is that scanning channels doesn't work, blue LED doesn't light up and the device is not heated up. I'm quite newbie in this field, is there a good way to know what registers to set exactly? I see that the working "mcentral" code had the following setting: #define EETI_DEFAULT_GPIO { \ .ts1_on = _BIT_VAL(EM28XX_GPIO0, 0, 0), \ .a_on = _BIT_VAL(EM28XX_GPIO1, 0, 0), \ .xc3028_sec = _BIT_VAL(EM28XX_GPIO2, 1, 0), \ /* reserved */ \ .t1_reset = _BIT_VAL(EM28XX_GPIO4, 0, 1), \ /* reserved */ \ .t1_on = _BIT_VAL(EM28XX_GPIO6, 0, 0), \ .t2_on = _BIT_VAL(EM28XX_GPIO7, 1, 0), \ \ .l1_on = _BIT_VAL(EM28XX_GOP2, 1, 0), \ .d1_reset = _BIT_VAL(EM28XX_GOP3, 0, 1), \ } But the v4l-dvb uses: static struct em28xx_reg_seq kworld_330u_digital[] = { {EM28XX_R08_GPIO, 0x6e, ~EM_GPIO_4, 10}, {EM2880_R04_GPO, 0x08, 0xff, 10}, { -1, -1, -1, -1}, }; Lauri ^ permalink raw reply [flat|nested] 4+ messages in thread
* Fwd: DVB support for MSI DigiVox A/D II and KWorld 320U 2009-10-13 6:54 ` DVB support for MSI DigiVox A/D II and KWorld 320U Lauri Laanmets @ 2009-11-13 8:37 ` Lauri Laanmets 2009-11-13 8:47 ` Markus Rechberger 0 siblings, 1 reply; 4+ messages in thread From: Lauri Laanmets @ 2009-11-13 8:37 UTC (permalink / raw) To: linux-media Hello I have managed to attach the device without any error messages now but the tuning and playback of DVB still doesn't work. I get a lot of these error messages: [ 247.268152] em28xx #0: reading i2c device failed (error=-110) [ 247.268161] xc2028 1-0061: i2c input error: rc = -110 (should be 2) and [ 433.232124] xc2028 1-0061: Loading SCODE for type=DTV6 ATSC OREN538 SCODE HAS_IF_5580 (60110020), id 0000000000000000. [ 433.256017] xc2028 1-0061: Incorrect readback of firmware version. [ 433.372019] xc2028 1-0061: Loading firmware for type=BASE F8MHZ (3), id 0000000000000000. [ 437.940029] xc2028 1-0061: Loading firmware for type=D2620 DTV78 (108), id 0000000000000000. Do anybody have an idea what to do next? Or maybe somebody is willing to help me understanding the mcentral code because that one works fine. Regards Lauri ----- Forwarded Message ----- From: "Lauri Laanmets" <lauri.laanmets@proekspert.ee> To: "Devin Heitmueller" <dheitmueller@kernellabs.com> Cc: linux-media@vger.kernel.org Sent: Tuesday, October 13, 2009 9:54:05 AM Subject: Re: DVB support for MSI DigiVox A/D II and KWorld 320U Hello > Check the dvb_gpio setting in the board profile. On some of those > boards you need to take put one of the GPO pins high to take the demod > out of reset. The KWorld 315u and 330u are both like that. Absolutely true. Using the same pin setting as KWorld 330U made the I2C communication work correctly and the device is found. Now the trouble is that scanning channels doesn't work, blue LED doesn't light up and the device is not heated up. I'm quite newbie in this field, is there a good way to know what registers to set exactly? I see that the working "mcentral" code had the following setting: #define EETI_DEFAULT_GPIO { \ .ts1_on = _BIT_VAL(EM28XX_GPIO0, 0, 0), \ .a_on = _BIT_VAL(EM28XX_GPIO1, 0, 0), \ .xc3028_sec = _BIT_VAL(EM28XX_GPIO2, 1, 0), \ /* reserved */ \ .t1_reset = _BIT_VAL(EM28XX_GPIO4, 0, 1), \ /* reserved */ \ .t1_on = _BIT_VAL(EM28XX_GPIO6, 0, 0), \ .t2_on = _BIT_VAL(EM28XX_GPIO7, 1, 0), \ \ .l1_on = _BIT_VAL(EM28XX_GOP2, 1, 0), \ .d1_reset = _BIT_VAL(EM28XX_GOP3, 0, 1), \ } But the v4l-dvb uses: static struct em28xx_reg_seq kworld_330u_digital[] = { {EM28XX_R08_GPIO, 0x6e, ~EM_GPIO_4, 10}, {EM2880_R04_GPO, 0x08, 0xff, 10}, { -1, -1, -1, -1}, }; Lauri ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: DVB support for MSI DigiVox A/D II and KWorld 320U 2009-11-13 8:37 ` Fwd: " Lauri Laanmets @ 2009-11-13 8:47 ` Markus Rechberger 2009-11-13 8:59 ` Lauri Laanmets 0 siblings, 1 reply; 4+ messages in thread From: Markus Rechberger @ 2009-11-13 8:47 UTC (permalink / raw) To: Lauri Laanmets; +Cc: linux-media On Fri, Nov 13, 2009 at 4:37 PM, Lauri Laanmets <lauri.laanmets@proekspert.ee> wrote: > Hello > > I have managed to attach the device without any error messages now but the tuning and playback of DVB still doesn't work. I get a lot of these error messages: > > [ 247.268152] em28xx #0: reading i2c device failed (error=-110) > [ 247.268161] xc2028 1-0061: i2c input error: rc = -110 (should be 2) > > and > > [ 433.232124] xc2028 1-0061: Loading SCODE for type=DTV6 ATSC OREN538 SCODE HAS_IF_5580 (60110020), id 0000000000000000. > [ 433.256017] xc2028 1-0061: Incorrect readback of firmware version. > [ 433.372019] xc2028 1-0061: Loading firmware for type=BASE F8MHZ (3), id 0000000000000000. > [ 437.940029] xc2028 1-0061: Loading firmware for type=D2620 DTV78 (108), id 0000000000000000. > > Do anybody have an idea what to do next? Or maybe somebody is willing to help me understanding the mcentral code because that one works fine. > Due some fundamental problems we do not recommend to use the em28xx-new code, it can damage your device(!) We are now working together with several manufacturers since we accepted their restrictions we got indepth details about how to handle those devices correctly in order to prevent damaged devices. Even if it works fine for you it might break the device the next day. The only way to get it right is to cooperate with the chip design companies. Markus ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: DVB support for MSI DigiVox A/D II and KWorld 320U 2009-11-13 8:47 ` Markus Rechberger @ 2009-11-13 8:59 ` Lauri Laanmets 0 siblings, 0 replies; 4+ messages in thread From: Lauri Laanmets @ 2009-11-13 8:59 UTC (permalink / raw) To: Markus Rechberger; +Cc: linux-media Hi Sorry if I wasn't clear enough. I'm trying to get V4l code working. So I'm playing around with GPIO's and have managed to get the I2C communication working but something is still missing. I was thinking that because mcentral code worked, maybe some information can be taken over from it but the code is so much different, I do not understand it fully. Or what should I try next? Lauri ----- Original Message ----- From: "Markus Rechberger" <mrechberger@gmail.com> To: "Lauri Laanmets" <lauri.laanmets@proekspert.ee> Cc: linux-media@vger.kernel.org Sent: Friday, November 13, 2009 10:47:03 AM Subject: Re: DVB support for MSI DigiVox A/D II and KWorld 320U On Fri, Nov 13, 2009 at 4:37 PM, Lauri Laanmets <lauri.laanmets@proekspert.ee> wrote: > Hello > > I have managed to attach the device without any error messages now but the tuning and playback of DVB still doesn't work. I get a lot of these error messages: > > [ 247.268152] em28xx #0: reading i2c device failed (error=-110) > [ 247.268161] xc2028 1-0061: i2c input error: rc = -110 (should be 2) > > and > > [ 433.232124] xc2028 1-0061: Loading SCODE for type=DTV6 ATSC OREN538 SCODE HAS_IF_5580 (60110020), id 0000000000000000. > [ 433.256017] xc2028 1-0061: Incorrect readback of firmware version. > [ 433.372019] xc2028 1-0061: Loading firmware for type=BASE F8MHZ (3), id 0000000000000000. > [ 437.940029] xc2028 1-0061: Loading firmware for type=D2620 DTV78 (108), id 0000000000000000. > > Do anybody have an idea what to do next? Or maybe somebody is willing to help me understanding the mcentral code because that one works fine. > Due some fundamental problems we do not recommend to use the em28xx-new code, it can damage your device(!) We are now working together with several manufacturers since we accepted their restrictions we got indepth details about how to handle those devices correctly in order to prevent damaged devices. Even if it works fine for you it might break the device the next day. The only way to get it right is to cooperate with the chip design companies. Markus ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-11-13 8:59 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <31497292.9391255416643929.JavaMail.root@mail>
2009-10-13 6:54 ` DVB support for MSI DigiVox A/D II and KWorld 320U Lauri Laanmets
2009-11-13 8:37 ` Fwd: " Lauri Laanmets
2009-11-13 8:47 ` Markus Rechberger
2009-11-13 8:59 ` Lauri Laanmets
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox