From: Mijhail Moreyra <mijhail.moreyra@gmail.com>
To: Steven Toth <stoth@linuxtv.org>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH] cx23885 analog TV and audio support for HVR-1500
Date: Fri, 29 Aug 2008 14:52:01 -0500 [thread overview]
Message-ID: <48B85361.6020508@gmail.com> (raw)
In-Reply-To: <48B4FB50.3020200@linuxtv.org>
Steven Toth wrote:
> Mijhail,
>
> http://linuxtv.org/hg/~stoth/cx23885-audio
>
> This tree contains your patch with some minor whitespace cleanups and
> fixes for HUNK related merge issues due to the patch wrapping at 80 cols.
>
> Please build this tree and retest in your environment to ensure I did
> not break anything. Does this tree still work OK for you?
>
> After this I will apply some other minor cleanups then invite a few
> other HVR1500 owners to begin testing.
>
> Thanks again.
>
> Regards,
>
> Steve
Hi, sorry for the delay.
I've tested the http://linuxtv.org/hg/~stoth/cx23885-audio tree and it
doesn't work well.
You seem to have removed a piece from my patch that avoids some register
modification in cx25840-core.c:cx23885_initialize()
- cx25840_write(client, 0x2, 0x76);
+ if (state->rev != 0x0000) /* FIXME: How to detect the bridge
type ??? */
+ /* This causes image distortion on a true cx23885 board */
+ cx25840_write(client, 0x2, 0x76);
As the patch says that register write causes a horrible image distortion
on my HVR-1500 which has a real cx23885 (not 23887, 23888, etc) board.
I don't know if it's really required for any bridge as everything seems
to be auto-configured by default, maybe it can be simply dropped.
Other than that the cx23885-audio tree works well.
WRT the whitespaces, 80 cols, etc; most are also in the sources I took
as basis, so I didn't think they were a problem.
Regards,
Mijhail Moreyra
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-08-29 19:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 20:33 [linux-dvb] [PATCH] cx23885 analog TV and audio support for HVR-1500 Mijhail Moreyra
2008-08-26 20:53 ` Steven Toth
2008-08-26 21:03 ` Mijhail Moreyra
2008-08-26 22:01 ` Steven Toth
2008-08-26 23:18 ` Mijhail Moreyra
2008-08-27 6:59 ` Steven Toth
2008-08-29 19:52 ` Mijhail Moreyra [this message]
2008-08-29 19:55 ` Steven Toth
2008-08-29 20:17 ` Mijhail Moreyra
2008-08-29 20:19 ` Steven Toth
-- strict thread matches above, loose matches on Subject: below --
2008-08-29 21:01 Tim Lucas
2008-08-29 21:56 ` Steven Toth
2008-08-30 0:41 ` Steven Toth
2008-08-30 18:11 ` Mijhail Moreyra
[not found] ` <e32e0e5d0808301411w1ae01563y65ce27d6c43e2beb@mail.gmail.com>
[not found] ` <e32e0e5d0808301456v4b5ca363l5a121b426438bd64@mail.gmail.com>
2008-08-31 22:04 ` Steven Toth
[not found] ` <e32e0e5d0809012006j72eb10e5r80ccf7e3211b8ee7@mail.gmail.com>
2008-09-02 16:08 ` Steven Toth
2008-09-03 2:28 ` Tim Lucas
2008-08-29 22:14 ` Michael Krufky
2008-08-29 23:02 ` Dustin Coates
2008-08-30 0:26 ` Michael Krufky
2008-08-30 0:30 ` Dustin Coates
2008-08-30 0:34 ` Steven Toth
2008-08-30 0:24 ` Mijhail Moreyra
2008-09-04 23:25 Tim Lucas
2008-09-05 13:22 ` Steven Toth
2008-09-05 14:31 Tim Lucas
2008-09-06 21:24 ` Tim Lucas
2008-09-08 23:22 ` Tim Lucas
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=48B85361.6020508@gmail.com \
--to=mijhail.moreyra@gmail.com \
--cc=linux-dvb@linuxtv.org \
--cc=stoth@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