linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "D.J. Barrow" <barrow_dj@yahoo.com>
To: 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, 8 Dec 2000 09:19:51 -0800 (PST)	[thread overview]
Message-ID: <20001208171951.96997.qmail@web10407.mail.yahoo.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1798 bytes --]


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.


It is also commonly used in embedded stuff, I wrote a
driver for apples tv tuner card on a performa 630 when
I was working for them.

I didn't talk i2c directly but talked to the cuda
manager on the mac os, however, I made a fake i2c bus
via 2 pins on the paralell port of a pc.

If you want to know more about this look for specs on
the cuda chip if you can find them. However I suspect
a
few things have changed since I did my stuff since
Apple loves moving asics around to keep chip designers
mentally masturbating :-).

--- Christof Petig <christof.petig@wtal.de> wrote:
>
> Iain Sandoe wrote:
>
> > duh! just read the whole thread...
> >
> > [...]
> > > Christof could always resort to petitioning
> Apple to release the specs, or
> > > digging though Darwin source code to discover
> the secret.
> >
> > the chip specs are freely available:
> >
> >
>
http://www.micronas.com/documentation/data_sheet/dac3550a_1ds.pdf
> >
> > Ben H might know something about driving the iBook
> i2c busses - I think that
> > they are the new Apple "cereal" style which are
> also present on the PCI host
> > bridges... but not quite sure.
>
> The link is dead, but
>
http://www.micronas.com/products/documentation/consumer/dac3550a/index.php
> works for me well.
>
> Thank you very much for this information!
>
> Christof
>
>
>


=====
D.J. Barrow Linux for S/390 kernel developer
eMail: djbarrow@de.ibm.com,barrow_dj@yahoo.com
Phone: +49-(0)7031-16-2583
IBM Germany Lab, Schönaicherstr. 220, 71032 Böblingen


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

             reply	other threads:[~2000-12-08 17:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-08 17:19 D.J. Barrow [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-08 19:34 AW: Sound on an iBook? Iain Sandoe
2000-12-12 19:01 ` Michel Lanners
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=20001208171951.96997.qmail@web10407.mail.yahoo.com \
    --to=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).