+#if defined (i386) defined (SVR4)
+/*
+ * PANIX returns DICOP standards based keycodes in using 106jp
+ * keyboard. We need to remap some keys.
+ */
+if(xf86Info.panix106 == TRUE){
+ switch (scanCode) {
+ case 0x56:scanCode = KEY_BSlash2; break;
On Wed, Jun 11, 2003 at 05:57:25PM +0200, Frank Murphy wrote:
+#if defined (i386) defined (SVR4)
+/*
+ * PANIX returns DICOP standards based keycodes in using 106jp
+ * keyboard. We need to remap some keys.
+ */
+if(xf86Info.panix106 == TRUE){
+ switch (scanCode)
On Sat, Jun 07, 2003 at 07:51:04PM +0700, Ivan Pascal wrote:
Hi,
The linux-ppc kernel has an option (CONFIG_MAC_ADBKEYCODES) to use the old
ADB-style keycodes. I imagine setting this option to no uses the conversion
you're talking about. For the record, the scancodes I see (from showkey
On Mon, Jun 09, 2003 at 03:31:01PM -0400, David Dawes wrote:
On Sat, Jun 07, 2003 at 07:51:04PM +0700, Ivan Pascal wrote:
Hi,
The linux-ppc kernel has an option (CONFIG_MAC_ADBKEYCODES) to use the old
ADB-style keycodes. I imagine setting this option to no uses the conversion
you're
Hi,
The linux-ppc kernel has an option (CONFIG_MAC_ADBKEYCODES) to use the old
ADB-style keycodes. I imagine setting this option to no uses the conversion
you're talking about. For the record, the scancodes I see (from showkey -s)
are as follows:
KeyPad Equals : 0x5c 0xdc
Left Arrow
:
Sent by:Subject: Re: iBook us-keyboard problem
[EMAIL PROTECTED
Hi,
OK, after some more resarch, I have some idea of what's going on. It seems
that the X server gets the scan codes from the kernel, then passes these scan
codes to the X client. xlib has some nice functions to then convert these
scan codes into keycodes, then into keysyms. (Correct me
I have an iBook with a US keyboard layout, and I'm having a wierd problem I
hope you can help with.
The mac keyboards have a keypad equals key. X doesn't support that as
separate from regular equals, but I'd like to use it to type equals. The
problem is that both this KP-equals and the
