From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Harald Welte <laforge@gnumonks.org>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH] ugly hack to make therm_pm72 work on XServe G5
Date: Fri, 06 Aug 2004 18:09:14 +1000 [thread overview]
Message-ID: <1091779753.9271.220.camel@gaston> (raw)
In-Reply-To: <20040806080406.GB11638@sunbeam2>
On Fri, 2004-08-06 at 18:04, Harald Welte wrote:
> I actually forgot that small userspace program ;)
>
> It is a total ripoff of the kernel driver and was implemented because
> it's easier to play with i2c from userspace during development.
>
> benh: Any reason why you implemented your own byte+word read/write
> routines? Apparently the i2c_smbus routines work quite fine, even from
> userspace...
I don't remember the exact reason, I had some issues, either with the
sensors or the FCU, or maybe it was for mimmicing OF code...
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-08-06 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 11:43 [PATCH] ugly hack to make therm_pm72 work on XServe G5 Harald Welte
2004-08-06 8:04 ` Harald Welte
2004-08-06 8:09 ` Benjamin Herrenschmidt [this message]
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=1091779753.9271.220.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=laforge@gnumonks.org \
--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).