Drivers Dvb-dtv Input Devices



  1. Drivers Dvb-dtv Input Devices Using
  2. Drivers Dvb-dtv Input Devices
  3. Drivers Dvb-dtv Input Devices Device
  4. Drivers Dvb-dtv Input Devices Input
  5. Drivers Dvb-dtv Input Devices Definition

Then it allocates a new input device structure with inputallocatedevice and sets up input bitfields. This way the device driver tells the other parts of the input systems what it is - what events can be generated or accepted by this input device. Our example device can only generate EVKEY type events, and from those only BTN0 event code. Using outdated or corrupt DVB-T drivers can cause system errors, crashes, and cause your computer or hardware to fail. Furthermore, installing the wrong DVB-T drivers can make these problems even worse. Recommendation: If you are inexperienced with updating DVB-T device drivers manually, we highly recommend downloading the DVB-T Driver Utility. Intel usb 3.0 extensible host controller driver free get the latest drivers for intel usb 3.0 extensible host controller. Or at low price in addition to 3. Tbs 5220 is an external usb mini tv stick which supports dvb-t2, dvb-t and dvb-c all in one.

I decided to add a second tuner to my Myth system. The current tuner I have is a Gigabyte U7100 which serves me fine except for the fact that the remote does not work. The computer shop did not have any of these in stock so I brought a Leadtek DTV Gold USB. It was much cheaper than the Gigabyte at $36 and a quick check beforehand on some posts showed that some people had it working with Linux.

The Leadtek Gold has an Afatech af9015 chip with a TDA18271 tuner. There is also an af9013 in there somewhere. Note that some older Leadtek Gold’s have a different tuner chip.

Doing some searching found that it was not supported by default in Fedora 10 (FC10) but was easy to install. The instructions are on so many blogs and posts so I will not go into the details, see

but the brief steps are

1. Download v4l for the af9015

This can be done by either downloading the compressed file from http://linuxtv.org/hg/~anttip/af9015/ or using mercurial hg as follows hg clone http://linuxtv.org/hg/~anttip/af9015/

2. Build the source by running make

You will need to have the kernel development files installed. Many posts tell you to get build-essentials and kernel-headers but this is an Ubuntu thing. For Fedora do a yum groupinstall “Development Tools”

3. Download the firmware

from http://www.otit.fi/~crope/v4l-vb/af9015/af9015_firmware_cutter/firmware_files/ and put it in /lib/firmware

4. Then you can do a make install. I chose not to do this and just inserted the modules from the build directory – v4l.

5. Insert the modules by doing the following, if the current ones are loaded you will need to unload them first

insmod dvb-core.ko
insmod dvb-usb.ko
insmod tda18271.ko
insmod af9013.ko
insmod dvb-usb-af9015.ko

6. Then just plug in the Leadtek Gold

To check that it has installed ok use dmesg or run tail –f /var/log/messages before you insert the Leadtek.

Drivers Dvb-dtv Input Devices Using

The output should be something like

Be sure to check that the firmware was installed

Testing

DevicesDrivers dvb-dtv input devices definition

Running ls /dev/dvb/adapter should show demux0 dvr0 frontend0 net0

To test it I did the following, you will need to have dvb-utils installed to do this (yum dvb-utils)

Drivers Dvb-dtv Input Devices

1. Create a channels file by running scandvb /usr/share/dvb/dvb-t/au-Sydney_North_Shore > ~/.mplayer/channels.conf
2. Run mplayer as mplayer dvb://
3. Use h and l to change channels

Remote

Next was to get the remote working. You may have noticed from the install messages that a HID device was created when the Leadtek was installed. This is because the Leadtek is recognised as an usbhid device. However there seems to be a problem with this, a key is recognized by the dvb remote module and the hid module and both are sent to /dev/input and are presented to the active application. This has some advantages in that you do not need to run something like lirc, the keys pressed are passed to the current application just as if it was pressed on a USB keyboard. Although it means that you get 2 keys pressed for every one. What is worse is that there seems to be a key repeating problem, when a key is pressed it initially appears and then keeps on repeating This seems to be coming from the usbhid module rather than the dvb-usb-remote module as I disabled the code in dvb-usb-remote and it still happened. A bit of searching showed that usbhid has a quirks mechanism where you can disable usbhid for specified USB Vendor Id. In this case for the Leadtek Gold the Vendor Id is 0x0413:0x6029. On Ubuntu this is quite easy as the usbhid is loaded as a module and therefore can be done in /etc/modprobe.conf by adding option usbhid quirks=0x0000:0x0000:0x04.

With Fedora, the usbhid is load with the kernel so it has to be dome on the kernel command line. This can be done by changing the bootloader. I use Grub so just edit /boot/grub/grub.conf and change

Drivers Dvb-dtv Input Devices

Drivers Dvb-dtv Input Devices Device

kernel /vmlinuz-2.6.27.5-117.fc10.i686 ro root=UUID=254134e3-d72f-46b2-b857-75753693b7aa rhgb quiet

to

Drivers Dvb-dtv Input Devices Input

kernel /vmlinuz-2.6.27.5-117.fc10.i686 ro root=UUID=254134e3-d72f-46b2-b857-75753693b7aa rhgb quiet usbhid.quirks=0x0413:0x6029:0x04

Drivers Dvb-dtv Input Devices Definition

Once this was done I had the remote working. No repeats and a single character appearing for each remote key press.

The remote emulates a keyboard with MCE functionality these however are not standard MythTv keys. There are a number of ways to fix this

1. Change the MythTv key mappings – this has the disadvantage that the keyboard can not be used to control MythTv,
2. Do linux key mappings, this has the same disadvantage as the first option.
3. Use lirc to do the mapping.

Lirc setup requires a device to read from, a setup file and a remote config file. When the Leadtek Gold is inserted it creates an input at /dev/input/eventx. The event number allocated can be determined by looking at /proc/ bus/input/devices

So to pass the keys from the dvb driver to lirc change /etc/sysconfig/lirc to