From: Mark Zimmerman <markzimm@frii.com>
To: linux-media@vger.kernel.org
Subject: Re: DViCO FusionHDTV7 Dual Express I2C write failed
Date: Wed, 19 Jan 2011 10:39:46 -0700 [thread overview]
Message-ID: <20110119173946.GA64847@io.frii.com> (raw)
In-Reply-To: <AANLkTi=FFV8CWrBU-20huQRDysTPWGaen2mtP2sBQJef@mail.gmail.com>
On Wed, Jan 19, 2011 at 09:22:28AM -0800, VDR User wrote:
> On Wed, Jan 19, 2011 at 8:13 AM, Devin Heitmueller
> <dheitmueller@kernellabs.com> wrote:
> >> Can someone please look into this and possibly provide a fix for the
> >> bug? ??I'm surprised it hasn't happened yet after all this time but
> >> maybe it's been forgotten the bug existed.
> >
> > You shouldn't be too surprised. ??In many cases device support for more
> > obscure products comes not from the maintainer of the actual driver
> > but rather from some random user who hacked in an additional board
> > profile (in many cases, not doing it correctly but good enough so it
> > "works for them"). ??In cases like that, the changes get committed, the
> > original submitter disappears, and then when things break there is
> > nobody with the appropriate knowledge and the hardware to debug the
> > problem.
>
> Good point. My understanding is that this is a fairly common card so
> I wouldn't think that would be the case. At any rate, hopefully we'll
> be able to narrow down the cause of the problem and get it fixed.
>
Were there changes to i2c between 2.6.35 and 2.6.36 that are missing
from the xc5000 driver? If so, is there another driver that has the
required updates so I can look at what changed? I would like to get
some traction on this but I really don't know where to start.
Thanks,
-- Mark
next prev parent reply other threads:[~2011-01-19 17:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101207190753.GA21666@io.frii.com>
2011-01-10 2:14 ` DViCO FusionHDTV7 Dual Express I2C write failed Mark Zimmerman
2011-01-19 15:59 ` VDR User
2011-01-19 16:13 ` Devin Heitmueller
2011-01-19 17:22 ` VDR User
2011-01-19 17:39 ` Mark Zimmerman [this message]
2011-01-24 15:49 ` Mark Zimmerman
2011-01-24 15:57 ` Devin Heitmueller
2011-01-25 14:27 ` Mark Zimmerman
2011-01-19 19:01 ` Timothy D. Lenz
2011-01-17 23:12 ` Timothy D. Lenz
2011-02-12 15:29 ` [get-bisect results]: " Mark Zimmerman
2011-02-12 16:27 ` Andy Walls
2011-02-12 16:36 ` Mark Zimmerman
2011-02-12 16:46 ` Andy Walls
2011-02-12 17:03 ` Mark Zimmerman
2011-02-12 19:05 ` Mark Zimmerman
2011-02-12 20:48 ` Andy Walls
2011-02-13 14:47 ` [corrected get-bisect " Mark Zimmerman
2011-02-13 14:52 ` Devin Heitmueller
2011-02-13 20:26 ` Mark Zimmerman
2011-02-13 21:26 ` Andy Walls
2011-02-14 0:16 ` Andy Walls
2011-02-14 14:29 ` Devin Heitmueller
2011-02-14 0:37 ` Mark Zimmerman
2011-02-14 8:05 ` Jean Delvare
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=20110119173946.GA64847@io.frii.com \
--to=markzimm@frii.com \
--cc=linux-media@vger.kernel.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