Re: Keyboard driver for X
Ricardo Baratto schrieb: At some point in the past you (Matthieu Herrb [EMAIL PROTECTED]) said: Robert wrote (in a message from Sunday 15) Brad Hards schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 12 Jun 2003 14:57 pm, Jason Kim wrote: Has anyone developed keyboard driver for X ? Or does anyone know current situation? XFree86 4.x has loadable drivers, including keyboard. really ? i thought the keyboard is compiled into server??? There are 2 keyboard drivers in XFree86 4.3.0. One is the legacy X driver which is part of the base X server and the 2nd one is a new Xinput based driver which is dynamically loadable. The name of this loadable module is kbd (while the legacy driver is named keyboard). and is it possible to disable the legacy keyboard driver and use only kbd (or a custom keyb driver)? yeah .. just replace keyboard as driver with kbd like this Driver kbd thanks, ricardo ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel -- _ *Robert Woerle Linux Customer Support* *PaceBlade Technology Europe SA* phone: +49 89 552 99935 fax:+49 89 552 99910 mobile: +49 179 474 45 27 email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] web:http://www.paceblade.com _ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Keyboard driver for X
David Dawes schrieb:
On Sun, Jun 15, 2003 at 01:49:56PM +0200, Robert wrote:
Matthieu Herrb schrieb:
Robert wrote (in a message from Sunday 15)
Brad Hards schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 12 Jun 2003 14:57 pm, Jason Kim wrote:
Has anyone developed keyboard driver for X ? Or does anyone know current
situation?
XFree86 4.x has loadable drivers, including keyboard.
really ?
i thought the keyboard is compiled into server???
There are 2 keyboard drivers in XFree86 4.3.0. One is the legacy X
driver which is part of the base X server and the 2nd one is a new
Xinput based driver which is dynamically loadable. The name of this
loadable module is kbd (while the legacy driver is named
keyboard).
so what is the deal then with the keyboard
my problem now is that i need to prevent X to generally map cetrain
Scancodes to a generic keycode ...which then makes some extra buttons on
my Tablet Pc send the samy keycode as Key-Up and i cannot put function
on this keycode so i ll loose my KEY_UP also ...
i changed also the file atKeynames .h accordingly ...
I read then that the keyboard is compiled into the server , and also
changing the Driver Keyboard into
Driver kbd did not start the X-server
the scancodes i need to be free to get a free keycode are
0x5a and 0x59
It looks like all of the other scancodes like these that are currently
returned for various 2-byte codes need to be remapped. I recently did
this for 0x5c, which is KP_Equal on Macs. The attached patch (relative
to the current CVS trunk) should handle the rest of them. Let me know
if it works for you. If it does, I'll commit it. The patch handles both
the built-in keyboard driver, and the modular kbd driver.
If we were starting over with this, we'd handle the mappings more cleanly.
We should probably do that for 5.0.
pls tell me some more things ...
i did these changes by hand in the vanilla X-4.3 source
then i did only recompile the kbd.o module and started but still i get
KEY_UP as keysym and keycode 98 ( using xev ) for my key with scancode
0x5a and KEY_HOME and keycode 97 for my key with scancode 0.59 ... .and
i did use kbd as driver in my InputSection !!!
will i have to recompile the whole X-server (XFree86 executable ) to
make these changes work ???
So the question is what parts will be needed to exchange to make these
cchanges valid !!!
David
Index: programs/Xserver/hw/xfree86/common/atKeynames.h
===
RCS file: /home/x-cvs/xc/programs/Xserver/hw/xfree86/common/atKeynames.h,v
retrieving revision 3.18
diff -u -r3.18 atKeynames.h
--- programs/Xserver/hw/xfree86/common/atKeynames.h 29 Sep 2001 20:40:30 -
3.18
+++ programs/Xserver/hw/xfree86/common/atKeynames.h 16 Jun 2003 16:23:40 -
@@ -199,6 +199,55 @@
#define KEY_NFER /* No Kanji Transfer 0x7b */ 123
#define KEY_Yen /* Yen 0x7d */ 125
+/*
+ * Fake 'scancodes' in the following ranges are generated for 2-byte
+ * codes not handled elsewhere. These correspond to most extended keys
+ * on so-called Internet keyboards:
+ *
+ * 0x79-0x93
+ * 0x96-0xa1
+ * 0xa3-0xac
+ * 0xb1-0xb4
+ * 0xba-0xbd
+ * 0xc2
+ * 0xcc-0xd2
+ * 0xd6-0xf7
+ */
+
+/*
+ * Remapped 'scancodes' are generated for single-byte codes in the range
+ * 0x59-0x5f,0x62-0x76. These are used for some extra keys on some keyboards.
+ */
+
+#define KEY_0x59 0x95
+#define KEY_0x5A 0xA2
+#define KEY_0x5B 0xAD
+#define KEY_0x5C KEY_KP_EQUAL
+#define KEY_0x5D 0xAE
+#define KEY_0x5E 0xAF
+#define KEY_0x5F 0xB0
+#define KEY_0x62 0xB5
+#define KEY_0x63 0xB6
+#define KEY_0x64 0xB7
+#define KEY_0x65 0xB8
+#define KEY_0x66 0xB9
+#define KEY_0x67 0xBE
+#define KEY_0x68 0xBF
+#define KEY_0x69 0xC0
+#define KEY_0x6A 0xC1
+#define KEY_0x6B 0xC3
+#define KEY_0x6C 0xC4
+#define KEY_0x6D 0xC5
+#define KEY_0x6E 0xC6
+#define KEY_0x6F 0xC7
+#define KEY_0x70 0xC8
+#define KEY_0x71 0xC9
+#define KEY_0x72 0xCA
+#define KEY_0x73 0xCB
+#define KEY_0x74 0xD3
+#define KEY_0x75 0xD4
+#define KEY_0x76 0xD5
+
/* These are for notused and unknown entries in translation maps. */
#define KEY_NOTUSED 0
#define KEY_UNKNOWN 255
Index: programs/Xserver/hw/xfree86/common/xf86Events.c
===
RCS file: /home/x-cvs/xc/programs/Xserver/hw/xfree86/common/xf86Events.c,v
retrieving revision 3.151
diff -u -r3.151 xf86Events.c
--- programs/Xserver/hw/xfree86/common/xf86Events.c 11 Jun 2003 16:06:27 - 3.151
+++ programs/Xserver/hw/xfree86/common/xf86Events.c 16 Jun 2003 16:25:30 -
@@ -490,7 +490,34 @@
#endif /* i386 SVR4 */
{
switch (scanCode) {
+ case 0x59:scanCode = KEY_0x59; break;
+ case 0x5a
Re: Keyboard driver for X
On Tue, Jun 17, 2003 at 10:08:11AM +0200, Robert Woerle wrote: David Dawes schrieb: On Sun, Jun 15, 2003 at 01:49:56PM +0200, Robert wrote: Matthieu Herrb schrieb: Robert wrote (in a message from Sunday 15) Brad Hards schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 12 Jun 2003 14:57 pm, Jason Kim wrote: Has anyone developed keyboard driver for X ? Or does anyone know current situation? XFree86 4.x has loadable drivers, including keyboard. really ? i thought the keyboard is compiled into server??? There are 2 keyboard drivers in XFree86 4.3.0. One is the legacy X driver which is part of the base X server and the 2nd one is a new Xinput based driver which is dynamically loadable. The name of this loadable module is kbd (while the legacy driver is named keyboard). so what is the deal then with the keyboard my problem now is that i need to prevent X to generally map cetrain Scancodes to a generic keycode ...which then makes some extra buttons on my Tablet Pc send the samy keycode as Key-Up and i cannot put function on this keycode so i ll loose my KEY_UP also ... i changed also the file atKeynames .h accordingly ... I read then that the keyboard is compiled into the server , and also changing the Driver Keyboard into Driver kbd did not start the X-server the scancodes i need to be free to get a free keycode are 0x5a and 0x59 It looks like all of the other scancodes like these that are currently returned for various 2-byte codes need to be remapped. I recently did this for 0x5c, which is KP_Equal on Macs. The attached patch (relative to the current CVS trunk) should handle the rest of them. Let me know if it works for you. If it does, I'll commit it. The patch handles both the built-in keyboard driver, and the modular kbd driver. If we were starting over with this, we'd handle the mappings more cleanly. We should probably do that for 5.0. pls tell me some more things ... i did these changes by hand in the vanilla X-4.3 source then i did only recompile the kbd.o module and started but still i get KEY_UP as keysym and keycode 98 ( using xev ) for my key with scancode 0x5a and KEY_HOME and keycode 97 for my key with scancode 0.59 ... .and i did use kbd as driver in my InputSection !!! will i have to recompile the whole X-server (XFree86 executable ) to make these changes work ??? These translations are built-in to the XFree86 server, even when using the kbd module. The kbd module is platform independent, but the translations may not be. David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Keyboard driver for X
On Tue, Jun 17, 2003 at 02:50:28PM +0200, Robert Woerle wrote: David Dawes schrieb: On Sun, Jun 15, 2003 at 01:49:56PM +0200, Robert wrote: Matthieu Herrb schrieb: Robert wrote (in a message from Sunday 15) Brad Hards schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 12 Jun 2003 14:57 pm, Jason Kim wrote: Has anyone developed keyboard driver for X ? Or does anyone know current situation? XFree86 4.x has loadable drivers, including keyboard. really ? i thought the keyboard is compiled into server??? There are 2 keyboard drivers in XFree86 4.3.0. One is the legacy X driver which is part of the base X server and the 2nd one is a new Xinput based driver which is dynamically loadable. The name of this loadable module is kbd (while the legacy driver is named keyboard). so what is the deal then with the keyboard my problem now is that i need to prevent X to generally map cetrain Scancodes to a generic keycode ...which then makes some extra buttons on my Tablet Pc send the samy keycode as Key-Up and i cannot put function on this keycode so i ll loose my KEY_UP also ... i changed also the file atKeynames .h accordingly ... I read then that the keyboard is compiled into the server , and also changing the Driver Keyboard into Driver kbd did not start the X-server the scancodes i need to be free to get a free keycode are 0x5a and 0x59 It looks like all of the other scancodes like these that are currently returned for various 2-byte codes need to be remapped. I recently did this for 0x5c, which is KP_Equal on Macs. The attached patch (relative to the current CVS trunk) should handle the rest of them. Let me know if it works for you. If it does, I'll commit it. The patch handles both the built-in keyboard driver, and the modular kbd driver. If we were starting over with this, we'd handle the mappings more cleanly. We should probably do that for 5.0. so i merged this changes for my specific 2 keys to the vanilla X-Free 4.3 sources and it works .. the only thing now is that i cannot use kdm as Loginmanager anymore what i have i s SUSE 8.2 what i do is recompile the XFree86 and kbd.o module then i copy them to their position and restart the X-server then when i let it start normally vi init() using kdm i get a II) XINPUT: Adding extended input device PaceBook (type: TOUCHSCREEN) (II) XINPUT: Adding extended input device Mouse[1] (type: MOUSE) (II) XINPUT: Adding extended input device Keyboard[0] (type: KEYBOARD) (II) Mouse[1]: ps2EnableDataReporting: succeeded AUDIT: Tue Jun 17 15:22:50 2003: 2519 X: client 2 rejected from local host Auth name: XDM-AUTHORIZATION-1 ID: -1 AUDIT: Tue Jun 17 15:22:51 2003: 2519 X: client 2 rejected from local host Auth name: XDM-AUTHORIZATION-1 ID: -1 XFree86 does not include XDM-AUTHORIZATION support (for reasons related to crypto export restrictions). You'll either need to add that in to your build (there should be someone here who can tell you how to do that), or disable its use by kdm. David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Keyboard driver for X
On Sun, Jun 15, 2003 at 01:49:56PM +0200, Robert wrote:
Matthieu Herrb schrieb:
Robert wrote (in a message from Sunday 15)
Brad Hards schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 12 Jun 2003 14:57 pm, Jason Kim wrote:
Has anyone developed keyboard driver for X ? Or does anyone know current
situation?
XFree86 4.x has loadable drivers, including keyboard.
really ?
i thought the keyboard is compiled into server???
There are 2 keyboard drivers in XFree86 4.3.0. One is the legacy X
driver which is part of the base X server and the 2nd one is a new
Xinput based driver which is dynamically loadable. The name of this
loadable module is kbd (while the legacy driver is named
keyboard).
so what is the deal then with the keyboard
my problem now is that i need to prevent X to generally map cetrain
Scancodes to a generic keycode ...which then makes some extra buttons on
my Tablet Pc send the samy keycode as Key-Up and i cannot put function
on this keycode so i ll loose my KEY_UP also ...
i changed also the file atKeynames .h accordingly ...
I read then that the keyboard is compiled into the server , and also
changing the Driver Keyboard into
Driver kbd did not start the X-server
the scancodes i need to be free to get a free keycode are
0x5a and 0x59
It looks like all of the other scancodes like these that are currently
returned for various 2-byte codes need to be remapped. I recently did
this for 0x5c, which is KP_Equal on Macs. The attached patch (relative
to the current CVS trunk) should handle the rest of them. Let me know
if it works for you. If it does, I'll commit it. The patch handles both
the built-in keyboard driver, and the modular kbd driver.
If we were starting over with this, we'd handle the mappings more cleanly.
We should probably do that for 5.0.
David
--
David Dawes
Founder/committer/developer The XFree86 Project
www.XFree86.org/~dawes
Index: programs/Xserver/hw/xfree86/common/atKeynames.h
===
RCS file: /home/x-cvs/xc/programs/Xserver/hw/xfree86/common/atKeynames.h,v
retrieving revision 3.18
diff -u -r3.18 atKeynames.h
--- programs/Xserver/hw/xfree86/common/atKeynames.h 29 Sep 2001 20:40:30 -
3.18
+++ programs/Xserver/hw/xfree86/common/atKeynames.h 16 Jun 2003 16:23:40 -
@@ -199,6 +199,55 @@
#define KEY_NFER /* No Kanji Transfer 0x7b */ 123
#define KEY_Yen /* Yen 0x7d */ 125
+/*
+ * Fake 'scancodes' in the following ranges are generated for 2-byte
+ * codes not handled elsewhere. These correspond to most extended keys
+ * on so-called Internet keyboards:
+ *
+ * 0x79-0x93
+ * 0x96-0xa1
+ * 0xa3-0xac
+ * 0xb1-0xb4
+ * 0xba-0xbd
+ * 0xc2
+ * 0xcc-0xd2
+ * 0xd6-0xf7
+ */
+
+/*
+ * Remapped 'scancodes' are generated for single-byte codes in the range
+ * 0x59-0x5f,0x62-0x76. These are used for some extra keys on some keyboards.
+ */
+
+#define KEY_0x59 0x95
+#define KEY_0x5A 0xA2
+#define KEY_0x5B 0xAD
+#define KEY_0x5C KEY_KP_EQUAL
+#define KEY_0x5D 0xAE
+#define KEY_0x5E 0xAF
+#define KEY_0x5F 0xB0
+#define KEY_0x62 0xB5
+#define KEY_0x63 0xB6
+#define KEY_0x64 0xB7
+#define KEY_0x65 0xB8
+#define KEY_0x66 0xB9
+#define KEY_0x67 0xBE
+#define KEY_0x68 0xBF
+#define KEY_0x69 0xC0
+#define KEY_0x6A 0xC1
+#define KEY_0x6B 0xC3
+#define KEY_0x6C 0xC4
+#define KEY_0x6D 0xC5
+#define KEY_0x6E 0xC6
+#define KEY_0x6F 0xC7
+#define KEY_0x70 0xC8
+#define KEY_0x71 0xC9
+#define KEY_0x72 0xCA
+#define KEY_0x73 0xCB
+#define KEY_0x74 0xD3
+#define KEY_0x75 0xD4
+#define KEY_0x76 0xD5
+
/* These are for notused and unknown entries in translation maps. */
#define KEY_NOTUSED 0
#define KEY_UNKNOWN255
Index: programs/Xserver/hw/xfree86/common/xf86Events.c
===
RCS file: /home/x-cvs/xc/programs/Xserver/hw/xfree86/common/xf86Events.c,v
retrieving revision 3.151
diff -u -r3.151 xf86Events.c
--- programs/Xserver/hw/xfree86/common/xf86Events.c 11 Jun 2003 16:06:27 -
3.151
+++ programs/Xserver/hw/xfree86/common/xf86Events.c 16 Jun 2003 16:25:30 -
@@ -490,7 +490,34 @@
#endif /* i386 SVR4 */
{
switch (scanCode) {
+ case 0x59:scanCode = KEY_0x59; break;
+ case 0x5a:scanCode = KEY_0x5A; break;
+ case 0x5b:scanCode = KEY_0x5B; break;
case 0x5c:scanCode = KEY_KP_Equal; break; /* Keypad Equal
Re: Keyboard driver for X
Brad Hards schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 12 Jun 2003 14:57 pm, Jason Kim wrote: Has anyone developed keyboard driver for X ? Or does anyone know current situation? XFree86 4.x has loadable drivers, including keyboard. really ? i thought the keyboard is compiled into server??? Where do you plan to get your input from? That is, which device node do you plan to open()? Brad -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+6/E2W6pHgIdAuOMRAgWLAKCv6MxMEADLh7wWS5RdUt+Rurk3YQCgqfuR 6adeYscQ1KH2t7d/4q9XvZQ= =s0Je -END PGP SIGNATURE- ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Keyboard driver for X
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 15 Jun 2003 18:55 pm, Robert wrote: XFree86 4.x has loadable drivers, including keyboard. really ? i thought the keyboard is compiled into server??? I've been wrong before, however on my install, the input drivers (including keyboard) look to be loadable: /usr/X11R6/lib/modules/input/ My logs don't actually show keyboard being loaded though, so maybe I should stop guessing and wait for someone that knows :-/ Brad -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+7D/GW6pHgIdAuOMRAnp/AJ9TO70TzyTgdZBuE1o6ni0DXs/J1QCdEVAt qgkdgG+ZlmvYyBZHy6+KMlA= =ifXb -END PGP SIGNATURE- ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Keyboard driver for X
Robert wrote (in a message from Sunday 15) Brad Hards schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 12 Jun 2003 14:57 pm, Jason Kim wrote: Has anyone developed keyboard driver for X ? Or does anyone know current situation? XFree86 4.x has loadable drivers, including keyboard. really ? i thought the keyboard is compiled into server??? There are 2 keyboard drivers in XFree86 4.3.0. One is the legacy X driver which is part of the base X server and the 2nd one is a new Xinput based driver which is dynamically loadable. The name of this loadable module is kbd (while the legacy driver is named keyboard). Matthieu ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Keyboard driver for X
Matthieu Herrb schrieb: Robert wrote (in a message from Sunday 15) Brad Hards schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 12 Jun 2003 14:57 pm, Jason Kim wrote: Has anyone developed keyboard driver for X ? Or does anyone know current situation? XFree86 4.x has loadable drivers, including keyboard. really ? i thought the keyboard is compiled into server??? There are 2 keyboard drivers in XFree86 4.3.0. One is the legacy X driver which is part of the base X server and the 2nd one is a new Xinput based driver which is dynamically loadable. The name of this loadable module is kbd (while the legacy driver is named keyboard). so what is the deal then with the keyboard my problem now is that i need to prevent X to generally map cetrain Scancodes to a generic keycode ...which then makes some extra buttons on my Tablet Pc send the samy keycode as Key-Up and i cannot put function on this keycode so i ll loose my KEY_UP also ... i changed also the file atKeynames .h accordingly ... I read then that the keyboard is compiled into the server , and also changing the Driver Keyboard into Driver kbd did not start the X-server the scancodes i need to be free to get a free keycode are 0x5a and 0x59 Matthieu ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Keyboard driver for X
Hi all.. Has anyone developedkeyboard driverfor X ?Or does anyone know current situation? (Current X-server accesses the console directly to read keyboard input.. right?) Have a nice night...
