All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir A. Gurevich <vag@paulidav.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Microcode patches for mpc8xx
Date: Sat, 21 May 2005 22:55:53 -0700	[thread overview]
Message-ID: <42901EE9.4090209@paulidav.org> (raw)

Hello,

I have a couple of questions about RAM microcode patches for MPC8xx CPUs:

   1. What is EXACTLY the patch in cpu/mpc8xx/upatch.c. Specifically,
      which CPU(s) it is applicable to? I looked at a couple of recent
      patches available at Freescale website and none of them resembles
      the stuff in upatch.c
   2. My impression is that different CPUs need different patches. I can
      at least see patches for MPC823, MPC850, MPC860 and MPC862. That
      means that we probably need to check not only CFG_*_UCODE_PATCH,
      but also the corresponding CONFIG_ variable for the CPU. I am
      about to add the appropriate patch for my board, and thus I have
      to #ifdef the older one and I'd better do it right.
   3. I noticed that there is special handling for SPI and I2C, but how
      about SMC? I use SCC3 in the ethernet mode and SMC1 as a console
      and definitely have a problem. (A simple change to scc.c seems to
      have fixed the problem for now, but I'd like to have a cleaner
      solution).
   4. Finally, what is the assumption about Linux. Is it supposed to
      reset the CP and reload the patches?

Thanks,
Vladimir

             reply	other threads:[~2005-05-22  5:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-22  5:55 Vladimir A. Gurevich [this message]
2005-05-22  8:38 ` [U-Boot-Users] Microcode patches for mpc8xx Wolfgang Denk
2005-05-22 17:14   ` Thomas Lange
2005-05-22 20:02     ` Wolfgang Denk
2005-05-22 18:02   ` Dan Malek
2005-05-22 20:06     ` Wolfgang Denk
2005-05-23  7:14   ` Vladimir A. Gurevich
2005-05-23  8:28     ` Wolfgang Denk
2005-05-23 13:46       ` Vladimir A. Gurevich
2005-05-23 20:30         ` 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=42901EE9.4090209@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.