public inbox for linux-media@vger.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: Fri, 19 Feb 2010 20:54:58 +0100	[thread overview]
Message-ID: <4B7EEC92.1090004@mailbox.hu> (raw)
In-Reply-To: <829197381002171559k10b692dcu99a3adc2f613437f@mail.gmail.com>

Well, it is not really a problem, if it is not merged, so this updated
version is only for those who want to test it:

http://www.sharemation.com/IstvanV/v4l/xc4000-winfast-14021dfc00f3.patch

  - in xc4000.c, power management may default to on or off depending on
    the card type
  - autodetects and (hopefully) supports cards with the following PCI
    IDs, based on Windows INF files:
      107D:6619  WinFast TV2000 XP Global (this is actually the same as
                 6618 and 6F18)
      107D:6F36  WinFast TV2000 XP Global with XC4100 (analog-only
                 XC4000 ?) tuner
      107D:6F38  WinFast DTV1800 H with XC4000 tuner
      107D:6F42  WinFast DTV2000 H Plus
      107D:6F43  WinFast TV2000 XP Global with XC4100 tuner and
                 different GPIOs
    Not all of these card versions may actually exist in practice,
    though, only 6F38 and 6F42 are confirmed so far.
  - added a new "sharpness" control to the CX88 driver

On 02/18/2010 12:59 AM, Devin Heitmueller wrote:

> I would hate to come across as a jerk here, but he cannot provide his
> SOB for this patch, as I wrote about 95% of the code here.  It's
> derived from a tree I have been working on for the PCTV 340e:

  parent reply	other threads:[~2010-02-19 19:50 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 [this message]
2010-03-10 23:17                       ` istvan_v

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=4B7EEC92.1090004@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox