From: Marc H. <mar...@in...> - 2011-04-10 01:31:01
|
The "streamzap" driver is not listed in the driver selection dialog of the lirc-0.9.0 setup. I tried ./configure --with-driver=streamzap. Apparently the streamzap driver is not currently supported. Please add the streamzap driver to lirc-0.9.0. Thanks, --Marc |
From: Jarod W. <ja...@wi...> - 2011-04-12 14:51:23
|
On Apr 9, 2011, at 9:11 PM, Marc Hurst wrote: > The "streamzap" driver is not listed in the driver selection dialog of > the lirc-0.9.0 setup. > > I tried ./configure --with-driver=streamzap. Apparently the streamzap > driver is not currently supported. > > Please add the streamzap driver to lirc-0.9.0. No. http://lirc.git.sourceforge.net/git/gitweb.cgi?p=lirc/lirc;a=commitdiff;h=a875cfd694ff9311e931e6cd363fdfaad8c4bc56 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/media/rc/streamzap.c;h=e435d94c0776d657403c391f6ca0b9877f100339;hb=HEAD -- Jarod Wilson ja...@wi... |
From: Jarod W. <ja...@wi...> - 2011-04-12 19:12:12
|
On Apr 12, 2011, at 3:05 PM, Marc Hurst wrote: > Thank you for responding Jarod. Sure, but please keep the conversation on the mailing list. There may be others with similar questions and/or additional feedback. > Please excuse my ignorance of linux and of IR. > > I see that my 2.6.38 kernel contains a "streamzap.ko" driver. Does that > mean that I don't need LIRC anymore? Yes and no. You *can* use the Streamzap remote without anything else, if the key mappings are all handled by your application. But its quite likely it doesn't, as X gobbles up way too much of the linux input keyspace (anything with a value > 255), in which case, you probably still want to use lirc. > Can you point me to a HOWTO to explain how I can make use of the > streamzap driver that ships with the kernal? You have two choices: 1) enable the lirc bridge driver and disable in-kernel decoding ('echo lirc > /sys/class/rc/rc0/protocols', more or less) and use it the same way you always have with lircd. 2) configure lircd via its devinput driver, attaching to the input event device created by the streamzap driver. > On Tue, 2011-04-12 at 10:51 -0400, Jarod Wilson wrote: >> On Apr 9, 2011, at 9:11 PM, Marc Hurst wrote: >> >>> The "streamzap" driver is not listed in the driver selection dialog of >>> the lirc-0.9.0 setup. >>> >>> I tried ./configure --with-driver=streamzap. Apparently the streamzap >>> driver is not currently supported. >>> >>> Please add the streamzap driver to lirc-0.9.0. >> >> No. >> >> http://lirc.git.sourceforge.net/git/gitweb.cgi?p=lirc/lirc;a=commitdiff;h=a875cfd694ff9311e931e6cd363fdfaad8c4bc56 >> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/media/rc/streamzap.c;h=e435d94c0776d657403c391f6ca0b9877f100339;hb=HEAD >> > -- Jarod Wilson ja...@wi... |
From: Marc H. <mar...@in...> - 2011-04-16 16:08:46
|
Thanks Jarod. Again, please excuse my ignorance. What am I doing wrong? 1. I copied lirc.conf.streamzap to /etc/lirc/lirc.conf 2. Enabled the lirc bridge driver and disabled in-kernel decoding by executing # echo lirc > /sys/class/rc/rc0/protocols 3. Started lircd by executing # lircd 4. Tried to test with # mode2 However, mode2 gives these messages: mode2: could not get file information for /dev/lirc mode2: default_init(): No such file or directory 5. Than I tried # mode2 --device=bridge and # mode2 --device=streamzap In each case mode2 gives a long list of available drivers that does not include bridge or streamzap. --Marc On Tue, 2011-04-12 at 15:12 -0400, Jarod Wilson wrote: > On Apr 12, 2011, at 3:05 PM, Marc Hurst wrote: > > > Thank you for responding Jarod. > > Sure, but please keep the conversation on the mailing list. There > may be others with similar questions and/or additional feedback. > > > > Please excuse my ignorance of linux and of IR. > > > > I see that my 2.6.38 kernel contains a "streamzap.ko" driver. Does that > > mean that I don't need LIRC anymore? > > Yes and no. You *can* use the Streamzap remote without anything > else, if the key mappings are all handled by your application. > But its quite likely it doesn't, as X gobbles up way too much of > the linux input keyspace (anything with a value > 255), in which > case, you probably still want to use lirc. > > > > Can you point me to a HOWTO to explain how I can make use of the > > streamzap driver that ships with the kernal? > > You have two choices: > > 1) enable the lirc bridge driver and disable in-kernel decoding > ('echo lirc > /sys/class/rc/rc0/protocols', more or less) and > use it the same way you always have with lircd. > > 2) configure lircd via its devinput driver, attaching to the input > event device created by the streamzap driver. > > > > > On Tue, 2011-04-12 at 10:51 -0400, Jarod Wilson wrote: > >> On Apr 9, 2011, at 9:11 PM, Marc Hurst wrote: > >> > >>> The "streamzap" driver is not listed in the driver selection dialog of > >>> the lirc-0.9.0 setup. > >>> > >>> I tried ./configure --with-driver=streamzap. Apparently the streamzap > >>> driver is not currently supported. > >>> > >>> Please add the streamzap driver to lirc-0.9.0. > >> > >> No. > >> > >> http://lirc.git.sourceforge.net/git/gitweb.cgi?p=lirc/lirc;a=commitdiff;h=a875cfd694ff9311e931e6cd363fdfaad8c4bc56 > >> > >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/media/rc/streamzap.c;h=e435d94c0776d657403c391f6ca0b9877f100339;hb=HEAD > >> > > > |
From: Jarod W. <ja...@wi...> - 2011-04-16 18:17:29
|
On Apr 16, 2011, at 12:06 PM, Marc Hurst wrote: > Thanks Jarod. Again, please excuse my ignorance. What am I doing wrong? > > 1. I copied lirc.conf.streamzap to /etc/lirc/lirc.conf > > 2. Enabled the lirc bridge driver and disabled in-kernel decoding by > executing > # echo lirc > /sys/class/rc/rc0/protocols > > 3. Started lircd by executing > # lircd > > 4. Tried to test with > # mode2 > However, mode2 gives these messages: > mode2: could not get file information for /dev/lirc > mode2: default_init(): No such file or directory That means "no such file /dev/lirc". Its probably /dev/lirc0. > 5. Than I tried > # mode2 --device=bridge > and > # mode2 --device=streamzap > In each case mode2 gives a long list of available drivers that does not > include bridge or streamzap. mode2 --device=/dev/lirc0 > On Tue, 2011-04-12 at 15:12 -0400, Jarod Wilson wrote: >> On Apr 12, 2011, at 3:05 PM, Marc Hurst wrote: >> >>> Thank you for responding Jarod. >> >> Sure, but please keep the conversation on the mailing list. There >> may be others with similar questions and/or additional feedback. >> >> >>> Please excuse my ignorance of linux and of IR. >>> >>> I see that my 2.6.38 kernel contains a "streamzap.ko" driver. Does that >>> mean that I don't need LIRC anymore? >> >> Yes and no. You *can* use the Streamzap remote without anything >> else, if the key mappings are all handled by your application. >> But its quite likely it doesn't, as X gobbles up way too much of >> the linux input keyspace (anything with a value > 255), in which >> case, you probably still want to use lirc. >> >> >>> Can you point me to a HOWTO to explain how I can make use of the >>> streamzap driver that ships with the kernal? >> >> You have two choices: >> >> 1) enable the lirc bridge driver and disable in-kernel decoding >> ('echo lirc > /sys/class/rc/rc0/protocols', more or less) and >> use it the same way you always have with lircd. >> >> 2) configure lircd via its devinput driver, attaching to the input >> event device created by the streamzap driver. >> >> >> >>> On Tue, 2011-04-12 at 10:51 -0400, Jarod Wilson wrote: >>>> On Apr 9, 2011, at 9:11 PM, Marc Hurst wrote: >>>> >>>>> The "streamzap" driver is not listed in the driver selection dialog of >>>>> the lirc-0.9.0 setup. >>>>> >>>>> I tried ./configure --with-driver=streamzap. Apparently the streamzap >>>>> driver is not currently supported. >>>>> >>>>> Please add the streamzap driver to lirc-0.9.0. >>>> >>>> No. >>>> >>>> http://lirc.git.sourceforge.net/git/gitweb.cgi?p=lirc/lirc;a=commitdiff;h=a875cfd694ff9311e931e6cd363fdfaad8c4bc56 >>>> >>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/media/rc/streamzap.c;h=e435d94c0776d657403c391f6ca0b9877f100339;hb=HEAD >>>> >>> >> > -- Jarod Wilson ja...@wi... |
From: Marc H. <mar...@in...> - 2011-04-17 17:11:53
|
Jarod, I'm really confused now. Apparently I'm not successfully building lirc. Should I be building lirc-0.8.7 and lirc-0.9.0? I've tried both versions. I'm getting /dev/lircd and /etc/lirc/lirc.conf, but no /dev/lirc, or lirc0, or anything similar. Do you have any ideas? Is there some peculiarity with the 2.6.38-1-amd64 kernel? Thanks, --Marc On Sat, 2011-04-16 at 14:17 -0400, Jarod Wilson wrote: > On Apr 16, 2011, at 12:06 PM, Marc Hurst wrote: > > > Thanks Jarod. Again, please excuse my ignorance. What am I doing wrong? > > > > 1. I copied lirc.conf.streamzap to /etc/lirc/lirc.conf > > > > 2. Enabled the lirc bridge driver and disabled in-kernel decoding by > > executing > > # echo lirc > /sys/class/rc/rc0/protocols > > > > 3. Started lircd by executing > > # lircd > > > > 4. Tried to test with > > # mode2 > > However, mode2 gives these messages: > > mode2: could not get file information for /dev/lirc > > mode2: default_init(): No such file or directory > > That means "no such file /dev/lirc". Its probably /dev/lirc0. > > > > 5. Than I tried > > # mode2 --device=bridge > > and > > # mode2 --device=streamzap > > In each case mode2 gives a long list of available drivers that does not > > include bridge or streamzap. > > mode2 --device=/dev/lirc0 > > > > On Tue, 2011-04-12 at 15:12 -0400, Jarod Wilson wrote: > >> On Apr 12, 2011, at 3:05 PM, Marc Hurst wrote: > >> > >>> Thank you for responding Jarod. > >> > >> Sure, but please keep the conversation on the mailing list. There > >> may be others with similar questions and/or additional feedback. > >> > >> > >>> Please excuse my ignorance of linux and of IR. > >>> > >>> I see that my 2.6.38 kernel contains a "streamzap.ko" driver. Does that > >>> mean that I don't need LIRC anymore? > >> > >> Yes and no. You *can* use the Streamzap remote without anything > >> else, if the key mappings are all handled by your application. > >> But its quite likely it doesn't, as X gobbles up way too much of > >> the linux input keyspace (anything with a value > 255), in which > >> case, you probably still want to use lirc. > >> > >> > >>> Can you point me to a HOWTO to explain how I can make use of the > >>> streamzap driver that ships with the kernal? > >> > >> You have two choices: > >> > >> 1) enable the lirc bridge driver and disable in-kernel decoding > >> ('echo lirc > /sys/class/rc/rc0/protocols', more or less) and > >> use it the same way you always have with lircd. > >> > >> 2) configure lircd via its devinput driver, attaching to the input > >> event device created by the streamzap driver. > >> > >> > >> > >>> On Tue, 2011-04-12 at 10:51 -0400, Jarod Wilson wrote: > >>>> On Apr 9, 2011, at 9:11 PM, Marc Hurst wrote: > >>>> > >>>>> The "streamzap" driver is not listed in the driver selection dialog of > >>>>> the lirc-0.9.0 setup. > >>>>> > >>>>> I tried ./configure --with-driver=streamzap. Apparently the streamzap > >>>>> driver is not currently supported. > >>>>> > >>>>> Please add the streamzap driver to lirc-0.9.0. > >>>> > >>>> No. > >>>> > >>>> http://lirc.git.sourceforge.net/git/gitweb.cgi?p=lirc/lirc;a=commitdiff;h=a875cfd694ff9311e931e6cd363fdfaad8c4bc56 > >>>> > >>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/media/rc/streamzap.c;h=e435d94c0776d657403c391f6ca0b9877f100339;hb=HEAD > >>>> > >>> > >> > > > |
From: Jarod W. <ja...@wi...> - 2011-04-18 19:02:32
|
On Apr 17, 2011, at 1:10 PM, Marc Hurst wrote: > Jarod, I'm really confused now. Apparently I'm not successfully building > lirc. Should I be building lirc-0.8.7 and lirc-0.9.0? 0.9.0. > I've tried both versions. I'm getting /dev/lircd > and /etc/lirc/lirc.conf, but no /dev/lirc, or lirc0, or anything > similar. > > Do you have any ideas? Sounds like maybe the lirc bridge driver isn't available in your kernel. What output do you get for: $ modinfo ir-lirc-codec ? > Is there some peculiarity with the 2.6.38-1-amd64 kernel? Don't know, that's a distro kernel for a distro I don't run. > On Sat, 2011-04-16 at 14:17 -0400, Jarod Wilson wrote: >> On Apr 16, 2011, at 12:06 PM, Marc Hurst wrote: >> >>> Thanks Jarod. Again, please excuse my ignorance. What am I doing wrong? >>> >>> 1. I copied lirc.conf.streamzap to /etc/lirc/lirc.conf >>> >>> 2. Enabled the lirc bridge driver and disabled in-kernel decoding by >>> executing >>> # echo lirc > /sys/class/rc/rc0/protocols >>> >>> 3. Started lircd by executing >>> # lircd >>> >>> 4. Tried to test with >>> # mode2 >>> However, mode2 gives these messages: >>> mode2: could not get file information for /dev/lirc >>> mode2: default_init(): No such file or directory >> >> That means "no such file /dev/lirc". Its probably /dev/lirc0. >> >> >>> 5. Than I tried >>> # mode2 --device=bridge >>> and >>> # mode2 --device=streamzap >>> In each case mode2 gives a long list of available drivers that does not >>> include bridge or streamzap. >> >> mode2 --device=/dev/lirc0 >> >> >>> On Tue, 2011-04-12 at 15:12 -0400, Jarod Wilson wrote: >>>> On Apr 12, 2011, at 3:05 PM, Marc Hurst wrote: >>>> >>>>> Thank you for responding Jarod. >>>> >>>> Sure, but please keep the conversation on the mailing list. There >>>> may be others with similar questions and/or additional feedback. >>>> >>>> >>>>> Please excuse my ignorance of linux and of IR. >>>>> >>>>> I see that my 2.6.38 kernel contains a "streamzap.ko" driver. Does that >>>>> mean that I don't need LIRC anymore? >>>> >>>> Yes and no. You *can* use the Streamzap remote without anything >>>> else, if the key mappings are all handled by your application. >>>> But its quite likely it doesn't, as X gobbles up way too much of >>>> the linux input keyspace (anything with a value > 255), in which >>>> case, you probably still want to use lirc. >>>> >>>> >>>>> Can you point me to a HOWTO to explain how I can make use of the >>>>> streamzap driver that ships with the kernal? >>>> >>>> You have two choices: >>>> >>>> 1) enable the lirc bridge driver and disable in-kernel decoding >>>> ('echo lirc > /sys/class/rc/rc0/protocols', more or less) and >>>> use it the same way you always have with lircd. >>>> >>>> 2) configure lircd via its devinput driver, attaching to the input >>>> event device created by the streamzap driver. >>>> >>>> >>>> >>>>> On Tue, 2011-04-12 at 10:51 -0400, Jarod Wilson wrote: >>>>>> On Apr 9, 2011, at 9:11 PM, Marc Hurst wrote: >>>>>> >>>>>>> The "streamzap" driver is not listed in the driver selection dialog of >>>>>>> the lirc-0.9.0 setup. >>>>>>> >>>>>>> I tried ./configure --with-driver=streamzap. Apparently the streamzap >>>>>>> driver is not currently supported. >>>>>>> >>>>>>> Please add the streamzap driver to lirc-0.9.0. >>>>>> >>>>>> No. >>>>>> >>>>>> http://lirc.git.sourceforge.net/git/gitweb.cgi?p=lirc/lirc;a=commitdiff;h=a875cfd694ff9311e931e6cd363fdfaad8c4bc56 >>>>>> >>>>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/media/rc/streamzap.c;h=e435d94c0776d657403c391f6ca0b9877f100339;hb=HEAD >>>>>> >>>>> >>>> >>> >> > -- Jarod Wilson ja...@wi... |
From: Marc H. <mar...@in...> - 2011-04-19 01:00:07
|
Jarod: Here's what I got: # modinfo ir-lirc-codec filename: /lib/modules/2.6.38-1-amd64/kernel/drivers/media/rc/ir-lirc-codec.ko description: LIRC IR handler bridge author: Red Hat Inc. (http://www.redhat.com) author: Jarod Wilson <ja...@re...> license: GPL depends: lirc_dev,rc-core intree: Y vermagic: 2.6.38-1-amd64 SMP mod_unload modversions # --Marc On Mon, 2011-04-18 at 15:02 -0400, Jarod Wilson wrote: > On Apr 17, 2011, at 1:10 PM, Marc Hurst wrote: > > > Jarod, I'm really confused now. Apparently I'm not successfully building > > lirc. Should I be building lirc-0.8.7 and lirc-0.9.0? > > 0.9.0. > > > I've tried both versions. I'm getting /dev/lircd > > and /etc/lirc/lirc.conf, but no /dev/lirc, or lirc0, or anything > > similar. > > > > Do you have any ideas? > > Sounds like maybe the lirc bridge driver isn't available in your > kernel. What output do you get for: > > $ modinfo ir-lirc-codec > > ? > > > > Is there some peculiarity with the 2.6.38-1-amd64 kernel? > > Don't know, that's a distro kernel for a distro I don't run. > > > > On Sat, 2011-04-16 at 14:17 -0400, Jarod Wilson wrote: > >> On Apr 16, 2011, at 12:06 PM, Marc Hurst wrote: > >> > >>> Thanks Jarod. Again, please excuse my ignorance. What am I doing wrong? > >>> > >>> 1. I copied lirc.conf.streamzap to /etc/lirc/lirc.conf > >>> > >>> 2. Enabled the lirc bridge driver and disabled in-kernel decoding by > >>> executing > >>> # echo lirc > /sys/class/rc/rc0/protocols > >>> > >>> 3. Started lircd by executing > >>> # lircd > >>> > >>> 4. Tried to test with > >>> # mode2 > >>> However, mode2 gives these messages: > >>> mode2: could not get file information for /dev/lirc > >>> mode2: default_init(): No such file or directory > >> > >> That means "no such file /dev/lirc". Its probably /dev/lirc0. > >> > >> > >>> 5. Than I tried > >>> # mode2 --device=bridge > >>> and > >>> # mode2 --device=streamzap > >>> In each case mode2 gives a long list of available drivers that does not > >>> include bridge or streamzap. > >> > >> mode2 --device=/dev/lirc0 > >> > >> > >>> On Tue, 2011-04-12 at 15:12 -0400, Jarod Wilson wrote: > >>>> On Apr 12, 2011, at 3:05 PM, Marc Hurst wrote: > >>>> > >>>>> Thank you for responding Jarod. > >>>> > >>>> Sure, but please keep the conversation on the mailing list. There > >>>> may be others with similar questions and/or additional feedback. > >>>> > >>>> > >>>>> Please excuse my ignorance of linux and of IR. > >>>>> > >>>>> I see that my 2.6.38 kernel contains a "streamzap.ko" driver. Does that > >>>>> mean that I don't need LIRC anymore? > >>>> > >>>> Yes and no. You *can* use the Streamzap remote without anything > >>>> else, if the key mappings are all handled by your application. > >>>> But its quite likely it doesn't, as X gobbles up way too much of > >>>> the linux input keyspace (anything with a value > 255), in which > >>>> case, you probably still want to use lirc. > >>>> > >>>> > >>>>> Can you point me to a HOWTO to explain how I can make use of the > >>>>> streamzap driver that ships with the kernal? > >>>> > >>>> You have two choices: > >>>> > >>>> 1) enable the lirc bridge driver and disable in-kernel decoding > >>>> ('echo lirc > /sys/class/rc/rc0/protocols', more or less) and > >>>> use it the same way you always have with lircd. > >>>> > >>>> 2) configure lircd via its devinput driver, attaching to the input > >>>> event device created by the streamzap driver. > >>>> > >>>> > >>>> > >>>>> On Tue, 2011-04-12 at 10:51 -0400, Jarod Wilson wrote: > >>>>>> On Apr 9, 2011, at 9:11 PM, Marc Hurst wrote: > >>>>>> > >>>>>>> The "streamzap" driver is not listed in the driver selection dialog of > >>>>>>> the lirc-0.9.0 setup. > >>>>>>> > >>>>>>> I tried ./configure --with-driver=streamzap. Apparently the streamzap > >>>>>>> driver is not currently supported. > >>>>>>> > >>>>>>> Please add the streamzap driver to lirc-0.9.0. > >>>>>> > >>>>>> No. > >>>>>> > >>>>>> http://lirc.git.sourceforge.net/git/gitweb.cgi?p=lirc/lirc;a=commitdiff;h=a875cfd694ff9311e931e6cd363fdfaad8c4bc56 > >>>>>> > >>>>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/media/rc/streamzap.c;h=e435d94c0776d657403c391f6ca0b9877f100339;hb=HEAD > >>>>>> > >>>>> > >>>> > >>> > >> > > > |
From: Jarod W. <ja...@wi...> - 2011-04-27 04:35:52
|
On Apr 18, 2011, at 8:58 PM, Marc Hurst wrote: > Jarod: > > Here's what I got: > > # modinfo ir-lirc-codec > filename: /lib/modules/2.6.38-1-amd64/kernel/drivers/media/rc/ir-lirc-codec.ko > description: LIRC IR handler bridge > author: Red Hat Inc. (http://www.redhat.com) > author: Jarod Wilson <ja...@re...> > license: GPL > depends: lirc_dev,rc-core > intree: Y > vermagic: 2.6.38-1-amd64 SMP mod_unload modversions Hrm. I'm mostly out of ideas here. Probably need to see dmesg output after boot or a manual reload of the streamzap driver to have a better idea of where things are falling down. > On Mon, 2011-04-18 at 15:02 -0400, Jarod Wilson wrote: >> On Apr 17, 2011, at 1:10 PM, Marc Hurst wrote: >> >>> Jarod, I'm really confused now. Apparently I'm not successfully building >>> lirc. Should I be building lirc-0.8.7 and lirc-0.9.0? >> >> 0.9.0. >> >>> I've tried both versions. I'm getting /dev/lircd >>> and /etc/lirc/lirc.conf, but no /dev/lirc, or lirc0, or anything >>> similar. >>> >>> Do you have any ideas? >> >> Sounds like maybe the lirc bridge driver isn't available in your >> kernel. What output do you get for: >> >> $ modinfo ir-lirc-codec >> >> ? >> >> >>> Is there some peculiarity with the 2.6.38-1-amd64 kernel? >> >> Don't know, that's a distro kernel for a distro I don't run. >> >> >>> On Sat, 2011-04-16 at 14:17 -0400, Jarod Wilson wrote: >>>> On Apr 16, 2011, at 12:06 PM, Marc Hurst wrote: >>>> >>>>> Thanks Jarod. Again, please excuse my ignorance. What am I doing wrong? >>>>> >>>>> 1. I copied lirc.conf.streamzap to /etc/lirc/lirc.conf >>>>> >>>>> 2. Enabled the lirc bridge driver and disabled in-kernel decoding by >>>>> executing >>>>> # echo lirc > /sys/class/rc/rc0/protocols >>>>> >>>>> 3. Started lircd by executing >>>>> # lircd >>>>> >>>>> 4. Tried to test with >>>>> # mode2 >>>>> However, mode2 gives these messages: >>>>> mode2: could not get file information for /dev/lirc >>>>> mode2: default_init(): No such file or directory >>>> >>>> That means "no such file /dev/lirc". Its probably /dev/lirc0. >>>> >>>> >>>>> 5. Than I tried >>>>> # mode2 --device=bridge >>>>> and >>>>> # mode2 --device=streamzap >>>>> In each case mode2 gives a long list of available drivers that does not >>>>> include bridge or streamzap. >>>> >>>> mode2 --device=/dev/lirc0 >>>> >>>> >>>>> On Tue, 2011-04-12 at 15:12 -0400, Jarod Wilson wrote: >>>>>> On Apr 12, 2011, at 3:05 PM, Marc Hurst wrote: >>>>>> >>>>>>> Thank you for responding Jarod. >>>>>> >>>>>> Sure, but please keep the conversation on the mailing list. There >>>>>> may be others with similar questions and/or additional feedback. >>>>>> >>>>>> >>>>>>> Please excuse my ignorance of linux and of IR. >>>>>>> >>>>>>> I see that my 2.6.38 kernel contains a "streamzap.ko" driver. Does that >>>>>>> mean that I don't need LIRC anymore? >>>>>> >>>>>> Yes and no. You *can* use the Streamzap remote without anything >>>>>> else, if the key mappings are all handled by your application. >>>>>> But its quite likely it doesn't, as X gobbles up way too much of >>>>>> the linux input keyspace (anything with a value > 255), in which >>>>>> case, you probably still want to use lirc. >>>>>> >>>>>> >>>>>>> Can you point me to a HOWTO to explain how I can make use of the >>>>>>> streamzap driver that ships with the kernal? >>>>>> >>>>>> You have two choices: >>>>>> >>>>>> 1) enable the lirc bridge driver and disable in-kernel decoding >>>>>> ('echo lirc > /sys/class/rc/rc0/protocols', more or less) and >>>>>> use it the same way you always have with lircd. >>>>>> >>>>>> 2) configure lircd via its devinput driver, attaching to the input >>>>>> event device created by the streamzap driver. >>>>>> >>>>>> >>>>>> >>>>>>> On Tue, 2011-04-12 at 10:51 -0400, Jarod Wilson wrote: >>>>>>>> On Apr 9, 2011, at 9:11 PM, Marc Hurst wrote: >>>>>>>> >>>>>>>>> The "streamzap" driver is not listed in the driver selection dialog of >>>>>>>>> the lirc-0.9.0 setup. >>>>>>>>> >>>>>>>>> I tried ./configure --with-driver=streamzap. Apparently the streamzap >>>>>>>>> driver is not currently supported. >>>>>>>>> >>>>>>>>> Please add the streamzap driver to lirc-0.9.0. >>>>>>>> >>>>>>>> No. >>>>>>>> >>>>>>>> http://lirc.git.sourceforge.net/git/gitweb.cgi?p=lirc/lirc;a=commitdiff;h=a875cfd694ff9311e931e6cd363fdfaad8c4bc56 >>>>>>>> >>>>>>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/media/rc/streamzap.c;h=e435d94c0776d657403c391f6ca0b9877f100339;hb=HEAD >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -- Jarod Wilson ja...@wi... |