linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <jason@openinformatics.com>
Cc: Ethan Blanton <eblanton@cs.ohiou.edu>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Shift keycodes on the iBook
Date: Tue, 3 Sep 2002 22:15:27 +0200	[thread overview]
Message-ID: <20020903201527.3753@192.168.4.1> (raw)
In-Reply-To: <87znuzksx9.fsf@openinformatics.com>


>> >Is this a hardware limitation, or just a limitation of the current
>> >maps?  If it is the latter, can it be easily fixed?  I'm willing to
>> >provide whatever information is necessary if the problem is just that
>> >the appropriate developer needs information about the iBook keyboard.
>>
>> AFAIK, it's a HW limitation (or at least a limitation of the PMU's
>> firmware), there is no workaround I know about.
>
>The interesting thing is that was what was believed for years about
>the locking capslock key as well...

The locking capslock is in HW as well, there is a hack to turn capslock
into some different key, but it's really a hack.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2002-09-03 20:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-31  5:56 Shift keycodes on the iBook Ethan Blanton
2002-09-02 17:28 ` Benjamin Herrenschmidt
2002-09-03 15:13   ` Jason E. Stewart
2002-09-03 19:21     ` Michel Lanners
2002-09-03 20:17       ` Benjamin Herrenschmidt
2002-09-05  6:03         ` Michel Lanners
2002-09-05  8:15           ` Benjamin Herrenschmidt
2002-09-05 23:39           ` Segher Boessenkool
2002-09-03 20:15     ` Benjamin Herrenschmidt [this message]

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=20020903201527.3753@192.168.4.1 \
    --to=benh@kernel.crashing.org \
    --cc=eblanton@cs.ohiou.edu \
    --cc=jason@openinformatics.com \
    --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).