From: Armin <akuster@pacbell.net>
To: andrew may <acmay@acmay.homeip.net>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: [PATCH] IBM ocp I2C
Date: Tue, 23 Apr 2002 21:36:37 -0700 [thread overview]
Message-ID: <3CC63655.1080108@pacbell.net> (raw)
In-Reply-To: 20020423200151.H20394@ecam.san.rr.com
andrew may wrote:
> On Tue, Apr 23, 2002 at 08:01:27PM -0700, andrew may wrote:
>
>>Would anyone be heartbroken if "struct i2c_algo_iic_data" went
>>away completely?
>>
>>In this patch I dump getown and getclock because they aren't
>>used and I am sure there is a better way to do things.
>>
>>Also calculate the I2C div value from the clock rate. I am
>>not sure if that will work on all 4xx types but it does the
>>right thing for my 405's.
>>
>>I also fixed a few C++ style comments.
>>
>>
> and the patch
>
Andrew,
could you provide a single patch that would be applied on top of the
*devel. I appreciate the changes and I will get back to you in on
"struct i2c_algo_iic_data". I will need to try the div changes on the
redwoods (stb03 & stb04 cpus).
armin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-24 4:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 3:01 [PATCH] IBM ocp I2C andrew may
2002-04-24 3:01 ` andrew may
2002-04-24 4:36 ` Armin [this message]
2002-04-24 15:18 ` andrew may
2002-04-24 18:26 ` andrew may
2002-04-24 18:45 ` Armin
2002-05-01 17:05 ` Armin
2002-04-26 20:48 ` Armin
2002-04-27 3:35 ` andrew may
2002-04-28 4:09 ` Armin
-- strict thread matches above, loose matches on Subject: below --
2002-04-29 21:40 [PATCH]IBM OCP I2C andrew may
[not found] ` <3CCDE113.5000700@pacbell.net>
2002-04-30 0:05 ` andrew may
2002-05-07 18:33 andrew may
2002-05-07 19:54 ` andrew may
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=3CC63655.1080108@pacbell.net \
--to=akuster@pacbell.net \
--cc=acmay@acmay.homeip.net \
--cc=linuxppc-embedded@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).