Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2013-02-24 Thread Matthew Gyurgyik
On 02/24/2013 05:23 PM, Antti Palosaari wrote: I rebased it to the latest LinuxTV 3.9. There is quite a lot of changes done for em28xx driver so it could work. Please test. http://git.linuxtv.org/anttip/media_tree.git/shortlog/refs/heads/HU345-Q regards Antti I checked out the branch and

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2013-02-16 Thread Matthew Gyurgyik
On 01/20/2013 12:46 PM, Antti Palosaari wrote: On 01/20/2013 04:40 PM, Matthew Gyurgyik wrote: On 01/02/2013 09:53 PM, Matthew Gyurgyik wrote: On 01/02/2013 03:59 PM, Antti Palosaari wrote: On 12/18/2012 05:08 AM, Matthew Gyurgyik wrote: I can test patches Tue and Wed this week. Afterwards

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2013-01-20 Thread Matthew Gyurgyik
On 01/02/2013 09:53 PM, Matthew Gyurgyik wrote: On 01/02/2013 03:59 PM, Antti Palosaari wrote: On 12/18/2012 05:08 AM, Matthew Gyurgyik wrote: I can test patches Tue and Wed this week. Afterwards, I probably won't be able to test anything until Dec 28th/29th as I will be away from my

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2013-01-02 Thread Matthew Gyurgyik
On 01/02/2013 03:59 PM, Antti Palosaari wrote: On 12/18/2012 05:08 AM, Matthew Gyurgyik wrote: I can test patches Tue and Wed this week. Afterwards, I probably won't be able to test anything until Dec 28th/29th as I will be away from my workstation. In regards to my issue compiling my kernel

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-17 Thread Matthew Gyurgyik
On 12/17/2012 06:08 AM, Antti Palosaari wrote: On 12/17/2012 11:33 AM, Antti Palosaari wrote: On 12/17/2012 03:37 AM, Matthew Gyurgyik wrote: On 12/16/2012 08:26 PM, Antti Palosaari wrote: On 12/17/2012 03:09 AM, Matthew Gyurgyik wrote: On 12/15/2012 06:21 PM, Frank Schäfer wrote: Matthew

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-17 Thread Matthew Gyurgyik
On 12/17/2012 11:14 AM, Mauro Carvalho Chehab wrote: Hi Matthew, Em 17-12-2012 09:17, Matthew Gyurgyik escreveu: On 12/17/2012 06:08 AM, Antti Palosaari wrote: On 12/17/2012 11:33 AM, Antti Palosaari wrote: On 12/17/2012 03:37 AM, Matthew Gyurgyik wrote: On 12/16/2012 08:26 PM, Antti

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-17 Thread Matthew Gyurgyik
On 12/17/2012 11:14 AM, Mauro Carvalho Chehab wrote: Hi Matthew, Em 17-12-2012 09:17, Matthew Gyurgyik escreveu: On 12/17/2012 06:08 AM, Antti Palosaari wrote: On 12/17/2012 11:33 AM, Antti Palosaari wrote: On 12/17/2012 03:37 AM, Matthew Gyurgyik wrote: On 12/16/2012 08:26 PM, Antti

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-16 Thread Matthew Gyurgyik
On 12/15/2012 06:21 PM, Frank Schäfer wrote: Matthew, could you please validate your test results and try Mauros patches ? If it doesn't work, please create another USB-log. Sorry it took me so long to test the patch, but the results look promising, I actually got various keycodes! dmesg:

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-16 Thread Matthew Gyurgyik
On 12/16/2012 08:26 PM, Antti Palosaari wrote: On 12/17/2012 03:09 AM, Matthew Gyurgyik wrote: On 12/15/2012 06:21 PM, Frank Schäfer wrote: Matthew, could you please validate your test results and try Mauros patches ? If it doesn't work, please create another USB-log. Sorry it took me so

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-10 Thread Matthew Gyurgyik
On 2012-12-10 10:39, Frank Schäfer wrote: Am 09.12.2012 18:53, schrieb Matthew Gyurgyik: On 12/09/2012 12:06 PM, Frank Schäfer wrote: Forget this sh... (never do multiple things at the same time ;) ) Reg 0x50 is set to according to rc_type specified in the selected remote control map. So

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-09 Thread Matthew Gyurgyik
On 12/09/2012 07:48 AM, Frank Schäfer wrote: Am 08.12.2012 23:04, schrieb Matthew Gyurgyik: On 12/08/2012 04:47 PM, Antti Palosaari wrote: On 12/08/2012 11:40 PM, Matthew Gyurgyik wrote: On 12/08/2012 12:49 PM, Frank Schäfer wrote: Am 08.12.2012 17:51, schrieb Matthew Gyurgyik

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-09 Thread Matthew Gyurgyik
On 12/09/2012 12:06 PM, Frank Schäfer wrote: Forget this sh... (never do multiple things at the same time ;) ) Reg 0x50 is set to according to rc_type specified in the selected remote control map. So if the correct map is selected, everything should be fine (as long as it is RC_TYPE_NEC or

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-08 Thread Matthew Gyurgyik
On 12/08/2012 08:52 AM, Frank Schäfer wrote: I lied, it works! I must have forgotten to do run make modules_install or something! This patch accurately states my current code changes: http://pyther.net/a/digivox_atsc/diff-Dec-06-v1.patch Great, that's a big one step forward. Based on this

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-08 Thread Matthew Gyurgyik
On 12/08/2012 10:20 AM, Frank Schäfer wrote: Am 08.12.2012 15:10, schrieb Matthew Gyurgyik: Ok, thanks. So the USB log was right and the bridge setup should be complete, except that the remote control doesn't work yet... Could you please test the patch in the attachment ? Changes from V3

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-08 Thread Matthew Gyurgyik
On 12/08/2012 12:49 PM, Frank Schäfer wrote: Am 08.12.2012 17:51, schrieb Matthew Gyurgyik: That shouldn't be necessary. I just noticed that there is a module parameter 'ir_debug'. ;) With ir_debug enabled, you should see messages em28xx_ir_handle_key: toggle: XX, count: XX, key

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-08 Thread Matthew Gyurgyik
On 12/08/2012 04:47 PM, Antti Palosaari wrote: On 12/08/2012 11:40 PM, Matthew Gyurgyik wrote: On 12/08/2012 12:49 PM, Frank Schäfer wrote: Am 08.12.2012 17:51, schrieb Matthew Gyurgyik: That shouldn't be necessary. I just noticed that there is a module parameter 'ir_debug'. ;) With ir_debug

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-07 Thread Matthew Gyurgyik
On 12/06/2012 10:21 PM, Devin Heitmueller wrote: On Thu, Dec 6, 2012 at 8:40 PM, Matthew Gyurgyik matt...@pyther.net wrote: I was able to do a bit of testing tonight and this is what I found. A channel scan was unsuccessful: http://pyther.net/a/digivox_atsc/dec06/scan.txt (no errors in dmesg

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-06 Thread Matthew Gyurgyik
On 12/06/2012 04:49 PM, Frank Schäfer wrote: Did you switch back to .mpeg_mode = LGDT3305_MPEG_SERIAL, .tpclk_edge = LGDT3305_TPCLK_FALLING_EDGE, in struct lgdt3305_config em2874_lgdt3305_dev (em28xx-dvb.c) before testing this ? I did not, but switching back doesn't

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-06 Thread Matthew Gyurgyik
On 12/06/2012 04:49 PM, Frank Schäfer wrote: Did you switch back to .mpeg_mode = LGDT3305_MPEG_SERIAL, .tpclk_edge = LGDT3305_TPCLK_FALLING_EDGE, in struct lgdt3305_config em2874_lgdt3305_dev (em28xx-dvb.c) before testing this ? You could also play with the other gpio

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-06 Thread Matthew Gyurgyik
On 12/06/2012 05:58 PM, Matthew Gyurgyik wrote: On 12/06/2012 04:49 PM, Frank Schäfer wrote: Did you switch back to .mpeg_mode = LGDT3305_MPEG_SERIAL, .tpclk_edge = LGDT3305_TPCLK_FALLING_EDGE, in struct lgdt3305_config em2874_lgdt3305_dev (em28xx-dvb.c) before

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-05 Thread Matthew Gyurgyik
On 12/05/2012 07:35 AM, Antti Palosaari wrote: There is something really wrong. I am not at US expert but why the hell us-Cable-Standard-center-frequencies-QAM256 scans up to 999MHz whilst demodulator max is set 858? Either one is wrong. Also, demod seems to be HAS_LOCK about all the time.

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-05 Thread Matthew Gyurgyik
On 12/05/2012 05:01 PM, Antti Palosaari wrote: OK, fine, I was then wrong. I have to say you have a lot of channels over there what I can see from scan result [1]. Those channels which says tuning failed are channels where is no transmission and those filter timeout pid means there is ta

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-05 Thread Matthew Gyurgyik
On 12/05/2012 07:55 PM, Antti Palosaari wrote: It was good snoop. I didn't saw nothing very interesting. But, I think I found the reason. Just add that one line writing 0x42 to register 0x0d. IIRC I saw earlier it caused that kind of bug... +static struct em28xx_reg_seq msi_digivox_atsc[] =

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-05 Thread Matthew Gyurgyik
On 12/04/2012 04:06 PM, Frank Schäfer wrote: I double-checked the log and it is indeed set to LGDT3305_MPEG_SERIAL, but LGDT3305_TPCLK_FALLING_EDGE is used instead of LGDT3305_TPCLK_RISING_EDGE. OTOH, the KWorld A340 bord sets this to LGDT3305_MPEG_PARALLEL... Matthew, could you please test V3

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-04 Thread Matthew Gyurgyik
On 12/04/2012 04:06 PM, Frank Schäfer wrote: I double-checked the log and it is indeed set to LGDT3305_MPEG_SERIAL, but LGDT3305_TPCLK_FALLING_EDGE is used instead of LGDT3305_TPCLK_RISING_EDGE. OTOH, the KWorld A340 bord sets this to LGDT3305_MPEG_PARALLEL... Matthew, could you please test V3

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-03 Thread Matthew Gyurgyik
On 12/03/2012 01:16 PM, Frank Schäfer wrote: Here is v2 of the patch (attached). Antti, could you please take a look at the std_map for the tuner ? I'm not sure what the correct and complete map is. For a first test, I've selected the same std_map as used with the KWorld A340 (LGDT3304 +

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-12-03 Thread Matthew Gyurgyik
On 12/03/2012 09:29 PM, Devin Heitmueller wrote: On Mon, Dec 3, 2012 at 9:15 PM, Matthew Gyurgyik matt...@pyther.net wrote: Although, it looked like tuning was semi-successful, I tried the following * cat /dev/dvb/adapter0/dvr0 (no output) * mplayer /dev/dvb/adapter0/dvr0 (no output

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-11-29 Thread Matthew Gyurgyik
On 11/29/2012 02:28 PM, Frank Schäfer wrote: Matthew, stay tuned but be patient. ;) Regards, Frank Sure thing, just let me know what you need me to do! -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-11-28 Thread Matthew Gyurgyik
On 11/28/2012 03:47 PM, Frank Schäfer wrote: Your device seems to use a EM2874 bridge. That is what appears on the chip. Any chance to open the device and find out which demodulator it uses ? To my surprise it was easier to open than expected. I think this is the demodulator: 7th Generation

Re: em28xx: msi Digivox ATSC board id [0db0:8810]

2012-11-28 Thread Matthew Gyurgyik
On 11/28/2012 05:55 PM, Antti Palosaari wrote: Very, very, good pics and sniffs!! From the sniff you could see I2C addresses 50 (a0 1) eeprom 0e (1c 1) demod 60 (c0 1) tuner EM2874, USB-bridge, clocked at 12MHz, crystal on other side of PCB. There is also 32k serial eeprom for EM2874.

em28xx: msi Digivox ATSC board id [0db0:8810]

2012-11-27 Thread Matthew Gyurgyik
Hi, I recently acquired a msi Digivox ATSC tuner. I believe this card has an em28xx chip (the windows driver included is em28xx). Looking at the em28xx wiki page and digging around in the code it does not seem like the em28xx driver has support for this card. Based on my limit (extremely)