[mythtv-users] Help me find the magic combo (remote/lirc)

Jarod Wilson jarod at wilsonet.com
Thu Dec 31 01:55:31 UTC 2009


On Dec 30, 2009, at 8:44 PM, Jan Johansson wrote:

>> Bull. You wind up with /dev/lirc0 for the imon, /dev/lirc1 for the
>> mce.
> 
> Then why can I still only use /dev/lircd?

That's the lirc daemon socket, created by lircd when it starts up. The device files are /dev/lirc0 and /dev/lirc1.

> I get Device or resource busy when tryinto use /dev/lirc0 /dev/lirc1,
> yes when I do not blacklist lirc_imon I see lirc0 lirc1 lircd (lircd is
> a symlink to /var/run/lirc/lircd.
> 
> (At least when trying with irw and mode2)

Doing It Wrong then. :)

$ lircd --help
Usage: lircd [options] [config-file]
	 -h --help			display this message
	 -v --version			display version
	 -n --nodaemon			don't fork to background
	 -p --permission=mode		file permissions for /var/run/lirc/lircd
	 -H --driver=driver		use given driver
	 -d --device=device		read from given device
	 -l --listen[=[address:]port]	listen for network connections
	 -c --connect=host[:port]	connect to remote lircd server
	 -o --output=socket		output socket filename
	 -P --pidfile=file		daemon pid file
	 -r --release[=suffix]		auto-generate release events
	 -a --allow-simulate		accept SIMULATE command
	 -u --uinput			generate Linux input events
	 -R --repeat-max=limit		allow at most this many repeats

The -o part is /dev/lircd. The -d part is /dev/lirc[0-9].

Once lircd is started with the correct options, irw only needs to be pointed at the correct socket (the -o part).

-- 
Jarod Wilson
jarod at wilsonet.com





More information about the mythtv-users mailing list