View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 79 posts ] 
Go to page Previous  1, 2, 3, 4, 5, 6  Next

Print view Previous topic   Next topic  
Author Message
Search for:
 Post subject:
PostPosted: Fri Dec 29, 2006 9:22 am 
Offline
Joined: Fri Nov 18, 2005 9:22 am
Posts: 777
Location: spencerport, ny (USA)
Quote:
I'm having conversation with myself....

Not at all! I'm hanging on every word....


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 29, 2006 11:03 am 
Offline
Joined: Fri Nov 18, 2005 9:22 am
Posts: 777
Location: spencerport, ny (USA)
dwaine wrote:
copied recently downloaded firmware and replaced/copied into
both /usr/lib/hotplug/firmware and /lib/firmware.

Where did you get that firmware from?
Is there a way to tell which version I've got?


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 29, 2006 11:29 am 
Offline
Joined: Wed Jun 15, 2005 9:14 pm
Posts: 72
File name, size, and MD5 would be nice.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 29, 2006 1:25 pm 
Offline
Joined: Fri Nov 18, 2005 9:22 am
Posts: 777
Location: spencerport, ny (USA)
Atamido wrote:
File name, size, and MD5 would be nice.

Here's mine, which presumably came with R5E50

-rw-r--r-- 1 root root 9584 Dec 28 13:33 dvb-fe-nxt2004.fw
2a7e38d3ebc392264f840dcb89e08829


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 29, 2006 2:16 pm 
Offline
Joined: Wed Jun 15, 2005 9:14 pm
Posts: 72
thornsoft wrote:
Where did you get that firmware from?

Well the get_dvb_firmware script mentioned here has this piece of code:
Code:
sub nxt2004 {
    my $sourcefile = "AVerTVHD_MCE_A180_Drv_v1.2.2.16.zip";
    my $url = "http://www.aver.com/support/Drivers/$sourcefile";
    my $hash = "111cb885b1e009188346d72acfed024c";
    my $outfile = "dvb-fe-nxt2004.fw";
    my $tmpdir = tempdir(DIR => "/tmp", CLEANUP => 1);
 
    checkstandard();
 
    wgetfile($sourcefile, $url);
    unzip($sourcefile, $tmpdir);
    verify("$tmpdir/3xHybrid.sys", $hash);
    extract("$tmpdir/3xHybrid.sys", 465304, 9584, $outfile);
 
    $outfile;
}
which downloads this file:
http://www.aver.com/support/Drivers/AVerTVHD_MCE_A180_Drv_v1.2.2.16.zip
and extracts 3xHybrid.sys from the archive and then extracts "dvb-fe-nxt2004.fw" from 3xHybrid.sys. The 3xHybrid.sys file in that download is from 2005-03-31, so I doubt it is any different than what you already have, but it might be worth checking just in case.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 29, 2006 2:36 pm 
Offline
Joined: Mon Apr 24, 2006 8:30 am
Posts: 91
Location: Pittsburgh, PA
interesting... tried that early on in case there was something wrong with the firmware and i get an error when i try to run the get_dvb_firmware script. it seems as though it won't unzip the file downloaded from aver.com. the error is something like (and this is from memory only) "error in line 345: file is not zipped or is part of a multi-disk archive; unzip failed." could it be a problem with the file from aver.com?

dwaine, did you download the firmware with this script?


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 29, 2006 4:14 pm 
Offline
Joined: Thu Dec 01, 2005 12:46 am
Posts: 135
lostmyshape wrote:
interesting... tried that early on in case there was something wrong with the firmware and i get an error when i try to run the get_dvb_firmware script. it seems as though it won't unzip the file downloaded from aver.com. the error is something like (and this is from memory only) "error in line 345: file is not zipped or is part of a multi-disk archive; unzip failed." could it be a problem with the file from aver.com?

dwaine, did you download the firmware with this script?


Yeah... I used the script with the kernel which I apt-get'dd. Same perl script as the ATSC110 instruction indicate.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 29, 2006 4:26 pm 
Offline
Joined: Thu Dec 01, 2005 12:46 am
Posts: 135
After a reboot, the same situation happens. Where the nxt2004 does not get loaded by saa7134-dvb. If I manually unload saa7134 and then modprobe saa7134 and saa7134-dvb it works.

So everyone having trouble, just try the following...

1. Kill the backend, make sure it's not running.
2. modprobe -r saa7134
3. modprobe saa7134
4. modprobe saa7134-dvb

Then you should see the wonderful output in messages....

Dec 29 17:02:24 mythtv kernel: saa7130/34: v4l2 driver version 0.2.14 loaded
Dec 29 17:02:24 mythtv kernel: saa7133[0]: found at 0000:00:0a.0, rev: 240, irq: 19, latency: 32, mmio: 0xe6000000
Dec 29 17:02:24 mythtv kernel: saa7133[0]: subsystem: 17de:7350, board: Kworld ATSC110 [card=90,autodetected]
Dec 29 17:02:24 mythtv kernel: saa7133[0]: board init: gpio is 100100
Dec 29 17:02:24 mythtv kernel: saa7133[0]: i2c eeprom 00: de 17 50 73 ff ff ff ff ff ff ff ff ff ff ff ff
Dec 29 17:02:24 mythtv kernel: saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 29 17:02:24 mythtv kernel: saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 29 17:02:24 mythtv kernel: saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 29 17:02:24 mythtv kernel: saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 29 17:02:24 mythtv kernel: saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 29 17:02:24 mythtv kernel: saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 29 17:02:24 mythtv kernel: saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Dec 29 17:02:24 mythtv kernel: saa7133[0]: registered device video0 [v4l2]
Dec 29 17:02:24 mythtv kernel: saa7133[0]: registered device vbi0
Dec 29 17:02:32 mythtv kernel: nxt200x: NXT2004 Detected
Dec 29 17:02:32 mythtv kernel: DVB: registering new adapter (saa7133[0]).
Dec 29 17:02:32 mythtv kernel: DVB: registering frontend 0 (Nextwave NXT200X VSB/QAM frontend)...
Dec 29 17:06:08 mythtv kernel: nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
Dec 29 17:06:08 mythtv kernel: nxt2004: Waiting for firmware upload(2)...
Dec 29 17:06:09 mythtv kernel: nxt2004: Firmware upload complete

Looks like entry for saa7134-dvb is getting ignored when a reboot happens, but it's there.
Also, it's not a problem just relating to R5E50. I have seen this problem with the older versions too. Usually, just downloading v4l/dvb cvs and compiling then make install fixes it.

Can people try unloading saa7134 and then manually loading both saa7134 and saa7134-dvb. Get back to this thread with the results.

Dwaine


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 29, 2006 4:30 pm 
Offline
Joined: Thu Dec 01, 2005 12:46 am
Posts: 135
Here is the patch for the remote to work. It does conflict with the KNC1 devices since it shares the same address as with the Kworld ATSC110. I'm going to fix up the patch and submit it to v4l/dvb. Hopefully before my holidays are over... It's been awhile since I have patched a copy of v4l/dvb cvs.

diff -rup /usr/src/a/linux/drivers/media/common/ir-keymaps.c /usr/src/b/linux/drivers/media/common/ir-keymaps.c
--- /usr/src/a/linux/drivers/media/common/ir-keymaps.c 2006-09-17 15:47:30.000000000 +0000
+++ /usr/src/b/linux/drivers/media/common/ir-keymaps.c 2006-09-17 14:19:46.000000000 +0000
@@ -64,6 +64,60 @@ IR_KEYTAB_TYPE ir_codes_proteus_2309[IR_
};

EXPORT_SYMBOL_GPL(ir_codes_proteus_2309);
+
+IR_KEYTAB_TYPE ir_codes_kworld_atsc110[IR_KEYTAB_SIZE] = {
+ [ 0x0 ] = KEY_1,
+ [ 0x1 ] = KEY_2,
+ [ 0x2 ] = KEY_3,
+ [ 0x3 ] = KEY_4,
+ [ 0x4 ] = KEY_5,
+ [ 0x5 ] = KEY_6,
+ [ 0x6 ] = KEY_7,
+ [ 0x7 ] = KEY_8,
+ [ 0x8 ] = KEY_9,
+ [ 0xa ] = KEY_0,
+ [ 0x9 ] = KEY_ESC, /* UP ARROW */
+ [ 0xc ] = KEY_POWER, /* POWER */
+ [ 0x0a ] = KEY_MUTE, /* MUTE */
+ [ 0x0d ] = KEY_EPG, /* GUIDE */
+ [ 0x1b ] = KEY_RECORD, /* RECORD */
+ [ 0x16 ] = KEY_PAUSE, /* PAUSE */
+ [ 0x1a ] = KEY_STOP, /* STOP */
+ [ 0x1d ] = KEY_VOLUMEDOWN, /* VOLUME- */
+ [ 0x1c ] = KEY_VOLUMEUP, /* VOLUME+ */
+ [ 0x1f ] = KEY_CHANNELDOWN, /* CHANNEL/PAGE- */
+ [ 0x1e ] = KEY_CHANNELUP, /* CHANNEL/PAGE+ */
+ [ 0x10 ] = KEY_UP, /* KEY_SCROLLUP */
+ [ 0x12 ] = KEY_LEFT, /* KEY_BACK */
+ [ 0xe ] = KEY_ENTER, /* KEY_ENTER */
+ [ 0x13 ] = KEY_RIGHT, /* KEY_FORWARD */
+ [ 0x11 ] = KEY_DOWN, /* KEY_SCROLLDOWN */
+ [ 0x14 ] = KEY_MUTE, /* MUTE */
+ [ 0x15 ] = KEY_AUDIO, /* STEREO */
+ [ 0x16 ] = KEY_VIDEO, /* SOURCE */
+ [ 0x17 ] = KEY_ZOOM, /* ZOOM */
+ [ 0x18 ] = KEY_PRINT, /* SHUTDOWN */
+ [ 0X19 ] = KEY_T, /* TIMESHIFT */
+ [ 0x44 ] = KEY_PLAYPAUSE, /* PAUSE/PLAY */
+ [ 0x45 ] = KEY_STOP, /* STOP */
+ [ 0x40 ] = KEY_REWIND, /* REWIND */
+ [ 0x41 ] = KEY_FORWARD, /* FASTFORWARD */
+ [ 0x42 ] = KEY_PREVIOUSSONG, /* PREVIOUS */
+ [ 0x43 ] = KEY_NEXTSONG, /* NEXT */
+
+ // buttons a-h
+ [ 0x48 ] = KEY_A,
+ [ 0x49 ] = KEY_B,
+ [ 0x4a ] = KEY_C,
+ [ 0x4b ] = KEY_D,
+ [ 0x4c ] = KEY_E,
+ [ 0x4d ] = KEY_F,
+ [ 0x4e ] = KEY_G,
+ [ 0x4f ] = KEY_H
+};
+
+EXPORT_SYMBOL_GPL(ir_codes_kworld_atsc110);
+
/* Matt Jesson <dvb@jesson.eclipse.co.uk */
IR_KEYTAB_TYPE ir_codes_avermedia_dvbt[IR_KEYTAB_SIZE] = {
[ 0x28 ] = KEY_0, //'0' / 'enter'
diff -rup /usr/src/a/linux/drivers/media/video/ir-kbd-i2c.c /usr/src/b/linux/drivers/media/video/ir-kbd-i2c.c
--- /usr/src/a/linux/drivers/media/video/ir-kbd-i2c.c 2006-09-17 15:47:30.000000000 +0000
+++ /usr/src/b/linux/drivers/media/video/ir-kbd-i2c.c 2006-09-17 13:17:36.000000000 +0000
@@ -348,10 +348,9 @@ static int ir_attach(struct i2c_adapter
}
break;
case 0x30:
- name = "KNC One";
- ir->get_key = get_key_knc1;
+ name = "Kworld ATSC110";
ir_type = IR_TYPE_OTHER;
- ir_codes = ir_codes_empty;
+ ir_codes = ir_codes_kworld_atsc110;
break;
case 0x7a:
case 0x47:
@@ -439,7 +438,7 @@ static int ir_probe(struct i2c_adapter *
*/

static const int probe_bttv[] = { 0x1a, 0x18, 0x4b, 0x64, 0x30, -1};
- static const int probe_saa7134[] = { 0x7a, 0x47, -1 };
+ static const int probe_saa7134[] = { 0x7a, 0x47, 0x30, -1 };
static const int probe_em28XX[] = { 0x30, 0x47, -1 };
const int *probe = NULL;
struct i2c_client c;
@@ -468,6 +467,36 @@ static int ir_probe(struct i2c_adapter *
for (i = 0; -1 != probe[i]; i++) {
c.addr = probe[i];
rc = i2c_master_recv(&c,&buf,0);
+
+ /* Special case for Kworld ATSC110 remote */
+ if (c.adapter->id == I2C_HW_SAA7134 && probe[i] == 0x30)
+ {
+ struct i2c_client c2;
+
+ dprintk(1,"Attempting special probe at 0x%x\n", probe[i]);
+
+ memset (&c2, 0, sizeof(c2));
+ c2.adapter = c.adapter;
+
+ /* Find a device that responds. If none found, oh well. */
+ for (c2.addr=127; c2.addr >= 0; c2.addr--)
+ {
+ if (0 == i2c_master_recv(&c2,&buf,0)) {
+ dprintk(1,"found another device, at addr 0x%02x\n", c2.addr);
+ break;
+ }
+ }
+
+ /* Now do the probe. The controller does not respond
+ to 0-byte reads, so we use a 1-byte read instead. */
+ rc = i2c_master_recv(&c,&buf,1);
+ rc--;
+ }
+ else
+ {
+ rc = i2c_master_recv(&c,&buf,0);
+ }
+
dprintk(1,"probe 0x%02x @ %s: %s\n",
probe[i], adap->name,
(0 == rc) ? "yes" : "no");
diff -rup /usr/src/a/linux/drivers/media/video/saa7134/saa7134-cards.c /usr/src/b/linux/drivers/media/video/saa7134/saa7134-cards.c
--- /usr/src/a/linux/drivers/media/video/saa7134/saa7134-cards.c 2006-09-17 15:47:30.000000000 +0000
+++ /usr/src/b/linux/drivers/media/video/saa7134/saa7134-cards.c 2006-09-17 12:46:37.000000000 +0000
@@ -3799,6 +3799,7 @@ int saa7134_board_init1(struct saa7134_d
break;
/* i2c remotes */
case SAA7134_BOARD_PINNACLE_PCTV_110i:
+ case SAA7134_BOARD_KWORLD_ATSC110:
case SAA7134_BOARD_UPMOST_PURPLE_TV:
dev->has_remote = SAA7134_REMOTE_I2C;
break;
diff -rup /usr/src/a/linux/drivers/media/video/saa7134/saa7134-i2c.c /usr/src/b/linux/drivers/media/video/saa7134/saa7134-i2c.c
--- /usr/src/a/linux/drivers/media/video/saa7134/saa7134-i2c.c 2006-09-17 15:47:30.000000000 +0000
+++ /usr/src/b/linux/drivers/media/video/saa7134/saa7134-i2c.c 2006-09-17 12:47:59.000000000 +0000
@@ -351,6 +351,8 @@ static int attach_inform(struct i2c_clie
switch (client->addr) {
case 0x7a:
case 0x47:
+ case 0xc2:
+ case 0x30:
{
struct IR_i2c *ir = i2c_get_clientdata(client);
d1printk("%s i2c IR detected (%s).\n",
diff -rup /usr/src/a/linux/drivers/media/video/saa7134/saa7134-input.c /usr/src/b/linux/drivers/media/video/saa7134/saa7134-input.c
--- /usr/src/a/linux/drivers/media/video/saa7134/saa7134-input.c 2006-09-17 15:47:30.000000000 +0000
+++ /usr/src/b/linux/drivers/media/video/saa7134/saa7134-input.c 2006-09-17 13:08:17.000000000 +0000
@@ -113,6 +113,49 @@ static int get_key_purpletv(struct IR_i2
return 1;
}

+static int get_key_kworld_atsc110(struct IR_i2c *ir, u32 *ir_key, u32 *ir_raw)
+{
+ unsigned char b;
+ int rc;
+ int gpio;
+
+
+ /* We need this to access GPIO. Used by the saa_readl macro. */
+ struct saa7134_dev *dev = ir->c.adapter->algo_data;
+ if (dev == NULL) {
+ dprintk ("ir->c.adapter->algo_data is NULL!\n");
+ return -EIO;
+ }
+
+ /* rising SAA7134_GPIO_GPRESCAN reads the status */
+ saa_clearb(SAA7134_GPIO_GPMODE3,SAA7134_GPIO_GPRESCAN);
+ saa_setb(SAA7134_GPIO_GPMODE3,SAA7134_GPIO_GPRESCAN);
+
+ gpio = saa_readl(SAA7134_GPIO_GPSTATUS0 >> 2);
+
+ if (gpio & 0x100)
+ return 0; /* No button press */
+
+
+ /* GPIO says there is a button press. Get it. */
+ if (1 != (rc=i2c_master_recv(&ir->c,&b,1))) {
+ dprintk("read error %d\n", rc);
+ return -EIO;
+ }
+
+ /* No button press */
+ if (b == 0xFF)
+ return 0;
+
+ /* repeating */
+ if (b & 0x80)
+ return 1;
+
+ *ir_key = b;
+ *ir_raw = b;
+ return 1;
+}
+
void saa7134_input_irq(struct saa7134_dev *dev)
{
struct saa7134_ir *ir = dev->remote;
@@ -181,6 +224,12 @@ int saa7134_input_init1(struct saa7134_d
break;
case SAA7134_BOARD_MD2819:
case SAA7134_BOARD_KWORLD_VSTREAM_XPERT:
+ case SAA7134_BOARD_KWORLD_ATSC110:
+ ir_codes = ir_codes_kworld_atsc110;
+ mask_keycode = 0x0;
+ mask_keydown = 0x0;
+ polling = 50; // ms
+ break;
case SAA7134_BOARD_AVERMEDIA_305:
case SAA7134_BOARD_AVERMEDIA_307:
case SAA7134_BOARD_AVERMEDIA_STUDIO_305:
@@ -346,6 +395,11 @@ void saa7134_set_i2c_ir(struct saa7134_d
ir->get_key = get_key_purpletv;
ir->ir_codes = ir_codes_purpletv;
break;
+ case SAA7134_BOARD_KWORLD_ATSC110:
+ snprintf(ir->c.name, sizeof(ir->c.name), "Kworld ATSC110");
+ ir->get_key = get_key_kworld_atsc110;
+ ir->ir_codes = ir_codes_kworld_atsc110;
+ break;
default:
dprintk("Shouldn't get here: Unknown board %x for I2C IR?\n",dev->board);
break;
diff -rup /usr/src/a/linux/include/media/ir-common.h /usr/src/b/linux/include/media/ir-common.h
--- /usr/src/a/linux/include/media/ir-common.h 2006-09-17 15:47:30.000000000 +0000
+++ /usr/src/b/linux/include/media/ir-common.h 2006-09-17 12:57:33.000000000 +0000
@@ -92,6 +92,7 @@ extern IR_KEYTAB_TYPE ir_codes_hauppauge
extern IR_KEYTAB_TYPE ir_codes_npgtech[IR_KEYTAB_SIZE];
extern IR_KEYTAB_TYPE ir_codes_norwood[IR_KEYTAB_SIZE];
extern IR_KEYTAB_TYPE ir_codes_proteus_2309[IR_KEYTAB_SIZE];
+extern IR_KEYTAB_TYPE ir_codes_kworld_atsc110[IR_KEYTAB_SIZE];

#endif


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 29, 2006 5:05 pm 
Offline
Joined: Thu Dec 01, 2005 12:46 am
Posts: 135
Atamido wrote:
File name, size, and MD5 would be nice.


2a7e38d3ebc392264f840dcb89e08829 /usr/src/linux-source-2.6.18/Documentation/dvb/dvb-fe-nxt2004.fw

Dwaine


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 29, 2006 5:09 pm 
Offline
Joined: Fri Nov 18, 2005 9:22 am
Posts: 777
Location: spencerport, ny (USA)
dwaine wrote:
Can people try unloading saa7134 and then manually loading both saa7134 and saa7134-dvb. Get back to this thread with the results.


Here's what I get:

Code:
saa7130/34: v4l2 driver version 0.2.14 loaded
saa7133[0]: found at 0000:01:06.0, rev: 240, irq: 21, latency: 32, mmio: 0xfdfff000
saa7133[0]: subsystem: 17de:7350, board: Kworld ATSC110 [card=90,autodetected]
saa7133[0]: board init: gpio is 100
saa7133[0]: i2c eeprom 00: de 17 50 73 ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
nxt200x: NXT2004 Detected
DVB: registering new adapter (saa7133[0]).
DVB: registering frontend 2 (Nextwave NXT200X VSB/QAM frontend)...


It's my 3rd card, so maybe that's why it says "frontend 2". But I don't see the firmware upload message.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 29, 2006 5:11 pm 
Offline
Joined: Fri Nov 18, 2005 9:22 am
Posts: 777
Location: spencerport, ny (USA)
dwaine wrote:
2a7e38d3ebc392264f840dcb89e08829 /usr/src/linux-source-2.6.18/Documentation/dvb/dvb-fe-nxt2004.fw


The mdsum matches mine, which I found tucked away in the system somewhere, so apparently it's the right one. That's good, anyway.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 29, 2006 5:30 pm 
Offline
Joined: Thu Dec 01, 2005 12:46 am
Posts: 135
thornsoft wrote:
dwaine wrote:
Can people try unloading saa7134 and then manually loading both saa7134 and saa7134-dvb. Get back to this thread with the results.


Here's what I get:

Code:
saa7130/34: v4l2 driver version 0.2.14 loaded
saa7133[0]: found at 0000:01:06.0, rev: 240, irq: 21, latency: 32, mmio: 0xfdfff000
saa7133[0]: subsystem: 17de:7350, board: Kworld ATSC110 [card=90,autodetected]
saa7133[0]: board init: gpio is 100
saa7133[0]: i2c eeprom 00: de 17 50 73 ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
nxt200x: NXT2004 Detected
DVB: registering new adapter (saa7133[0]).
DVB: registering frontend 2 (Nextwave NXT200X VSB/QAM frontend)...


It's my 3rd card, so maybe that's why it says "frontend 2". But I don't see the firmware upload message.


You should be good to go. Now just setup the card with mythtv-frontend.

Dwaine


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 29, 2006 5:48 pm 
Offline
Joined: Mon Apr 24, 2006 8:30 am
Posts: 91
Location: Pittsburgh, PA
BRAVO! worked for me, too.

now... could someone point me to instructions on how to apply that remote control patch?

thanks again!


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 29, 2006 7:07 pm 
Offline
Joined: Thu Dec 01, 2005 12:46 am
Posts: 135
lostmyshape wrote:
BRAVO! worked for me, too.

now... could someone point me to instructions on how to apply that remote control patch?

thanks again!


I just manually do it and then recompile v4l. The patch was whipped up a couple of months ago, and I have not removed the repeat function and also the issue with the same address as KNC1 cards. I'm not sure that the patch will cleanly apply to a recent v4l/dvb cvs.

The remote patch works great though...


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 79 posts ] 
Go to page Previous  1, 2, 3, 4, 5, 6  Next



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu