From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Subject: XF4, SysRq, VT, mouse buttons, Keymaps and all that
Date: Tue, 17 Apr 2001 22:14:22 +0100 [thread overview]
Message-ID: <20010417211637.DEDEEDBA73@atlas.valhalla.net> (raw)
Thanks to those who gave help in getting XF4 (basically) going.
I haven't been able to try Ani's patch yet - the xfree86.org cvs server
pings - but no response yet today to cvs login :-(
ati (mach64): (G3/beige, 2.4.4-pre3)
a kludge of putting the 4.0.99.1-0f libfbdevhw.a library into the latest
code gives me ati accel. Thanks Kaoru & Scott. (Will try Ani's proper fix
as soon as I can co the XFree86 tree).
Michel's advice to "option XkbDisable" gives partial functionality (VT
switches, server re-start).... but... with no mouse button emulation or
SysRq. (haven't tried MoL yet).
===
I may be going blind - but I can't see _any_ locale-specific mac keycode
tables in the X11R6 tree...
So the next question set is...
1/ Is there a description anywhere of the flow of keycode translation
adb -> linux_keycodes -> X (there isn't in linux/Documentation AFAICT).
Especially:
where to look for the tables to edit at each stage - and
what exists to examine the codes.
2/ the (ISO Mac Keyboard) SysRq key is no longer a single value (according
to showkey it sends two codes) but this needs to be caught earlier on (in
the kernel) - so is this supposed to be before or after the translation
adb->linux_keycodes? ... or how can I find the value to modify the match
code in the kernel? AFAICT SysRq is not working.
3/ how does one find the keycode values for <option>-key combinations so
that the mouse_button2 & 3 keycodes can be re-assigned (it is really
irritating losing them)... [the kernel build has this emulation enabled]
4/ Notwithstanding the PMac-specific nature of some of these questions - Is
there a HOW-to on creating a keymap (I'm happy to do one for the UK keyboard
if someone can point at the mechanism).
5/ num-lock never worked for me (even under 3.3.6 - it put the keyboard
light on but made no difference to the retured codes) I'd like to get this
fixed because some apps (like cdp) use the keypad.
any pointers appreciated and thanks again for the help so far,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-04-17 21:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 21:14 Iain Sandoe [this message]
2001-04-17 22:15 ` XF4, SysRq, VT, mouse buttons, Keymaps and all that Michel Dänzer
2001-04-17 22:49 ` Martin Costabel
-- strict thread matches above, loose matches on Subject: below --
2001-04-18 0:06 Iain Sandoe
2001-04-18 0:08 ` Michel Dänzer
2001-04-18 0:28 Iain Sandoe
2001-04-18 3:40 ` Tony Mantler
2001-04-18 4:04 ` Steven Hanley
2001-04-18 9:03 Iain Sandoe
2001-04-18 11:40 ` Martin Costabel
2001-04-18 12:03 Iain Sandoe
2001-04-18 12:13 ` Michel Dänzer
2001-04-18 12:24 ` Tony Mantler
2001-04-18 12:44 Iain Sandoe
2001-04-18 13:06 ` Tony Mantler
2001-04-18 13:39 ` Gabriel Paubert
2001-04-18 14:54 ` Franz Sirl
2001-04-18 16:10 ` Gabriel Paubert
2001-04-18 13:16 Iain Sandoe
2001-04-18 13:23 ` Tony Mantler
2001-04-18 15:18 ` Michel Dänzer
2001-04-19 14:36 Iain Sandoe
2001-04-19 19:32 ` Martin Costabel
2001-04-20 10:12 ` Franz Sirl
2001-04-21 22:45 ` Martin Costabel
2001-04-21 22:59 ` Michel Dänzer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010417211637.DEDEEDBA73@atlas.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).