public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Büsch" <m@bues.ch>
To: gennarone@gmail.com
Cc: Hans-Frieder Vogt <hfvogt@gmx.net>, linux-media@vger.kernel.org
Subject: Re: [PATCH 2/3] Basic AF9035/AF9033 driver
Date: Tue, 20 Mar 2012 17:37:24 +0100	[thread overview]
Message-ID: <20120320173724.4d3f2f0f@milhouse> (raw)
In-Reply-To: <4F68B001.1050809@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1841 bytes --]

On Tue, 20 Mar 2012 17:27:45 +0100
Gianluca Gennari <gennarone@gmail.com> wrote:

> Hi Michael,
> 
> Il 20/03/2012 14:04, Michael Büsch ha scritto:
> > Thank you for working on a af903x driver.
> > 
> > I tried to test the driver on a debian 3.2 kernel, after applying a small fix:
> > It should be CONFIG_DVB_USB_AF903X here.
> 
> this issue is fixed in version "1.02" of the driver, posted by Hans a
> few days ago.

I can only find the post from Feb 22th, which includes this glitch.
Can you point me to the newer post in the list archives?

> > So I'm wondering how big the differences between the fc0011 and fc0012 are.
> > Can the 0011 be implemented in the 0012 driver, or does it require a separate driver?
> > Please give me a few hints, to I can work on implementing support for that tuner.
> 
> I have no idea about the real differences between the two tuner models,
> but here you can find an old "leaked" af9035 driver with support for
> several tuners, including fc0011 and fc0012:
> 
> https://bitbucket.org/voltagex/af9035/src
>
> (look under the "api" subdir for the tuners).

Yeah I know about that "thing". It makes my eyes bleed, though.

But the author of this document pointed me to this:
http://linuxtv.org/wiki/index.php/Fitipower
That seems pretty useful, in addition to the existing crap driver.

> The driver is not working with recent kernels, but probably you can
> extract the information needed to implement a proper kernel driver for
> fc0011, using the fc0012 driver written by Hans as a reference.

Yeah after looking at things it seems best to have a separate module.
I already started to put the boilerplate code together and I'm currently
putting the various device specific bits in place.

-- 
Greetings, Michael.

PGP encryption is encouraged / 908D8B0E

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-03-20 16:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 22:21 [PATCH 2/3] Basic AF9035/AF9033 driver Hans-Frieder Vogt
2012-03-11 15:23 ` [PATCH] AF903X driver update, v1.02 Hans-Frieder Vogt
2012-03-12 17:10   ` Gianluca Gennari
2012-03-12 20:01     ` Malcolm Priestley
2012-03-20  0:28 ` [PATCH 2/3] Basic AF9035/AF9033 driver Mauro Carvalho Chehab
2012-03-20 13:04   ` Michael Büsch
2012-03-20 16:27     ` Gianluca Gennari
2012-03-20 16:37       ` Michael Büsch [this message]
2012-03-20 16:49         ` Gianluca Gennari
2012-03-20 17:32           ` Michael Büsch
2012-03-20 21:44             ` Add fc0011 tuner support (was: [PATCH 2/3] Basic AF9035/AF9033 driver) Michael Büsch
2012-03-21  7:52       ` [PATCH 2/3] Basic AF9035/AF9033 driver Oliver Schinagl

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=20120320173724.4d3f2f0f@milhouse \
    --to=m@bues.ch \
    --cc=gennarone@gmail.com \
    --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