Hi Everyone
Does anyone know the correct keycodes for the
CTRL/ALT/left-hand-side Apple keys?
For an alubook5,8, qwertz (DE) keyboard? Even those for another region
layout might work, provided it is a pb5,8 ..
I need them for sysctrl.conf entries, like those:
dev/mac_hid
Hi,
Is there a relation between the keycodes from the event devices
/dev/input/event% and the X11 key events? Which?
How can I get the event deveice keycodes in an X11 application
without opening the /dev/input/event% devices?
Best Regards
Matthias
--
To UNSUBSCRIBE, email to [EMAIL
On Thursday 18 November 2004 11:00 am, Wolfgang Pfeiffer wrote:
> Hi All
>
> Titanium IV here.
> console-tools: Installed: 1:0.2.3dbs-55
>
> I'm trying to change the keyboard map on console: I have to know the
> appropriate keycodes for that ...
> The problem is t
Hi All
Titanium IV here.
console-tools: Installed: 1:0.2.3dbs-55
I'm trying to change the keyboard map on console: I have to know the
appropriate keycodes for that ...
The problem is the keycodes shown by "showkey --keymap" differ heavily
from those in my current /etc/console/b
On Wed, 2003-12-24 at 21:05, Joerg Sommer wrote:
> Hi,
>
> I get two keycodes if I press the power key or capslock. Both in X (with
> xev) and in the console (with showkey). Unfortunately sends capslock the
> same keycode like powerkey. How can I correct this? Is this a problem
Hi,
I get two keycodes if I press the power key or capslock. Both in X (with
xev) and in the console (with showkey). Unfortunately sends capslock the
same keycode like powerkey. How can I correct this? Is this a problem of
the kernel?
I'm using the 2.6.0-test11-benh kernel on a iBook G4 (g
Julien Kirmaier wrote:
Must be a lack of coffee.
A serious drawback... ;)
Regards, Ismael
Bonjour Michel,
le jeudi 03 juillet vers 00:54 Michel Dänzer m'a raconté:
> > > How can i see the keycodes?
> >
> > You start xev in X (shell), it shows up a little window, you move the
> > pointer on it and the keycodes corresponding to the characters you t
On Wed, 2003-07-02 at 17:05, Julien Kirmaier wrote:
> le mercredi 02 juillet vers 00:50 [EMAIL PROTECTED] a dit:
>
> > How can i see the keycodes?
>
> You start xev in X (shell), it shows up a little window, you move the pointer
> on it and the keycodes corresponding to th
xev only shows the X keycodes. He needs the console keycodes which can be
gotten with showkey run on a console (not in an XTerm).
> use the program "xev"
>
> On Wed, Jul 02, 2003 at 12:50:44AM -0500, [EMAIL PROTECTED]
wrote:
> > How can i see the keycodes?
> >
&g
Am Mit, 2003-07-02 um 17.05 schrieb Julien Kirmaier:
> le mercredi 02 juillet vers 00:50 [EMAIL PROTECTED] a dit:
>
> > How can i see the keycodes?
>
> You start xev in X (shell), it shows up a little window, you move the pointer
> on it and the keycodes corresponding to th
le mercredi 02 juillet vers 00:50 [EMAIL PROTECTED] a dit:
> How can i see the keycodes?
You start xev in X (shell), it shows up a little window, you move the pointer
on it and the keycodes corresponding to the characters you type in will be
logged in the shell. Ctrl-Btn1 to close.
Hope t
On Wed, Jul 02, 2003 at 12:50:44AM -0500, [EMAIL PROTECTED] wrote:
> How can i see the keycodes?
>
> i want to configure the 2 and 3 mouse button, but in the keys i want.
>
> dev/mac_hid/mouse_button2_keycode=68
> dev/mac_hid/mouse_button3_keycode=87
>
> is for F9 and
use the program "xev"
On Wed, Jul 02, 2003 at 12:50:44AM -0500, [EMAIL PROTECTED] wrote:
> How can i see the keycodes?
>
> i want to configure the 2 and 3 mouse button, but in the keys i want.
>
> dev/mac_hid/mouse_button2_keycode=68
> dev/mac_hid/mouse_button3_keyco
Am Mit, 2003-07-02 um 07.50 schrieb [EMAIL PROTECTED]:
> How can i see the keycodes?
>
use showkey on a virtual console (not in X)
gaudenz
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
On Wed, 2003-07-02 at 06:50, [EMAIL PROTECTED] wrote:
> How can i see the keycodes?
>
> i want to configure the 2 and 3 mouse button, but in the keys i want.
>
> dev/mac_hid/mouse_button2_keycode=68
> dev/mac_hid/mouse_button3_keycode=87
>
> is for F9 and F10, but i need
How can i see the keycodes?
i want to configure the 2 and 3 mouse button, but in the keys i want.
dev/mac_hid/mouse_button2_keycode=68
dev/mac_hid/mouse_button3_keycode=87
is for F9 and F10, but i need diferent keys
Thanks.
why it did this, but it works now.
Thanks,
Steven
--- Claas Langbehn <[EMAIL PROTECTED]> wrote:
> > Now I have trouble that the keyboard maps are wrong. According to
> the
> > "PowerPC Keycodes Change" document on the website, this shouldn't
> > hap
Ok, thanks to those who helped me on my previous problem. I eventuall
got it working by installing MacOS 8 and then installing Debian, and
now it uses BootX. Not as elegant as before, but oh well.
Now I have trouble that the keyboard maps are wrong. According to the
"PowerPC Keycodes C
On Wed, 2002-10-09 at 08:51, Mike Johnson wrote:
> I tried to google on this, but didn't find too many clues. I want to use
> different keys than listed in the examples for the iBook2 setup for the
> middle- and right-buttons (currently f10 and f11).
>
> xev seems to be re
Hi all,
I tried to google on this, but didn't find too many clues. I want to use
different keys than listed in the examples for the iBook2 setup for the
middle- and right-buttons (currently f10 and f11).
xev seems to be returning keycodes for something else, is there a way to
find these?
T
> > I agree it _should_ default to 0 but was it really set up that way?
>
> You've got it completely reversed. ;)
Entirely possible - the whole Linux keycodes issue is just too confusing
:-) I must have removed Linux keycodes support long ago from my kernels...
Michael
> > My sysctl.conf is empty. _I_ certainly have not ran it, and I don't
> > know if another program may have ran it at boot time.
>
> grep -lr keyboard_sends_linux_keycodes /etc (or / if you don't mind
> waiting a bit ;) might be interesting.
The fault is mine! It seems that, at some point, I
On Wed, 2001-11-28 at 17:19, Ali Bahar wrote:
> On Wed, Nov 28, 2001 at 12:51:25PM +0100, Michel Dänzer wrote:
> > that you set the sysctl from userland, e.g. in /etc/sysctl.conf?
>
> My sysctl.conf is empty. _I_ certainly have not ran it, and I don't
> know if another program may have ran it at b
On Wed, Nov 28, 2001 at 12:51:25PM +0100, Michel Dänzer wrote:
> On Wed, 2001-11-28 at 12:05, Michael Schmitz wrote:
> > > I tried it yet again. This time, on a virgin source tree. I got the
> > > same result ie ADBKEYCODES and keyboard_sends_linux_keycodes co-exist!
> Does Linus' tree behave dif
; No, I said the opposite. It should default to 0 when ADB keycodes are
> > enabled. (And if they're disabled, the sysctl doesn't exist in 2.4
> > kernels)
>
> I agree it _should_ default to 0 but was it really set up that way?
You've got it completely reversed. ;)
> > And? Didn't Michel say keyboard_sends_linux_keycodes defaults to 1
> > whenever you have the CONFIG_INPUT (or whatever it's called) set?
> > Regardless of the ADBKEYCODES setting?
>
> No, I said the opposite. It should default to 0 when ADB keycodes are
> e
> whenever you have the CONFIG_INPUT (or whatever it's called) set?
> Regardless of the ADBKEYCODES setting?
No, I said the opposite. It should default to 0 when ADB keycodes are
enabled. (And if they're disabled, the sysctl doesn't exist in 2.4
kernels)
Does Linus' tree be
egardless of the ADBKEYCODES setting?
It's called 'convincing users that Linux keycodes are, in fact, the way to
go' or some such :-)
Michael
On Mon, Nov 26, 2001 at 12:48:31PM -0500, Ali wrote:
> On Mon, Nov 26, 2001 at 05:50:10PM +0100, Michel D<81>nzer wrote:
> > If ADB keycodes are enabled in the kernel config,
> > keyboard_sends_linux_keycodes is 0 by default, meaning the keyboard
> That has not been my
On Mon, Nov 26, 2001 at 05:50:10PM +0100, Michel D<81>nzer wrote:
> If ADB keycodes are enabled in the kernel config,
> keyboard_sends_linux_keycodes is 0 by default, meaning the keyboard
> sends ADB keycodes. That's why we recommend disabling ADB keycodes
> in
> th
On Mon, 2001-11-26 at 17:26, Ali Bahar wrote:
> On Mon, Nov 26, 2001 at 12:49:19PM +0100, Michel Dänzer wrote:
> > On Mon, 2001-11-26 at 00:44, Ali Bahar wrote:
>
> > A kernel which doesn't support ADB keycodes has no choice but to use
> > Linux keycodes.
>
>
On Mon, Nov 26, 2001 at 12:49:19PM +0100, Michel Dänzer wrote:
> On Mon, 2001-11-26 at 00:44, Ali Bahar wrote:
> A kernel which doesn't support ADB keycodes has no choice but to use
> Linux keycodes.
That's what I assumed. But then how do you explain their appar
licitly says that
> CONFIG_MAC_ADBKEYCODES=n
> would result in
> keyboard_sends_linux_keycodes=1
A kernel which doesn't support ADB keycodes has no choice but to use
Linux keycodes.
> Also note that running 'dpkg-reconfigure console-data' had no complaints
> w
[EMAIL PROTECTED] (Chris Tillman) writes:
> On Sun, Nov 25, 2001 at 08:42:56AM +, Ali Bahar wrote:
> > [EMAIL PROTECTED] (Chris Tillman) writes:
> > CONFIG_MAC_ADBKEYCODES=n would set this!
> >
> > If it's consistent with your post, then ignore this.
> >
>
> Well no, I haven't seen it wor
> We're only talking about Debian here. We can't enforce our policy on
> everybody (unfortunately ;).
No, that's a Good Thing (considering the confusion about 'which key will
work as alt key in the next release' that's bound to happen now) :-)
Michael
and works on virtual terminals as
> well as in X) configuration which has a slight discrepancy with your
> post:
>
Any input is welcome.
> > You can use an older kernel (with CONFIG_MAC_ADBKEYCODES=y) with a
> > linux keycodes keymap, if you use
> > append="keybo
with your
post:
> You can use an older kernel (with CONFIG_MAC_ADBKEYCODES=y) with a
> linux keycodes keymap, if you use
> append="keyboard_sends_linux_keycodes=1" in your config file to
> pass the keycode config to the kernel on startup. If you don't fix
[EMAIL PRO
nf, ran quik, and
> > rebooted. When I did, my keymap didn't work.
>
> Dan, could you fix this please? Also, (on a semi-related topic) could
> you not compile in DevFS support at all (not just having support, but
> disabled by default)? It makes the boot-floppies puke complete
nels).
> >
> > The ADB keymaps are still there for those who know what they're doing,
> > but only those for Linux keycodes are presented in the arch list and
> > officially supported.
>
> So,
>
> was changed to present linux keycode maps for installatio
ate present and future conflicts, woody's console-data package
> > was changed to install linux keycode maps instead of ADB keycode maps
> > (which used to be the norm for powerpc kernels).
>
> The ADB keymaps are still there for those who know what they're doing,
> b
prints a warning?
Not a bad idea, but then official kernels shouldn't support ADB keycodes
(or at least default to Linux keycodes) anyway, and this doesn't well
cover custom kernels.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
On Sat, Nov 24, 2001 at 04:18:10AM -0500, Colin Walters wrote:
> Chris Tillman <[EMAIL PROTECTED]> writes:
>
> > I was trying to track down a crashing bug, and decided to try the
> > system with the 2.4.12 kernel from kernel-image-2.4.12-powerpc. I
> > did apt-get on that package (and kernel-sourc
linux keycode maps instead of ADB keycode maps
> (which used to be the norm for powerpc kernels).
The ADB keymaps are still there for those who know what they're doing,
but only those for Linux keycodes are presented in the arch list and
officially supported.
> The installation system&
Chris Tillman <[EMAIL PROTECTED]> writes:
> I was trying to track down a crashing bug, and decided to try the
> system with the 2.4.12 kernel from kernel-image-2.4.12-powerpc. I
> did apt-get on that package (and kernel-source / kernel-patch for
> good measure). There were no bad messages during t
n for the new kernel in my quik.conf, ran quik, and
rebooted. When I did, my keymap didn't work.
This was the same behavior I had gotten when changing keycodes in the
2.2.19 kernel. So, I figured the same solution would work: add
keyboard_sends_linux_keycodes=1 to the kernel arguments. But
to swap.
Works well for me, but may need some attention if there are apple
keyboards with right option or command keys that send distinguishable
keycodes.
My keyboard section looks like this:
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" &q
On Thu, 11 Oct 2001, Charles Sebold wrote:
> > Please note that the Capslock -> Control thing will only work if you
> > use a hacked kernel...
>
> Or if you have one of the new full-size Apple keyboards, in which
> CapsLock is a normal key, or replace your Apple keyboard with somebody
> else's PC-
On 24 Tishrei 5762, Gregory P. Keeney wrote:
> Please note that the Capslock -> Control thing will only work if you
> use a hacked kernel...
Or if you have one of the new full-size Apple keyboards, in which
CapsLock is a normal key, or replace your Apple keyboard with somebody
else's PC-style USB
correctly. By default,
there is no Mod bit set up for meta, which means that even if you define
one, it won't work as expected.
Please note that the Capslock -> Control thing will only work if you use
a hacked kernel...
Also notice that I set up the PowerBook keys to send XF86 keycodes (I
th
At 7:58 AM -0700 10/11/01, Gregory P. Keeney wrote:
Of course us poor incorrigible emacs user are quite happy with the
command key being were it is, and making option Alt... That way, the
command key becomes Meta, and we have both Meta and Alt... (Throw in a
Hyper and Super, and let the custom ke
On Thu, 2001-10-11 at 02:43, Ethan Benson wrote:
> I agree, the key labeled alt should be alt by default. However the
> fact is Apple's keyboards put alt in the wrong damn place and anyone
> who has ever typed on a normal keyboard will be annoyed as hell at
> this and thus need a trivial and quick
Ethan Benson wrote:
>
> On Wed, Oct 10, 2001 at 06:49:26PM -0500, Branden Robinson wrote:
> >
> > As far as hacking keymaps goes, yes. If the xkb data is wrong for a
> > model of keyboard, I think it should be fixed and I'd like to receive
> > patches to this effect.
>
> the trouble is nobody ca
On Wed, Oct 10, 2001 at 08:21:45PM -0500, Branden Robinson wrote:
>
> These are easily taken care of with little option files that you can
> manipulate with XKbOption. Like "ctrl:nocaps" on the PC keyboard.
>
> It's not an insuperable problem at all.
>
> (Though how anyone can expect the "alt"
On Wed, Oct 10, 2001 at 04:05:23PM -0800, Ethan Benson wrote:
> the trouble is nobody can agree whether `command == meta' is `wrong'
> or not.
>
> given the option key is the one with `alt' engraved on it one would
> presume it should be treated as alt, regardless of the fact that apple
> put it
On Wed, Oct 10, 2001 at 06:49:26PM -0500, Branden Robinson wrote:
>
> As far as hacking keymaps goes, yes. If the xkb data is wrong for a
> model of keyboard, I think it should be fixed and I'd like to receive
> patches to this effect.
the trouble is nobody can agree whether `command == meta' is
On Wed, Oct 10, 2001 at 03:26:30PM -0800, Ethan Benson wrote:
> what for? Branden has already `fixed' the Xsession scripts to ignore
> /etc/X11/Xmodmap as well as the ~/.Xmodmap (or whatever) since xmodmap
> is allegedly `deprecated'
>
> apparently were supposed to just hack the raw keymaps themse
On Wed, Oct 10, 2001 at 03:25:33PM -0400, Adam C Powell IV wrote:
> Ethan Benson wrote:
>
> >http://master.penguinppc.org/~eb/Xmodmap
> >
> Thanks very much, this looks great! I'll fiddle with it slightly on my
> setup so both alt and meta are on 115 and 116.
>
> Can we suggest that to Branden
On Wed, Oct 10, 2001 at 03:25:33PM -0400, Adam C Powell IV wrote:
> That's very odd. ~/.Xmodmap still seems to work, are you saying
> /etc/X11/Xmodmap will no longer be used? Bummer!
xmodmap is now deprecated but not difficult to support. I continue to
ship the old /etc/X11/Xmodmap in xfree86-
Ethan Benson wrote:
http://master.penguinppc.org/~eb/Xmodmap
Thanks very much, this looks great! I'll fiddle with it slightly on my
setup so both alt and meta are on 115 and 116.
Can we suggest that to Branden for (commented) inclusion in
/etc/X11/Xmodmap (or have you done so already)?
> keycode 115 = Alt_L
> keycode 125 = Alt_L
> keycode 126 = Alt_L
>
> The command keys do nothing here... Any ideas?
Try adding the following line after the above:
add mod1 = Alt_L
See 'man xmodmap' for details.
http://master.penguinppc.org/~eb/Xmodmap
note this won't work with the XFree packages in sid since xmodmap
support has been removed from the Xsession scripts since its allegedly
`deprecated' and as far as anyone has told me no replacement has been
documented. (other then fscking with the keymap
Greetings,
Using Linux keycodes, I'm trying to map the command keys (next to the
spacebar on an ADB keyboard) to alt using xmodmap, but nothing I've
tried works. [I use the alt keys for button emulation, keycodes 56 and
100; would like command for alt since alt is next to the sp
On Sat, 29 Sep 2001, Bruce McIntyre wrote:
> > Are you sure they ever produced different keycodes? Jens Schmalzing thought
> > so
> > as well but couldn't reproduce it.
>
> I just rebooted; and yes, it is working again. Keycodes of 97 and 100 in
> mac_hid work, a
ght alt or ctl
> > > keys. Both alt keys echo 56 both control keys echo 28.
> > >
> > > I think this is the `key' to the above problem, but don't know how to fix
> > > it.
>
> Are you sure they ever produced different keycodes? Jens Schmalzing tho
* Michel Dänzer ([EMAIL PROTECTED]) wrote:
> Bruce McIntyre wrote:
> >
> > > Are you sure they ever produced different keycodes? Jens Schmalzing
> > > thought so as well but couldn't reproduce it.
> >
> > I'm, say, 80% sure they did; at least I
think this is the `key' to the above problem, but don't know how to fix
> > it.
Are you sure they ever produced different keycodes? Jens Schmalzing thought so
as well but couldn't reproduce it.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
* Bruce McIntyre ([EMAIL PROTECTED]) wrote:
> Hello all,
> For some reason or other mouse button emulation in x and gdm has just
> stopped working (upon reboot).
>
> keyboard_lock_keycodes = 0 keyboard_sends_linux_keycodes = 1
> mouse_button_emulation = 1 mouse_button2_keycode = 97
> mou
On Mon, Sep 17, 2001 at 11:24:03PM +0200, Michael Schmitz wrote:
> > > That'll bring you back to default booting MacOS if a) you keep it
> > > installed and b) your boot-device variable ever gets reset (a hard
> > > kernel crash often does that for me). OF seems to default to the
> > > first 'bless
> > That'll bring you back to default booting MacOS if a) you keep it
> > installed and b) your boot-device variable ever gets reset (a hard
> > kernel crash often does that for me). OF seems to default to the
> > first 'blessed' filesystem it can find, that's why having the
> > bootstrap partition
Michael Schmitz <[EMAIL PROTECTED]> writes:
> That'll bring you back to default booting MacOS if a) you keep it
> installed and b) your boot-device variable ever gets reset (a hard
> kernel crash often does that for me). OF seems to default to the
> first 'blessed' filesystem it can find, that's w
On Mon, Sep 17, 2001 at 09:53:09AM +0200, Michael Schmitz wrote:
> Regardless of what Ethan thinks, I'm a far cry from a clueless newbie.
i don't think your a clueless newbie.
> Now imagine the newbie, having partitioned and set up his system the Wrong
> Way (tm), then forgotten about the detai
> > crash often does that for me). OF seems to default to the first 'blessed'
> > filesystem it can find, that's why having the bootstrap partition first is
> > nicer.
>
> Um. You still have Command-Option-O-F, which will get you to an OF prompt,
> at which point you can do 'boot hd:13,\\:tbxi' (ch
On Sun, Sep 16, 2001 at 09:53:15AM +0200, Michel Lanners wrote:
>
> Remember that physical order on disk doesn't necessarily mean the same
> thing as order in the partition map.
correct.
> AFAIR, you can have your partitions physically in any order you want
> (with the one exception beeing the f
Folks,
On 15 Sep, this message from Ethan Benson echoed through cyberspace:
> On Sat, Sep 15, 2001 at 12:50:28PM -0600, Derrik Pates wrote:
>>
>> The partition's location doesn't matter. Remember, you don't have to deal
>
> yes it does. OF won't boot it by default from default settings if its
On Sat, Sep 15, 2001 at 02:23:09PM -0600, Derrik Pates wrote:
> On Sat, 15 Sep 2001, Michael Schmitz wrote:
>
> > That'll bring you back to default booting MacOS if a) you keep it
> > installed and b) your boot-device variable ever gets reset (a hard kernel
> > crash often does that for me). OF se
On Sat, Sep 15, 2001 at 12:50:28PM -0600, Derrik Pates wrote:
>
> The partition's location doesn't matter. Remember, you don't have to deal
yes it does. OF won't boot it by default from default settings if its
not first.
--
Ethan Benson
http://www.alaska.net/~erbenson/
pgpQhk6aRFkiU.pgp
De
On Sat, Sep 15, 2001 at 08:01:07PM +0200, Roland Wegmann wrote:
> /dev/hda1 Apple_partition_map Apple
> /dev/hda2 Apple_Driver43 Macintosh
> /dev/hda3 Apple_Driver43 Macintosh
> /dev/hda4 Apple_Driver_ATA Macintosh
> /dev/hda5 Apple_Driver_ATA Macintosh
> /dev/hda6 Apple_FWDri
On Sat, 15 Sep 2001, Michael Schmitz wrote:
> That'll bring you back to default booting MacOS if a) you keep it
> installed and b) your boot-device variable ever gets reset (a hard kernel
> crash often does that for me). OF seems to default to the first 'blessed'
> filesystem it can find, that's w
> The partition's location doesn't matter. Remember, you don't have to deal
> with the broken BIOS that x86's have, and all the ass-backwards
> limitations of real mode, so it can be at the beginning or the end (on an
> iBook I've been using, the Apple_Bootstrap partition is the last one on
> the d
On Sat, 15 Sep 2001, Roland Wegmann wrote:
> Now I can't use vi anymore. But I need it to modify "yaboot.conf" etc. When
> I type for example "vi sources.list" I got the message "vi: wrapper couldn't
> execute /usr/bin/vi nor /bin/elvis-tiny". What's wrong with vi?
Do you have nvi installed? If s
Roland Wegmann wrote:
> Secondly, I want to change my keyboard layout from US to Swiss german (or at
> least German). On this maillist I heard a lot about linux keycodes. After my
> difficulties with "console common" I may ask you if linux keycodes are
> another way to a
erman (or at
least German). On this maillist I heard a lot about linux keycodes. After my
difficulties with "console common" I may ask you if linux keycodes are
another way to adapt the keyboard? Are there any howto's or examples on this
topic?
Thirdly, I have a semi installed yaboo
With all this stuff about keycodes, I'm not sure which
keycodes I have enabled right now; I had removed the
kernel sources and was partway through a new download
via rsync (intermittently, while logged on) of benh's
kernel tree.
I need to recompile the kernel anyway, to get somethin
> I tried using the 0xff keycode first, to no effect. I looked at the
> iControl code and saw that the key code used was 127 (0x7f); that
The keycode is masked with 0x7f as the high bit is used to distinguish
press from release.
> worked. I have a TiBook... Are the keycodes different
>>>>> On Fri, 31 Aug 2001 10:15:11 -0700, "Gregory P. Keeney" <[EMAIL
>>>>> PROTECTED]> said:
g> I tried using the 0xff keycode first, to no effect. I looked at the
g> iControl code and saw that the key code used was 127 (0x7f); that
g> wo
trol, as I had it mapped to
control under X)...
> I've attached a slightly different patch for adbhid.c which
> may be a little more tolerant of spurious 0xff keycodes. You should
> be able to hit CapsLock again if it gets into a bad state. (This only
> generates the extra Caps
releasing capslock (or press and release another key before
m> releasing capslock). If that generates a 0x39 for the second capslock
m> press we can just remeber the last key pressed, otherwise we'll need to
m> keep track of capslock state.
On either keyboard, it doesn&#x
ginal code for OSX to see if it's
completely stable?
I've attached a slightly different patch for adbhid.c which
may be a little more tolerant of spurious 0xff keycodes. You should
be able to hit CapsLock again if it gets into a bad state. (This only
generates the extra CapsLock pr
> Thanks for answering my silly question. I've got this three button
> adb mouse, you see, but I've never been able to get the other two
> mouse buttons to do anything other than act like the first one. I'd
This usually means the mouse powers up in a Mac mouse compatible mode, and
the MacOS driv
Michael Schmitz wrote:
>
> > What about mouse data on the adb bus? Would the device address be
> > the resolution for whether it is mouse or keyboard?
>
> The mouse data packets will have a different device address
> (data[0]>>4) & 0xf, so you can filter on that for debugging purpose (the
> adbh
> What about mouse data on the adb bus? Would the device address be
> the resolution for whether it is mouse or keyboard?
The mouse data packets will have a different device address
(data[0]>>4) & 0xf, so you can filter on that for debugging purpose (the
adbhid input routine returns if the device
What about mouse data on the adb bus? Would the device address be
the resolution for whether it is mouse or keyboard?
a
Michael Schmitz wrote:
>
> > >From the iControl code, it would appear that there is more to an ADB
> > event than just the key code... And that there is enough extra
> > infor
> >From the iControl code, it would appear that there is more to an ADB
> event than just the key code... And that there is enough extra
> information to determine whether the event is a caps-lock event or not.
What additional information would there be? (The only place it could
possibly be is the
I would recomend not using the diff I posted... There are some problems
(which others, more wise than I,predicted). I really don't know anything
of how ADB works, and I have no previous experience working with the
linux kernel. I really had no grounds to expect my code to work
correctly.
>From the
> >> 1st press:0x39
> >> 1st release: 0x80
> >> 2nd press:0xb9
> >> 2nd release: 0x80
>
> As noted previously, the PowerBook CapsLock generates:
>
> 1st press:0x39
> 1st release: 0xff
> 2nd press:0xff
> 2nd release: 0xb9
>
> Note the difference in order of events for second
> On Wed, 29 Aug 2001 09:47:43 +0200 (CEST), Michael Schmitz <[EMAIL
> PROTECTED]> said:
>> Well, I know of at least one other type of ADB keyboard where
>> this wouldn't work. The keyboard on my old PowerWave generates
>> different events for CapsLock:
>>
>> 1st press:0x39
>> 1st r
> Well, I know of at least one other type of ADB keyboard where
> this wouldn't work. The keyboard on my old PowerWave generates
> different events for CapsLock:
>
> 1st press:0x39
> 1st release: 0x80
> 2nd press:0xb9
> 2nd release: 0x80
>
> So that requires a different hack to
> On Tue, 28 Aug 2001 14:47:45 +0200 (CEST), Michael Schmitz <[EMAIL
> PROTECTED]> said:
m> Caution with the 0xff response byte - I think I've seen that as first byte
m> for a number of 'sporadic' ADB events as well, such as regular interrupts
m> from the ADB controller once a second (on
Richard Clamp wrote:
Don't just tease, please post a patch, and we'll love you forever :)
Below is my attempt to implement the Cap Lock fix. It seems to work on
my TiBook (but then again I have only been using my modified kernel
for about 5 minutes...).
Hope this is usefull.
Gregory P. Keen
1 - 100 of 165 matches
Mail list logo
