http://qa.mandrakesoft.com/show_bug.cgi?id=3358
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |UNCONFIRMED
------- Additional Comments From [EMAIL PROTECTED] 2003-03-18 15:38 -------
Directly specifying the DEVICE=/dev/ttyS0 works. Can the inline documentation in the
/etc/sysconfig/lirc file be expanded a little to include that as a possibility? I
posted a
recommended lirc file that was more verbose in the various options available, such as
telling
the user where the 3rd party modules were, etc.
So, in your comment #2 where you said that devfs would automatically create the device
when
the driver loads, that's true in all cases except for direct serial access because the
Mandrake
kernel has serial compiled into the source, correct?
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date:
description:
I have a pinnacle systems "dumb" IR receiver which connects to the COM1 / COM2 serial
port.
The example /etc/sysconfig/lircd file gives the user no indication that they need to
create a
symlink between the actual tty device and the /dev/lirc entry.
Here's a working example:
# Customized setings for lirc daemon
# The hardware driver to use, run lircd --driver=? for a list
DRIVER=pinsys
# Hardware driver module to load
HWMOD=serial
# The device node that communicates with the IR device.
# with devfs enabled
DEVICE=/dev/lirc/1
<snip>
[EMAIL PROTECTED] dev]# ls -l /dev/lirc/1
lr-xr-xr-x 1 root root 10 Mar 15 21:48 /dev/lirc/1 -> /dev/ttyS1
It took me about 2 hours to figure this out. I recommend that the lircd file be a
little more
verbose with examples.
Here is an updated /etc/sysconfig/lircd file that I think explains things better.
(Note that the symlink is created correctly when manually installing lirc from a
tarball because
the lirc configure program does this as a part of the installation process)
[EMAIL PROTECTED] sysconfig]# cat lircd
# Customized setings for lirc daemon
# The hardware driver to use, run lircd --driver=? for a list
DRIVER=UNCONFIGURED
# Hardware driver module to load
# Choices are:
# serial
# lirc_serial (for home-brew serial port IR receivers)
# lirc_parallel
# etc. See /lib/modules/{kern-version}/kernel/3rdparty/lirc for a
# list of modules.
HWMOD=UNCONFIGURED
# The device node that communicates with the IR device.
# If you are using a serial device, create a symlink between the actual
# hardware device and the /dev/lirc/ entry
# Example for receiver connected to COM1
# <as root># cd /dev
# <as root># ln -sf ttyS0 lirc/0
# or <as root># ln -sf ttyS0 lirc/serial
# If you are using devfs, use one of the following and create the symlink
# as shown above
# DEVICE=/dev/lirc/0
# DEVICE=/dev/lirc/serial
# Without devfs:
# If you are using a serial device, create a symlink between the actual
# hardware device and the /dev/lirc entry
# Example for receiver connected to COM1
# <as root># cd /dev
# <as root># ln -sf ttyS0 lirc
# DEVICE=/dev/lirc
# Serial port for the receiver (for serial driver)
# COM1 (/dev/ttyS0)
#COM_PORT=/dev/ttyS0
#DRIVER_OPTS="irq=4 io=0x3f8"
# COM2 (/dev/ttyS1)
#COM_PORT=/dev/ttyS1
#DRIVER_OPTS="irq=3 io=0x2f8"
# COM3 (/dev/ttyS2)
#COM_PORT=/dev/ttyS2
#DRIVER_OPTS="irq=4 io=0x3e8
# COM4 (/dev/ttyS3)
#COM_PORT=/dev/ttyS3
#DRIVER_OPTS="irq=3 io=0x2e8"
