mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: alex <gsmdib@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: plz help fixing lirc_igorplugusb kernel module
Date: Tue, 20 Jan 2009 21:39:06 +0200	[thread overview]
Message-ID: <567e52cd0901201139s1bd4e585o4a3af400c213d237@mail.gmail.com> (raw)

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@algo.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).

             reply	other threads:[~2009-01-20 19:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 19:39 alex [this message]
2009-01-21 10:58 ` Dick Streefland
2009-01-22 14:25   ` gsmd
2009-01-22 14:36     ` Dick Streefland
2009-01-22 15:43       ` gsmd
2010-02-09  9:25         ` luckygala

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=567e52cd0901201139s1bd4e585o4a3af400c213d237@mail.gmail.com \
    --to=gsmdib@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®