[vdr] Input driver problem (was: Re: Name-space conflict)

[Oliver Endriss <o.endriss@gmx.de>]

Rene Bartsch wrote:
> > What options did you use to compile vdr, REMOTE=???
>
> REMOTE=KBD
>
> > I do not understand why/how remote control events could be passed
> > to a tty. Please explain "some keys are available on the ttys".
>
> All numbers in the keyset (e.g. 1, 2, 3, ...) and some charakters
> (e.g. [, ], ...). Obviously they come from the
> driver input-device.
>
> > Which tty device(s) get(s) the remote control events?
>
> The tty which is currently active.

Very strange. Indeed, your remote control events are
passed to the console input, too.

> > Please post output of "ls -l /dev/input" and "ls -l /dev/ttyX"
> > where ttyX is the tty which gets the keys.
>
> 304379 0 crw------- 1 root root 13, 64 Aug 31 01:31 event0
> ...

Looks good.

> > Just an idea: Are you using an USB keyboard?´
>
> No. PS/2
>
> > > So I'll need to disable output to tty. Anyone having a idea how
> > > to set this up in DVB-driver?
> >
> > See above. Try to compile vdr with REMOTE=NONE.
> > This will disable keyboard input.
>
> Why I didn't have that simple idea? Seems I've to recalibrate my
> brain ... ;o)
>
> Works fine now, but I can't use keyboard anymore to control VDR :o( 
> Schnief ...

Well, this is a workaround, not the solution.
I tested with REMOTE=KBD and I it works perfectly for me...
I'm using a vanilla kernel 2.4.19 from kernel.org

In the kernel docs I found the following (Documentation/input/input.txt):
| ...
| The right way would be to pass the events to keyboard.c directly, best if
| keyboard.c would itself be an event handler. This is done in the input
| patch, available on the webpage mentioned below.
| ...

If your Red Hat kernel contains this "input patch", it would explain
what's going on. I'm not sure whether this is a bug or a feature...

You have the following options:
(1) Use the feature:
Modify your rc5 keymap in a way that the remote control will 
create the same event codes as your keyboard does.
You don't need the remote plugin anymore!

(2) Get kernel sources from kernel.org and build your own kernel.

(3) Use a keymap with non-conflicting keycodes
Modify your *.rc5 file in a way that the remote does not create 
the same events as the keyboard. For example, it is not necessary
that the 'up' key of your remote generates a KEY_UP event.
You can assign *any* KEY_XXX event. You can even create 
your own events (see av7110_loadkeys/input_fake.h).

(4) Compile vdr with REMOTE=NONE.
Well, you already did this.

Oliver



-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe vdr" as subject.