From: Brad Boyer <flar@allandria.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Nico Schottelius <nico-linux-ppc@schottelius.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Heartbeat LED for iBook
Date: Fri, 18 Feb 2005 09:58:22 -0800 [thread overview]
Message-ID: <20050218175822.GA30616@pants.nu> (raw)
In-Reply-To: <629f63c4608b762de8bf6f962b6180ef@kernel.crashing.org>
On Fri, Feb 18, 2005 at 02:00:32PM +0100, Segher Boessenkool wrote:
> There is no manual. You can look at some Darwin source code,
> I guess, or there is some code in Linux to do this as well, IIRC.
There is some minimal documentation available. Some Apple docs:
ADB-The Untold Story: Space Aliens Ate My Mouse
http://developer.apple.com/technotes/hw/hw_01.html
Inside Macintosh: Devices / Chapter 5 - ADB Manager
http://developer.apple.com/documentation/mac/Devices/Devices-203.html
These will tell you the basic design of ADB as well as the packet
formats and information about keyboards and mice.
Note that these document ADB in a generic sense, so nothing PMU
specific is in them. Apple has been very reluctant to document
the PMU and it's functions.
Brad Boyer
flar@allandria.com
next prev parent reply other threads:[~2005-02-18 18:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 9:42 [PATCH] Heartbeat LED for iBook Joerg Dorchain
2005-01-26 11:35 ` Nico Schottelius
2005-01-26 13:42 ` Benjamin Herrenschmidt
2005-02-08 7:54 ` Nico Schottelius
2005-02-14 13:14 ` Segher Boessenkool
2005-02-18 11:13 ` Nico Schottelius
2005-02-18 12:11 ` Segher Boessenkool
2005-02-18 12:20 ` Nico Schottelius
2005-02-18 13:00 ` Segher Boessenkool
2005-02-18 17:58 ` Brad Boyer [this message]
2005-02-18 18:10 ` Segher Boessenkool
2005-02-19 19:17 ` Brad Boyer
2005-01-27 16:36 ` Joerg Dorchain
2005-02-18 14:57 ` ibook-led (finished) (was: [PATCH] Heartbeat LED for iBook) Nico Schottelius
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=20050218175822.GA30616@pants.nu \
--to=flar@allandria.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=nico-linux-ppc@schottelius.org \
--cc=segher@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.