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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21605162.post@talk.nabble.com>
Date:	Thu, 22 Jan 2009 06:25:44 -0800 (PST)
From:	gsmd <gsmdib@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: plz help fixing lirc_igorplugusb kernel module



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.

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ