From: "Thomas Goerke" <tom@goeng.com.au>
To: "'Devin Heitmueller'" <devin.heitmueller@gmail.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Hauppauge WinTV-NOVA-T-500 New Firmware (dvb-usb-dib0700-1.20.fw) causes problems
Date: Fri, 29 Aug 2008 10:40:28 +0800 [thread overview]
Message-ID: <008201c90980$9b7ffd10$d27ff730$@com.au> (raw)
In-Reply-To: <412bdbff0808281905w1a76f8eald99de203fd0c18be@mail.gmail.com>
> 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
> --
> 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
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-08-29 2:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 15:17 [linux-dvb] Hauppauge WinTV-NOVA-T-500 New Firmware (dvb-usb-dib0700-1.20.fw) causes problems Thomas Goerke
2008-08-28 15:24 ` Devin Heitmueller
2008-08-28 23:24 ` Thomas Goerke
2008-08-28 23:38 ` Devin Heitmueller
2008-08-29 0:05 ` Thomas Goerke
2008-08-29 0:31 ` Devin Heitmueller
2008-08-29 0:54 ` Thomas Goerke
2008-08-29 1:24 ` Devin Heitmueller
2008-08-29 2:05 ` Devin Heitmueller
2008-08-29 2:40 ` Thomas Goerke [this message]
2008-08-29 2:50 ` Devin Heitmueller
2008-08-29 3:29 ` Thomas Goerke
2008-08-29 3:43 ` Devin Heitmueller
2008-08-29 3:49 ` Thomas Goerke
2008-08-29 4:25 ` Thomas Goerke
2008-08-29 4:44 ` Devin Heitmueller
2008-08-29 10:25 ` Patrick Boettcher
2008-08-29 13:26 ` Devin Heitmueller
2008-08-28 16:33 ` Nicolas Will
2008-08-28 17:18 ` Devin Heitmueller
2008-08-28 17:38 ` Nicolas Will
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='008201c90980$9b7ffd10$d27ff730$@com.au' \
--to=tom@goeng.com.au \
--cc=devin.heitmueller@gmail.com \
--cc=linux-dvb@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.