[Kwintv] remote control support

[Zsolt Rizsanyi]

On Wednesday 13 April 2005 22.18, Hans-Peter Jansen wrote:
> Well, I have this problem too and filed already a related bug report:
> http://bugs.kde.org/show_bug.cgi?id=103668
> after some digging in the code and creating a hauppauge remote
> definition for the linux-input-layer. I wouldn't mind comparing it with
> yours, preferably combined with your /etc/lircd.conf..

You may compare it, altough my /etc/lircd.conf directly comes from Gerd 
Knorr website.
But it would be really nice to merge our kdelirc remote definition files.
Mine currently only contains the buttons I have on my remote. I'm attaching 
it, hoping that you will do the work :)

> Unfortunately, Gav hasn't replied to it, and I refrained from bugging
> him directly. Is there a related ML for such problems, which seem not
> that uncommon, as I already know from somebody else, that he can
> reproduce this problem, but hasn't an idea either: Gerd "Mr. BTTV
> et.al." Knorr.

I have investigated the problem and found the reason. The problem is that 
the program tries to read the whole data about the remotes in one go and 
because the 380 buttons in linux-input-layer doesn't fit in the buffer of 
the socket it fails.
I will be adding more detailed explanation to the bug you opened.

> I predict, that when SuSE 9.3 ships, all those with a Hauppauge WinTV,
> who try to use irkick will complain...
>
> Funny is, in some (rare) tries, it works.

Yes, it might work sometimes :)
Also theoretically it should always work, if you press some button on your 
remote about 200 times. After that it will work :)

> BTW, are you able to select certain buttons directly via your remote
> when adding actions? Does your key list contain all keys defined in
> /etc/lircd?
>
> Unfortunately, both answers are negative here :-(

As you may have already guessed it turned out that it doesn't work for me 
either.
I have just recently tried to set up kdelirc with my 2.6 kernel and when I 
have created the remotes definition file I thought I have solved all the 
problems, but did not really check if it works.
So you are right. Kdelirc is broken with remotes which have many buttons 
(about 200 buttons cause the problem).
I will be committing my fix to KDE cvs soon. Currently only to HEAD, but I 
may be backporting it to 3.3 and 3.4 branches too (altough I will ask 
somebody if that is allowed without explicit permission).
But just in case you cannot wait, I'm attaching the patch which solves the 
issue.

Regards,
Zsolt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linux-input-layer.remote.xml
Type: text/xml
Size: 3907 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kwintv/attachments/20050417/44f6d66f/linux-input-layer.remote.xml
-------------- next part --------------
A non-text attachment was scrubbed...
Name: irkick-long-button-list-fix.patch
Type: text/x-diff
Size: 903 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kwintv/attachments/20050417/44f6d66f/irkick-long-button-list-fix.bin