| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <87c.4976ffbf.5f61c@altium.nl> Date: Wed, 21 Jan 2009 10:58:07 -0000 From: dick.streefland@...ium.nl (Dick Streefland) To: linux-kernel@...r.kernel.org Subject: Re: plz help fixing lirc_igorplugusb kernel module alex <gsmdib@...il.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@...ium.nl (@ @) http://www.altium.com --------------------------------oOO--(_)--OOo--------------------------- -- 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