public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: linux-media@vger.kernel.org, Stuart <mailing-lists@enginuities.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Patch for DigitalNow TinyTwin remote.
Date: Mon, 16 Mar 2009 23:36:28 +0200	[thread overview]
Message-ID: <49BEC65C.8070302@iki.fi> (raw)
In-Reply-To: <200903140506.00723.mailing-lists@enginuities.com>

hei Stuart,

Stuart wrote:
> First of all, thanks to those involved in getting the TinyTwin working!
> 
> I haven't found any support for the remote control yet so I would like to offer what I've managed to do so far (in case I've done something wrong as this is the first time I've tried to submit a patch).
> 
> The remote I'm referring to is pictured here (albeit with a few buttons labeled differently):
> 
> http://www.digitalnow.com.au/images/ProRemote.jpg

Same remote as TwinHan AzureWave AD-TU700(704J).
This is just same device as AzureWave.

> I extracted an ir table from the .bin file located in:
> 
> http://www.digitalnow.com.au/DNTV/TinyTwinRemote4MCE.zip
> (listed at the bottom of http://www.digitalnow.com.au/downloads.html)
> 
> After changing linux/drivers/media/dvb/dvb-usb/af9015.[ch] I got a response from the remote, however, it would auto-repeat indefinitely. I believe this is caused by no "key up" event with the usbhid driver. To stop usbhid from attaching to the device I've modified a 
> couple of files in the kernel. This appears to leave dvb-usb-af9015 in charge of creating events for the remote by polling (is this the correct method to go about it?).

Someone should really examine that more. Take some sniffs to see how 
Windows handle that.
http://www.linuxtv.org/pipermail/linux-dvb/2008-November/030292.html
http://linuxtv.org/wiki/index.php/MSI_DigiVox_mini_II_V3.0

> Some keys don't work (I don't know if it's possible to get them working with a revised ir table), they're labeled on the remote as:
> 
> Tab, Capture, PIP, L/R, Recall, Zoom-, Red
> 
> The included patches apply to the following versions:
> 
> af9015: a57ea2073e77
> kernel: 2.6.29_rc7
> 
> I'm not sure if this is the correct approach, however, it seems to be working for me so any feedback would be appreciated!

I am also not sure about HID changes.
And also could you test whether AzureWave IR-tables are OK because 
device looks just same, even remote.

regards
Antti
-- 
http://palosaari.fi/

  reply	other threads:[~2009-03-16 21:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13 18:06 [linux-dvb] Patch for DigitalNow TinyTwin remote Stuart
2009-03-16 21:36 ` Antti Palosaari [this message]
2009-03-17  3:10   ` Stuart
2009-03-27 15:20     ` Antti Palosaari
     [not found]       ` <49D13111.9020300@iki.fi>
2009-03-31 14:04         ` Stuart
     [not found] ` <49D23920.5010903@iki.fi>
     [not found]   ` <49D24315.8020107@iki.fi>
2009-04-01 13:43     ` Stuart
2009-04-01 22:38       ` Antti Palosaari
2009-04-02  1:17         ` Stuart
2009-04-02  8:33           ` Antti Palosaari
2009-04-22  7:25         ` Stuart
2009-04-22 18:18           ` Antti Palosaari
2009-04-26 15:08             ` Stuart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49BEC65C.8070302@iki.fi \
    --to=crope@iki.fi \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mailing-lists@enginuities.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox