From: Wolfgang Denk <wd@denx.de>
To: "Stephan Linke" <Stephan.Linke@epygi.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:29:45 +0100 [thread overview]
Message-ID: <20020326102950.BDF16109F3@denx.denx.de> (raw)
In-Reply-To: Your message of "Tue, 26 Mar 2002 11:03:47 +0100." <FCEAKDJJAPHPLJFINDAJEENDCDAA.Stephan.Linke@epygi.de>
In message <FCEAKDJJAPHPLJFINDAJEENDCDAA.Stephan.Linke@epygi.de> you wrote:
>
> At the moment all my tries are based on the existing drivers in PPCBOOT.
Which version of PPCBoot? The official releases (1.1.5) should work
just fine; they do so on several tested systems.
If you're using the top of tree on the CVS server (i. e. the version
which includes the "Grand Unifying I2C interface patch") you may have
to adjust a couple of things; this is not that well tested / working
yet.
> Using no microcode patch, and DPRAM allocation.
I wonder why you use the CPM code at all. I always found it much
easier to use CONFIG_SOFT_I2C ...
> DPRAM allocation pointed out a bug so I guess it's not that well tested yet
> :( .
> Trying fixed DPRAM offsets and microcode now...
Please submit a patch!
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 price of curiosity is a terminal experience.
- Terry Pratchett, _The Dark Side of the Sun_
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-26 10:29 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
2002-03-26 10:29 ` Wolfgang Denk [this message]
[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=20020326102950.BDF16109F3@denx.denx.de \
--to=wd@denx.de \
--cc=Stephan.Linke@epygi.de \
--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).