[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <567e52cd0901201139s1bd4e585o4a3af400c213d237@mail.gmail.com>
Date: Tue, 20 Jan 2009 21:39:06 +0200
From: alex <gsmdib@...il.com>
To: linux-kernel@...r.kernel.org
Subject: plz help fixing lirc_igorplugusb kernel module
Hi.
It turns out that lirc_igorplugusb.c is part of the 2.6.28 kernel
(http://lkml.org/lkml/2008/9/9/13) and the bad news is that it's
broken.
--
Jan 20 19:05:33 s lirc_igorplugusb: USB remote driver for LIRC v0.1
Jan 20 19:05:33 s lirc_igorplugusb: Jan M. Hochstein
<hochstein@...o.informatik.tu-darmstadt.de>
Jan 20 19:05:33 s lirc_dev: lirc_register_plugin: sample_rate: 100
Jan 20 19:05:33 s lirc_igorplugusb[3]: Yuri M. Karelin, (c) 2007
ElMark IR remote control on usb3:3
Jan 20 19:05:33 s usbcore: registered new interface driver lirc_igorplugusb
Jan 20 19:10:00 s lircd-0.8.4[25107]: could not open config file
'/etc/lircd.conf'
Jan 20 19:10:00 s lircd-0.8.4[25107]: No such file or directory
Jan 20 19:10:00 s lircd-0.8.4[25108]: lircd(default) ready
.....
Jan 20 19:11:42 s lircd-0.8.4[25108]: accepted new client on /dev/lircd
Jan 20 19:11:42 s lirc_igorplugusb[3]: Device buffer overrun.
Jan 20 19:11:48 s lirc_igorplugusb[3]: Device buffer overrun.
Jan 20 19:11:49 s lirc_igorplugusb[3]: Device buffer overrun.
--
The problem naturally lies in the last third lines which reflect the
way kernel module reacts to key presses on remote. The very same
device works flawlessly under Win + Girder.
I'd be very thankful if someone could help me fixing the issue (or
rather if I could help fixing this issue).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists