From: hermann pitton <hermann-pitton@arcor.de>
To: "Евгений Бацман" <evgenbatsman@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Add AverTV Studio 509UA
Date: Mon, 22 Mar 2010 02:16:26 +0100 [thread overview]
Message-ID: <1269220586.4189.25.camel@localhost> (raw)
In-Reply-To: <1269211942.3339.33.camel@localhost>
>
> I think best would be to create two patches.
>
> 1/2 adds the new tuner. (tuner-types.c/tuner.h/tveeprom.c)
> 2/2 adds the new Avermedia card.
>
> Else it looks fine.
To add some for the record here for those eventually later on it.
We have seen over so many years now, that hundreds of "new" can tuners
did appear and, IIRC, we got them all with any combination of previous
chips.
The filters, mainly the SAW filters did make a difference to the
original products they follow all in what ever combination concerning
quality.
However, a main annoyance was, that lots of such clones did appear and
some did start to use extra radio tuners on cheap silicon on separate
addresses, hard to track, since hidden under some welded shielding.
This was with all such clones all over Asia and the extra silicon radio
tuner was always Philips/NXP in the beginning.
What is new now, I think, and first seen, is that the last can tuner
flagship MK5 series has a FQ non radio variant on a AverMedia using some
extra silicon from Philips/NXP/Trident _themselves_ to make some extra
profit against a FM MK5 they have.
I would call this a management disaster, but my education might be
outdated.
Cheers,
Hermann
prev parent reply other threads:[~2010-03-22 1:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 18:32 Add AverTV Studio 509UA Евгений Бацман
2010-03-20 0:38 ` hermann pitton
[not found] ` <6137756e1003200708v5486c0aah1074361be42e1d64@mail.gmail.com>
2010-03-21 22:52 ` hermann pitton
2010-03-22 1:16 ` hermann pitton [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=1269220586.4189.25.camel@localhost \
--to=hermann-pitton@arcor.de \
--cc=evgenbatsman@gmail.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