> 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, or am I mis
> 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> worked. I have a TiBook... Are the keycodes different, or am
On 30 Aug 2001 23:57:16 -0700, [EMAIL PROTECTED] wrote:
> What problems did you experience? My first attempt was
> similar and I noticed that it would occassionally get into a bad
> state, as if a spurious 0xff keycode has caused the temp state
> variable for the CapsLock key to be "invert
> On Wed, 29 Aug 2001 11:01:35 +0200 (CEST), Michael Schmitz <[EMAIL
> PROTECTED]> said:
[clone keyboard:]
>> >> 1st press:0x39
>> >> 1st release: 0x80
>> >> 2nd press:0xb9
>> >> 2nd release: 0x80
>>
>> As noted previously, the PowerBook CapsLock generates:
>>
>> 1st press:
> On Tue, 28 Aug 2001 09:05:36 -0700, "Gregory P. Keeney" <[EMAIL
> PROTECTED]> said:
g> I would recomend not using the diff I posted... There are some problems
g> (which others, more wise than I,predicted). I really don't know anything
g> of how ADB works, and I have no previous experien
> 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
> > So, I tried a quick hack in adbhid_input_keycode
> > (drivers/macintosh/adbhid.c)
> > to translate the events appropriately and it seems to work (at last!).
>
> Don't just tease, please post a patch, and we'll love you forever :)
Caution with the 0xff response byte - I think I've seen that as
On Mon, Aug 27, 2001 at 10:06:00PM -0700, Gregorio Gervasio Jr. wrote:
> So, I tried a quick hack in adbhid_input_keycode (drivers/macintosh/adbhid.c)
> to translate the events appropriately and it seems to work (at last!).
Don't just tease, please post a patch, and we'll love you forever :)
--
> On Mon, 27 Aug 2001 19:55:01 -0400, Adam Lazur <[EMAIL PROTECTED]> said:
>> That is sort of what I did. However, the way the caps lock key works
>> makes it impracticle: The keypress event is sent when you first press
>> the key... The key release event is sent when the key is released the
>
Gregory P. Keeney ([EMAIL PROTECTED]) said:
> That is sort of what I did. However, the way the caps lock key works
> makes it impracticle: The keypress event is sent when you first press
> the key... The key release event is sent when the key is released the
> second time. This leads to rather inco
Gregory P. Keeney writes:
> [Albert Cahalan]
>> So for a Ctrl-A you get:
>>
>> 1. crummy key down
>> 2. 'A' key down
>> 3. 'A' key up
>> 4. generate synthetic key-up event for the crummy key
>
> That is sort of what I did. However, the way the caps lock key works
> makes it impracticle: The keypre
Michael Schmitz wrote:
Haven't we hashed this out previously here?
Michael
A couple times...
Thanks for the more accurate description of the problem.
Gregory P. Keeney
> That is sort of what I did. However, the way the caps lock key works
> makes it impracticle: The keypress event is sent when you first press
> the key... The key release event is sent when the key is released the
Nope, it's subtly different: a release event is inserted each time the key
is press
"Gregory P. Keeney" <[EMAIL PROTECTED]> writes:
> Particularly, the following post:
> http://www.macslash.com/comments.pl?sid=01/08/23/1916219&cid=7
Um, wow. I don't think I'm quite ready to go there yet :)
That is sort of what I did. However, the way the caps lock key works
makes it impracticle: The keypress event is sent when you first press
the key... The key release event is sent when the key is released the
second time. This leads to rather inconsistant behaivior. The
workaround would be to tra
Gregory P. Keeney writes:
> Particularly, the following post:
> http://www.macslash.com/comments.pl?sid=01/08/23/1916219&cid=7
>
> Well, now I know where to begin. The only thing stopping me from doing
> this tonight is the cost of a backup keyboard... Maybe I will pick up
> an inexpensive USB ke
I just found the following on MacSlash:
http://www.macslash.com/articles/01/08/23/1916219.shtml
Particularly, the following post:
http://www.macslash.com/comments.pl?sid=01/08/23/1916219&cid=7
Well, now I know where to begin. The only thing stopping me from doing
this tonight is the cost of a b
On Mon, Aug 20, 2001 at 12:20:22 -0700, NeilFred Picciotto wrote:
> but! "alt" is now the option key instead of the command key...
On my iBook Dual USB with US keyboard, the option key is:
/\
| alt|
| option |
\/
Sound keymap does right thing now ;-)
--
E
On Mon, Aug 20, 2001 at 12:20:22PM -0700, NeilFred Picciotto wrote:
> just made the switch to linux keycodes on my Pismo running woody with
> benh's rsync kernel. i've got the "keyboard_sends_linux_keycodes=1" thing
> in the append line of my yaboot.conf, and i've got "powerpcps2" in my
> XF86Conf
On 1 Elul 5761, Colin Walters wrote:
> But the real solution is to send mail to Apple and ask them to fix
> their hardware.
Sad, because they finally shipped a keyboard for their desktop
machines that handles this correctly (the "new" Apple keyboard which
has been shipping with everything for the
NeilFred Picciotto <[EMAIL PROTECTED]> writes:
> but! "alt" is now the option key instead of the command key...
> searching the archive of this list, i see mentions of this fact,
> including someone saying it's easy to switch that back. but they
> didn't say *how* to do so, only that it's easy..
> On Mon, 20 Aug 2001 13:13:07 -0700, "Gregory P. Keeney" <[EMAIL
> PROTECTED]> said:
g> Sadly, this nasty business of the Caps-Lock key is done in the
g> hardware on Powerbooks. This is causes me incredible frustration with
g> my TiBook (especially after a long session in emacs...). I ha
"Gregory P. Keeney" <[EMAIL PROTECTED]> writes:
> Sadly, this nasty business of the Caps-Lock key is done in the
> hardware on Powerbooks. This is causes me incredible frustration
> with my TiBook (especially after a long session in emacs...).
Yeah, I agree completely. One thing that has made i
NeilFred Picciotto wrote:
> but! "alt" is now the option key instead of the command key...
Try an Apple USB keymap in console. In X, you'll have to use xmodmap(1x).
> searching the archive of this list, i see mentions of this fact, including
> someone saying it's easy to switch that back. but
"Colin Walters" <[EMAIL PROTECTED]> writes:
> NeilFred Picciotto <[EMAIL PROTECTED]> writes:
>
> > oh, and on the subject of the keyboard, is it still the case that
> > there's no way to make Pismo's caps-lock key be control?
>
> Yep, I believe this is because they key press generates one hard
Sadly, this nasty business of the Caps-Lock key is done in the hardware
on Powerbooks. This is causes me incredible frustration with my TiBook
(especially after a long session in emacs...). I have been looking into
a hardware solution (e.g., run a small wire from the control key to the
caps loc
NeilFred Picciotto <[EMAIL PROTECTED]> writes:
> oh, and on the subject of the keyboard, is it still the case that
> there's no way to make Pismo's caps-lock key be control?
Yep, I believe this is because they key press generates one hardware
interrupt, but the key-up never generates an interru
37 matches
Mail list logo
