From: Dan C. <dc...@ac...> - 2005-03-06 19:44:38
|
I'm really glad a few folks have had the time to look into this and build a driver for the new remotes. If i ever have free time (hah!) i'll look into the interrupt vs bulk thing. Strange that it only advertises bulk endpoints but you can use them as interrupt - if that works on the older remotes too then it might make sense to add the initialization stuff and the vendor/product id the older remotes use into the new driver, since i think people might get confused between the two. Some MCE2005 remotes are microsoft branded. Thanks again Jim and Martin, also thanks to Troy Roberts did some initial investigation into the new remotes. Martin Blatter wrote: > Well, I just installed kernel 2.6.11 based on the input I got from this list > and guess what, initialization works every time! > > It looks like the problem lies within USB enumeration in the Linux kernel > code. So I'm afraid you'll have to install kernel 2.6.10 or higher to use > this driver. > > The interrupt-driven version is attached. You might want to rename > it to lirc_mceusb for easier installation when testing. Don't forget to > change the driver name on line 55 as well. > > I will add some finishing touches and clean up the code later this week > and eventually submit it to the lirc folks. > > Have fun playing with the remote ;-) > > regards > martin > > On Wed, 02 Mar 2005 22:28:45 -0700, Jim Cottrell <Jim...@ut...> wrote: > >>The timeout message is normal, because the driver polls the receiver for >>data. Martin Blatter has told me his driver uses interrupts, which I >>didn't think was possible with this receiver. So, we might be able to >>do away with the timeouts. |