From: Segher Boessenkool <segher@koffie.nl>
To: mlan@cpu.lu
Cc: benh@kernel.crashing.org, jason@openinformatics.com,
eblanton@cs.ohiou.edu, linuxppc-dev@lists.linuxppc.org
Subject: Re: Shift keycodes on the iBook
Date: Fri, 06 Sep 2002 01:39:38 +0200 [thread overview]
Message-ID: <3D77EE69.8F0A942A@koffie.nl> (raw)
In-Reply-To: E17mpjY-0000DD-00@piglet.grunz.lu
Michel Lanners wrote:
>
> On 3 Sep, this message from Benjamin Herrenschmidt echoed through cyberspace:
> >>> The interesting thing is that was what was believed for years about
> >>> the locking capslock key as well...
> >>
> >>Ah, but that depends on the specific model of keyboard. At least some of
> >>Apple's ADB keyboards _do_ indead have a mechanical capslock.
> >>
> >>I don't know for USB keyboards, but obviously the PowerBook keyboards
> >>have a regular (non-locking) key as capslock. Whether the lock is done
> >>in the ADB driver or in the keyboard controller, I don't know...
> >
> > Actually, the lock itself isn't, but the keycode sent by the PMU behave
> > like a HW lock (and the LED is driven that way too).
> >
> > In both cases, there may be ways to instruct the PMU to behave differently
> > but I don't know about them.
>
> Anybody up for sucking the PMU firmware out of the little beast and
> reverse-engineering it? Might be a fun project :-))
There's a little program for doing the "sucking" part of this available on
my page at penguinppc.org; Apple was nice enough to include some commands
in the CPU<->PMU interface language for reading any part of the PMU memory.
The PMU is a Mitsubishi MCU; afaik, it's a M30624FGMGP, which is a member of the
M16C/62 family. Mitsubishi's documentation pages have been much improved
lately; you can actually find the pdf's you need now :)
Reverse engineering something as big as this is quite a bit of work, though;
especially if you don't know which of the 88 i/o lines on the chip are
connected where ;)
Cheers,
Segher
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-09-05 23:39 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 [this message]
2002-09-03 20:15 ` Benjamin Herrenschmidt
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=3D77EE69.8F0A942A@koffie.nl \
--to=segher@koffie.nl \
--cc=benh@kernel.crashing.org \
--cc=eblanton@cs.ohiou.edu \
--cc=jason@openinformatics.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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).