All of lore.kernel.org
 help / color / mirror / Atom feed
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 13:51:05 -0700	[thread overview]
Message-ID: <44318AB9.2070209@paulidav.org> (raw)
In-Reply-To: <20060403201825.0EE49353C10@atlas.denx.de>

Hello Wolfgang,

Wolfgang Denk wrote:

>Please don't call empty functions if you can avoid it. It adds to the
>code size, and makes understanding the code much harder.
>  
>
No problem. I can easily #ifdef the call to UcodeCopy rather than the 
body itself, since it's predicated on the need for the patch. But 
cpm_load_patch() should still has to be called unconditionally and if no 
relocation is required at all, it will be empty. This is a small price 
to pay for the ability to handle different cases automatically without 
the need to worry about whether a microcode patch is actually needed 
(because depending on the CPU and actual settings there might be no 
relocation or relocation with or without a patch).

I believe that we need some centralized code, because certain 
combination of patches/devices do affect other devices (that's the 
nature of microcode patches provided my Motorola) that might not really 
be used by a certain board, but still have to be programmed correctly. 
For example, the combined I2C/SPI/SMC relocation patch requires correct 
rpbase settings on both SMC1 and SMC2 regardless of whether you plan to 
use them or not.

Unfortunately, all these dependancies are a little difficult to express 
via C preprocessor (at least not without making the configuration much 
more complex and error prone). You can see that  the code in 
mpc8xx_upatch.h got pretty complex on its own.

Regards,
Vladimir

  reply	other threads:[~2006-04-03 20:51 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
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 [this message]
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=44318AB9.2070209@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 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.