public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Hans-Frieder Vogt <hfvogt@gmx.net>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 0/3] Support for AF9035/AF9033
Date: Thu, 23 Feb 2012 19:59:28 +0200	[thread overview]
Message-ID: <4F467E80.4060302@iki.fi> (raw)
In-Reply-To: <201202222320.56583.hfvogt@gmx.net>

On 23.02.2012 00:20, Hans-Frieder Vogt wrote:
> I have written a driver for the AF9035&  AF9033 (called af903x), based on the
> various drivers and information floating around for these chips.
> Currently, my driver only supports the devices that I am able to test. These
> are
> - Terratec T5 Ver.2 (also known as T6)
> - Avermedia Volar HD Nano (A867)
>
> The driver supports:
> - diversity and dual tuner (when the first frontend is used, it is in diversity
> mode, when two frontends are used in dual tuner mode)
> - multiple devices
> - pid filtering
> - remote control in NEC and RC-6 mode (currently not switchable, but depending
> on device)
> - support for kernel 3.1, 3.2 and 3.3 series
>
> I have not tried to split the driver in a DVB-T receiver (af9035) and a
> frontend (af9033), because I do not see the sense in doing that for a
> demodulator, that seems to be always used in combination with the very same
> receiver.

That was how I originally implemented it. Reason for that is simple: 
af9033 demodulator exists as single chip. I think it is also used for 
dual tuner devices or is there 2 af9035 chips used, like one is master 
and one is slave and working as a demod?

Situation is rather same for af9005/af9003 and af9015/af9013. Search 
from the mailing list and see there is devices using af9003 demod but as 
it is not split correctly from the af9005 those devices are never 
supported (due to fact af9003 demod is not split out).

Reason behind my af9035/af9033 is not merged to the Kernel is that I 
never found people from ITE who was able to give permission to merge 
that. As it contains some vendor code I didn't want to merge it without 
permission.

It is not many day work to write all vendor code out from the driver and 
get it clean. If you want I can do it for you and merge that to the 
Kernel. You can then take whole driver and start hacking if you wish. 
What do you think? I am currently busy as hell and I don't want more 
drivers to maintain so you can take maintaining responsibility.

> The patch is split in three parts:
> Patch 1: support for tuner fitipower FC0012
> Patch 2: basic driver
> Patch 3: firmware
>
> Hans-Frieder Vogt                       e-mail: hfvogt<at>  gmx .dot. net

regards
Antti

-- 
http://palosaari.fi/

  parent reply	other threads:[~2012-02-23 17:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 22:20 [PATCH 0/3] Support for AF9035/AF9033 Hans-Frieder Vogt
2012-02-23  9:19 ` Oliver Schinagl
2012-02-23 22:02   ` Hans-Frieder Vogt
2012-02-24 10:04     ` Oliver Schinagl
2012-02-24 10:22       ` Oliver Schinagl
2012-02-25 23:42         ` Hans-Frieder Vogt
2012-02-23 16:40 ` Gianluca Gennari
2012-02-23 22:12   ` Hans-Frieder Vogt
2012-02-24 15:44     ` Gianluca Gennari
2012-02-23 17:59 ` Antti Palosaari [this message]
2012-02-23 22:28   ` Hans-Frieder Vogt
2012-02-24  3:46     ` Antti Palosaari

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=4F467E80.4060302@iki.fi \
    --to=crope@iki.fi \
    --cc=hfvogt@gmx.net \
    --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