With my newly hacked lirc_zilog, try using the 'tx_only' parameter please. It's not quite ready yet, but I'd like to know if it can bind. If you already loaded a lirc_zilog without my latest patches, the i2c subsystem might have bogus crud still registered. A reboot might be needed for a valid test. R, Andy Jarod Wilson <jarod@xxxxxxxxxxxx> wrote: >On Jan 15, 2011, at 12:37 AM, Jarod Wilson wrote: >... >>> BTW, a checkpatch and compiler tested lirc_zilog.c is here: >>> >>> http://git.linuxtv.org/awalls/media_tree.git?a=shortlog;h=refs/heads/z8 >>> >>> It should fix all the binding and allocation problems related to >>> ir_probe()/ir_remove(). Except I suspect it may leak the Rx poll >>> kthread. That's possibly another bug to add to the list. >>> >>> Anyway, $DIETY knows if the lirc_zilog module actually still works after >>> all my hacks. Give it a test if you are adventurous. I won't be able >>> to test until tomorrow evening. >> >> I'll try to grab those and give them a test tomorrow, and hey, I've even got >> a baseline to test against now. > >Forgot to mention: I think it was suggested that one could use ir-kbd-i2c >for receive and lirc_zilog for transmit, at the same time. With ir-kbd-i2c >already loaded, lirc_zilog currently won't bind to anything. > >-- >Jarod Wilson >jarod@xxxxxxxxxxxx > > > >-- >To unsubscribe from this list: send the line "unsubscribe linux-media" in >the body of a message to majordomo@xxxxxxxxxxxxxxx >More majordomo info at http://vger.kernel.org/majordomo-info.html ÿô.nÇ·®+%˱é¥wÿº{.nÇ·¥{±þg¯â^nr¡öë¨è&£ûz¹Þúzf£¢·h§~Ûÿÿïÿê_èæ+v¨þ)ßø