[linux-dvb] IR for Afatech 901x

[linux-dvb] IR for Afatech 901x

[pjama]

Hi,
I see there's some activity from Antti in the af9015-mxl500x-copy-fw area
for remotes.

I got, compiled and installed the latest (although there's a NEW one just
4 minutes old) code 737994f33e83 to see if there's any action for my IR
remote bundled with my DigitalNow TinyTwin USB stick. I'm running
mythbuntu 8.04

I'm not even sure if I'm on the right track here but entries like the
following in dmesg got me excited!
input: IR-receiver inside an USB DVB receiver as
/devices/pci0000:00/0000:00:02.1/usb2/2-2/input/input7
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: DigitalNow TinyTwin DVB-T Receiver successfully initialized and
connected.

I'm not having ANY luck extracting any life out of IR though:

# sudo irrecord -d /devices/pci0000:00/0000:00:02.1/usb2/2-2/input/input7
test.conf
irrecord -  application for recording IR-codes for usage with lirc
Copyright (C) 1998,1999 Christoph Bartelmus(lirc@bartelmus.de)
irrecord: could not get file information for
/devices/pci0000:00/0000:00:02.1/usb2/2-2/input/input7
irrecord: default_init(): No such file or directory
irrecord: could not init hardware (lircd running ? --> close it, check
permissions)

Same story with /dev/input/event7, I've turned lirc off and irw just
refuses  to connect.

Is there anything I should try or anything I can test?

Thanks
Peter


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] IR for Afatech 901x

[Antti Palosaari]

pjama wrote:
> Hi,
> I see there's some activity from Antti in the af9015-mxl500x-copy-fw area
> for remotes.

yes, I fixed one bug that has killed remote. Now it works again.

> I got, compiled and installed the latest (although there's a NEW one just
> 4 minutes old) code 737994f33e83 to see if there's any action for my IR
> remote bundled with my DigitalNow TinyTwin USB stick. I'm running
> mythbuntu 8.04

Probably there is wrong ir-table loaded to the device by the driver. 
Ir-table in device and ir-codes from remote should match. Otherwise it 
will not work.

> I'm not even sure if I'm on the right track here but entries like the
> following in dmesg got me excited!
> input: IR-receiver inside an USB DVB receiver as
> /devices/pci0000:00/0000:00:02.1/usb2/2-2/input/input7
> dvb-usb: schedule remote query interval to 150 msecs.
> dvb-usb: DigitalNow TinyTwin DVB-T Receiver successfully initialized and
> connected.

Yes, thats correct. AF9015 implements also HID-remote but I have never 
got it working. I think it could be due to hw bug. Luckily there is 
other way to read remote - polling from the driver.

> I'm not having ANY luck extracting any life out of IR though:
> 
> # sudo irrecord -d /devices/pci0000:00/0000:00:02.1/usb2/2-2/input/input7
> test.conf
> irrecord -  application for recording IR-codes for usage with lirc
> Copyright (C) 1998,1999 Christoph Bartelmus(lirc@bartelmus.de)
> irrecord: could not get file information for
> /devices/pci0000:00/0000:00:02.1/usb2/2-2/input/input7
> irrecord: default_init(): No such file or directory
> irrecord: could not init hardware (lircd running ? --> close it, check
> permissions)
> 
> Same story with /dev/input/event7, I've turned lirc off and irw just
> refuses  to connect.
> 
> Is there anything I should try or anything I can test?

I just tested using...

1)
[root@localhost ~]# hexdump -v -e '"\t" "0x" 1/1 "%02x " "\n"' < 
/dev/input/by-path/pci-1-5--event-ir

2)
[root@localhost ~]# av7110_evtest /dev/input/by-path/pci-1-5--event-ir
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0x15a4 product 0x9016 version 0x200
Input device name: "IR-receiver inside an USB DVB receiver"
Supported events:
   Event type 0 (Reset)
     Event code 0 (Reset)
     Event code 1 (Key)
   Event type 1 (Key)
     Event code 2 (1)
     Event code 3 (2)
     Event code 4 (3)
     Event code 5 (4)
     Event code 6 (5)
     Event code 7 (6)
     Event code 8 (7)
     Event code 9 (8)
     Event code 10 (9)
     Event code 11 (0)
     Event code 113 (Mute)
     Event code 114 (VolumeDown)
     Event code 115 (VolumeUp)
     Event code 116 (Power)
     Event code 354 (Goto)
     Event code 372 (Zoom)
     Event code 402 (ChannelUp)
     Event code 403 (ChannelDown)
Testing ... (interrupt to exit)

Remember that the HID one does not work at all.

> 
> Thanks
> Peter

Antti
-- 
http://palosaari.fi/

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] IR for Afatech 901x

[pjama]

<snip>

> yes, I fixed one bug that has killed remote. Now it works again.
>
>> I got, compiled and installed the latest (although there's a NEW one
>> just
>> 4 minutes old) code 737994f33e83 to see if there's any action for my IR
>> remote bundled with my DigitalNow TinyTwin USB stick. I'm running
>> mythbuntu 8.04

OK just for fun I've now got, compiled and installed 884d9a07c4e1.

>
> Probably there is wrong ir-table loaded to the device by the driver.
> Ir-table in device and ir-codes from remote should match. Otherwise it
> will not work.

How do I confirm this? Should there be something in dmesg?

>
>> I'm not even sure if I'm on the right track here but entries like the
>> following in dmesg got me excited!
>> input: IR-receiver inside an USB DVB receiver as
>> /devices/pci0000:00/0000:00:02.1/usb2/2-2/input/input7
>> dvb-usb: schedule remote query interval to 150 msecs.
>> dvb-usb: DigitalNow TinyTwin DVB-T Receiver successfully initialized and
>> connected.
>
> Yes, thats correct. AF9015 implements also HID-remote but I have never
> got it working. I think it could be due to hw bug. Luckily there is
> other way to read remote - polling from the driver.

So based on the following dmesg extract I should use input7 which equates
to /dev/input/event7 ?

[   33.019604] input: Afatech DVB-T 2 as
/devices/pci0000:00/0000:00:02.1/usb2/2-2/2-2:1.1/input/input1
[   33.032972] input,hidraw0: USB HID v1.01 Keyboard [Afatech DVB-T 2] on
usb-0000:00:02.1-2
[   33.038411] input: HID 0430:0100 as
/devices/pci0000:00/0000:00:02.0/usb1/1-5/1-5:1.0/input/input2
[   33.048961] input,hidraw1: USB HID v1.00 Mouse [HID 0430:0100] on
usb-0000:00:02.0-5
[   33.054403] input: HID 0430:0005 as
/devices/pci0000:00/0000:00:02.0/usb1/1-6/1-6:1.0/input/input3
[   33.068909] input,hidraw2: USB HID v1.00 Keyboard [HID 0430:0005] on
usb-0000:00:02.0-6
[   33.068930] usbcore: registered new interface driver usbhid
[   33.068936] /build/buildd/linux-2.6.24/drivers/hid/usbhid/hid-core.c:
v2.6:USB HID core driver
.......
[   47.868646] mxl500x_attach: MXL500x tuner succesfully attached
[   47.868732] input: IR-receiver inside an USB DVB receiver as
/devices/pci0000:00/0000:00:02.1/usb2/2-2/input/input7
[   47.889081] dvb-usb: schedule remote query interval to 150 msecs.
[   47.889090] dvb-usb: DigitalNow TinyTwin DVB-T Receiver successfully
initialized and connected.
[   47.889094] af9015_init:
[   47.889097] af9015_init_endpoint: USB speed:3
[   47.944449] af9015_download_ir_table:
[   48.215278] usbcore: registered new interface driver dvb_usb_af9015

>
>> I'm not having ANY luck extracting any life out of IR though:
>>
>> # sudo irrecord -d
>> /devices/pci0000:00/0000:00:02.1/usb2/2-2/input/input7
>> test.conf
>> irrecord -  application for recording IR-codes for usage with lirc
>> Copyright (C) 1998,1999 Christoph Bartelmus(lirc@bartelmus.de)
>> irrecord: could not get file information for
>> /devices/pci0000:00/0000:00:02.1/usb2/2-2/input/input7
>> irrecord: default_init(): No such file or directory
>> irrecord: could not init hardware (lircd running ? --> close it, check
>> permissions)
>>
>> Same story with /dev/input/event7, I've turned lirc off and irw just
>> refuses  to connect.
>>
>> Is there anything I should try or anything I can test?
>
> I just tested using...
>
> 1)
> [root@localhost ~]# hexdump -v -e '"\t" "0x" 1/1 "%02x " "\n"' <
> /dev/input/by-path/pci-1-5--event-ir

What's this do in the grand scheme of things? I get no output what so ever
and it returns straight to the prompt.

>
> 2)
> [root@localhost ~]# av7110_evtest /dev/input/by-path/pci-1-5--event-ir
> Input driver version is 1.0.0
> Input device ID: bus 0x3 vendor 0x15a4 product 0x9016 version 0x200
> Input device name: "IR-receiver inside an USB DVB receiver"
> Supported events:
>    Event type 0 (Reset)
>      Event code 0 (Reset)
>      Event code 1 (Key)
>    Event type 1 (Key)
>      Event code 2 (1)
>      Event code 3 (2)
>      Event code 4 (3)
>      Event code 5 (4)
>      Event code 6 (5)
>      Event code 7 (6)
>      Event code 8 (7)
>      Event code 9 (8)
>      Event code 10 (9)
>      Event code 11 (0)
>      Event code 113 (Mute)
>      Event code 114 (VolumeDown)
>      Event code 115 (VolumeUp)
>      Event code 116 (Power)
>      Event code 354 (Goto)
>      Event code 372 (Zoom)
>      Event code 402 (ChannelUp)
>      Event code 403 (ChannelDown)
> Testing ... (interrupt to exit)

This looks promising....
$ evtest /dev/input/event7
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0x13d3 product 0x3226 version 0x200
Input device name: "IR-receiver inside an USB DVB receiver"
Supported events:
  Event type 0 (Reset)
    Event code 0 (Reset)
    Event code 1 (Key)
  Event type 1 (Key)
    Event code 2 (1)
    Event code 3 (2)
    Event code 4 (3)
    Event code 5 (4)
    Event code 6 (5)
    Event code 7 (6)
    Event code 8 (7)
    Event code 9 (8)
    Event code 10 (9)
    Event code 11 (0)
    Event code 113 (Mute)
    Event code 114 (VolumeDown)
    Event code 115 (VolumeUp)
    Event code 116 (Power)
    Event code 354 (Goto)
    Event code 372 (Zoom)
    Event code 402 (ChannelUp)
    Event code 403 (ChannelDown)
Testing ... (interrupt to exit)

>
> Remember that the HID one does not work at all.

evtest gives me a somewhat extended output from event1.


I'm not actually "at" my PC right now os I can't see what button presses
on the remote do ATM.

So based on the above which device do I use for lirc? /dev/input/event7
(or more stable link to same)?

Cheers
Peter



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] IR for Afatech 901x

[Antti Palosaari]

pjama wrote:
>> Probably there is wrong ir-table loaded to the device by the driver.
>> Ir-table in device and ir-codes from remote should match. Otherwise it
>> will not work.
> 
> How do I confirm this? Should there be something in dmesg?

I can try to look correct tables from sniffs I have... but it can take 
some time. Maybe tomorrow.

> This looks promising....
> $ evtest /dev/input/event7
> Input driver version is 1.0.0
> Input device ID: bus 0x3 vendor 0x13d3 product 0x3226 version 0x200
> Input device name: "IR-receiver inside an USB DVB receiver"

Thats the correct one.


-- 
http://palosaari.fi/

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] IR for Afatech 901x

[Antti Palosaari]

Antti Palosaari wrote:
> pjama wrote:
>>> Probably there is wrong ir-table loaded to the device by the driver.
>>> Ir-table in device and ir-codes from remote should match. Otherwise it
>>> will not work.
>> How do I confirm this? Should there be something in dmesg?
> 
> I can try to look correct tables from sniffs I have... but it can take 
> some time. Maybe tomorrow.

I did it. Please test
http://linuxtv.org/hg/~anttip/af9015-mxl500x-copy-fw/

For a little luck some buttons may work.

I think all buttons you have makes events and can see in usb-transfers. 
But there is still mappings to do...

Load driver with debug=2 (rmmod dvb-usb-af9015; modprobe dvb-usb-af9015 
debug=2) and tail -f /var/log/messages to see if there is now some bytes 
coming from remote.

>> This looks promising....
>> $ evtest /dev/input/event7
>> Input driver version is 1.0.0
>> Input device ID: bus 0x3 vendor 0x13d3 product 0x3226 version 0x200
>> Input device name: "IR-receiver inside an USB DVB receiver"
> 
> Thats the correct one.

Antti
-- 
http://palosaari.fi/

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] IR for Afatech 901x

[pjama]

> Antti Palosaari wrote:
>> pjama wrote:
>>>> Probably there is wrong ir-table loaded to the device by the driver.
>>>> Ir-table in device and ir-codes from remote should match. Otherwise it
>>>> will not work.
>>> How do I confirm this? Should there be something in dmesg?
>>
>> I can try to look correct tables from sniffs I have... but it can take
>> some time. Maybe tomorrow.
>
> I did it. Please test
> http://linuxtv.org/hg/~anttip/af9015-mxl500x-copy-fw/

That's got to be the quickest "Maybe tomorrow." I've ever come across. :)

>
> For a little luck some buttons may work.
>
> I think all buttons you have makes events and can see in usb-transfers.
> But there is still mappings to do...
>
> Load driver with debug=2 (rmmod dvb-usb-af9015; modprobe dvb-usb-af9015
> debug=2) and tail -f /var/log/messages to see if there is now some bytes
> coming from remote.

OK linux lesson time here but when I do "rmmod dvb-usb-af9015" I loose the
/dev/input/event7 and associated links files. When I do "modprobe
dvb-usb-af9015 debug=2" the files don't come back. There's probably
something really obvious I'm supposed to do here but I've no idea what it
is...

from /var/log/messages
May 20 13:51:41 SunU20 kernel: [  420.212086] usbcore: deregistering
interface driver dvb_usb_af9015
May 20 13:51:41 SunU20 kernel: [  420.212305] af9015_usb_device_exit:
May 20 13:51:41 SunU20 kernel: [  420.212310] af9015_i2c_exit:
May 20 13:51:41 SunU20 kernel: [  420.240392] dvb-usb: DigitalNow TinyTwin
DVB-T Receiver successfully deinitialized and disconnected.

May 20 13:53:21 SunU20 kernel: [  519.937166] >>> 22 00 a1 00 31 00 01 01
May 20 13:53:22 SunU20 kernel: [  520.936533] dvb_usb_af9015: probe of
2-2:1.0 failed with error -110
May 20 13:53:22 SunU20 kernel: [  520.936782] usbcore: registered new
interface driver dvb_usb_af9015


Once again I'm not "at" my PC so I can't press any buttons on the remote
but I suspect it won't work at this point.

Cheers
Peter


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] IR for Afatech 901x

[pjama]

>
> Load driver with debug=2 (rmmod dvb-usb-af9015; modprobe dvb-usb-af9015
> debug=2) and tail -f /var/log/messages to see if there is now some bytes
> coming from remote.

As mentioned in an earlier response to this post, the above trashes the
device /dev/input/event7. Is there any way I can boot with debug set?

>
>>> This looks promising....
>>> $ evtest /dev/input/event7
>>> Input driver version is 1.0.0
>>> Input device ID: bus 0x3 vendor 0x13d3 product 0x3226 version 0x200
>>> Input device name: "IR-receiver inside an USB DVB receiver"
>>
>> Thats the correct one.

Doing evtest on /dev/input/event7 then pushing remote buttons give me
nothing. I have confirmed remote/receiver works by booting into windows
and using vendor supplied app.

Cheers
Peter


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] IR for Afatech 901x

[Antti Palosaari]

pjama wrote:
>> Load driver with debug=2 (rmmod dvb-usb-af9015; modprobe dvb-usb-af9015
>> debug=2) and tail -f /var/log/messages to see if there is now some bytes
>> coming from remote.
> 
> As mentioned in an earlier response to this post, the above trashes the
> device /dev/input/event7. Is there any way I can boot with debug set?

1) unplug your device
2) make sure new drivers are installed
3) reboot your machine
4) modprobe dvb-usb-af9015 debug=2
5) tail -f /var/log/messages
6) plug stick (now it should start pushing lines to /var/log/messages 
(or /var/log/debug) ?)

Remote buttons should now recognized in debug dumps.

> Doing evtest on /dev/input/event7 then pushing remote buttons give me
> nothing. I have confirmed remote/receiver works by booting into windows
> and using vendor supplied app.

It does not work because driver does not have mappings to your remote 
controller buttons yet. You should find correct mappings from debug dump 
described above.

Antti
-- 
http://palosaari.fi/

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] IR for Afatech 901x

[pjama]

Antti Palosaari wrote:
> pjama wrote:
>> As mentioned in an earlier response to this post, the above trashes the
>> device /dev/input/event7. Is there any way I can boot with debug set?
>
> 1) unplug your device

<unplugs device>

> 2) make sure new drivers are installed

$ modprobe -l | grep 9015
/lib/modules/2.6.24-16-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-af9015.ko
$

> 3) reboot your machine

$ sudo reboot

> 4) modprobe dvb-usb-af9015 debug=2

$ sudo modprobe dvb-usb-af9015 debug=2
<no visible output to console or /var/log/messages>

> 5) tail -f /var/log/messages


> 6) plug stick (now it should start pushing lines to /var/log/messages (or /var/log/debug) ?)

from /var/log/debug
May 23 07:17:54 SunU20 NetworkManager: <debug> [1211491074.409994] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_13d3_3226_010101010600001').
May 23 07:17:54 SunU20 NetworkManager: <debug> [1211491074.542633] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_ffffffff_ffffffff_noserial').
May 23 07:17:54 SunU20 NetworkManager: <debug> [1211491074.645105] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_ffffffff_ffffffff_noserial').
May 23 07:17:54 SunU20 NetworkManager: <debug> [1211491074.752626] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_ffffffff_ffffffff_noserial').
May 23 07:17:54 SunU20 NetworkManager: <debug> [1211491074.778197] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_ffffffff_ffffffff_noserial').
May 23 07:17:54 SunU20 NetworkManager: <debug> [1211491074.787075] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_13d3_3226_010101010600001').
May 23 07:17:54 SunU20 NetworkManager: <debug> [1211491074.976377] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_13d3_3226_010101010600001').
May 23 07:17:55 SunU20 NetworkManager: <debug> [1211491075.092114] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_13d3_3226_010101010600001_dvb').
May 23 07:17:55 SunU20 NetworkManager: <debug> [1211491075.178304] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_13d3_3226_010101010600001_dvb_0').
May 23 07:17:55 SunU20 NetworkManager: <debug> [1211491075.243582] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_13d3_3226_010101010600001_dvb_1').
May 23 07:17:55 SunU20 NetworkManager: <debug> [1211491075.245446] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_ffffffff_ffffffff_noserial').
May 23 07:17:55 SunU20 NetworkManager: <debug> [1211491075.741105] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_13d3_3226_010101010600001_dvb_2').
May 23 07:17:55 SunU20 NetworkManager: <debug> [1211491075.826068] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_13d3_3226_010101010600001_dvb_3').
May 23 07:17:55 SunU20 NetworkManager: <debug> [1211491075.860566] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_13d3_3226_010101010600001_dvb_4').
May 23 07:17:55 SunU20 NetworkManager: <debug> [1211491075.885109] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_13d3_3226_010101010600001_dvb_5').
May 23 07:17:56 SunU20 NetworkManager: <debug> [1211491076.558260] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_13d3_3226_010101010600001_dvb_6').
May 23 07:17:56 SunU20 NetworkManager: <debug> [1211491076.686901] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_13d3_3226_010101010600001_logicaldev_input').
May 23 07:17:57 SunU20 NetworkManager: <debug> [1211491077.468914] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_13d3_3226_010101010600001_if1').
May 23 07:17:57 SunU20 NetworkManager: <debug> [1211491077.620294] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_13d3_3226_010101010600001_if1_logicaldev_input').


from /var/log/messages
May 23 07:17:54 SunU20 kernel: [  540.173598] usb 2-2: new high speed USB device using ehci_hcd and address 4
May 23 07:17:54 SunU20 kernel: [  540.310477] usb 2-2: configuration #1 chosen from 1 choice
May 23 07:17:54 SunU20 kernel: [  540.318760] af9015_usb_probe: interface:0
May 23 07:17:54 SunU20 kernel: [  540.321138] af9015_read_config: TS mode:1
May 23 07:17:54 SunU20 kernel: [  540.323141] af9015_read_config: [0] xtal:2 set adc_clock:28000
May 23 07:17:54 SunU20 kernel: [  540.327127] af9015_read_config: [0] IF1:4570
May 23 07:17:54 SunU20 kernel: [  540.331126] af9015_read_config: [0] MT2060 IF1:0
May 23 07:17:54 SunU20 kernel: [  540.333122] af9015_read_config: [0] tuner id:30
May 23 07:17:54 SunU20 kernel: [  540.335122] af9015_read_config: [1] xtal:2 set adc_clock:28000
May 23 07:17:54 SunU20 kernel: [  540.339118] af9015_read_config: [1] IF1:4570
May 23 07:17:54 SunU20 kernel: [  540.343114] af9015_read_config: [1] MT2060 IF1:0
May 23 07:17:54 SunU20 kernel: [  540.345114] af9015_read_config: [1] tuner id:30
May 23 07:17:54 SunU20 kernel: [  540.346862] af9015_identify_state: reply:01
May 23 07:17:54 SunU20 kernel: [  540.346867] dvb-usb: found a 'DigitalNow TinyTwin DVB-T Receiver' in cold state, will try to load a firmware
May 23 07:17:54 SunU20 kernel: [  540.382541] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
May 23 07:17:54 SunU20 kernel: [  540.382549] af9015_download_firmware:
May 23 07:17:54 SunU20 kernel: [  540.495783] af9015_usb_probe: interface:1
May 23 07:17:54 SunU20 kernel: [  540.495892] usb 2-2: USB disconnect, address 4
May 23 07:17:54 SunU20 kernel: [  540.497615] af9015_usb_device_exit:
May 23 07:17:54 SunU20 kernel: [  540.497621] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
May 23 07:17:54 SunU20 kernel: [  540.497697] af9015_usb_device_exit:
May 23 07:17:54 SunU20 kernel: [  540.497700] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
May 23 07:17:54 SunU20 kernel: [  540.737250] usb 2-2: new high speed USB device using ehci_hcd and address 5
May 23 07:17:54 SunU20 kernel: [  540.874852] usb 2-2: configuration #1 chosen from 1 choice
May 23 07:17:54 SunU20 kernel: [  540.875266] af9015_usb_probe: interface:0
May 23 07:17:54 SunU20 kernel: [  540.876726] af9015_read_config: TS mode:1
May 23 07:17:54 SunU20 kernel: [  540.883959] af9015_read_config: [0] xtal:2 set adc_clock:28000
May 23 07:17:54 SunU20 kernel: [  540.887726] af9015_read_config: [0] IF1:4570
May 23 07:17:54 SunU20 kernel: [  540.891715] af9015_read_config: [0] MT2060 IF1:0
May 23 07:17:54 SunU20 kernel: [  540.893713] af9015_read_config: [0] tuner id:30
May 23 07:17:54 SunU20 kernel: [  540.895707] af9015_read_config: [1] xtal:2 set adc_clock:28000
May 23 07:17:54 SunU20 kernel: [  540.899704] af9015_read_config: [1] IF1:4570
May 23 07:17:54 SunU20 kernel: [  540.903700] af9015_read_config: [1] MT2060 IF1:0
May 23 07:17:54 SunU20 kernel: [  540.905700] af9015_read_config: [1] tuner id:30
May 23 07:17:55 SunU20 kernel: [  540.907448] af9015_identify_state: reply:02
May 23 07:17:55 SunU20 kernel: [  540.907453] dvb-usb: found a 'DigitalNow TinyTwin DVB-T Receiver' in warm state.
May 23 07:17:55 SunU20 kernel: [  540.907520] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
May 23 07:17:55 SunU20 kernel: [  540.908586] DVB: registering new adapter (DigitalNow TinyTwin DVB-T Receiver)
May 23 07:17:55 SunU20 kernel: [  540.908871] af9015_af9013_frontend_attach: init I2C
May 23 07:17:55 SunU20 kernel: [  540.908875] af9015_i2c_init:
May 23 07:17:55 SunU20 kernel: [  540.908899] af9015_eeprom_dump:
May 23 07:17:55 SunU20 kernel: [  540.966659] 00: 2a 88 9b 0b 00 00 00 00 d3 13 26 32 00 02 01 02
May 23 07:17:55 SunU20 kernel: [  541.009863] 10: 03 80 00 fa fa 10 40 ef 01 30 31 30 31 30 39 31
May 23 07:17:55 SunU20 kernel: [  541.053354] 20: 34 30 36 30 30 30 30 31 ff ff ff ff ff ff ff ff
May 23 07:17:55 SunU20 kernel: [  541.097560] 30: 00 01 3a 01 00 08 02 00 da 11 00 00 1e ff ff ff
May 23 07:17:55 SunU20 kernel: [  541.137636] 40: ff ff ff ff ff 08 02 00 da 11 00 00 1e ff ff ff
May 23 07:17:55 SunU20 kernel: [  541.181502] 50: ff ff ff ff ff 24 00 00 04 03 09 04 10 03 41 00
May 23 07:17:55 SunU20 kernel: [  541.213478] 60: 66 00 61 00 74 00 65 00 63 00 68 00 10 03 44 00
May 23 07:17:55 SunU20 kernel: [  541.245458] 70: 56 00 42 00 2d 00 54 00 20 00 32 00 20 03 30 00
May 23 07:17:55 SunU20 kernel: [  541.277433] 80: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00
May 23 07:17:55 SunU20 kernel: [  541.309409] 90: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff
May 23 07:17:55 SunU20 kernel: [  541.341385] a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 23 07:17:55 SunU20 kernel: [  541.373361] b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 23 07:17:55 SunU20 kernel: [  541.405329] c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 23 07:17:55 SunU20 kernel: [  541.437314] d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 23 07:17:55 SunU20 kernel: [  541.469290] e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 23 07:17:55 SunU20 kernel: [  541.501263] f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 23 07:17:55 SunU20 kernel: [  541.562963] af9013: firmware version:4.95.0
May 23 07:17:55 SunU20 kernel: [  541.582960] DVB: registering frontend 0 (Afatech AF9013 DVB-T)...
May 23 07:17:55 SunU20 kernel: [  541.583019] af9015_tuner_attach:
May 23 07:17:55 SunU20 kernel: [  541.674600] mxl500x_attach: Attaching ...
May 23 07:17:55 SunU20 kernel: [  541.674608] mxl500x_attach: MXL500x tuner succesfully attached
May 23 07:17:55 SunU20 kernel: [  541.674614] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
May 23 07:17:55 SunU20 kernel: [  541.675238] DVB: registering new adapter (DigitalNow TinyTwin DVB-T Receiver)
May 23 07:17:55 SunU20 kernel: [  541.675520] af9015_copy_firmware:
May 23 07:17:56 SunU20 kernel: [  542.183518] af9015_copy_firmware: firmware copy done
May 23 07:17:56 SunU20 kernel: [  542.289426] af9015_copy_firmware: firmware boot cmd status:0
May 23 07:17:56 SunU20 kernel: [  542.393349] af9015_copy_firmware: firmware status cmd status:0 fw status:0c
May 23 07:17:56 SunU20 kernel: [  542.399344] af9013: firmware version:4.95.0
May 23 07:17:56 SunU20 kernel: [  542.419332] DVB: registering frontend 1 (Afatech AF9013 DVB-T)...
May 23 07:17:56 SunU20 kernel: [  542.419391] af9015_tuner_attach:
May 23 07:17:56 SunU20 kernel: [  542.419458] mxl500x_attach: Attaching ...
May 23 07:17:56 SunU20 kernel: [  542.419461] mxl500x_attach: MXL500x tuner succesfully attached
May 23 07:17:56 SunU20 kernel: [  542.419541] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:02.1/usb2/2-2/input/input6
May 23 07:17:56 SunU20 kernel: [  542.448249] dvb-usb: schedule remote query interval to 150 msecs.
May 23 07:17:56 SunU20 kernel: [  542.448259] dvb-usb: DigitalNow TinyTwin DVB-T Receiver successfully initialized and connected.
May 23 07:17:56 SunU20 kernel: [  542.448264] af9015_init:
May 23 07:17:56 SunU20 kernel: [  542.448267] af9015_init_endpoint: USB speed:3
May 23 07:17:56 SunU20 kernel: [  542.526252] af9015_download_ir_table:
May 23 07:17:57 SunU20 kernel: [  543.257845] input: Afatech DVB-T 2 as /devices/pci0000:00/0000:00:02.1/usb2/2-2/2-2:1.1/input/input7
May 23 07:17:57 SunU20 kernel: [  543.287701] input,hidraw2: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-0000:00:02.1-2

>
> Remote buttons should now recognized in debug dumps.

nada. No more output to debug when pressing remote buttons, enter, left right 1,2,3 vol+/- etc


cheers
Peter

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb