All of lore.kernel.org
 help / color / mirror / Atom feed
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 11:29:59 +0800	[thread overview]
Message-ID: <008301c90987$866b3e60$9341bb20$@com.au> (raw)
In-Reply-To: <412bdbff0808281950r48f40835w3f81f506c32eaff3@mail.gmail.com>

> 
> 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
> 
> --
> 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 =
&reg, .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
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-08-29  3:29 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
2008-08-29  2:50                 ` Devin Heitmueller
2008-08-29  3:29                   ` Thomas Goerke [this message]
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='008301c90987$866b3e60$9341bb20$@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.