From: "Stephan Linke" <Stephan.Linke@epygi.de>
To: <wd@denx.de>
Cc: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: problems running I2C and/or SPI on 857 board
Date: Tue, 26 Mar 2002 11:03:47 +0100 [thread overview]
Message-ID: <FCEAKDJJAPHPLJFINDAJEENDCDAA.Stephan.Linke@epygi.de> (raw)
In-Reply-To: <20020325131107.8D3B6109F3@denx.denx.de>
At the moment all my tries are based on the existing drivers in PPCBOOT.
Using no microcode patch, and DPRAM allocation.
DPRAM allocation pointed out a bug so I guess it's not that well tested yet
:( .
Trying fixed DPRAM offsets and microcode now...
Thanks, Stephan
> -----Original Message-----
> From: wd@denx.de [mailto:wd@denx.de]
> Sent: Montag, 25. März 2002 14:11
> To: Stephan Linke
> Cc: Linuxppc-Embedded
> Subject: Re: problems running I2C and/or SPI on 857 board
>
>
> In message <FCEAKDJJAPHPLJFINDAJCEMMCDAA.Stephan.Linke@epygi.de>
> you wrote:
> >
> > I'm trying to get I2C and/or SPI running on a 857 board.
> Register settings
> > and BDs look good. But when the start command is issued nearly nothing
> > happens as if there would be no clock.
>
> I guess your implementation is basedon existing code? Which one?
> [Hint: we have I2C running on a couple of systems...]
>
> > Is there anyone who has an idea?
>
> Start from some code that is known to work?
>
> Wolfgang Denk
>
> --
> Software Engineering: Embedded and Realtime Systems, Embedded Linux
> Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
> The existence of god implies a violation of causality.
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-26 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 12:59 problems running I2C and/or SPI on 857 board Stephan Linke
2002-03-25 13:11 ` Wolfgang Denk
2002-03-26 10:03 ` Stephan Linke [this message]
2002-03-26 10:29 ` Wolfgang Denk
[not found] <FCEAKDJJAPHPLJFINDAJIENECDAA.Stephan.Linke@epygi.de>
2002-03-26 12:25 ` Wolfgang Denk
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=FCEAKDJJAPHPLJFINDAJEENDCDAA.Stephan.Linke@epygi.de \
--to=stephan.linke@epygi.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@denx.de \
/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.