From: Armin Kuster <akuster@mvista•com>
To: andrew may <acmay@acmay•homeip.net>
Cc: linuxppc-embedded <linuxppc-embedded@lists•linuxppc.org>
Subject: Re: Status on 405GP i2c driver
Date: Tue, 23 Apr 2002 10:54:33 -0700 [thread overview]
Message-ID: <3CC59FD9.1090606@mvista.com> (raw)
In-Reply-To: 20020422141601.B16319@ecam.san.rr.com
andrew may wrote:
> It looks like this question was lasted asked around Jan/Feb, but
> I have not seen an update on the status recently.
>
> I have looked at the i2c-2.6.3 and I am reluctant to spend any
> time working on it since it needs to go through some formating
> changes to get rid of the C++ style comments. I don't want to
> deal with a merge issues of doing a style change unless I know
> it will go in.
>
> I am also more inclined to use the actual transfer function
> I have worked with in the PPCBoot rather than the functions
> in the linux i2c code.
>
then I recommend using ppcboot.
--armin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-23 17:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 21:16 Status on 405GP i2c driver andrew may
2002-04-23 17:54 ` Armin Kuster [this message]
2002-04-23 18:15 ` andrew may
2002-04-23 18:35 ` Armin Kuster
2002-04-23 19:14 ` andrew may
2002-04-23 23:05 ` Matt Porter
[not found] ` <20020423182301.B19665@ecam.san.rr.com>
2002-04-24 1:38 ` andrew may
2002-04-24 1:39 ` andrew may
2002-04-24 1:39 ` Status on 405GP i2c driver [PATCH] 2nd andrew may
2002-04-24 1:46 ` Status on 405GP i2c driver [PATCH] 3rd andrew may
2002-04-24 1:46 ` Status on 405GP i2c driver [PATCH] 4th andrew may
2002-04-24 1:47 ` Status on 405GP i2c driver [PATCH] last andrew may
2002-04-24 14:47 ` Status on 405GP i2c driver Matt Porter
2002-04-24 15:39 ` andrew may
2002-04-24 18:21 ` Matt Porter
2002-04-24 18:23 ` Armin
2002-04-25 8:04 ` file missing ? (was :Re: Status on 405GP i2c driver) "David Müller (ELSOFT AG)"
2002-04-25 14:36 ` Matt Porter
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=3CC59FD9.1090606@mvista.com \
--to=akuster@mvista$(echo .)com \
--cc=acmay@acmay$(echo .)homeip.net \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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