From: Tino K. <tin...@ti...> - 2007-06-22 05:48:12
|
On Thu, Jun 21, 2007 at 23:47:41 +0100, Stephen Williams wrote: [...] > Well, there's nothing obvious from the out put. Have you tried from a > cleanly booted system without ever loading the apple_ir module, just > trying to rule out any interaction. Yes, I moved the appleir.ko file into my home directory, so that the kernel hadn't a chance to load it, and rebooted. > > I don't suppose you might be using a different version of the mac mini > could you, i'm using one of the latest Intel core duo models... It is the first Core Duo model with an Intel CPU (Superdrive, 80 GB hard disk, 1,66 GHz CPU) > I'm afraid that all I can really state is that is works fine for me, > as an early adopter you may have to resort some debugging to find out > exactly what data is being read from the device. Fortunately there's > nothing complicated about the code. OK, maybe I'll try this if I find the time. A last question: does it work with remotes other than the Apple remote as well? My plan was to use the remote for my DVB-T receiver with the macmini driver, as the IR sensor in the DVB-T box is _really_ weak compared to the sensor in the Mac mini. I can see it in the kernel log when the Mac mini sensor received IR events from the DVB-T remote because the kernel complains about unknown keycodes. Maybe it would just be enough to modify the appleir driver in the kernel so that it knows the codes of the DVB-T remote. Regards, Tino |