From: gsmd <gsmdib@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: plz help fixing lirc_igorplugusb kernel module
Date: Thu, 22 Jan 2009 06:25:44 -0800 (PST) [thread overview]
Message-ID: <21605162.post@talk.nabble.com> (raw)
In-Reply-To: <87c.4976ffbf.5f61c@altium.nl>
Dick Streefland wrote:
>
> This error is caused by an IR code longer than 36 pulse/space periods.
> Perhaps the Windows driver simply ignores this condition? Did you try
> to remove the code that handles this case and where this message is
> issued?
>
It probably does, yet the code is received (so I can assign any command to
that key).
Here's the section from lirc_igorplugusb.c
(ftp.gnu.org/tmp/linux-libre-fsf2_2.6.28/linux-2.6.28/ubuntu/lirc/lirc_igorplugusb/lirc_igorplugusb.c)
that displays the message:
--
if (ir->buf_in[2] != 0) {
printk(DRIVER_NAME "[%d]: Device buffer overrun.\n",
ir->devnum);
/* start at earliest byte */
i = DEVICE_HEADERLEN + ir->buf_in[2];
/* where are we now? space, gap or pulse? */
}
--
With my limited C knowledge I don't see what would prevent displaying the
key code (when I run irw) after the message. Haven't tried removing it
though.
Also checked with 3 different remote controls, the result is all the same.
--
View this message in context: http://www.nabble.com/plz-help-fixing-lirc_igorplugusb-kernel-module-tp21570131p21605162.html
Sent from the linux-kernel mailing list archive at Nabble.com.
next prev parent reply other threads:[~2009-01-22 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 19:39 plz help fixing lirc_igorplugusb kernel module alex
2009-01-21 10:58 ` Dick Streefland
2009-01-22 14:25 ` gsmd [this message]
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=21605162.post@talk.nabble.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