linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: bh40@calva.net
Cc: frodol@dds.nl, linuxppc-dev@lists.linuxppc.org
Subject: Re: Support for Hydra i2c
Date: Fri, 30 Apr 1999 22:05:59 +0200 (CEST)	[thread overview]
Message-ID: <199904302005.WAA00302@piglet.cpu.lu> (raw)
In-Reply-To: <19990428192735.002083@mail.mipsys.com>


On  28 Apr, this message from Benjamin Herrenschmidt echoed through cyberspace:
[snip]
> On non-CHRP PowerMacs, there is at least one I2C bus (maybe more) driven
> by Cuda. It's used for things like planB video input,

Not that it matters much, but for correctness: the Apple planb ASIC
includes its own I2C bus interface, controlling the I2C bus on which
the video decoder chip is connected.

By the way, this I2C interface is quite simple: write a (sub)address,
write a value, and off it goes. However, it seems to be hardcoded to
access only the SAA7196 video decoder, and reading that chip is done
with a different interface.

Which gives me another thought, completely unrelated to the subject of
this mail: I'm wondering whether the video output chips in the 8x00
also have I2C, and if yes, how they are accessed...

> and maybe some more stuffs.

The only device on this I2C bus in the PCI Macs that I know off is the
RADACAL RAMDAC/CLUT (used at least with the control chip), which gets
its timebase factors via I2C.

> Unfortunately, I think we only know how to write to the i2c bus.

Yes.

> More hacking needed before we can implement this one too.

One problem might be that there is as yet no readable device on the bus
;-).

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-04-30 20:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-28  9:20 Support for Hydra i2c Geert Uytterhoeven
1999-04-28 14:09 ` Frodo Looijaard
1999-04-28 17:27   ` Benjamin Herrenschmidt
1999-04-30 20:05     ` Michel Lanners [this message]
1999-05-10  8:48       ` Geert Uytterhoeven
1999-05-10 19:43         ` Michel Lanners
1999-04-30  9:42   ` Geert Uytterhoeven
1999-04-29  7:28 ` Gabriel Paubert

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=199904302005.WAA00302@piglet.cpu.lu \
    --to=mlan@cpu.lu \
    --cc=bh40@calva.net \
    --cc=frodol@dds.nl \
    --cc=linuxppc-dev@lists.linuxppc.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 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).