public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Will <nico@youplala.net>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] dib0700 new i2c implementation
Date: Wed, 27 Aug 2008 09:25:28 +0100	[thread overview]
Message-ID: <1219825528.7191.11.camel@acropora> (raw)
In-Reply-To: <617be8890808270010j640f4cb7je46e74c7234b978b@mail.gmail.com>

On Wed, 2008-08-27 at 09:10 +0200, Eduard Huguet wrote:
> 
>         ---------- Missatge reenviat ----------
>         From: "Devin Heitmueller" <devin.heitmueller@gmail.com>
>         To: linux-dvb <linux-dvb@linuxtv.org>
>         Date: Tue, 26 Aug 2008 21:15:20 -0400
>         Subject: [linux-dvb] dib0700 new i2c implementation
>         The attached patch implements the new dib0700 i2c API, which
>         requires
>         v1.20 of the firmware.  It addresses some classes of i2c
>         problems (in
>         particular the one I had where i2c reads were being sent onto
>         the bus
>         as i2c write calls)
>         
>         I would appreciate it if those with dib0700 based devices
>         would try
>         out the patch and provide feedback as to whether they have any
>         problems.  I've done testing with the Pinnacle PCTV HD Pro USB
>         801e
>         stick, but I don't have any other dib0700 based devices.
>         
>         Thanks to Patrick Boettcher for providing the firmware, sample
>         code,
>         and peer review of the first version of this patch.
> 
> Hi, 
>     Thanks for your work, first of all. ¿Do you think this patch might
> solve the problems that seem to be appeared since the new firmware is
> out with the Hauppauge Nova-T 500, like random reboots, etc... (what's
> ths state on this, anyway?) ?

Sorry I for my going AWOL...

I've spending most of my time out of my country of residence for a
project these last 6 months.

Testing is a bit difficult for me. My WAF goes down when I spent part of
the week end on the TV computer testing stuff instead of spending
quality time with the family.  Also, I do not want to leave the only TV
system in the house in an unstable state right before leaving for a
trip.

However, it seems that my problems with the 1.20 firmware were most
probably due to leftover 1.10 files scattered
around /lib/firmware/linux*.

I may be wrong and I did not spend much time on this, as I reverted to
1.10 before boarding yet another plane.

I may have experienced a remote control issue too.

But again, I did not take the time to properly sit in front of the
system and test things with a clear mind and some proper process.

Sorry.

Maybe this week-end.

> 
> I delayed the adoption of the new 1.20 firmware because of those
> problems, because I didn't want to leave the machine in a complete
> unusable state...

I hear you.

Nico


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  parent reply	other threads:[~2008-08-27  8:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27  7:10 [linux-dvb] dib0700 new i2c implementation Eduard Huguet
2008-08-27  8:24 ` Patrick Boettcher
2008-08-27  9:12   ` Eduard Huguet
2008-08-27 13:49     ` Devin Heitmueller
2008-08-27 14:02       ` Nicolas Will
2008-08-27 14:21       ` Eduard Huguet
2008-08-27  8:25 ` Nicolas Will [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-27  1:15 Devin Heitmueller

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=1219825528.7191.11.camel@acropora \
    --to=nico@youplala.net \
    --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