From: poma <pomidorabelisima@gmail.com>
To: linux-media@vger.kernel.org
Cc: Okkel Klaver <vbroek@iae.nl>
Subject: Re: af9015 and nxp tda182128 support
Date: Tue, 16 Nov 2010 03:49:29 +0100 [thread overview]
Message-ID: <4CE1F139.1030509@gmail.com> (raw)
In-Reply-To: <4CE16387.3040103@iae.nl>
Okkel Klaver wrote:
...
> I own a brandless hdtv usb dvb-t stick.
>
> lsusb identifies it as:
> Bus 001 Device 005: ID 15a4:9016 Afatech Technologies, Inc. AF9015 DVB-T
> USB2.0 stick
>
> I'm using debian with kernel 2.6.32. This kernel doesn't have support
> for the nxp tda18218 tuner on the stick.
> I compiled the latest v4l-dvb source tree from mercural. Now i get the
> following error message when i plugin the stick:
> af9015: tuner NXP TDA18218 not supported yet
>
> Searching the archives of this list i found some messages concerning nxp
> tda18218 support. It seems to me that there is support for the nxp
> tda18218 in the current source tree, but support for the new tuner
> driver is lacking from the af9015 driver.
>
> Now is my question: are there any plans to support the nxp tda18218
> tuner in the af9015 driver?
>
==> [ANNOUNCE] new experimental building system <==
...
If you want to test the new building system, all you need to do is:
$ git clone git://linuxtv.org/mchehab/new_build.git
$ cd new_build
$ ./build.sh
This will download the newest tarball from linuxtv.org, apply the
backport patches
and build it.
After that, you may install the new drivers with:
$ make install
...
Regards,
poma
next prev parent reply other threads:[~2010-11-16 2:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 16:44 af9015 and nxp tda182128 support Okkel Klaver
2010-11-16 2:49 ` poma [this message]
2010-11-16 9:37 ` Davor Emard
-- strict thread matches above, loose matches on Subject: below --
2010-11-15 16:43 Biologisch Tuinbouwbedrijf 'Van het Land'
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=4CE1F139.1030509@gmail.com \
--to=pomidorabelisima@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=vbroek@iae.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.