From: Max S. <ms...@em...> - 2000-06-11 06:04:26
|
I want to add support for the Slink-e (http://www.nirvis.com/slink-e.htm) to lircd. Since Slink-e delivers already an IR signal via the serial port as a sequence of pulse/space durations, it wasn't too difficult to start with the decoder source for the logitech receiver. But now, I'm somewhat puzzled in what to do with such a pulse/space timing sequence. Clearly, my decoder needs to convert it into a hex code by making use of the parameters coming from a lircd.conf. But these parameters in the lircd.conf confuse me even more. I'd appreciate if someone could help me here. -Max |
From: <col...@hi...> - 2000-06-12 14:12:57
|
Hi! Max Spring "ms...@em..." wrote: MS> I want to add support for the Slink-e MS> (http://www.nirvis.com/slink-e.htm) to lircd. Since Slink-e delivers MS> already an IR signal via the serial port as a sequence of pulse/space MS> durations, it wasn't too difficult to start with the decoder source MS> for the logitech receiver. MS> MS> But now, I'm somewhat puzzled in what to do with such a pulse/space MS> timing sequence. Clearly, my decoder needs to convert it into a hex MS> code by making use of the parameters coming from a lircd.conf. But MS> these parameters in the lircd.conf confuse me even more. I'd MS> appreciate if someone could help me here. You will have to base your new module on hw_default.c (at least I thing that will be the most easy way to do it). Just like in hw_default.c you will have to use the functions from receive.c to convert the pulse/space sequences into hex codes. You don't have receive.c in your source tree? Never mind, I uploaded it to CVS 5 minutes ago. Christoph |
From: Max S. <ms...@em...> - 2000-06-15 05:13:16
|
Christoph, thanks for your advise on receive.c and CVS. I did that and what I saw in receive.c looks promising. However, I have difficulties in getting this latest version to play. So far, I did the same thing which I was doing with the 0.6.0 version: I added my hw_slinke module, everything compiled fine, my slinke_init() gets called and then it hangs in waitfordata() in the second select call: int waitfordata(unsigned long maxusec) { ... while(1) { ... do{ do{ ... if(maxusec>0) { ... ret=select(maxfd+1,&fds,NULL,NULL,&tv); ... } else { ret=select(maxfd+1,&fds,NULL,NULL,NULL); /* this select call never returns */ } ... } I've no idea what could be the reason. Maybe you know? In either case, my goal is first to have the 0.6.1 version working at the same level I was with 0.6.0. Then I'll try to make use of the decoding functionality in receive.c. From what I've seen so far I will probably need to add an additional function there by which I fill this rec_buffer in one shot. Regards, -Max > From: col...@hi... (Christoph Bartelmus) > X-ZC-PGP-Key-Avail: > X-Gateway: ZCONNECT UR hit.handshake.de [DUUCP BETA vom 01.05.2000] > Date: 12 Jun 2000 11:17:00 +0200 > X-Mailman-Version: 1.1 > List-Id: LIRC mailing list <lirc-list.lists.sourceforge.net> > X-BeenThere: lir...@li... > > Hi! > > Max Spring "ms...@em..." wrote: > > MS> I want to add support for the Slink-e > MS> (http://www.nirvis.com/slink-e.htm) to lircd. Since Slink-e delivers > MS> already an IR signal via the serial port as a sequence of pulse/space > MS> durations, it wasn't too difficult to start with the decoder source > MS> for the logitech receiver. > MS> > MS> But now, I'm somewhat puzzled in what to do with such a pulse/space > MS> timing sequence. Clearly, my decoder needs to convert it into a hex > MS> code by making use of the parameters coming from a lircd.conf. But > MS> these parameters in the lircd.conf confuse me even more. I'd > MS> appreciate if someone could help me here. > > You will have to base your new module on hw_default.c (at least I thing > that will be the most easy way to do it). Just like in hw_default.c you > will have to use the functions from receive.c to convert the pulse/space > sequences into hex codes. > > You don't have receive.c in your source tree? Never mind, I uploaded it to > CVS 5 minutes ago. > > Christoph |