From: Vladimir Gurevich <vag@paulidav.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] SPI relocation fix
Date: Mon, 03 Apr 2006 10:37:43 -0700 [thread overview]
Message-ID: <44315D67.9050107@paulidav.org> (raw)
In-Reply-To: <4dd15d180604031032w7a2624e8ycf467e69bd91e950@mail.gmail.com>
Hello David,
David Ho wrote:
>MPC852T skips the microcode patch does it not?
>
>
Well, it depends on the actual combination of the parameters, but the
idea was that cpm_load_patch() will be called nonetheless and will
program the rpbase whether or not the actual patch is required.
>For the case where you intentionally want to move SPI to elsewhere
>(using ENET on SCC2), I will have to define CFG_SPI_DPMEM_OFFSET.
>since CFG_SPI_DPMEM_OFFSET is not assigned to spi->rpbase for MPC852T
>( microcode patch is skipped), SPI is not relocated using your patch.
>
>
That's exactly the case I describe above. Could you make sure
cpm_load_patch() is being called?
Happy hacking,
Vladimir
next prev parent reply other threads:[~2006-04-03 17:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 21:07 [U-Boot-Users] [PATCH] SPI relocation fix David Ho
2006-03-30 23:05 ` Wolfgang Denk
2006-03-31 3:14 ` Vladimir Gurevich
2006-03-31 15:22 ` David Ho
2006-03-31 16:29 ` Wolfgang Denk
2006-03-31 21:44 ` David Ho
2006-03-31 21:52 ` Vladimir Gurevich
2006-04-03 15:09 ` David Ho
2006-04-03 16:53 ` David Ho
2006-04-03 17:18 ` Vladimir Gurevich
2006-04-03 17:32 ` David Ho
2006-04-03 17:37 ` Vladimir Gurevich [this message]
2006-04-03 18:12 ` David Ho
2006-04-03 18:26 ` Vladimir Gurevich
2006-04-03 19:00 ` David Ho
2006-04-03 19:51 ` Vladimir Gurevich
2006-04-03 19:59 ` David Ho
2006-04-03 20:18 ` Wolfgang Denk
2006-04-03 20:51 ` Vladimir Gurevich
2006-04-03 21:36 ` Wolfgang Denk
2006-04-03 21:51 ` Vladimir Gurevich
2006-04-03 20:15 ` Wolfgang Denk
2006-03-31 3:12 ` Vladimir Gurevich
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=44315D67.9050107@paulidav.org \
--to=vag@paulidav.org \
--cc=u-boot@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox