Difference between revisions of "Talk:LIRC"

From MythTV Official Wiki
Jump to: navigation, search
(LIRC definition vs HOWTO)
 
m (→‎Cleaning Up)
 
(8 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 
IMHO, I think that the page "LIRC" (parent of this talk page, that is), should be simply a definition of LIRC. Then a HOWTO should be on a different page. Thoughts?<br>-[[User:TylerDrake|TylerDrake]] 20:34, 18 October 2006 (UTC)
 
IMHO, I think that the page "LIRC" (parent of this talk page, that is), should be simply a definition of LIRC. Then a HOWTO should be on a different page. Thoughts?<br>-[[User:TylerDrake|TylerDrake]] 20:34, 18 October 2006 (UTC)
 +
 +
== Cleaning Up ==
 +
* There are still multiple LIRC pages that could be better organized -- [[User:Ghormann]] -- 17 April 2011
 +
** [[LIRC]]
 +
** [[Ubuntu Serial Lirc Install]]
 +
** [[Using an IR Blaster with MythTV]]
 +
** [[Homebrew lirc reciever parts]]
 +
** [[LIRC on Debian Etch]]
 +
** [[Ubuntu lirc configuration files]]
 +
** [[Generic_HID_"MCE"_Remotes]]
 +
 +
LIRC: the section about the incompatible update (yes, my bad, sorry for that...). Anyway, the bad link is automagically removed these days. And restoring /usr/lib/systemd/system/lirc.service from a backup is really a bad idea, it will be overwritten at next update. If you really want to restore old file it's better to copy it to /etc/systemd/system/lirc.service.
 +
 +
However, this is also a bad idea. Among other things it will expose a random bug related to in which order units are started; this is what using lircd.socket actually fixes. So it's better to actually use the new services as you described.
 +
 +
Make the LIRC device static: this is just too complicated. lircd actually supports a naming scheme like  --device=name=STRING or phys=STRING to cope with dynamic devices; lircd will look in /dev/input to find a device with a matching description. See the lircd manpage.
 +
 +
Create a file in /etc/udev/rules.d called remote-control-lirc.rule: We should mention the fedora package "lirc-disable-kernel" package here; it does the same thing (but with a much simpler approach: SUBSYSTEM=="rc", ATTR{protocols}="lirc")
 +
 +
LircSocket: This section is confusing. First, all modern linuxes uses /dev/lirc0, not /dev/lirc (this is since the rc driver subsystem i. e., ~2.6.35). Furthermore, the /dev/lirc0 device is raw IR data which is decoded by lirc into key symbols. I cannot see any situation where mythtv should have this data (which BTW only can be read by one process). If this ever has worked it's probably due to some very strange symlinking. OTOH, the /var/run/lirc/lircdX sockets are the ones delivering decoded data, what myth needs.
 +
 +
== Keyboard Focus ==
 +
 +
I'd like to add a section on keyboard focus to this article.  Basically there's very little information around on LIRC and how it relates to keyboard focus.  Some of the features of myth-tv require keyboard focus even when LIRC is the main form of input.  Are there any suggestions for how I can improve this article with a section on keyboard focus?  Thanks.  [[User:Arichnad|Arichnad]] 19:40, 31 May 2008 (UTC)
 +
 +
== Lirc namespace aspects are missing ==
 +
 +
Since some time (2009?) lirc is in the process to use standardised key symbols, as provided by e. g. irrecord -l. This aspect is missing here, and makes at least the statement about arbitrary key names plain wrong.
 +
 +
== Hands-on example! ==
 +
 +
Although there are indeed a lot of resources on how to configure lirc, a simple how-to in the mythtv context is still needed. Note that by using the standardised, namespace key symbols, a generic lircrc should be possible to use. In fact, it should be part of the distribution IMHO.
 +
 +
Besides, I agree that the how-to parts should be kept separate and that keyboard focus documentation would be great.
 +
 +
I'd like to add a personal plea that some hint be given of conventional file locations. MythBuntu for one doesn't include a lircrc file, and I've spent weeks trying to figure out whether it should go in /etc/lirc or /home/mythtv or some other directory... --[[User:Nouglywires|Nouglywires]] 19:34, 21 November 2013 (UTC)
 +
: It goes in ${MYTHCONFDIR}/lircrc, if defined, or else ${HOME}/.mythtv/lircrc.  MythTV only looks in those two locations.  Check MythTV's runtime environment to figure out where those are. [[User:Wagnerrp|wagnerrp]] 03:05, 22 November 2013 (UTC)

Latest revision as of 09:17, 25 February 2014

IMHO, I think that the page "LIRC" (parent of this talk page, that is), should be simply a definition of LIRC. Then a HOWTO should be on a different page. Thoughts?
-TylerDrake 20:34, 18 October 2006 (UTC)

Cleaning Up

LIRC: the section about the incompatible update (yes, my bad, sorry for that...). Anyway, the bad link is automagically removed these days. And restoring /usr/lib/systemd/system/lirc.service from a backup is really a bad idea, it will be overwritten at next update. If you really want to restore old file it's better to copy it to /etc/systemd/system/lirc.service.

However, this is also a bad idea. Among other things it will expose a random bug related to in which order units are started; this is what using lircd.socket actually fixes. So it's better to actually use the new services as you described.

Make the LIRC device static: this is just too complicated. lircd actually supports a naming scheme like --device=name=STRING or phys=STRING to cope with dynamic devices; lircd will look in /dev/input to find a device with a matching description. See the lircd manpage.

Create a file in /etc/udev/rules.d called remote-control-lirc.rule: We should mention the fedora package "lirc-disable-kernel" package here; it does the same thing (but with a much simpler approach: SUBSYSTEM=="rc", ATTR{protocols}="lirc")

LircSocket: This section is confusing. First, all modern linuxes uses /dev/lirc0, not /dev/lirc (this is since the rc driver subsystem i. e., ~2.6.35). Furthermore, the /dev/lirc0 device is raw IR data which is decoded by lirc into key symbols. I cannot see any situation where mythtv should have this data (which BTW only can be read by one process). If this ever has worked it's probably due to some very strange symlinking. OTOH, the /var/run/lirc/lircdX sockets are the ones delivering decoded data, what myth needs.

Keyboard Focus

I'd like to add a section on keyboard focus to this article. Basically there's very little information around on LIRC and how it relates to keyboard focus. Some of the features of myth-tv require keyboard focus even when LIRC is the main form of input. Are there any suggestions for how I can improve this article with a section on keyboard focus? Thanks. Arichnad 19:40, 31 May 2008 (UTC)

Lirc namespace aspects are missing

Since some time (2009?) lirc is in the process to use standardised key symbols, as provided by e. g. irrecord -l. This aspect is missing here, and makes at least the statement about arbitrary key names plain wrong.

Hands-on example!

Although there are indeed a lot of resources on how to configure lirc, a simple how-to in the mythtv context is still needed. Note that by using the standardised, namespace key symbols, a generic lircrc should be possible to use. In fact, it should be part of the distribution IMHO.

Besides, I agree that the how-to parts should be kept separate and that keyboard focus documentation would be great.

I'd like to add a personal plea that some hint be given of conventional file locations. MythBuntu for one doesn't include a lircrc file, and I've spent weeks trying to figure out whether it should go in /etc/lirc or /home/mythtv or some other directory... --Nouglywires 19:34, 21 November 2013 (UTC)

It goes in ${MYTHCONFDIR}/lircrc, if defined, or else ${HOME}/.mythtv/lircrc. MythTV only looks in those two locations. Check MythTV's runtime environment to figure out where those are. wagnerrp 03:05, 22 November 2013 (UTC)
Retrieved from "http://www.mythtv.org/wiki?title=Talk:LIRC&oldid=59976"