Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[linux-dvb] Re: NEWSTRUCT and Remote Control
> On Wed, 25 Sep 2002, Oliver Endriss wrote:
> > Holger Waechtler wrote:
> > > Oliver Endriss wrote:
> > > > Holger Waechtler wrote:
> > > >
> > > > The new lirc extension is just another driver compiled into
> > > > lircd. /dev/lirc is not used! It simply takes the codes from
> > > > /dev/input/eventX and feeds them into lircd. This way it should
> > > > be possible to use any /dev/input/* device to control lirc. The
> > > > driver itself is very short. The hard thing is understanding
> > > > the lirc source code :-)
> > >
> > > (one more reason for a direct input driver;)
> > Perhaps, but it's already working. :-)
> will you provide a working piece of code for lirc working with the
> NEWSTRUCT branch??
Yes, I will. I'll submit it to the lirc people as soon as I have done
some more testing and the autorepeat issues are solved.
I don't like submitting a piece of code that won't work.
> > > > Ok, I'll try.
> > > > 1. If I press a key on my hauppauge remote control, the *old*
> > > > firmware emits a key-down event. When I release the key, a
> > > > key-up event is generated.
> > >
> > > no. Key up events were gererated in the firmware immidiatly after
> > > each key down event.
> > Sorry, but this is wrong (with the haupauge remote control, at
> > least). I am absolutely sure about this, see the following excerpt
> > from /var/log/messages (note the timestanmps):
> > hold down the key '1':
> > | Sep 25 13:24:36 orion kernel: GPIO0 irq 8 4
> > | Sep 25 13:24:36 orion kernel: GPIO0 irq 08
> > | Sep 25 13:24:36 orion kernel: dvb: ircommand = 80000001
> > | Sep 25 13:24:36 orion kernel: GPIO0 irq exit 0
> > release the key '1':
> > | Sep 25 13:24:42 orion kernel: GPIO0 irq 8 4
> > | Sep 25 13:24:42 orion kernel: GPIO0 irq 08
> > | Sep 25 13:24:42 orion kernel: dvb: ircommand = 00000001
> > | Sep 25 13:24:42 orion kernel: GPIO0 irq exit 0
> looks like a timing problem, because the values for the key-down and
> key-up event are fully correct.. only the key-up is some seconds
No, there is no problem at all!
The point is that the key-up event is not generated *before* I release
the key. Therfore the hauppauge remote control works perfectly with the
old driver. Do not change this! :-)
To unsubscribe send a mail to email@example.com with "unsubscribe linux-dvb" as subject.
Main Index |