All of lore.kernel.org
 help / color / mirror / Atom feed
From: "istvan_v@mailbox.hu" <istvan_v@mailbox.hu>
To: linux-media@vger.kernel.org
Subject: Re: [PATCH] DTV2000 H Plus issues
Date: Thu, 11 Mar 2010 00:17:15 +0100	[thread overview]
Message-ID: <4B98287B.4030506@mailbox.hu> (raw)
In-Reply-To: <4B7EEC92.1090004@mailbox.hu>

I have finally received some feedback on DVB-T, and it reportedly works,
although with a minor bug: it was necessary to use the "cable" connector
instead of the "antenna" one. There is an updated patch at the web page
http://www.sharemation.com/IstvanV/v4l/xc4000.html that attempts to
correct this problem. It also includes a few CX88 changes that are not
related to adding support for XC4000 based cards, and could possibly be
released as separate patches:
 - implements a "sharpness" control using the CX2388x peaking filter
   and changing the notch filter
 - in two places (cx88-core.c and cx88-video.c) code that checked for
   CX88_VMUX_TELEVISION did not also check for CX88_VMUX_CABLE; this
   was the reason why selecting the audio standard did not work for the
   cable input
 - in cx88-mpeg.c, there was code that set core->input to CX88_VMUX_DVB;
   this does not seem to make sense, since core->input is an index to an
   array (core->board.input), while the CX88_VMUX_* values are not
   intended to be used as indexes, but rather values of the 'type'
   member of struct cx88_input. But it is also not obvious if this has
   any actual effect other than what is reported as the current input
   when queried by an application. In any case, I changed the code to
   search for an input of type CX88_VMUX_DVB, or set the input to 0 if
   it is not found

      reply	other threads:[~2010-03-10 23:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-02 16:10 DTV2000 H Plus issues Raena Lea-Shannon
2010-01-02 16:57 ` istvan_v
2010-01-03  8:21   ` Raena Lea-Shannon
2010-01-03 11:31     ` Samuel Rakitnican
2010-01-04 13:01       ` Raena Lea-Shannon
2010-01-04 16:48     ` istvan_v
2010-01-05  1:25       ` Raena Lea-Shannon
2010-01-07 19:49         ` istvan_v
2010-01-07 20:00           ` Devin Heitmueller
2010-01-07 21:07             ` istvan_v
2010-02-09 17:35           ` istvan_v
2010-02-11 19:16             ` istvan_v
2010-02-11 19:21               ` Devin Heitmueller
2010-02-11 19:35                 ` istvan_v
2010-02-12 18:26               ` istvan_v
2010-02-12 18:34                 ` istvan_v
2010-02-17 18:06               ` [PATCH] " istvan_v
2010-02-17 23:51                 ` Mauro Carvalho Chehab
2010-02-17 23:59                   ` Devin Heitmueller
2010-02-18  0:08                     ` Mauro Carvalho Chehab
2010-02-18  0:11                       ` Devin Heitmueller
2010-03-14 17:58                         ` istvan_v
2010-03-15  4:15                           ` Devin Heitmueller
2010-03-16 18:24                             ` istvan_v
2010-03-22 18:33                             ` istvan_v
2010-03-24 11:38                               ` istvan_v
2010-03-14 17:50                       ` istvan_v
2010-02-19 19:54                     ` istvan_v
2010-03-10 23:17                       ` istvan_v [this message]

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=4B98287B.4030506@mailbox.hu \
    --to=istvan_v@mailbox.hu \
    --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.