Remote controllers-V4L - Revision history

Jimbley: Added category: Hardware

2009-05-03T01:44:06Z

Added category: Hardware

← Older revision		Revision as of 01:44, 3 May 2009
Line 163:		Line 163:
	saa7133[0]/ir: build_key gpio=0x0 mask=0x0 data=0		saa7133[0]/ir: build_key gpio=0x0 mask=0x0 data=0
	saa7133[0]/ir: build_key gpio=0x40 mask=0x0 data=0		saa7133[0]/ir: build_key gpio=0x40 mask=0x0 data=0
		+	[[Category:Hardware]]

CityK: 21 revision(s)

2008-12-27T17:46:53Z

21 revision(s)

← Older revision

Revision as of 17:46, 27 December 2008

CityK: Remote controllers moved to Remote controllers-V4L: name

2008-11-02T19:51:41Z

Remote controllers moved to Remote controllers-V4L: name

← Older revision

Revision as of 19:51, 2 November 2008

Ariclone: /* How to add remote control support to a card (GPIO remotes) */

2007-09-04T21:26:36Z

How to add remote control support to a card (GPIO remotes)

← Older revision		Revision as of 21:26, 4 September 2007
Line 120:		Line 120:
	The operation is as follows (at least it is how i did it):		The operation is as follows (at least it is how i did it):

-	# you make ~~detinitions of~~ your board to have remote control (in saa7134-cards.c).	+	# you make definitions for your board to have remote control (in saa7134-cards.c).
	# in saa7134-input.c, you add a case for it into the switch statement, with mask_keycode=0. Use any ir_codes array for the start. Well, you should also determine whenever polling is needed, too.		# in saa7134-input.c, you add a case for it into the switch statement, with mask_keycode=0. Use any ir_codes array for the start. Well, you should also determine whenever polling is needed, too.
	# Load saa7134 module with ir_debug=1 parameter.		# Load saa7134 module with ir_debug=1 parameter.

Arcee at 00:59, 14 March 2007

2007-03-14T00:59:55Z

← Older revision		Revision as of 00:59, 14 March 2007
Line 65:		Line 65:

	lircd versions newer than 0.7.0 support reading events from		lircd versions newer than 0.7.0 support reading events from
-	the linux input layer (via event device). The input layer tools tarball comes with a lircd config file.	+	the linux input layer (via event device). This method '''replaces''' ''lirc_gpio'' and ''lirc_i2c'', so make sure you don't have any of those modules loaded. The input layer tools tarball comes with a lircd config file.

	=====Quick instructions=====		=====Quick instructions=====

Arcee at 00:49, 14 March 2007

2007-03-14T00:49:48Z

← Older revision		Revision as of 00:49, 14 March 2007
Line 90:		Line 90:

	* Now you've identified the input device, it's time to record the keys for your remote so it can be used with LIRC. Type "irrecord -H dev/input -d /dev/input/eventX /tmp/my-remote" (X is the value you got from the H: line in the previous step. In this case, it would be "/dev/input/event2"). If all goes well, LIRC should start giving you instructions to configure your keys. Follow them.		* Now you've identified the input device, it's time to record the keys for your remote so it can be used with LIRC. Type "irrecord -H dev/input -d /dev/input/eventX /tmp/my-remote" (X is the value you got from the H: line in the previous step. In this case, it would be "/dev/input/event2"). If all goes well, LIRC should start giving you instructions to configure your keys. Follow them.
		+
		+	* In recent versions of LIRC, you can use the device name or physical location as an alternative to the device path at /dev. For the previous example, it would be ''irrecord -H dev/input -d name="bttv IR (card=137)"'', or ''irrecord -H dev/input -d phys=pci-0000:00:08.0/ir0''. This is especially useful when the number of the device keeps changing (with Cardbus os USB devices)

	* If during the above configuration you fail at the step "hold down a key" with the error "can not find gap" or similar, repeat the process but instead of holding down a key, press and release a key continuously ("click" a key).		* If during the above configuration you fail at the step "hold down a key" with the error "can not find gap" or similar, repeat the process but instead of holding down a key, press and release a key continuously ("click" a key).
Line 95:		Line 97:
	* When you finish configuring your keys, you'll be left with a /tmp/my-remote file. Copy it to ''/etc/lircd.conf'' or, if /etc/lirc exists, ''/etc/lirc/lircd.conf''.		* When you finish configuring your keys, you'll be left with a /tmp/my-remote file. Copy it to ''/etc/lircd.conf'' or, if /etc/lirc exists, ''/etc/lirc/lircd.conf''.

-	* Start lircd using the same options you used for irrecord (i.e. "lircd -H dev/input -d /dev/input/eventX"). If you have a configuration file for lirc (in Fedora Core, for example, it's ''/etc/sysconfig/lircd''; in Debian, it's ''/etc/lirc/hardware.conf'' and may be altered via "dpkg-reconfigure lirc"), edit it and add those options there.	+	* Start lircd using the same options you used for irrecord (i.e. ''lircd -H dev/input -d /dev/input/eventX'', or ''lircd -H dev/input -d name="bttv IR (card=137)"'' ). If you have a configuration file for lirc (in Fedora Core, for example, it's ''/etc/sysconfig/lircd''; in Debian, it's ''/etc/lirc/hardware.conf'' and may be altered via "dpkg-reconfigure lirc"), edit it and add those options there.

	* Run '''irw''' and press a few keys on the remote. You should see the names you gave the keys appearing. Congratulations, you now have LIRC running with your remote.		* Run '''irw''' and press a few keys on the remote. You should see the names you gave the keys appearing. Congratulations, you now have LIRC running with your remote.

Arcee at 12:04, 2 March 2007

2007-03-02T12:04:36Z

← Older revision		Revision as of 12:04, 2 March 2007
Line 90:		Line 90:

	* Now you've identified the input device, it's time to record the keys for your remote so it can be used with LIRC. Type "irrecord -H dev/input -d /dev/input/eventX /tmp/my-remote" (X is the value you got from the H: line in the previous step. In this case, it would be "/dev/input/event2"). If all goes well, LIRC should start giving you instructions to configure your keys. Follow them.		* Now you've identified the input device, it's time to record the keys for your remote so it can be used with LIRC. Type "irrecord -H dev/input -d /dev/input/eventX /tmp/my-remote" (X is the value you got from the H: line in the previous step. In this case, it would be "/dev/input/event2"). If all goes well, LIRC should start giving you instructions to configure your keys. Follow them.
		+
		+	* If during the above configuration you fail at the step "hold down a key" with the error "can not find gap" or similar, repeat the process but instead of holding down a key, press and release a key continuously ("click" a key).

	* When you finish configuring your keys, you'll be left with a /tmp/my-remote file. Copy it to ''/etc/lircd.conf'' or, if /etc/lirc exists, ''/etc/lirc/lircd.conf''.		* When you finish configuring your keys, you'll be left with a /tmp/my-remote file. Copy it to ''/etc/lircd.conf'' or, if /etc/lirc exists, ''/etc/lirc/lircd.conf''.

Nsh at 08:34, 30 September 2006

2006-09-30T08:34:35Z

← Older revision		Revision as of 08:34, 30 September 2006
Line 138:		Line 138:
	Try to find existing table matching your one. If there's one, use it. If none is found, build your own.		Try to find existing table matching your one. If there's one, use it. If none is found, build your own.

-	~~That~~'s ~~basically it~~.	+	Please note that sometimes gpio is enabled by some gpio output chip. In that case I would recommend
		+	to collect regspy output first. It will show if gpio values really change.
		+
		+	===Combined GPIO remotes===
		+
		+	Sometimes remotes are not pure gpio and acts a bit differently. For example, keypress can be signalled by gpio and keyvalue can be read from i2c device. If you seen only 1 bit is changing in gpio once it's probably this situation.
		+
		+	saa7133[0]/ir: build_key gpio=0x0 mask=0x0 data=0
		+	saa7133[0]/ir: build_key gpio=0x40 mask=0x0 data=0
		+
		+	Sometimes the rc5 value is delivered directly to gpio. In that case you'll see a lot of changes
		+	when you press a single key
		+
		+	saa7133[0]/ir: build_key gpio=0x0 mask=0x0 data=0
		+	saa7133[0]/ir: build_key gpio=0x40 mask=0x0 data=0
		+	saa7133[0]/ir: build_key gpio=0x0 mask=0x0 data=0
		+	saa7133[0]/ir: build_key gpio=0x40 mask=0x0 data=0
		+	saa7133[0]/ir: build_key gpio=0x0 mask=0x0 data=0
		+	saa7133[0]/ir: build_key gpio=0x40 mask=0x0 data=0
		+	saa7133[0]/ir: build_key gpio=0x0 mask=0x0 data=0
		+	saa7133[0]/ir: build_key gpio=0x40 mask=0x0 data=0

Liontooth: /* Basics */ --formatting

2006-03-27T12:12:20Z

Basics: --formatting

← Older revision		Revision as of 12:12, 27 March 2006
Line 20:		Line 20:
	from [http://dl.bytesex.org/cvs-snapshots/ http://dl.bytesex.org/cvs-snapshots/input-<date>.tar.gz]		from [http://dl.bytesex.org/cvs-snapshots/ http://dl.bytesex.org/cvs-snapshots/input-<date>.tar.gz]

-	~~Modules you have to load:~~	+	<br>

-	~~saa7134 Depending on the board, you might just need the saa7134 driver, or to use ir-kbd-i2c as a~~	+	<table border="10" cellpadding="5" width="70%" cellspacing="3" frame="hsides" rules="all">
-	~~helper. As of now (Oct 2005) there are 2 known boards requiring ir-kbd-i2c: The Upmost Purple~~	+
-	~~TV, and the latest ''~~"~~i-series~~"~~'' Pinnacle PCTV boards (110i, 50i)~~	+
-	~~bttv same thing as saa7134. Known cards needing ir-kbd-i2c include Pixelview and Hauppauge cards.~~	+

-	V4L doesn't support all the cards that lirc supports	+	<tr>
-	(yet), mainly for the reason that the code of lirc_i2c and lirc_gpio	+	<th>Card</th>
-	was very confusing and I decided to basically start over from scratch.	+	<th>Modules to load</th>
-	Feel free to contact me in case of trouble. Note that the ir-kbd-i2c	+	</tr>
-	module works on 2.6.x kernels only through ...	+
		+	<tr>
		+	<td>saa7134</td>
		+	<td>Most cards need only the saa7134 driver, but a few need the ir-kbd-i2c helper. Boards known to require ir-kbd-i2c include the Upmost Purple TV and the latest ''"i-series"'' Pinnacle PCTV boards (110i, 50i)</td>
		+	</tr>
		+
		+	<tr>
		+	<td>bttv</td>
		+	<td>Most cards need only the bttv driver, but a few need the ir-kbd-i2c helper. Known cards needing ir-kbd-i2c include Pixelview and Hauppauge cards.</td>
		+	</tr>
		+
		+	</table>
		+
		+	<br>
		+
		+	V4L doesn't support all the cards that lirc supports (yet), mainly for the reason that the code of lirc_i2c and lirc_gpio was very confusing and I decided to basically start over from scratch. Feel free to contact me in case of trouble. Note that the ir-kbd-i2c module works on 2.6.x kernels only through ...

	====How it works====		====How it works====

Arcee at 00:53, 27 March 2006

2006-03-27T00:53:51Z

← Older revision		Revision as of 00:53, 27 March 2006
Line 25:		Line 25:
	helper. As of now (Oct 2005) there are 2 known boards requiring ir-kbd-i2c: The Upmost Purple		helper. As of now (Oct 2005) there are 2 known boards requiring ir-kbd-i2c: The Upmost Purple
	TV, and the latest ''"i-series"'' Pinnacle PCTV boards (110i, 50i)		TV, and the latest ''"i-series"'' Pinnacle PCTV boards (110i, 50i)
-	bttv ~~ir-kbd-gpio or~~ ir-kbd-i2c ~~depending on your card~~.	+	bttv same thing as saa7134. Known cards needing ir-kbd-i2c include Pixelview and Hauppauge cards.

-	~~ir-kbd-gpio and ir-kbd-i2c don~~'t support all the cards that lirc supports	+	V4L doesn't support all the cards that lirc supports
	(yet), mainly for the reason that the code of lirc_i2c and lirc_gpio		(yet), mainly for the reason that the code of lirc_i2c and lirc_gpio
	was very confusing and I decided to basically start over from scratch.		was very confusing and I decided to basically start over from scratch.
-	Feel free to contact me in case of trouble. Note that the ir-kbd-*	+	Feel free to contact me in case of trouble. Note that the ir-kbd-i2c
-	~~modules work~~ on 2.6.x kernels only through ...	+	module works on 2.6.x kernels only through ...

	====How it works====		====How it works====
Line 99:		Line 99:
	Note that the linux keyboard driver interface (the '''really''' old one, not the linux input layer added in 2.4) has a limitation on the number of keys it can distingish -- it's 200 plus something. That is inherited from PS/2. As long as X11 still used the old kbd driver instead of the linux input layer, it will have problems supporting all keys :-/		Note that the linux keyboard driver interface (the '''really''' old one, not the linux input layer added in 2.4) has a limitation on the number of keys it can distingish -- it's 200 plus something. That is inherited from PS/2. As long as X11 still used the old kbd driver instead of the linux input layer, it will have problems supporting all keys :-/

-	~~Have fun,~~
-
-	~~Gerd~~
-
-	--
-	~~Gerd Knorr <kraxel@bytesex.org>~~

	===How to add remote control support to a card (GPIO remotes) ===		===How to add remote control support to a card (GPIO remotes) ===