From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <mlan@cpu.lu>
Cc: <jason@openinformatics.com>, <eblanton@cs.ohiou.edu>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: Shift keycodes on the iBook
Date: Thu, 5 Sep 2002 10:15:19 +0200 [thread overview]
Message-ID: <20020905081519.28373@192.168.4.1> (raw)
In-Reply-To: <E17mpjY-0000DD-00@piglet.grunz.lu>
>Anybody up for sucking the PMU firmware out of the little beast and
>reverse-engineering it? Might be a fun project :-))
Already beeing done, though I'll let the culprit tell about it
himself if he wants to ;)
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-09-05 8: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 [this message]
2002-09-05 23:39 ` Segher Boessenkool
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=20020905081519.28373@192.168.4.1 \
--to=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).