From: "Iain Sandoe" <iain@sandoe.co.uk>
To: "Michel Dänzer" <michdaen@iiic.ethz.ch>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: XF4, SysRq, VT, mouse buttons, Keymaps and all that
Date: Wed, 18 Apr 2001 01:28:52 +0100 [thread overview]
Message-ID: <20010418002843.8305BDBACB@atlas.valhalla.net> (raw)
Michel Dänzer wrote:
> Iain Sandoe wrote:
>> On Tue, Apr 17, 2001, Michel Dänzer wrote:
>> > Iain Sandoe wrote:
>> [..]
>> >> 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).
>> >
>> > The latter two aren't X but kernel issues.
>>
>> agreed - so how come installing a new version of X blows them away :-/
>> (maybe it's a co-incidence... hmmm... did I try 2.4.4 _before_ I
>> upgraded... can't remember)...
>>
>> AH! I know what I changed - I've left off the "Xpmac backward compatibility"
>> CONFIG option ... should I still use that with XF4 ?
>
> Don't think so. The thing is XF4 doesn't do mouse button emulation, the kernel
> does that.
Yep. But maybe it puts the emulated button presses on different keys
with/without backward compat. I'll have a look in a minute.
The frustration is that the keycodes are listed in
/proc/sys/dev/mac_hid/mouse_buttonX_keycode - but finding out which physical
key combination relates to the numbers doesn't appear to be trivial.
>For SysRq I suspect that has to do with Linux keycodes?
Not soley/directly - I've had linux keycodes enabled (and the new input
layer) for months... (including in 2.2.x back-ported version in Ben's old
tree).
I know I'm asking dumb questions... but it's gradually beginning to make
some sense..
thanks,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-04-18 0:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 0:28 Iain Sandoe [this message]
2001-04-18 3:40 ` XF4, SysRq, VT, mouse buttons, Keymaps and all that Tony Mantler
2001-04-18 4:04 ` Steven Hanley
-- strict thread matches above, loose matches on Subject: below --
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
2001-04-18 13:16 Iain Sandoe
2001-04-18 13:23 ` Tony Mantler
2001-04-18 15:18 ` Michel Dänzer
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 12:03 Iain Sandoe
2001-04-18 12:13 ` Michel Dänzer
2001-04-18 12:24 ` Tony Mantler
2001-04-18 9:03 Iain Sandoe
2001-04-18 11:40 ` Martin Costabel
2001-04-18 0:06 Iain Sandoe
2001-04-18 0:08 ` Michel Dänzer
2001-04-17 21:14 Iain Sandoe
2001-04-17 22:15 ` Michel Dänzer
2001-04-17 22:49 ` Martin Costabel
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=20010418002843.8305BDBACB@atlas.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michdaen@iiic.ethz.ch \
/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).