<html><body bgcolor="#FFFFFF"><div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">On 03/08/2010, at 1:44 AM, Travis Tabbal <<a href="mailto:travis@tabbal.net">travis@tabbal.net</a>> wrote:</span><br></div><div><br></div><div></div><blockquote type="cite"><div><br><br><div class="gmail_quote">On Sun, Aug 1, 2010 at 12:06 PM, Calvin Harrigan <span dir="ltr"><<a href="mailto:charriglists@bellsouth.net"><a href="mailto:charriglists@bellsouth.net">charriglists@bellsouth.net</a></a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div>Sorry about that, it's connected via usb, though through an ftdi chip, so it shows up as a plain serial port on the host.<br></div>
I've been browsing the lirc mailing list, but no luck finding anything that would explain what exactly is going on in LIRC.<br></blockquote></div><br><br>I think you need a driver. LIRC is set up to do the decoding itself. You might be able to crib some of it from the driver for the IRMAN and similar, they decode and pass decoded values to LIRC. <br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>mythtv-users mailing list</span><br><span><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a></span><br><span><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a></span><br></div></blockquote><br><div>If it displays as a serial port would Lirc_serial be able to interpret it?</div><div><br></div><div>Cheers,</div><div><br></div><div>Anthony</div></body></html>