On Sun, 22 Feb 2004, [iso-8859-2] Pawe³ Sikora wrote: >Date: Sun, 22 Feb 2004 11:13:06 +0100 >From: "[iso-8859-2] Pawe³ Sikora" <pluto@xxxxxxxxxxxxx> >To: xfree86@xxxxxxxxxxx >Reply-To: xfree86@xxxxxxxxxxx >Content-Type: text/plain; > charset="iso-8859-1" >Subject: Re: atkbd.c: This is an XFree86 bug. It shouldn't access hardware > directly. > >On Sunday 22 of February 2004 06:48, Zuckerman wrote: >> Hi, I'm from São Paulo / Brasil. >> >> In dmesg appear this: >> >> atkbd.c: Unknown key released (translated set 2, code 0x7a on >> isa0060/serio0). >> atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. >> atkbd.c: Unknown key released (translated set 2, code 0x7a on >> isa0060/serio0). >> atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. >> >> How I can resolve this? > >Apply this patch: >http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/XFree86-lnx_kbd.patch I've applied that to 4.3.0 and it does not fix the problem. The code that gets called to set the repeat rate is actually in lnx_io.c, as a more or less verbatim cut and pasted copy of lnx_kbd.c's code, and it is what ends up getting called. After closer inspection of things it appears to me, that this was a work in progress that never got finished cleanly perhaps? When the patch is applied to both files, it fails to compile with: lnx_io.c:93: warning: string length `565' is greater than the length `509' ISO C89 compilers are required to support lnx_io.c: In function `xf86SetKbdRepeat': lnx_io.c:216: `pInfo' undeclared (first use in this function) lnx_io.c:216: (Each undeclared identifier is reported only once lnx_io.c:216: for each function it appears in.) I'm currently investigating this issue now as well. Will post back if I get time to figure it out tonight. -- Mike A. Harris _______________________________________________ XFree86 mailing list XFree86@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/xfree86
