All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephan Linke" <Stephan.Linke@epygi.de>
To: <bart@ardistech.com>, <joakim.tjernlund@lumentis.se>
Cc: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: 8xx i2c refers to unspecified chip errata
Date: Fri, 11 Oct 2002 14:31:37 +0200	[thread overview]
Message-ID: <FCEAKDJJAPHPLJFINDAJMENOCJAA.Stephan.Linke@epygi.de> (raw)
In-Reply-To: <3DA6C0C3.A34624CA@ardistech.com>


Hi Bart and Joakim,

Well. No, I'm not shure. But I see what you mean Bart. :) I'll see what
happens now.

And I have a question to Joakim. In your code you wrote (cpm_iic_init):

	i2c->i2c_i2mod = 0x80; /* Filter clock */

I think this is not what you intended. I didn't find that bit (bit 0) in my
862 manual. But there's the FLT flag (bit 4) that matches your comment. So I
think It should be:

	i2c->i2c_i2mod = 0x08; /* Filter clock */

Thanks, Stephan

> -----Original Message-----
> From: bart [mailto:bart]On Behalf Of bart@ardistech.com
> Sent: Freitag, 11. Oktober 2002 14:15
> To: Stephan Linke
> Cc: Linuxppc-Embedded
> Subject: Re: 8xx i2c refers to unspecified chip errata
>
>
> Hi Stephan,
>
> > I had a look at you code. Some of the changes I already did in
> my code. :)
> > I couldn't find any thing that looks like it's fixing the memory problem
> > that you mentioned. I'm looking for a memory problem by my self
> and I wonder
> > what you might have figured out.
> >
> You're sure it not a cache invalidate problem you're looking at?
>
> Cheers,
> 	Bart
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-10-11 12:31 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09 20:14 8xx i2c refers to unspecified chip errata Barker Michael-r43496
2002-10-10 10:35 ` Joakim Tjernlund
2002-10-10 16:18   ` Dan Malek
2002-10-10 16:35     ` Dr. Craig Hollabaugh
2002-10-11  7:28     ` Joakim Tjernlund
2002-10-11  7:50       ` bart
2002-10-11  9:12         ` Joakim Tjernlund
2002-10-11  9:56           ` bart
2002-10-11 12:02           ` Stephan Linke
2002-10-11 12:14             ` bart
2002-10-11 12:31               ` Stephan Linke [this message]
2002-10-11 12:46                 ` Joakim Tjernlund
2002-10-11 12:44             ` Joakim Tjernlund
2002-10-11 12:55               ` bart
2002-10-11 13:10                 ` Joakim Tjernlund
2002-10-15 16:57           ` Tom Rini
2002-10-22  9:15             ` Joakim Tjernlund
2005-05-19  6:23               ` Joakim Tjernlund
2002-10-24 16:10               ` Tom Rini
2005-05-19  6:23                 ` Tom Rini
2002-10-24 18:21                 ` Joakim Tjernlund
2005-05-19  6:23                   ` Joakim Tjernlund
2002-11-01 11:01                   ` Joakim Tjernlund
2002-11-01 19:19                     ` Tom Rini
2002-11-17 20:51                   ` Mark D. Studebaker
2005-05-19  6:23                     ` Mark D. Studebaker
2002-11-17 21:44                     ` Joakim Tjernlund
2002-11-18 14:10                       ` Tom Rini
2005-05-19  6:23                         ` Tom Rini
2002-11-18 19:04                         ` Mark D. Studebaker
2005-05-19  6:23                           ` Mark D. Studebaker
2002-11-18 19:24                           ` Joakim Tjernlund
2005-05-19  6:23                             ` Joakim Tjernlund
2002-11-18 19:31                             ` Tom Rini
2005-05-19  6:23                               ` Tom Rini
2002-11-18 19:42                             ` Jean Delvare
2005-05-19  6:23                               ` Jean Delvare
2002-11-18 19:46                               ` Tom Rini
2005-05-19  6:23                                 ` Tom Rini
2005-05-19  6:23               ` Joakim Tjernlund
2005-05-19  6:23               ` Tom Rini
2005-05-19  6:23               ` Mark D. Studebaker
  -- strict thread matches above, loose matches on Subject: below --
2002-10-10 17:01 Barker Michael-r43496

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=FCEAKDJJAPHPLJFINDAJMENOCJAA.Stephan.Linke@epygi.de \
    --to=stephan.linke@epygi.de \
    --cc=bart@ardistech.com \
    --cc=joakim.tjernlund@lumentis.se \
    --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 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.