From: Pekka Sarnila <sarnila@adit.fi>
To: Antti Palosaari <crope@iki.fi>
Cc: Jiri Slaby <jslaby@suse.cz>, Jiri Kosina <jkosina@suse.cz>,
Pekka Sarnila <pekka.sarnila@qvantel.com>,
linux-media@vger.kernel.org, pb@linuxtv.org, js@linuxtv.org
Subject: Re: dvb-usb-remote woes [was: HID: ignore afatech 9016]
Date: Tue, 02 Feb 2010 17:54:13 +0200 [thread overview]
Message-ID: <4B684AA5.8040107@adit.fi> (raw)
In-Reply-To: <4B674637.8020403@iki.fi>
Ok, that was it, I had the old firmware. Now it works with the patch. I
can now see that the afateck driver does not use the HID
interface/endpoint (1/83) at all, but vendor specific bulk endpoint (0/81).
The fact that manufacturers have started to more more use the usb vendor
class instead of the HID class is probably partly a consequence of HID
specification being poorly designed. Oh, well. More work for driver writers.
Anyway, I'm still of the opinion that the ir-to-code translate should be
per remote controller not per tv-stick (ideally loaded by kernel from
the userspace table, and easily modifiable by userspace program).
All in all the remote controller stack is IMHO a real mess: different
level translates (in kernel and in user space), different user program
interfaces (keyboard with or without the special keys (many programs
recognize only the standard keyboard keys), lircd direct, lircd/dcop).
Really easiest is to modify kernel to get what you want. For average
user the task of getting remote to do what they want is close to mission
impossible. Hope someone would do something about this.
Pekka
Antti Palosaari wrote:
> On 02/01/2010 09:42 PM, Jiri Slaby wrote:
>
>> On 02/01/2010 07:28 PM, Jiri Kosina wrote:
>>
>>> On Mon, 1 Feb 2010, Pekka Sarnila wrote:
>>>
>>>> I pulled few days ago latest
>>>>
>>>>
>>>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>>>>
>>>> and compiled it. Everything works fine including the tv-stick and the
>>>> remote. However I get:
>>>>
>>>> <3>af9015: command failed:255
>>>> <3>dvb-usb: error while querying for an remote control event.
>>
>>
>> Yes, I saw this quite recently too. For me it appears when it is booted
>> up with the stick in. It's still to be fixed.
>
>
> I suspect you are using old firmware, 4.65.0.0 probably, that does not
> support remote polling and thus this 255 errors seen.
>
> regards
> Antti
next prev parent reply other threads:[~2010-02-02 15:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 19:59 [PATCH 1/1] HID: ignore afatech 9016 Jiri Slaby
2010-01-13 20:20 ` Jiri Kosina
2010-01-13 20:34 ` Jiri Slaby
2010-01-13 20:44 ` Jiri Kosina
2010-01-13 20:39 ` [PATCH v2 " Jiri Slaby
2010-01-26 0:56 ` Jiri Kosina
2010-01-26 11:06 ` Pekka Sarnila
[not found] ` <4B5EFD69.4080802@adit.fi>
[not found] ` <alpine.LNX.2.00.1001262344200.30977@pobox.suse.cz>
[not found] ` <4B671C31.3040902@qvantel.com>
[not found] ` <alpine.LNX.2.00.1002011928220.15395@pobox.suse.cz>
2010-02-01 19:42 ` dvb-usb-remote woes [was: HID: ignore afatech 9016] Jiri Slaby
2010-02-01 21:23 ` Antti Palosaari
2010-02-01 21:41 ` Jiri Slaby
2010-02-02 16:16 ` Pekka Sarnila
2010-02-02 15:54 ` Pekka Sarnila [this message]
2010-02-02 16:02 ` Pekka Sarnila
2010-02-05 15:47 ` Pekka Sarnila
2010-02-08 15:52 ` Jiri Kosina
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=4B684AA5.8040107@adit.fi \
--to=sarnila@adit.fi \
--cc=crope@iki.fi \
--cc=jkosina@suse.cz \
--cc=js@linuxtv.org \
--cc=jslaby@suse.cz \
--cc=linux-media@vger.kernel.org \
--cc=pb@linuxtv.org \
--cc=pekka.sarnila@qvantel.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