[linux-dvb] AF9015 Driver (USB)

[Manu Abraham]

Hi,

I saw your post on the ML also, rather than replying to both, will just
add CC to the list.

Hi Manu, I was trying the af9015 driver you're working on at
http://jusst.de/hg/af901x/summary but not having much success - I
suspect i have the wrong firmware (got it from
Would you be able to send it to me?

The firmwares are here: http://jusst.de/manu/fw/AFA/
The reference fw, uses the newer version, 0x447000 instead of 0x441000
But i don't think there exists a large difference except for some refinements

I'm using a DigitalNow TinyTwin USB dual tuner

The maxlinear devices are not supported atm, waiting for some complications
to be flushed out from the af901x tree.

I guess most probably you have the Twin maxlinear device based ones.
Can you please do a lsusb and check the vendor and product ID's ?

if you add in your vendor and product id's, most probably loading the af901x
module, it will tell you about your hardware configuration.

Thanks - Lindsay

Regards,
Manu

[Antti Palosaari]

morjens
I put my version also online if there is someone who wants to play with
it. Many Finnish people have reported it working very well with A-Link
DTU(m) and Fujitech stick. No any success reports outside Finland still...
Latest firmware, version 4.95.0, and the driver patch can be found from
link below.
http://otit.fi/~crope/v4l-dvb/af9015/

regards
Antti

Post by Manu Abraham
Hi,
I saw your post on the ML also, rather than replying to both, will just
add CC to the list.

Hi Manu, I was trying the af9015 driver you're working on at
http://jusst.de/hg/af901x/summary but not having much success - I
suspect i have the wrong firmware (got it from
Would you be able to send it to me?

The firmwares are here: http://jusst.de/manu/fw/AFA/
The reference fw, uses the newer version, 0x447000 instead of 0x441000
But i don't think there exists a large difference except for some refinements

I'm using a DigitalNow TinyTwin USB dual tuner

The maxlinear devices are not supported atm, waiting for some complications
to be flushed out from the af901x tree.
I guess most probably you have the Twin maxlinear device based ones.
Can you please do a lsusb and check the vendor and product ID's ?
if you add in your vendor and product id's, most probably loading the af901x
module, it will tell you about your hardware configuration.

Thanks - Lindsay

Regards,
Manu

[Lindsay Mathieson]

Post by Antti Palosaari
morjens
I put my version also online if there is someone who wants to play
with it. Many Finnish people have reported it working very well with
A-Link DTU(m) and Fujitech stick. No any success reports outside
Finland still...
Latest firmware, version 4.95.0, and the driver patch can be found
from link below.
http://otit.fi/~crope/v4l-dvb/af9015/

Thanks Antti, I had a go with it but couldn't get it to recognise my
TinyTwin, even after I added the Product and Vendor Id (0x13d3 /
0x3226) to the usb table

[Antti Palosaari]

Post by Lindsay Mathieson

Post by Antti Palosaari
morjens
I put my version also online if there is someone who wants to play
with it. Many Finnish people have reported it working very well with
A-Link DTU(m) and Fujitech stick. No any success reports outside
Finland still...
Latest firmware, version 4.95.0, and the driver patch can be found
from link below.
http://otit.fi/~crope/v4l-dvb/af9015/

Thanks Antti, I had a go with it but couldn't get it to recognise my
TinyTwin, even after I added the Product and Vendor Id (0x13d3 /
0x3226) to the usb table

Your stick uses most likely tuners from Maxilinear. This driver supports
only AF9015 reference with MT2060 and MT2061F tuners. Manu's tree should
support your stick. But if there is really AF9015 it should dump at
least some information to log, e.g. eeprom dump and and errors saying
that tuner is not recognized if not errors even before that. Look debug
and message logs for more information.

regards
Antti

[Lindsay Mathieson]

LindsYour stick uses most likely tuners from Maxilinear. This driver
supports only AF9015 reference with MT2060 and MT2061F tuners. Manu's
tree should support your stick. But if there is really AF9015 it
should dump at least some information to log, e.g. eeprom dump and and
errors saying that tuner is not recognized if not errors even before
that. Look debug and message logs for more information.

Yes, it uses the Maxilinear tuner. I've just been looking at the dmesg
output, where would I find the debug logs?

Thanks -Lindsay

[Antti Palosaari]

Post by Lindsay Mathieson

LindsYour stick uses most likely tuners from Maxilinear. This driver
supports only AF9015 reference with MT2060 and MT2061F tuners. Manu's
tree should support your stick. But if there is really AF9015 it
should dump at least some information to log, e.g. eeprom dump and and
errors saying that tuner is not recognized if not errors even before
that. Look debug and message logs for more information.

Yes, it uses the Maxilinear tuner. I've just been looking at the dmesg
output, where would I find the debug logs?

It depends on distribution. If I remember correctly Ubuntu logs debug by
default to /var/log/debug. On Fedora you should enable debug logging. It
is done by syslog, /etc/syslog.conf.

Examples to try:
*.debug;*.info;mail.none;authpriv.none;cron.none /var/log/messages
*.debug /var/log/debug

Remember restart syslogd if configuration is changed.

And check also that there is no race condition in drivers that same
usb-id is used in more than one driver at the time. You need to remove
driver duplicate driver module and install new one. Or broke usb-id from
driver you don't want to use and install broken driver and then install
driver with correct usb-id.

/antti

[Rafael Antoniello]

Hi.
I finally get your driver working very well with my usb-tdt-stick.
So you can add to the HW-supported list the BestBuy Easy TV USB Stick
(AF9015 + MT2061).
If someone is interested, I am running it on an 2.6.9 kernel (minimal
changes are to be added to compile v4l with these drivers).
Now I am trying to embed these drivers on a ***@300MHz based system,
without success yet. It seems that performance has something to do in
this reduced environment (not actually sure). If someone is interested
or has experience in this task, suggestions are welcome.
Please continue reporting new releases for the drivers (I will). Thank
you very much Antti and Manu.
Cheers,
Rafael.

Post by Antti Palosaari
morjens
I put my version also online if there is someone who wants to play
with it. Many Finnish people have reported it working very well with
A-Link DTU(m) and Fujitech stick. No any success reports outside
Finland still...
Latest firmware, version 4.95.0, and the driver patch can be found
from link below.
http://otit.fi/~crope/v4l-dvb/af9015/
regards
Antti

Post by Manu Abraham
Hi,
I saw your post on the ML also, rather than replying to both, will
just add CC to the list.

Hi Manu, I was trying the af9015 driver you're working on at
http://jusst.de/hg/af901x/summary but not having much success - I
suspect i have the wrong firmware (got it from
Would you be able to send it to me?

The firmwares are here: http://jusst.de/manu/fw/AFA/
The reference fw, uses the newer version, 0x447000 instead of 0x441000
But i don't think there exists a large difference except for some refinements

I'm using a DigitalNow TinyTwin USB dual tuner

The maxlinear devices are not supported atm, waiting for some
complications
to be flushed out from the af901x tree.
I guess most probably you have the Twin maxlinear device based ones.
Can you please do a lsusb and check the vendor and product ID's ?
if you add in your vendor and product id's, most probably loading the af901x
module, it will tell you about your hardware configuration.

Thanks - Lindsay

Regards,
Manu

[Diego]

Hi. Sorry for my english

I supposed that patch its for .23 kernels right? I change the sources on default Ubuntu kernel (2.6.22) for get that your driver working on this kernel (got errors when patching and want other module supports that .23 dont give me atm) and works.

Work good, after few probes sometimes the video freeze (no audio freeze) and sometimes can't deattach dvb_usb_af9015 after a hang but that occur in very rare occasions.

Other thing its sometimes when change channel its a bit slow (10s,7s)(....... LOCKED.)
but i can live with that



thx for the work Antti.


how can i extract the diff between kernels for extract a patch?

-----------------------
Chips: mt2061/af9016

lsusb:
Bus 001 Device 002: ID 15a4:9016

Kernel:
Linux 2.6.22.15 #5 SMP Sat Nov 24 12:32:42 CET 2007 x86_64 GNU/Linux
Linux-sources-2.6.22 (Ubuntu)

dmesg:
[ 121.462592] usb 1-2: new high speed USB device using ehci_hcd and address 2
[ 121.538411] usb 1-2: configuration #1 chosen from 1 choice
[ 121.669023] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware
[ 121.698091] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
[ 121.749314] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state.
[ 121.749586] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 121.749955] DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick).
[ 122.067803] af9013: firmware version: 4.95.0
[ 122.067860] DVB: registering frontend 0 (Afatech AF9013 DVB-T)...
[ 122.081959] MT2060: successfully identified (IF1 = 1220)
[ 122.341910] dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected.
[ 122.418480] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state.
[ 122.418831] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 122.419122] DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick).
[ 122.708844] dvb-usb: no frontend was attached by 'Afatech AF9015 DVB-T USB2.0 stick'
[ 122.708851] dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected.
[ 122.785461] usbcore: registered new interface driver dvb_usb_af9015
[ 122.837721] usbcore: registered new interface driver hiddev
[ 122.837797] usbcore: registered new interface driver usbhid
[ 122.837850] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver

[Antti Palosaari]

Diego wrote:
Thank you for reporting.

Post by Diego
I supposed that patch its for .23 kernels right? I change the sources on default Ubuntu kernel (2.6.22) for get that your driver working on this kernel (got errors when patching and want other module supports that .23 dont give me atm) and works.

Patch is not kernel dependent. It was done against current
v4l-dvb-master found from http://linuxtv.org/hg/v4l-dvb/ . Just download
v4l-dvb-master, patch it, compile and install.

Post by Diego
Work good, after few probes sometimes the video freeze (no audio freeze) and sometimes can't deattach dvb_usb_af9015 after a hang but that occur in very rare occasions.

What kind of situations it hangs? Is your signal weak => errors in picture?

Post by Diego
Other thing its sometimes when change channel its a bit slow (10s,7s)(....... LOCKED.)
but i can live with that

Oh, takes very long. Weak signal? AF9015 demodulator seems to be rather
slow to lock but over ten seconds is far away I can imagine. I have one
idea to try get faster lock, but haven't tested & looked it more.

Post by Diego
how can i extract the diff between kernels for extract a patch?

If you use Mercurial, as v4l-dvb-project uses, it can be taken simply by
entering command hg diff inside of the tree downloaded from
linuxtv.org. Diffing against vanilla kernel is not so easy, but is there
really need?

Post by Diego
-----------------------
Chips: mt2061/af9016
Bus 001 Device 002: ID 15a4:9016
Linux 2.6.22.15 #5 SMP Sat Nov 24 12:32:42 CET 2007 x86_64 GNU/Linux
Linux-sources-2.6.22 (Ubuntu)
[ 121.462592] usb 1-2: new high speed USB device using ehci_hcd and address 2
[ 121.538411] usb 1-2: configuration #1 chosen from 1 choice
[ 121.669023] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware
[ 121.698091] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
[ 121.749314] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state.
[ 121.749586] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 121.749955] DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick).
[ 122.067803] af9013: firmware version: 4.95.0
[ 122.067860] DVB: registering frontend 0 (Afatech AF9013 DVB-T)...
[ 122.081959] MT2060: successfully identified (IF1 = 1220)
[ 122.341910] dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected.

Everything for there one looks OK.

Post by Diego
[ 122.418480] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state.
[ 122.418831] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 122.419122] DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick).
[ 122.708844] dvb-usb: no frontend was attached by 'Afatech AF9015 DVB-T USB2.0 stick'

hmm, I should put error writings to see why this happens.

Post by Diego
[ 122.708851] dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected.
[ 122.785461] usbcore: registered new interface driver dvb_usb_af9015
[ 122.837721] usbcore: registered new interface driver hiddev
[ 122.837797] usbcore: registered new interface driver usbhid
[ 122.837850] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver

Does it always load driver two times? It should go warm after firmware
is downloaded. After that it should not do reconnect nor boot. Does it
print every time, when plugging stick, that it founds stick in warm
state two times? Looks like it is reconnecting stick in usb-bus after
firmware download. I have commented out this reconnecting stuff from
firmware download because it was not needed and that's why it is very
strange to see it now...

regards
Antti

[Antti Palosaari]

Yep hangs when got errors in picture but its rare...

Many DVB-sticks has problems when signal goes weak, maybe it is issue
that can be handled and fixed with driver. I haven't looked this more...

About changing channels perhaps its that (low signal) because some channels change fast
and others no, then display some picture errors but after few seconds the image its
fine, i experience video freeze too (no audio freeze) sometimes but perhaps its the same
problem with weak signal.

Driver uses automatic parameter detection currently, only bandwidth and
frequency are set from userspace application. I will check this later
today and add support for manual & automatic demodulator parameters
settings (TPS).

On boot up if i have the dvbt plugged that load driver but not work.
"klear" says can't open dvb display.

Frontend does not attach as it should. Can be fixed easily. I will fix
this also.

I apply the patch agains agains v4l, perhaps i make something wrong on patch the kernel
2.6.22 but seems that not the problem.
dvb plugged on boot (not work)
dvb attached after boot (work)

I still did not understand why it (system) attach this driver twice.

regards
Antti

[Antti Palosaari]

moi
problems reported should be fixed now, please test.
http://linuxtv.org/hg/~anttip/af9015/

regards
Antti

Post by Antti Palosaari

Yep hangs when got errors in picture but its rare...

Many DVB-sticks has problems when signal goes weak, maybe it is issue
that can be handled and fixed with driver. I haven't looked this more...

About changing channels perhaps its that (low signal) because some channels change fast
and others no, then display some picture errors but after few seconds the image its
fine, i experience video freeze too (no audio freeze) sometimes but perhaps its the same
problem with weak signal.

Driver uses automatic parameter detection currently, only bandwidth and
frequency are set from userspace application. I will check this later
today and add support for manual & automatic demodulator parameters
settings (TPS).

On boot up if i have the dvbt plugged that load driver but not work.
"klear" says can't open dvb display.

Frontend does not attach as it should. Can be fixed easily. I will fix
this also.

I apply the patch agains agains v4l, perhaps i make something wrong on patch the kernel
2.6.22 but seems that not the problem.
dvb plugged on boot (not work)
dvb attached after boot (work)

I still did not understand why it (system) attach this driver twice.
regards
Antti

[Antti Palosaari]

On Wed, 28 Nov 2007 01:40:01 +0200

Post by Antti Palosaari
moi
problems reported should be fixed now, please test.
http://linuxtv.org/hg/~anttip/af9015/

Something are broke in that sources. Check attach.

Errors seen in log provided are most likely your fault. Looks like you
are mixing v4l-dvb modules from different builds. Binary interface
between modules is changed from build to build and thats why there is
now incompatibility.
You should:
* became root
su - or sudo -s
* go to correct build development tree
cd /patch/to/tree
* to clean all build setup to default:
make distclean
* compile modules
make
* install modules
make install

And finally reboot your machine to take new modules use.

regards
Antti