Hauppauge WinTV-NOVA-T-500 New Firmware (dvb-usb-dib0700-1.20.fw) causes problems
I have been using the dvb-usb-dib0700-1.10.fw firmware for the past month with no issues. After following the instructions on
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 and updating the firmware to dvb-usb-dib0700-1.20.fw the card was no longer useable. When using Mythbuntu backend the card was not detected correctly and gave an unknown error. Rolling back to dvb-usb-dib0700-1.10.fw corrected the problem.
Tom
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
2008/8/28 Thomas Goerke <[email protected]>:
Quoted 7 lines
I have been using the dvb-usb-dib0700-1.10.fw firmware for the past month with no issues. After following the instructions on
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 and updating the firmware to dvb-usb-dib0700-1.20.fw the card was no longer useable. When using Mythbuntu backend the card was not detected correctly and gave an unknown error. Rolling back to dvb-usb-dib0700-1.10.fw corrected the problem.
Well I'm glad the 1.20 support didn't just get checked in then. Thanks for doing this testing.
Do you happen to have the dmesg output from the failed attempt, which might have information on the nature of the failure? I would like to get to the bottom of the issue.
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 5 lines · Thomas Goerke
After following the instructions on
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 and updating the firmware to dvb-usb-dib0700-1.20.fw the card was no longer useable. When using Mythbuntu backend the card was not detected correctly and gave an unknown error.
Weird, once I cleaned up my fw files, things went very well with MythTV using fw 1.20, no reconfig or anything else needed.
Nico
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
On Thu, Aug 28, 2008 at 12:33 PM, Nicolas Will <[email protected]>
Quoted 2 lines
Weird, once I cleaned up my fw files, things went very well with MythTV using fw 1.20, no reconfig or anything else needed.
Just to be clear, Nicolas, are you using a WinTV NOVA-T 500? This could be an issue with Thomas's particular product if your experience is based on a different product.
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 8 lines · Devin Heitmueller
On Thu, Aug 28, 2008 at 12:33 PM, Nicolas Will <[email protected]>
Quoted 1 line
Weird, once I cleaned up my fw files, things went very well with
MythTV
Quoted 1 line
using fw 1.20, no reconfig or anything else needed.
Just to be clear, Nicolas, are you using a WinTV NOVA-T 500? This could be an issue with Thomas's particular product if your experience is based on a different product.
yup, Nova-T 500.
System here:
http://www.youplala.net/linux/home-theater-pc
Nico
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 10 lines
Well I'm glad the 1.20 support didn't just get checked in then. Thanks for doing this testing.
Do you happen to have the dmesg output from the failed attempt, which might have information on the nature of the failure? I would like to get to the bottom of the issue.
Devin
Devin, I looked at the dmesg output and it showed no errors. So I tested it again using both symbolic link and hard copy. This time it worked correctly. I am not sure what was causing the problem before but rolling back to the .10 definitely fixed it. Apologies for the multicast on this but all seems ok now using the .20 firmware.
Tom
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 5 lines · Thomas Goerke
Devin, I looked at the dmesg output and it showed no errors. So I tested it again using both symbolic link and hard copy. This time it worked correctly. I am not sure what was causing the problem before but rolling back to the .10 definitely fixed it. Apologies for the multicast on this but all seems ok now using the .20 firmware.
Hmmm... You're the second person to see that behavior. Weird.
Did you apply the patch I sent out for the driver as well, or did you just replace the firmware file?
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 6 lines
Hmmm... You're the second person to see that behavior. Weird.
Did you apply the patch I sent out for the driver as well, or did you just replace the firmware file?
Quoted 7 lines
Devin
--
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller
Devin,
I did a little more debugging and it seems that the I still have a problem with the .20 version. However, you only see it after a cold reset ie when you need to load the firmware. See below for the first dmesg which is with the .20 firmware. As you can see the card is found but only in a cold state. The second dmesg is with the .10 firmware and the card is found firstly in a cold state and then in a warm state. Each of these dmesg outputs have been after a power off from the power supply for 10 seconds ie no power to backplane.
.20 Firmware - Not working:
[ 33.016231] dib0700: loaded with support for 7 different device-types [ 33.016463] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware -- [ 33.071378] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' [ 33.080751] input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1a.2-2.3 [ 33.080763] usbcore: registered new interface driver usbhid [ 33.080771] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver [ 33.277932] usbcore: registered new interface driver dvb_usb_dib0700 [ 33.611862] lp: driver loaded but no devices found [ 33.656757] w83627ehf: Found W83627DHG chip at 0x290 [ 33.679680] coretemp coretemp.0: Using undocumented features, absolute temperature might be wrong! [ 33.679707] coretemp coretemp.1: Using undocumented features, absolute temperature might be wrong! [ 33.889981] Adding 9847804k swap on /dev/sda5. Priority:-1 extents:1 across:9847804k [ 34.561845] EXT3 FS on sda1, internal journal
.10 Firmware Working:
[ 32.242798] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware [ 32.275449] Linux video capture interface: v2.00 -- [ 32.316276] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' -- [ 32.659286] dib0700: firmware started successfully. -- [ 33.159764] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. [ 33.159793] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 33.159925] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 33.273283] DVB: registering frontend 1 (DiBcom 3000MC/P)... [ 33.312133] MT2060: successfully identified (IF1 = 1258) [ 33.786468] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 33.786660] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 33.792214] DVB: registering frontend 2 (DiBcom 3000MC/P)... [ 33.796959] MT2060: successfully identified (IF1 = 1255) [ 34.352045] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1e.0/0000:05:00.2/usb9/9-1/input/input6 [ 34.378748] dvb-usb: schedule remote query interval to 150 msecs. [ 34.378750] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully
initialized and connected.
Files:
ls -al /lib/firmware
-rw-r--r-- 1 root root 34306 2008-08-29 07:38 dvb-usb-dib0700-1.10.fw -rw-r--r-- 1 root root 34306 2008-08-28 09:11
dvb-usb-dib0700-1.10.fw.original
-rw-r--r-- 1 root root 33768 2008-08-28 09:10 dvb-usb-dib0700-1.20.fw
I have not applied the patch as I followed instructions on
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 which doesnt mention this. I am using the latest v4l-dvb source.
I can apply the patch to test if required. Can you please let me know where this is and I will try it.
Tom
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 8 lines · Thomas Goerke
I did a little more debugging and it seems that the I still have a problem with the .20 version. However, you only see it after a cold reset ie when you need to load the firmware. See below for the first dmesg which is with the .20 firmware. As you can see the card is found but only in a cold state. The second dmesg is with the .10 firmware and the card is found firstly in a cold state and then in a warm state. Each of these dmesg outputs have been after a power off from the power supply for 10 seconds ie no power to backplane.
Wow, that's so early in the loading process for the device, it's hard to see how that can have anything to do with my i2c changes.
Patrick, do you have any changelogs that describe the differences between 1.10 and 1.20 other than the addition of the new i2c API?
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 7 lines
Wow, that's so early in the loading process for the device, it's hard to see how that can have anything to do with my i2c changes.
Patrick, do you have any changelogs that describe the differences between 1.10 and 1.20 other than the addition of the new i2c API?
Quoted 6 lines
Devin
--
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller
Devin,
I have applied the latest patch, swapped back to the .20firmware and now get the following output from dmesg:
[ 32.161603] Linux video capture interface: v2.00 -- [ 32.407733] dib0700: loaded with support for 7 different device-types [ 32.408042] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware [ 32.451939] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' [ 32.654066] dib0700: firmware started successfully. [ 33.157310] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. [ 33.157342] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 33.157430] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 33.221594] dib0700: i2c write error (status = -32) [ 33.221595] [ 33.225841] dib0700: i2c write error (status = -32) [ 33.225841] [ 33.237332] DVB: registering frontend 0 (DiBcom 3000MC/P)... [ 33.237582] dib0700: i2c write error (status = -32) [ 33.237582] [ 33.282556] dib0700: i2c write error (status = -32) [ 33.282557] [ 33.282559] mt2060 I2C read failed [ 33.282587] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 33.282867] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 33.284802] DVB: registering frontend 1 (DiBcom 3000MC/P)... [ 33.285055] dib0700: i2c write error (status = -32) [ 33.285056] [ 33.286178] dib0700: i2c write error (status = -32) [ 33.286179] [ 33.286180] mt2060 I2C read failed [ 33.286242] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1e.0/0000:05:00.2/usb6/6-1/input/input6 [ 33.333182] dvb-usb: schedule remote query interval to 150 msecs. [ 33.333186] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected. [ 33.333286] usbcore: registered new interface driver dvb_usb_dib0700
Please note that the tuners are available within MythTV but are unable to tune to any channel.
Tom
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 2 lines · Thomas Goerke
I have applied the latest patch, swapped back to the .20firmware and now get the following output from dmesg:
<snip>
Ok, so it looks like there are i2c errors accessing the dib3000 and mt2060. That's bad, but at least it's exercising the new code.
Let me look at the code and see what I can find out.
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 2 lines · Thomas Goerke
I have applied the latest patch, swapped back to the .20firmware and now get the following output from dmesg:
Let's try this to rule out whether it's the new i2c interface or some other aspect of the 1.20 firmware:
Add the following line to the dib0700_devices.c at line 78:
st->fw_use_legacy_i2c_api = 1;
It should end up looking like:
=======
static int bristol_frontend_attach(struct dvb_usb_adapter *adap)
{
struct dib0700_state *st = adap->dev->priv;
st->fw_use_legacy_i2c_api = 1;
if (adap->id == 0) {....
=======
That will tell it to fall back to the legacy i2c interface (which was working fine for you in the 1.10 firmware).
Make that change, reboot your system, and send me the dmesg output so we can see if you still get i2c errors.
Thanks,
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 26 lines
Let's try this to rule out whether it's the new i2c interface or some other aspect of the 1.20 firmware:
Add the following line to the
dib0700_devices.cat line 78:
st->fw_use_legacy_i2c_api= 1;It should end up looking like:
=======
static intbristol_frontend_attach(struct dvb_usb_adapter *adap){ struct dib0700_state *st = adap->dev->priv; st->fw_use_legacy_i2c_api = 1; if (adap->id == 0) {....
=======That will tell it to fall back to the legacy i2c interface (which was working fine for you in the 1.10 firmware).
Make that change, reboot your system, and send me the dmesg output so we can see if you still get i2c errors.
Quoted 7 lines
Thanks,
Devin
--
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller
Devin,
See output below. Tuners are now working correctly with MythTV.
[ 32.498881] dib0700: loaded with support for 7 different device-types [ 32.498961] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware -- [ 32.537956] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' -- [ 32.778909] dib0700: firmware started successfully. [ 33.281095] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. [ 33.281127] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 33.281295] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 33.390157] DVB: registering frontend 0 (DiBcom 3000MC/P)... [ 33.448122] MT2060: successfully identified (IF1 = 1258) [ 33.923079] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 33.923271] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 33.928451] DVB: registering frontend 1 (DiBcom 3000MC/P)... [ 33.932949] MT2060: successfully identified (IF1 = 1255) [ 34.416827] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1e.0/0000:05:00.2/usb11/11-1/input/input6 [ 34.444154] dvb-usb: schedule remote query interval to 150 msecs. [ 34.444157] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected. [ 34.444269] usbcore: registered new interface driver dvb_usb_dib0700
--
FYI copy of code that I edited (dib0700_devices.c)
static int bristol_frontend_attach(struct dvb_usb_adapter *adap)
{
struct dib0700_state *st = adap->dev->priv;
st->fw_use_legacy_i2c_api = 1;
if (adap->id == 0) {
dib0700_set_gpio(adap->dev, GPIO6, GPIO_OUT, 0);
msleep(10);
dib0700_set_gpio(adap->dev, GPIO6, GPIO_OUT, 1);
msleep(10);
dib0700_set_gpio(adap->dev, GPIO10, GPIO_OUT, 0);
msleep(10);
dib0700_set_gpio(adap->dev, GPIO10, GPIO_OUT, 1);msleep(10);
if (force_lna_activation)
dib0700_set_gpio(adap->dev, GPIO0, GPIO_OUT, 1);
else
dib0700_set_gpio(adap->dev, GPIO0, GPIO_OUT, 0);
if (dib3000mc_i2c_enumeration(&adap->dev->i2c_adap, 2,
DEFAULT_DIB3000P_I2C_ADDRESS, bristol_dib3000mc_config) != 0) {
dib0700_set_gpio(adap->dev, GPIO6, GPIO_OUT, 0);
msleep(10);
return -ENODEV;
}
}
st->mt2060_if1[adap->id] = 1220;
return (adap->fe = dvb_attach(dib3000mc_attach,
&adap->dev->i2c_adap,
(10 + adap->id) << 1, &bristol_dib3000mc_config[adap->id]))== NULL ? -ENODEV : 0;
}
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 3 lines · Thomas Goerke
Devin,
See output below. Tuners are now working correctly with MythTV.
Well that's promising. Could you please reboot the system a few times and test both cold and warm starts so you are comfortable that everything is working?
Once you're confident everything works, could you please try the following:
1. Comment out the "st->fw_use_legacy_i2c_api = 1" line you added in the previous email
2. Add "| I2C_M_NOSTART" to line 46 of mt2060.c so it looks like the following:
{ .addr = priv->cfg->i2c_address, .flags = I2C_M_RD | I2C_M_NOSTART, .buf = val, .len = 1 },
make, make install, reboot
Then let me know if the dmesg output contains i2c errors (and send the output if it does).
We're getting close here....
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 21 lines
Well that's promising. Could you please reboot the system a few times and test both cold and warm starts so you are comfortable that everything is working?
Once you're confident everything works, could you please try the following:
1. Comment out the "
st->fw_use_legacy_i2c_api= 1" line you added in the previous email
2. Add "|I2C_M_NOSTART" to line 46 ofmt2060.cso it looks like the following:{ .addr =
priv->cfg->i2c_address, .flags =I2C_M_RD|I2C_M_NOSTART, .buf = val, .len = 1 },make, make install, reboot
Then let me know if the dmesg output contains i2c errors (and send the output if it does).
Quoted 8 lines
We're getting close here....
Devin
--
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller
Devin,
See below for dmesg o/p with i2c errors.
[ 31.882627] dib0700: loaded with support for 7 different device-types [ 31.882929] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware -- [ 31.929078] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' -- [ 32.130509] dib0700: firmware started successfully. [ 32.632225] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. [ 32.632258] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 32.632400] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 32.696537] dib0700: i2c write error (status = -32) [ 32.696539] [ 32.700785] dib0700: i2c write error (status = -32) [ 32.700786] [ 32.712278] DVB: registering frontend 0 (DiBcom 3000MC/P)... [ 32.712527] dib0700: i2c write error (status = -32) [ 32.712527] [ 32.748254] dib0700: i2c write error (status = -32) [ 32.748256] [ 32.748258] mt2060 I2C read failed [ 32.748286] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 32.748570] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 32.750502] DVB: registering frontend 1 (DiBcom 3000MC/P)... [ 32.750775] dib0700: i2c write error (status = -32) [ 32.750776] [ 32.751879] dib0700: i2c write error (status = -32) [ 32.751880] [ 32.751882] mt2060 I2C read failed [ 32.751962] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1e.0/0000:05:00.2/usb9/9-1/input/input6 [ 32.793080] dvb-usb: schedule remote query interval to 150 msecs. [ 32.793084] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully
initialized and connected.
--
Copy of file (mt2060.c) modifications:
static int mt2060_readreg(struct mt2060_priv *priv, u8 reg, u8 *val)
{
struct i2c_msg msg[2] = {
{ .addr = priv->cfg->i2c_address, .flags = 0, .buf =
®, .len = 1 },
{ .addr = priv->cfg->i2c_address, .flags = I2C_M_RD |
I2C_M_NOSTART, .buf = val, .len = 1 },
};
if (i2c_transfer(priv->i2c, msg, 2) != 2) {
printk(KERN_WARNING "mt2060 I2C read failed\n");
return -EREMOTEIO;
}
return 0;
}Tom
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 1 line · Thomas Goerke
See below for dmesg o/p with i2c errors.
Thanks for doing this test. I've done some additional reading which suggests the mt2060 has an extended history of flaky i2c behavior. Given that I don't have the hardware, I don't think I'm going to be able to debug it further. I'm going to submit to have that device fall back to the legacy interface, so it shouldn't be any worse with 1.20, but at least it won't block other devices that use 1.20 from being committed.
Thanks,
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 11 lines
Thanks for doing this test. I've done some additional reading which suggests the mt2060 has an extended history of flaky i2c behavior. Given that I don't have the hardware, I don't think I'm going to be able to debug it further. I'm going to submit to have that device fall back to the legacy interface, so it shouldn't be any worse with 1.20, but at least it won't block other devices that use 1.20 from being committed.
Thanks,
Quoted 7 lines
Devin
--
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller
OK np. For the time being I will roll back to the .10 firmware and use the v4l-dvb tree. I am not sure of then benefit of the .20 firmware as the .10 version has been very stable.
Let me know in the future if you want any additional testing.
Tom
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 8 lines
OK np. For the time being I will roll back to the .10 firmware and use the
v4l-dvb tree. I am not sure of then benefit of the .20 firmware as the .10
version has been very stable.Let me know in the future if you want any additional testing.
Quoted 7 lines
Tom
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Devin,
Is it worth updating
(http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#Firmware) to include some information related to having to use the patched source code if using the .20 firmware?
Tom
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 6 lines · Thomas Goerke
Devin,
Is it worth updating
(http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#Firmware) to include some information related to having to use the patched source code if using the .20 firmware?
Average users probably shouldn't be using the 1.20 firmware until the patch is checked in to the v4l-dvb, so we can control which devices use 1.20 and the new i2c functionality (based on actual testing).
My original plan was to keep everybody at 1.10 in the initial patch, and once maintainers of individual devices tested 1.20, they could submit a patch to make that the default for said device. Patrick felt strongly that 1.20 should be a drop-in replacement for 1.20, but based on this evening's experience I'm thinking we should go back to my original plan.
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Honestly spoken I never tried the 1.20 firmware on the NOVA-T 500. (This card was last used in DiBcom 3 years ago.)
It might be that using the new i2c-requests along with the I2C-master do not work with some boards.
In that case you can still use the new i2c-requests but you need to select the gpio-bus instead of the i2c-master-bus.
Patrick.
Quoted 10 lines · Devin Heitmueller
Quoted 8 lines · Thomas Goerke
I did a little more debugging and it seems that the I still have a problem with the .20 version. However, you only see it after a cold reset ie when you need to load the firmware. See below for the first dmesg which is with the .20 firmware. As you can see the card is found but only in a cold state. The second dmesg is with the .10 firmware and the card is found firstly in a cold state and then in a warm state. Each of these dmesg outputs have been after a power off from the power supply for 10 seconds ie no power to backplane.
Quoted 13 lines
Wow, that's so early in the loading process for the device, it's hard to see how that can have anything to do with my i2c changes.
Patrick, do you have any changelogs that describe the differences between 1.10 and 1.20 other than the addition of the new i2c API?
Devin
Signature · 3 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 8 lines · Patrick Boettcher
Honestly spoken I never tried the 1.20 firmware on the NOVA-T 500. (This card was last used in DiBcom 3 years ago.)
It might be that using the new i2c-requests along with the I2C-master do not work with some boards.
In that case you can still use the new i2c-requests but you need to select the gpio-bus instead of the i2c-master-bus.
Do you think we would need to use the gpio-bus for all requests within the device, or only for talking to the mt2060? If it's device-wide, I can just add another flag to dib0700_state, otherwise I'm not sure what I'm going to have to do here.
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb