Re: [linux-dvb] Patch for DigitalNow TinyTwin remote.

From: Stuart <mailing-lists@enginuities.com>
To: Antti Palosaari <crope@iki.fi>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Patch for DigitalNow TinyTwin remote.
Date: Mon, 27 Apr 2009 01:08:13 +1000	[thread overview]
Message-ID: <200904270108.15538.mailing-lists@enginuities.com> (raw)
In-Reply-To: <49EF5F85.2040909@iki.fi>

Hi Antti,

> I have ~same stick (AzureWave) as you have and Fedora 10
> x86 and same fw. It is strange that this repeating issue does not affect
>   me :o I have seen this problem earlier, but don't remember which hw,
> fw and Fedora version was running.

The drivers contain firmware that is downloaded at offset 0x5100. Perhaps 
different devices have different firmware below this value, I believe mine is 
V3.0 (I'll explain later).

The only other thing I can think of is to do with polling. You may find slightly 
different behaviour with:

echo "1" > /sys/module/dvb_usb/parameters/disable_rc_polling

Also, if you have debugfs and usbmon then looking at the usbmon output for the 
device when a key is pressed on the remote may be interesting as well (obviously 
with polling disabled).

In case you're interested here's my list:

Kernel: 2.6.29
Distribution: Gentoo
Device: DigitalNow TinyTwin

Driver firmware issues:
4.95.0: 17x delay bug
All: Incorrectly report bInterval as full speed for high speed bus (can be 
worked around using HID quirks).

> I think hw is very much used Intel 8051 based, it could be nice to see
> decompile from various firmwares. I tried that before but without
> success - probably I don't have experience needed to set-up decompiler
> parameters.

It certainly seems to be an 8051/2 style uC. I've managed to download the memory 
up to 0x5100, combine this with the different versions of firmware from the 
drivers and disassemble them.

Looking at the memory downloaded from the device shows 'V3.0' at offset 0x0542, 
leading me to believe that may be the version for the code pre-programmed in to 
this device (as opposed to the driver firmware version).

> Probably I can try to ask manufacturer also fix for fw, don't know
> what's their response because AF9015 is old chipset and AF9035 is
> current one.

It would be best if they could help in some way, if they won't fix the firmware 
then if they could provide some source code that would be fantastic, otherwise 
some documentation would go a long way. I've managed to work out some of the 
simpler things and started to run it through a simulator but it'll take a while 
to work through the code without any documentation/source code!

Cheers,

Stuart

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb