public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: dick.streefland@altium.nl (Dick Streefland)
To: linux-kernel@vger.kernel.org
Subject: Re: plz help fixing lirc_igorplugusb kernel module
Date: Wed, 21 Jan 2009 10:58:07 -0000	[thread overview]
Message-ID: <87c.4976ffbf.5f61c@altium.nl> (raw)
In-Reply-To: 567e52cd0901201139s1bd4e585o4a3af400c213d237@mail.gmail.com

alex <gsmdib@gmail.com> wrote:
| 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).

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?

<plug>
You can also try my USBtiny implementation, which also works with this
driver. It limits the number of periods to 35 by wrapping the last 16
periods: http://www.xs4all.nl/~dicks/avr/usbtiny/
</plug>

-- 
Dick Streefland                      ////                      Altium BV
dick.streefland@altium.nl           (@ @)          http://www.altium.com
--------------------------------oOO--(_)--OOo---------------------------


  reply	other threads:[~2009-01-21 11:06 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 [this message]
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=87c.4976ffbf.5f61c@altium.nl \
    --to=dick.streefland@altium.nl \
    --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