<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Jarod Wilson wrote:<br>
<blockquote cite="mid:200908301310.35465.jarod@wilsonet.com" type="cite">
<blockquote type="cite">
<pre wrap="">This is all a bit strange but I went back to double check and my Antext
Fusion Black 430 is definitely reporting:
Bus 001 Device 003: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote Controller
and it definitely is only accepting RC-6 codes on mine. It is running
linux with lircd 0.8.3-CVS-pvr150-2 (which is what Knoppmyth bundles in).
</pre>
</blockquote>
</blockquote>
Actually I was running 0.8.4a. I believe I updated it to get lcd_proc.<br>
<blockquote cite="mid:200908301310.35465.jarod@wilsonet.com" type="cite">
<pre wrap=""><!---->
Hrm. Interesting. Perhaps the ffdc actually *can* be put into either
imon or rc6 protocol mode, its just done differently than on the newer
devices. That, or you actually *do* have tx control endpoints on your
ffdc device, which is entirely possible. SoundGraph made the entirely
sucktastic decision to use the ffdc device ID for a LOT of different
devices, wasn't until recently they got a clue... Can you try to load
lirc_imon with debug=1 and see what all spits out? Curious to see what
all is reported about yours...
</pre>
</blockquote>
ok. With lirc 0.8.4a (what I have on this production front end at the
moment) I did the following:<br>
root@myththeatre2:# rmmod -f -v lirc_imon<br>
rmmod lirc_imon, wait=no force<br>
root@myththeatre2:# modprobe -v lirc_imon debug=1<br>
insmod /lib/modules/2.6.23-chw-4/misc/lirc_imon.ko debug=1<br>
root@myththeatre2:#<br>
<br>
And received the following in /var/log/messages after modprobe:<br>
Sep 6 13:08:59 myththeatre2 kernel:
/usr/src/lirc-0.8.4a/drivers/lirc_imon/lirc_imon.c: Driver for
Soundgraph iMON MultiMedia IR/VFD, v0.3<br>
Sep 6 13:08:59 myththeatre2 kernel:
/usr/src/lirc-0.8.4a/drivers/lirc_imon/lirc_imon.c: Venky Raju
<a class="moz-txt-link-rfc2396E" href="mailto:dev@venky.ws"><dev@venky.ws></a><br>
Sep 6 13:08:59 myththeatre2 kernel:
/usr/src/lirc-0.8.4a/drivers/lirc_imon/lirc_imon.c: imon_probe: found
IMON device<br>
Sep 6 13:08:59 myththeatre2 kernel:
/usr/src/lirc-0.8.4a/drivers/lirc_imon/lirc_imon.c: imon_probe: found
IR endpoint<br>
Sep 6 13:08:59 myththeatre2 kernel:
/usr/src/lirc-0.8.4a/drivers/lirc_imon/lirc_imon.c: imon_probe: found
VFD endpoint<br>
Sep 6 13:08:59 myththeatre2 kernel:
/usr/src/lirc-0.8.4a/drivers/lirc_imon/lirc_imon.c: ir_onboard_decode: 1<br>
Sep 6 13:08:59 myththeatre2 kernel:
/usr/src/lirc-0.8.4a/drivers/lirc_imon/lirc_imon.c: vfd_proto_6p: 1<br>
Sep 6 13:08:59 myththeatre2 kernel: lirc_dev: lirc_register_plugin:
sample_rate: 0<br>
Sep 6 13:08:59 myththeatre2 kernel:
/usr/src/lirc-0.8.4a/drivers/lirc_imon/lirc_imon.c: imon_probe:
Registered iMON plugin(minor:1)<br>
Sep 6 13:08:59 myththeatre2 kernel:
/usr/src/lirc-0.8.4a/drivers/lirc_imon/lirc_imon.c: Registering VFD
with devfs<br>
Sep 6 13:08:59 myththeatre2 kernel:
/usr/src/lirc-0.8.4a/drivers/lirc_imon/lirc_imon.c: imon_probe: iMON
device on usb<3:2> initialized<br>
Sep 6 13:08:59 myththeatre2 kernel: usbcore: registered new interface
driver lirc_imon<br>
<br>
It is worth noting that it says it found a VFD endpoint but I actually
have an LCD.<br>
<br>
<br>
</body>
</html>