public inbox for linux-media@vger.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:49:12 +0800	[thread overview]
Message-ID: <008401c9098a$35ccf090$a166d1b0$@com.au> (raw)
In-Reply-To: <412bdbff0808282043y572a74b4o69fdc71a956131f0@mail.gmail.com>

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

  reply	other threads:[~2008-08-29  3:48 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
2008-08-29  3:43                     ` Devin Heitmueller
2008-08-29  3:49                       ` Thomas Goerke [this message]
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='008401c9098a$35ccf090$a166d1b0$@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox