Bug 1836 - [PATCH] undesired keycode conversion for NEC PC-98x1
Summary: [PATCH] undesired keycode conversion for NEC PC-98x1
Status: RESOLVED DUPLICATE of bug 2561
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 6.8.2
Hardware: Other FreeBSD
: high normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2004-11-11 23:02 UTC by Satoshi KImura
Modified: 2007-04-08 10:17 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
for K/B on PC9821 (879 bytes, patch)
2005-12-12 22:54 UTC, Satoshi KImura
no flags Details | Splinter Review

Description Satoshi KImura 2004-11-11 23:02:45 UTC
1. BUG
 On Xorg 6.7.0, some keycodes are converted for PC AT,
but this conversion is undesired for NEC PC-98x1.
So, following bugs occur.
(1) Some kyes (CTRL, CAPS, SHIFT, Kana, Alt) become to make
  no sense. (i.e which have no functions to be assigned.)
(2) Some Keys (F9, VF3) have wrong funcions.

2. patch
  Following patch is available to avoid the bug.
(Note: This patch is made for XFree86 4.4.0.)

begin 644 patch.kbd.gz
M'XL("`Y9L$```W!A=&-H+FMB9`"=4F%KXD`0_=S\BG<<%#7JJLEN;.3`NZ,?
MRE$H%8[KI[*N4PVM26\W;962_]Y,8KQ2M!\ND.QFWINW,V^GU^MA8\2CS996
MKYWXX\@^DQ6K%[&YLT1C)4RV7F=I^3M6Y\^4YJYO^IE=GEQF*2[U%@@P&L5!
M$(?E9C`(/=_W_T/S9/94ZXT"#%4L92QW>M,I>C(,NPH^+Q&F4P_\%*`'1QZ^
M4KI([B`Z2(*QPNDI9K^O0W1$37OU_&I%R6E]X3,OW)4Y&[?:[1*K(;B7)#<K
MM)S1Z<]L0>\@HQUAL)%G,1KRCH1O^'5^<\O8!'-+^G[R,4E_DO1]GU2U&-4M
M1O)=BWNA2!X7BN21TR/U29+ZF%0T/A5@+U&Z>LBRO:^%5W^JZI64W>$`OI)1
M=SAJZN\@7]$6*=$">88EY1R`TVO"?0D8KDB[*CCGFCE8SE5#VHD\KK8N,?J!
MX7FF[8(W_1H47/6QF^7XO\[KUF=;=TU_R>5M[Y`S5S9)\\H3'JZ#"C_8MB/9
7^LG1A$LJFKED'K^BX[T!7,O$SVX#````
`
end
Comment 1 Satoshi KImura 2005-12-11 22:56:57 UTC
  Following patch for Xorg 6.8.2 is available to avoid the bug.

begin 644 patch.kbd.gz
M'XL("!H3G$,``W!A=&-H+FMB9`"=4EU/XS`0?":_8DY(J&W:.FD3-Z1"*E\/
MZ'02@M-]/)U<=VDB:`)V@%8H__VR2=M#J.7A(B5V=G;'L^/M]7I8:O%H\KE1
M"RM^63(O9$3R*I9WABB20N>+19Y5OY&\?*&LL'W=STTZ/_A),UR0AA_"#^*A
MC/T``\\+'-=U_X/TX'ORC&]J!7]0T<1A%'L^\X7.9()>./2[$BXO(TPF#O@I
M00^6'!Q2-DOO(#I(AY'$T1%N?]P$Z(@F[<UQZQ553NL+GWEEK_5QU&JW*ZR!
M8%_30B=H6:VR\WQ&[R"M+,%;AL<Q-LGK))S@Z^7O/XR-,36D[L<?B]0G1:?;
MHKI%V;0H!^]:W!*-POU$HW#/Z2/Y29'\6%1N?"K!7J)R=9=E6U]+I_G4ZF4P
MZ/H>7!D$W>H&U_H[*!):(:-J5HH<<RHX`*L6A/L*T*Q(V3HX9<T<S+-MTIKD
M,5G95*L'AJ>Y,C/>]!M0L.I]-\OQ?YTWK=^N[`T]D2W:SBYGKDV:%;4G/%P[
=&<[8MCW5ZMG2F"65F[GD/'Y%Q_D+L5U$=F\#````
`
end
Comment 2 Alan Coopersmith 2005-12-12 03:38:50 UTC
When submitting patches, please use the "Create a New Attachement" link in
bugzilla to attach files as plain text (not gzip'ped and not uuencoded).
Comment 3 Satoshi KImura 2005-12-12 22:54:22 UTC
Created attachment 4073 [details] [review]
for K/B on PC9821
Comment 4 Satoshi KImura 2005-12-12 22:55:26 UTC
I see. Please check Attachment #4073 [details].
Comment 5 Erik Andren 2006-04-18 05:03:14 UTC
adding patch keyword
Comment 6 Daniel Stone 2007-02-27 01:24:36 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 7 Daniel Stone 2007-04-07 15:20:34 UTC
since the old keyboard code no longer exists, marking as a dupe of the kbd bug.

*** This bug has been marked as a duplicate of bug 2561 ***
Comment 8 Satoshi KImura 2007-04-08 09:39:13 UTC
I see. Since I had sent report to X.Org and FreeBSD, the later sent the same report as #2561.

> since the old keyboard code no longer exists, 
The source of X.Org 7.? was already modified by #2561, but 6.9.0 was not modified.
Tha last version of FreeBSD (6.2) makes use of X.Org 6.9.0 with modification.

If next FreeBSD will use X.Org 7.2 or so, need not to modify 6.9.0 any more.
So we can close here.
Comment 9 Daniel Stone 2007-04-08 10:17:34 UTC
i don't know, i can't speak for freebsd.  but 6.9.0 is a dead codebase, so i sure hope it starts using 7.x ...


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.