<br><br><div class="gmail_quote">On Sun, Aug 30, 2009 at 9:51 PM, Jarod Wilson <span dir="ltr"><<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On Sunday 30 August 2009 20:27:40 Jack Perveiler wrote:<br>
> On Sun, Jul 5, 2009 at 10:00 PM, Jarod Wilson <<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>> wrote:<br>
><br>
> > On 07/05/2009 05:47 PM, Jarod Wilson wrote:<br>
> ><br>
> >> Just wanted to give folks a heads up... I just committed changes in lirc<br>
> >> cvs that merge support for the first-gen mceusb receiver and all the<br>
> >> others into a single driver, which going forward, is going to be called<br>
> >> 'lirc_mceusb' -- dropping the 2 off the end for the newer devices, so<br>
> >> lirc_mceusb2 is (will be) no more.<br>
> >><br>
> >> Of course, it'll have a modalias of lirc_mceusb2, and it should still<br>
> >> auto-load for supported devices anyway, but I figured folks might want<br>
> >> to know what's going on just the same. It'll show up officially in lirc<br>
> >> 0.8.6 (and probably soonish in a 0.8.6pre2 snap), as well as in a Fedora<br>
> >> development kernel near you...<br>
> >><br>
> >> For those with the 1st-gen device, in theory, your device should now be<br>
> >> able to transmit as well as receive, but I've not yet bothered to test<br>
> >> xmit... If it doesn't work, it shouldn't be terribly difficult to get it<br>
> >> working, since most of the necessary code should already be in place. If<br>
> >> you get around to testing xmit before I do, please do let me know.<br>
> >><br>
> ><br>
> > So I actually tried testing... Doesn't seem to be working. But it could be<br>
> > that it doesn't like the blaster cable I plugged into it, which is from a<br>
> > different device. (I don't have the original blaster cables from this<br>
> > thing). More likely the cables are find though, and there's simply some<br>
> > remaining work to be done to get transmit working on the 1st-gen device.<br>
> > Will poke more later, additional testing feedback still welcomed,<br>
> > particularly from someone who has the original blaster cables...<br>
> ><br>
> ><br>
> I have the original blaster cables (well, I THINK they're the original... I<br>
> got the cable+transceiver from ebay, but things LOOK new) and like you<br>
> nothing happened when I tried blasting. I'm open to suggestions and am a<br>
> willing tester (I just don't know what to look for).<br>
<br>
</div></div>There's been some recent work done over on the lirc list. The second<br>
port is sending stuff, and every once in a while, its actually correct,<br>
so transmit support on these should be functional relatively soon...<br>
<br></blockquote></div><br>Thanks, I hadn't realized debug was actually ongoing. I found the thread over on the lirc list, and it does sound promising. I'll follow things over there.<br><br>Thanks again,<br><br>
--Jack<br>