[Kwintv] remote control support

[Hans-Peter Jansen]

Am Sunday 17 April 2005 00:28 schrieb 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 :)

Will do, but it will take some time, since holiday always take precedence ;-)
I've fiddled with both /etc/lircd.conf and remote.xml, but need to figure out 
the least invasive way..

> > 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.

This is really great, but still doesn't solve the problems here for 100%.
In fact, if I restart lircd, while irkick is running, it works fine, but that 
isn't the way, things are normally triggered, unfortunately :-(. 

Otherwise, the condition        if(remotes.begin() == remotes.end())
is still met in KCMLirc::updateModes(), thus keeping it in unconfigurable 
state. I ran irkick for 10 times with the same result to backup my claim, but 
with restarting lircd, while irkick is running, it worked on the first try. 
Don't think this is a pure hazard. 

I've no idea, how to delay KCMLirc::updateModes() until the remotes are 
stable, most definitely caused by the many key definitions..

Atfer recompiling lircd with debug infos, it revealed a strange behavior of 
irkick always resetting twice in a row, which is (somewhat) visible also 
through the overlapping passive popups, announcing the several state 
changes.. It would be nice, if you find a way to cut the time needed to 
initialize that beast, while at it ;-)

> > 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 :)

I'm typically not _that_ patient ;)

> > 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.

After applying your fix under the above constraints, it works really fine and 
let me explore its possibilities, which are really great! Can't wait to apply 
this setup to my TV system, but it will need to wait, 'til I'm ready to roll 
out SuSE 9.3 diskless... ;-)

Zsolt, you're my hero of the day!

Cheers,
Pete