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]
Date:	Thu, 22 Jan 2009 14:36:56 -0000
From:	dick.streefland@...ium.nl (Dick Streefland)
To:	linux-kernel@...r.kernel.org
Subject: Re: plz help fixing lirc_igorplugusb kernel module

gsmd <gsmdib@...il.com> wrote:
| 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.

The variable 'i' is modified, which affects the amount of data that is
returned to LIRC. I suggest removing at least this line, to see if
that helps.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ