From: Frodo Looijaard <frodol@dds.nl>
To: Geert.Uytterhoeven@cs.kuleuven.ac.be (Geert Uytterhoeven)
Cc: lm78@stimpy.netroedge.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: Support for Hydra i2c
Date: Wed, 28 Apr 1999 16:09:05 +0200 (CEST) [thread overview]
Message-ID: <199904281409.QAA01267@arda.frodo.local> (raw)
In-Reply-To: <Pine.LNX.4.10.9904281104050.12292-300000@mercator.cs.kuleuven.ac.be> from "Geert Uytterhoeven" at Apr 28, 99 11:20:36 am
Geert Uytterhoeven wrote:
>
> The attached patch adds support for the i2c interface on the Apple `Hydra' Mac
> I/O, found on CHRP PPC motherboards. The patch is relative to the anon CVS
> version of yesterday evening.
Congratulations! You are the first to add support for a non-Intel
architecture. I am very excited by your contribution! To be honest, I did
not even know the PPC architecture had an I2C interface. Very nice indeed!
I will merge your code in later today, and if necessary I will send you some
feedback on it. You may want CVS write access; it will make maintaining
everything a lot easier for all of us. Phil is the one who needs to make
an account for you; he also manages the mailing list, which might be
interesting to you too. Phil, can you contact Geert for this?
> - prog/dump/isadump.c
>
> o glibc 2.1 doesn't have <sys/perm.h>
> o make it compile on PPC (ISA I/O is memory mapped, but it doesn't work
> anyway because different types of PPC boxes have ISA I/O space at
> different addresses :-(
> o fix a typo (datareg -> addrreg)
This was a very Intel-centered program :=). On Intel PCs, we often have
some hardware sensors attached to the ISA bus. We will have to find out
whether this is the case with PPCs too.
> The only things on my i2c bus are 2 SPD EEPROMS. I attached the output of the
> decode-dimms Perl script. It looks a bit weird though.
Again, you need to talk to Phil. He wrote the EEPROM decode routines.
I am very curious whether anybody on the PPC has hardware monitoring sensors
attached. People, the sensors-detect script should work for you, but don't
try to do the ISA probing (you are asked whether you want it or not).
Good luck,
Frodo
--
Frodo Looijaard <frodol@dds.nl> PGP key and more: http://huizen.dds.nl/~frodol
At my homepage you will also find a guide for installing glibc under Linux.
New: Linux hardware monitoring kernel modules (LM78/79/80, Winbond etc.)
[[ 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-04-28 14:09 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 [this message]
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
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=199904281409.QAA01267@arda.frodo.local \
--to=frodol@dds.nl \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=lm78@stimpy.netroedge.com \
/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.