From: "Iain Sandoe" <iain@sandoe.co.uk>
To: "D.J. Barrow" <barrow_dj@yahoo.com>,
"linuxppc-dev" <linuxppc-dev@lists.linuxppc.org>
Cc: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
"Halfmann, Klaus" <khalfmann@libra.de>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: AW: Sound on an iBook?
Date: Fri, 08 Dec 2000 19:34:47 +0000 [thread overview]
Message-ID: <200012081959.TAA30962@hyperion.valhalla.net> (raw)
D.J. Barrow wrote:
> No I2C is as old as the hills, I2C is a philips serial
> bus standard for talking to upto 256 devices on the
> one two wire bus. It is pretty crappy simple & slow &
> philips generally used it to talk to digital tuners on
> radios.
well, there are other versions faster and with bigger address ranges... but
that wasn't my point.
we are all quite familiar with i2c.
the new thing here is the particular Apple hardware, registers etc. used to
implement the bus interface... another set of stuff we may have to deduce
the hard way.
it's not the cuda - the iBook doesn't have a cuda - AFAIK. (PMU, I expect).
and... actually, I think the asics are more there to keep costs down... but
each to his own ;-)
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-12-08 19:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 19:34 Iain Sandoe [this message]
2000-12-12 19:01 ` AW: Sound on an iBook? Michel Lanners
-- strict thread matches above, loose matches on Subject: below --
2000-12-08 17:19 D.J. Barrow
2000-12-08 15:36 Iain Sandoe
2000-12-08 12:05 Iain Sandoe
2000-12-08 15:01 ` Christof Petig
2000-12-08 11:56 Iain Sandoe
2000-12-08 8:38 Halfmann, Klaus
2000-12-08 11:35 ` Michael Schmitz
2000-12-08 12:12 ` Benjamin Herrenschmidt
2000-12-08 14:36 ` Christof Petig
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=200012081959.TAA30962@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=barrow_dj@yahoo.com \
--cc=khalfmann@libra.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
/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).