linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Büsch" <m@bues.ch>
To: Hans-Frieder Vogt <hfvogt@gmx.net>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 2/3] Basic AF9035/AF9033 driver
Date: Tue, 20 Mar 2012 14:04:11 +0100	[thread overview]
Message-ID: <20120320140411.58b5808b@milhouse> (raw)
In-Reply-To: <4F67CF24.8050601@redhat.com>

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

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:

> diff -Nupr a/drivers/media/dvb/dvb-usb/Makefile b/drivers/media/dvb/dvb-usb/Makefile
> --- a/drivers/media/dvb/dvb-usb/Makefile        2012-01-22 02:53:17.000000000 +0100
> +++ b/drivers/media/dvb/dvb-usb/Makefile        2012-02-20 23:22:38.385877784 +0100
> @@ -75,6 +75,9 @@ obj-$(CONFIG_DVB_USB_DTV5100) += dvb-usb
>  dvb-usb-af9015-objs = af9015.o
>  obj-$(CONFIG_DVB_USB_AF9015) += dvb-usb-af9015.o
>  
> +dvb-usb-af903x-objs = af903x-core.o af903x-devices.o af903x-fe.o af903x-tuners.o
> +obj-$(DVB_USB_AF903X) += dvb-usb-af903x.o

It should be CONFIG_DVB_USB_AF903X here.

> +
>  dvb-usb-cinergyT2-objs = cinergyT2-core.o cinergyT2-fe.o
>  obj-$(CONFIG_DVB_USB_CINERGY_T2) += dvb-usb-cinergyT2.o


Unfortunately it turns out that my stick uses an older tuner:

[   91.396087] usb 1-1: new high-speed USB device number 4 using ehci_hcd
[   91.534709] usb 1-1: New USB device found, idVendor=15a4, idProduct=1001
[   91.534724] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   91.534735] usb 1-1: Product: AF9035A USB Device
[   91.534743] usb 1-1: Manufacturer: Afa Technologies Inc.
[   91.534752] usb 1-1: SerialNumber: AF0102020700001
[   91.537709] af903x: 1 Tuners of Type=0x28, Arch Mode=DCA, Remote=NEC
[   91.552954] dvb-usb: found a 'ITEtech USB2.0 DVB-T Recevier' in cold state, will try to load a firmware
[   91.565312] dvb-usb: downloading firmware from file 'dvb-usb-af9035-03.fw'
[   91.875659] af903x: device init ...
[   91.875671] af903x: requested tuner id 40 not enabled
[   91.875682] af903x: device_init Fail: -22

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.

-- 
Greetings, Michael.

PGP encryption is encouraged / 908D8B0E

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

  reply	other threads:[~2012-03-20 13:04 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 [this message]
2012-03-20 16:27     ` Gianluca Gennari
2012-03-20 16:37       ` Michael Büsch
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=20120320140411.58b5808b@milhouse \
    --to=m@bues.ch \
    --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;
as well as URLs for NNTP newsgroup(s).