From: Mike <michael.stock@iinet.net.au>
To: linux-media@vger.kernel.org
Subject: Re: Bug in HVR1300. Found part of a patch, if reverted
Date: Thu, 12 May 2011 22:14:42 +0800 [thread overview]
Message-ID: <4DCBEB52.5060808@iinet.net.au> (raw)
Hi there
in the latest kernel (and all those since when the patch was written)
this patch is still required for the HVR-1300 to work, any chance of it
getting incorporated?
thanks
Mike
> Hi list,
>
> there seems to be a bug in cx88 (HVR1300) that is responsible for not
> switching channels, and not being able to scan.
> Complete description can be found on launchpad:
>
> https://bugs.launchpad.net/mythtv/+bug/439163 (starting from comment #16)
>
> Anyway, i digged it down to this patch:
> http://www.mail-archive.com/linuxtv-commits@xxxxxxxxxxx/msg02195.html
>
> When reverting the following part of the patch it starts working again:
>
> snip----------
>
> diff -r 576096447a45 -r d2eedb425718
> linux/drivers/media/video/cx88/cx88-dvb.c
> - --- a/linux/drivers/media/video/cx88/cx88-dvb.c Thu Dec 18 07:28:18
2008
> - -0200
> +++ b/linux/drivers/media/video/cx88/cx88-dvb.c Thu Dec 18 07:28:35 2008
> - -0200
> @@ -1135,40 +1135,44 @@ static int cx8802_dvb_advise_acquire(str
> * on the bus. Take the bus from the cx23416 and enable the
> * cx22702 demod
> */
> - - cx_set(MO_GP0_IO, 0x00000080); /* cx22702 out of reset and
> enable */
> + /* Toggle reset on cx22702 leaving i2c active */
> + cx_set(MO_GP0_IO, 0x00000080);
> + udelay(1000);
> + cx_clear(MO_GP0_IO, 0x00000080);
> + udelay(50);
> + cx_set(MO_GP0_IO, 0x00000080);
> + udelay(1000);
> + /* enable the cx22702 pins */
> cx_clear(MO_GP0_IO, 0x00000004);
> udelay(1000);
> break;
> - ---------snip
>
> Regards
>
> Frank Sagurna
next reply other threads:[~2011-05-12 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 14:14 Mike [this message]
2011-07-05 1:17 ` Bug in HVR1300. Found part of a patch, if reverted Devin Heitmueller
2011-07-09 17:12 ` Mike
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=4DCBEB52.5060808@iinet.net.au \
--to=michael.stock@iinet.net.au \
--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 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.