LIRC - Revision history

Karellen at 02:20, 23 July 2020

2020-07-23T02:20:20Z

← Older revision		Revision as of 02:20, 23 July 2020
Line 207:		Line 207:
	{{Gotham updated}}		{{Gotham updated}}

	~~[[Category:Manual]]~~
	[[Category:Linux]]		[[Category:Linux]]
	[[Category:Remotes]]		[[Category:Remotes]]
	~~[[Category:Supplemental tools]]~~

Karellen at 01:45, 19 July 2020

2020-07-19T01:45:58Z

← Older revision		Revision as of 01:45, 19 July 2020
Line 141:		Line 141:
	{{see also\|Userdata}}		{{see also\|Userdata}}

	'''A custom Lircmap.xml''' - This file merely defines the translation, bridging a '''LIRC_button''' to a '''XBMC_button'''. The file is literally named '''Lircmap.xml''' and is stored in the [[userdata]] directory. Do not confuse the '''Lircmap.xml''' with [[Keyboard.xml]].		'''A custom Lircmap.xml''' - This file merely defines the translation, bridging a '''LIRC_button''' to a '''XBMC_button'''. The file is literally named '''Lircmap.xml''' and is stored in the [[userdata]] directory. Do not confuse the '''Lircmap.xml''' with [[Keymap\|Keyboard.xml]].

	'''LIRC_Button''' - what your lircd.conf calls the physical button on your remote control.		'''LIRC_Button''' - what your lircd.conf calls the physical button on your remote control.
Line 149:		Line 149:
	'''device name''' - is defined in your lircd.conf file in the "name" field.		'''device name''' - is defined in your lircd.conf file in the "name" field.

	This information can be had using the test application "irw" and then hitting some buttons~~. More on this in the [[Lirc and Lircmap.xml#Testing Lirc Output]] section below~~.		This information can be had using the test application "irw" and then hitting some buttons.

	=== File format ===		=== File format ===
Line 164:		Line 164:

	=== Device name ===		=== Device name ===
	The device name is defined in your lircd.conf file in the "name" field. This information can be had using the test application "irw" and then hitting some buttons~~. More on this in the [[Lirc and Lircmap.xml#Testing Lirc Output]] section below~~.		The device name is defined in your lircd.conf file in the "name" field. This information can be had using the test application "irw" and then hitting some buttons.

	=== Kodi button names ===		=== Kodi button names ===
Line 175:		Line 175:
	<menu>		<menu>

	These buttons are predefined in [[keymap.xml]] and handle all functions needed for a working system. For a complete list of buttons see [[~~keymap.xml~~#~~Remote Buttons~~]].		These buttons are predefined in [[Keymap\|keymap.xml]] and handle all functions needed for a working system. For a complete list of buttons see [[Keymap#Remotes]].

	* Customized buttons are for people who require more buttons than are defined by default. For example;		* Customized buttons are for people who require more buttons than are defined by default. For example;
Line 183:		Line 183:
	<obc254>BUTTON254</obc254>		<obc254>BUTTON254</obc254>

	Note : These obc buttons must be defined in [[keymap.xml]] under the [[<universalremote>]] heading		Note : These obc buttons must be defined in [[Keymap\|keymap.xml]] under the <universalremote> heading

	FYI : obc stands for original button code and is a legacy of the old xbox IR remote system		FYI : obc stands for original button code and is a legacy of the old xbox IR remote system

Muddysteel: /* Overview of LIRC */

2019-06-02T13:57:57Z

Overview of LIRC

← Older revision		Revision as of 13:57, 2 June 2019
Line 44:		Line 44:

	If setting LIRC up with Linux, one needs to focus on using one path from the kernal to LIRC (via UAPI, or via LIRC's kernel device driver). Modern Linux kernels should focus on using the UAPI sequence. As Kodi continues to evolve, using the UAPI layer directly allows it to take advantage of non-IR-remote input controls, say an eyeball tracker, or voice controller.		If setting LIRC up with Linux, one needs to focus on using one path from the kernal to LIRC (via UAPI, or via LIRC's kernel device driver). Modern Linux kernels should focus on using the UAPI sequence. As Kodi continues to evolve, using the UAPI layer directly allows it to take advantage of non-IR-remote input controls, say an eyeball tracker, or voice controller.

			{{notice\|raw=This page assumes the UAPI -> LIRC -> Kodi route. If the older (and should be discontinued approach) is used, it is called out.}}

	== How LIRC works with Kodi ==		== How LIRC works with Kodi ==

Muddysteel at 13:44, 2 June 2019

2019-06-02T13:44:50Z

← Older revision		Revision as of 13:44, 2 June 2019
Line 40:		Line 40:
	</pre>		</pre>
	However, Kodi (to this day) still relies on the to-the-right-of-the-kernel aspects of LIRC. '''This is why LIRC setup can be so confusing.'''		However, Kodi (to this day) still relies on the to-the-right-of-the-kernel aspects of LIRC. '''This is why LIRC setup can be so confusing.'''

			{{tip\|When LIRC is in use, Kodi '''only''' requires the use of <code>lircd</code>.}}

	If setting LIRC up with Linux, one needs to focus on using one path from the kernal to LIRC (via UAPI, or via LIRC's kernel device driver). Modern Linux kernels should focus on using the UAPI sequence. As Kodi continues to evolve, using the UAPI layer directly allows it to take advantage of non-IR-remote input controls, say an eyeball tracker, or voice controller.		If setting LIRC up with Linux, one needs to focus on using one path from the kernal to LIRC (via UAPI, or via LIRC's kernel device driver). Modern Linux kernels should focus on using the UAPI sequence. As Kodi continues to evolve, using the UAPI layer directly allows it to take advantage of non-IR-remote input controls, say an eyeball tracker, or voice controller.

Muddysteel: /* Installation */

2019-06-02T13:40:44Z

Installation

← Older revision		Revision as of 13:40, 2 June 2019
Line 127:		Line 127:
	= Installation =		= Installation =
	Generally, lirc is installed as a dependency by any system that requires it when installing Kodi.		Generally, lirc is installed as a dependency by any system that requires it when installing Kodi.


			== Re-installing LIRC ==
			TODO - clarify new vs. old dependencies

	If for whatever reason you have to install/reinstall lirc, note that the manual says systemctl should be configured to enable/start lircd.socket, and lircd.socket will start lircd.service itself. This is NOT the case if you're installing for Kodi: Kodi will open its own socket, so you should enable only lircd.service for it to function properly.		If for whatever reason you have to install/reinstall lirc, note that the manual says systemctl should be configured to enable/start lircd.socket, and lircd.socket will start lircd.service itself. This is NOT the case if you're installing for Kodi: Kodi will open its own socket, so you should enable only lircd.service for it to function properly.

Muddysteel: /* Overview of LIRC */

2019-05-27T15:08:16Z

Overview of LIRC

← Older revision		Revision as of 15:08, 27 May 2019
Line 96:		Line 96:
	</source>		</source>

			=== Stale LIRCD conf file ===

	'''<code>lircd.conf:</code>'''		'''<code>lircd.conf:</code>'''

Muddysteel at 14:51, 27 May 2019

2019-05-27T14:51:08Z

← Older revision		Revision as of 14:51, 27 May 2019
Line 40:		Line 40:
	</pre>		</pre>
	However, Kodi (to this day) still relies on the to-the-right-of-the-kernel aspects of LIRC. '''This is why LIRC setup can be so confusing.'''		However, Kodi (to this day) still relies on the to-the-right-of-the-kernel aspects of LIRC. '''This is why LIRC setup can be so confusing.'''

			If setting LIRC up with Linux, one needs to focus on using one path from the kernal to LIRC (via UAPI, or via LIRC's kernel device driver). Modern Linux kernels should focus on using the UAPI sequence. As Kodi continues to evolve, using the UAPI layer directly allows it to take advantage of non-IR-remote input controls, say an eyeball tracker, or voice controller.

	== How LIRC works with Kodi ==		== How LIRC works with Kodi ==

Muddysteel at 14:48, 27 May 2019

2019-05-27T14:48:31Z

← Older revision		Revision as of 14:48, 27 May 2019
Line 13:		Line 13:
	Prior to the input subsystem, Infrared Remote (IR) controls were integrated to Linux via LIRC.		Prior to the input subsystem, Infrared Remote (IR) controls were integrated to Linux via LIRC.

	Kodi came into being before UAPI existed, and thus relied exclusively on LIRC. Thus, when UAPI arrived, Kodi and IR remotes looked like this:		Kodi came into being before UAPI existed, and thus relied exclusively on LIRC. Thus, when UAPI '''arrived''', Kodi and IR remotes looked like this:
	<pre>		<pre>
	---------- -------------- ---------------		---------- -------------- ---------------

Muddysteel at 14:47, 27 May 2019

2019-05-27T14:47:57Z

← Older revision		Revision as of 14:47, 27 May 2019
Line 7:		Line 7:

	= Overview of LIRC =		= Overview of LIRC =

			== Historical Information ==
			Modern Linux kernels "unify" input signals from any input device (keyboard, mouse, remote control, touchscreen, etc.) via the [https://www.kernel.org/doc/html/v4.15/input/input_uapi.html Linux User API Input Subsystem], or UAPI.

			Prior to the input subsystem, Infrared Remote (IR) controls were integrated to Linux via LIRC.

			Kodi came into being before UAPI existed, and thus relied exclusively on LIRC. Thus, when UAPI arrived, Kodi and IR remotes looked like this:
			<pre>
			---------- -------------- ---------------
			\| \|--->---\| Linux UAPI \|-->---\| Application \|
			\| \| -------------- ---------------
			--->------\| \|
			IR remote \| kernel \|
			\| \|
			\| \| ------------ ---------------
			\| \|---->--\| lirc \|---->---\| Kodi \|
			\| \| ------------ ---------------
			----------
			</pre>
			As the UAPI matured, LIRC adopted the ability to use both pathways - UAPI ''and'' LIRC, allowing for:
			<pre>
			---------- -------------- ---------------
			\| \|--->---\| Linux UAPI \|-->---\| Application \|
			\| \| -------------- ---------------
			--->------\| \| \|
			IR remote \| kernel \| v
			\| \| \|
			\| \| ------------ ---------------
			\| \|---->--\| lirc \|---->---\| Kodi \|
			\| \| ------------ ---------------
			----------
			</pre>
			However, Kodi (to this day) still relies on the to-the-right-of-the-kernel aspects of LIRC. '''This is why LIRC setup can be so confusing.'''

	== How LIRC works with Kodi ==		== How LIRC works with Kodi ==

Muddysteel at 18:59, 26 May 2019

2019-05-26T18:59:20Z

Show changes