A [[DVB-T]] [[Demodulator|demodulator]] from [[Afatech]]. This is the company's second generation COFDM demodulator, and is the successor to the [[Afatech AF9005|AF900x]] family of chips.

+

A combination [[DVB-T]] [[Demodulator|demodulator]] and [[USB]] [[USB interface chipsets|bridge]] chip from [[Afatech]]. This is the company's second generation COFDM demodulator, and is the successor to the [[Afatech AF9005|AF900x]] family of chips. Given the chip's dual nature, the AF9015 is fairly complex. It is also very flexible, supporting a wide variety of device configurations (single USB, dual USB, Platform mode, PCI/PCIe based devices, and even SPI is supported by it with some tuners (such as for a Consumer Electronics product that runs Windows CE)). Documentation for the AF901x family can be obtained from AFA (under [[NDA]]), but it is apparently confusing, as well as incomplete -- as there are a lot of areas that are undocumented.

+

+

Unfortunately, tuner devices build on these chips are known to be unstable demanding frequent cold boots.

The AF901x family consists of the following chips:

The AF901x family consists of the following chips:

−

* (list chips here)

+

* ''(list chips here ...or perhaps start a new article for the AF901x family, and leave this one dedicated to the AF9015)''

−

The AF9015 chip is the main USB control/demux in found in some currently available [[DVB-T USB Devices|DVB-T USB devices]], such as:

+

{{Device_List_Low_Detail/Header

+

| content =

+

{{USB_Device_Data

+

|renderwith=Device_List_Low_Detail/Row

+

|selatt1=usbbridge

+

|selval1=af9015

+

}}

+

}}

−

* The WandTV

+

Examples of [[DVB-T USB Devices|DVB-T USB devices]] in which the AF9015 chip can be found include:

The AF9015 chip is fairly complex and supports a wide variety of device configurations (single USB, dual USB, Platform mode, PCI/PCIe based devices, and even SPI is supported by it with some tuners (such as for a Consumer Electronics product that runs Windows CE)).

−

−

Documentation for the AF901x family can be obtained from AFA (under [[NDA]]), but it is apparently confusing, as well as incomplete -- as there are a lot of areas that are undocumented.

==Drivers==

==Drivers==

−

At present there are three different drivers Linux drivers available for the AF901x. That may strike one as being strange or showing signs of a state of dis-coordination, but in actuality, each driver has its own reason for being, and collectively they highlight the relative complexity of the chip and the flexibility in device design that its usage permits.

+

+

At present there are three different Linux drivers available for the AF901x. That may strike one as being strange or showing signs of a state of dis-coordination, but in actuality, each driver has its own reason for coming into existence. In addition, taken collectively, the development of three different drivers highlights the relative complexity of the chip, as well as the flexibility in device design that its employment permits.

===Opensource Mercurial Repositories===

===Opensource Mercurial Repositories===

−

* http://jusst.de/hg/af901x ... This is a second driver attempt for the AF901x by Manu Abrahams. In his personal assessment, he got many things right, but some things are still wrong. In addition, his driver works with just one particular device

+

−

* http://linuxtv.org/hg/~anttip/af9015/ (Supported tuners are: MT2060, MT2061 and QT1010.) ... This is a driver written from scratch, first by reverse engineering and afterwards finalized from the reference kit, by Antti Palosaari, that is specific to the AF9015 chip alone, and for device's with a "MASTER based configuration".

+

The open source driver is now included in the linux kernel trunk since version 2.6.28. It should work out of the box !

+

+

* http://jusst.de/hg/af901x ... This is a second driver attempt for the AF901x by Manu Abrahams. In his personal assessment, he got many things right, but some things are still wrong. In addition, his driver works with just one particular device.

+

+

* http://linuxtv.org/hg/~anttip/af9015/ (Supported tuners are: MT2060, MT2061 and QT1010.) ... This is a driver written from scratch, first by reverse engineering and afterwards finalized from the reference kit, by Antti Palosaari, that is specific to the AF9015 chip alone, and for devices with a "MASTER based configuration".

+

** You might also need to fetch a firmware file from http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ before the driver works. The driver expects to find it in /lib/firmware/<kernel-version>/dvb-usb-af9015.fw

+

+

===Vendor Released Driver (Last Up to date)===

+

No external firmware needed !

+

+

* The modified Vendor released driver for current kernels (2.6.24+) is available from http://tombcore.free.fr/af9015.tar.bz2

+

Install linux headers, merge it with the last v4l-dvb source, then make, make install and enjoy.

+

+

* DKMS package for the driver available here : http://tombcore.free.fr/af9015.deb

* A vendor-written driver specific to the AF9015 chip alone is available from http://af.zsolttech.com/. Apparently, AFA had this driver written (authour, Rick Huang?) specifically for a single device from one customer, who then in turn ended up violating the NDA. (It was from that leaked driver that Antti was able to largely base/ and derive his RE attempts; see above discussion).

+

−

+

* A vendor-written driver specific to the AF9015 chip alone is available from http://www.digittrade.de/shop/info/stick_treiber/linux/Linux_MT2060_2.6.20.tar . Apparently, AFA had this driver written (author Rick Huang?) specifically for a single device from one customer, who then in turn ended up violating the NDA.

+

http://www.linuxtv.org/pipermail/linux-dvb/2007-November/022050.html

In any regard, users have reported that this vendor driver is indeed working, including for x64_64 (for some further information see the threads [http://forum.ubuntuusers.de/topic/127976/#1029411 here] and [http://marc.info/?l=linux-dvb&m=119437137719022&w=2 here].

In any regard, users have reported that this vendor driver is indeed working, including for x64_64 (for some further information see the threads [http://forum.ubuntuusers.de/topic/127976/#1029411 here] and [http://marc.info/?l=linux-dvb&m=119437137719022&w=2 here].

Line 37:

Line 75:

typedef unsigned int UData_t;

typedef unsigned int UData_t;

−

Then compile, install, modprobe dvb_usb_af9015 and you are finished.

+

Then compile, install, modprobe dvb_usb_af9015 and you are finished.

−

===A Comprehensive OSS Driver===

+

=== Original Vendor-released driver ===

−

For its part, Afatech does not want any of the above driver attempts to make their way into the kernel, as none of them are very robust in terms of chip support.

+

−

Instead, AFA has embarked upon the development of yet another OSS driver, which will be generic in that it will be capable of supporting the entire AF901x family as well as all possible device configurations permitted. In addition to the expectation that it will be this driver that is eventually adopted into the kernel, AFA have also signaled that they intend provide continuous support (i.e. they will stay on as the driver's maintainer).

Currently, this newest driver has reached a second round of testing in AFA labs, but that has only been in conjunction (with some peripheral manufacturers) with a few devices, and, as it stands, the code is still not particularly generic (due to both the complexities of the chip itself as well as those involved in getting the various device configurations to work). So, as of yet, there currently isn't anything for the end user to test. However, as soon things progress past this stage, there will be something released for users to test. There is no specific release timeframe set for this, but hopefully it will be soon, as the chip manufacturer (as well as everybody else involved) is under pressure, due to the large adoption of the chip by different peripheral manufacturers (Avermedia, Terratec, Azurewave, DigitalNow, Pinnacle, as well as some number of unbranded Chinese manufacturers too). In short, a lot more devices based on this chipset are expected to materialize.

+

This original code has since been modified by somebody else (at afatech?)

+

to use the MXL5005 tuner and the Digitalnow TinyTwin is partly functional.

For its part, Afatech does not want any of the above driver attempts to make their way into the kernel, as none of them are very robust in terms of chip support.

−

------

+

Instead, AFA has embarked upon the development of yet another OSS driver, which will be generic in that it will be capable of supporting the entire AF901x family as well as all possible device configurations permitted. In addition to the expectation that it will be this driver that is eventually adopted into the kernel, AFA have also signaled that they intend provide continuous support (i.e. they will stay on as the driver's maintainer).

+

Currently, this newest driver has reached a second round of testing in AFA labs, but that has only been in conjunction (with some peripheral manufacturers) with a few devices, and, as it stands, the code is still not particularly generic (due to both the complexities of the chip itself as well as those involved in getting the various device configurations to work). So, as of yet, there currently isn't anything for the end user to test. However, as soon things progress past this stage, there will be something released for users to test. There is no specific release timeframe set for this, but hopefully it will be soon, as the chip manufacturer (as well as everybody else involved) is under pressure, due to the large adoption of the chip by different peripheral manufacturers (Avermedia, Terratec, Azurewave, DigitalNow, Pinnacle, as well as some number of unbranded Chinese manufacturers too). In short, a lot more devices based on this chipset are expected to materialize.

−

{{Note|The following was likely written by Andrew Leech, and submitted under the name (corona). It is believed that Andrew did not progress further from where he had left off in his development log. An attempt to contact him will be made so that his development log can be removed (as it no longer pertains, nor is consequential, to AF901x driver development), but have him move (so that he maintains credit/acknowledgement/attribution in the wiki) the very nice introductory articles related to driver development for a usb device to a more appropriate place in the wiki .... as he had wrote, there currently isn't much available in that regard for new developers to go by, so it would indeed be very desirable to get some development related howto articles started)}}

+

=== Missing drivers ===

−

==Driver Development Log==

+

There are a number of devices based on the TDA18218HK tuner chip currently not working in Linux but work is being done by subscribers of the gmane.linux.drivers.video-input-infrastructure group: [http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/13208]

−

I'm currently writing a driver for this chip, and as there's not much around in terms of a howto on this subject, I thought it might be worth documenting the process.

+

−

I've got a head start in that there is an earlier chip from [[Afatech]], the [[Afatech AF9005|AF9005]], for which drivers were recently written/developed. I've got the driver source code for that chip along with the documentation for that and my chip, so I'm going to be working on modifying the [[Afatech AF9005|AF9005]] drivers to work with the AF9015. I'm not sure if I'm allowed to post the documentations here, I'll find out and if so a link will be posted.

+

==External Links==

−

+

−

To start with, there are some great Linux USB tutorials on Linux Journal:

You will find the usb drivers are in ''./v4l-dvb/linux/drivers/media/dvb/dvb-usb''. Have a bit of a browse through them while you're reading through the first article above, get a feel for how the driver is put together. (There is a procedure described in http://www.ubuntuforums.org/showthread.php?p=1067326).

+

Revision as of 11:43, 29 October 2012

A combination DVB-Tdemodulator and USBbridge chip from Afatech. This is the company's second generation COFDM demodulator, and is the successor to the AF900x family of chips. Given the chip's dual nature, the AF9015 is fairly complex. It is also very flexible, supporting a wide variety of device configurations (single USB, dual USB, Platform mode, PCI/PCIe based devices, and even SPI is supported by it with some tuners (such as for a Consumer Electronics product that runs Windows CE)). Documentation for the AF901x family can be obtained from AFA (under NDA), but it is apparently confusing, as well as incomplete -- as there are a lot of areas that are undocumented.

Unfortunately, tuner devices build on these chips are known to be unstable demanding frequent cold boots.

The AF901x family consists of the following chips:

(list chips here ...or perhaps start a new article for the AF901x family, and leave this one dedicated to the AF9015)

Drivers

At present there are three different Linux drivers available for the AF901x. That may strike one as being strange or showing signs of a state of dis-coordination, but in actuality, each driver has its own reason for coming into existence. In addition, taken collectively, the development of three different drivers highlights the relative complexity of the chip, as well as the flexibility in device design that its employment permits.

Opensource Mercurial Repositories

The open source driver is now included in the linux kernel trunk since version 2.6.28. It should work out of the box !

http://jusst.de/hg/af901x ... This is a second driver attempt for the AF901x by Manu Abrahams. In his personal assessment, he got many things right, but some things are still wrong. In addition, his driver works with just one particular device.

http://linuxtv.org/hg/~anttip/af9015/ (Supported tuners are: MT2060, MT2061 and QT1010.) ... This is a driver written from scratch, first by reverse engineering and afterwards finalized from the reference kit, by Antti Palosaari, that is specific to the AF9015 chip alone, and for devices with a "MASTER based configuration".

In any regard, users have reported that this vendor driver is indeed working, including for x64_64 (for some further information see the threads here and here.

For devices based on the MT2060 tuner (such as the Geniatech T328B) you may need to patch the file MT2060M.h in the following way:

replace

typedef unsigned long UData_t;

with

typedef unsigned int UData_t;

Then compile, install, modprobe dvb_usb_af9015 and you are finished.

Original Vendor-released driver

The above device driver probably originated from the code found at
[18].

This original code has since been modified by somebody else (at afatech?)
to use the MXL5005 tuner and the Digitalnow TinyTwin is partly functional.

A Comprehensive OSS Driver

For its part, Afatech does not want any of the above driver attempts to make their way into the kernel, as none of them are very robust in terms of chip support.

Instead, AFA has embarked upon the development of yet another OSS driver, which will be generic in that it will be capable of supporting the entire AF901x family as well as all possible device configurations permitted. In addition to the expectation that it will be this driver that is eventually adopted into the kernel, AFA have also signaled that they intend provide continuous support (i.e. they will stay on as the driver's maintainer).

Currently, this newest driver has reached a second round of testing in AFA labs, but that has only been in conjunction (with some peripheral manufacturers) with a few devices, and, as it stands, the code is still not particularly generic (due to both the complexities of the chip itself as well as those involved in getting the various device configurations to work). So, as of yet, there currently isn't anything for the end user to test. However, as soon things progress past this stage, there will be something released for users to test. There is no specific release timeframe set for this, but hopefully it will be soon, as the chip manufacturer (as well as everybody else involved) is under pressure, due to the large adoption of the chip by different peripheral manufacturers (Avermedia, Terratec, Azurewave, DigitalNow, Pinnacle, as well as some number of unbranded Chinese manufacturers too). In short, a lot more devices based on this chipset are expected to materialize.

Missing drivers

There are a number of devices based on the TDA18218HK tuner chip currently not working in Linux but work is being done by subscribers of the gmane.linux.drivers.video-input-infrastructure group: [19]