From: Michel Lanners <mlan@cpu.lu>
To: Geert.Uytterhoeven@cs.kuleuven.ac.be
Cc: bh40@calva.net, frodol@dds.nl, linuxppc-dev@lists.linuxppc.org
Subject: Re: Support for Hydra i2c
Date: Mon, 10 May 1999 21:43:21 +0200 (CEST) [thread overview]
Message-ID: <199905101943.VAA00322@piglet.cpu.lu> (raw)
In-Reply-To: <Pine.LNX.4.10.9905101046110.10789-100000@mercator.cs.kuleuven.ac.be>
Hi all,
On 10 May, this message from Geert Uytterhoeven echoed through cyberspace:
[snip]
>> > 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.
On the other hand, you I2C gurus mihgt know that, but the R/W bit on the
I2C bus is actually the lsb of the address; i.e address a device with
an even address, and it expects to recive some data; address it with an
odd address, and the device will write data to the bus.
>> > 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
>> ;-).
>
> Really? Since i2c devices need to identify on the bus, you must be able to read
> something from them.
I did some experimentation on the cuda I2C bus while searching for the
PlanB I2C device. I scanned a whole range of I2C addresses, both read
and write, but didn't find anything apart from RADACAL.
> Are there OF methods for the i2c bus on those Macs? My CHRP box has them under
> /pci/mac-io@2/misc@0/iic/.
I'll check in OF on the next reboot ;-)
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. ]]
next prev parent reply other threads:[~1999-05-10 19:43 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
1999-05-10 8:48 ` Geert Uytterhoeven
1999-05-10 19:43 ` Michel Lanners [this message]
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=199905101943.VAA00322@piglet.cpu.lu \
--to=mlan@cpu.lu \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--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).