From: Thomas Lange <thomas@corelatus.se>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Microcode patches for mpc8xx
Date: Sun, 22 May 2005 19:14:16 +0200 [thread overview]
Message-ID: <4290BDE8.8020102@corelatus.se> (raw)
In-Reply-To: <20050522083835.856FCC1512@atlas.denx.de>
Wolfgang Denk wrote:
>In message <42901EE9.4090209@paulidav.org> you wrote:
>
>
>>I have a couple of questions about RAM microcode patches for MPC8xx CPUs:
>>
>>
>
>This is a neglected area in U-Boot; usually U-Boot needs little
>resources and uCode patches are needed at all. actually none of the
>existing configurations seems to use the code.
>
>
>
>> 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
>>
>>
>
>The existing code was added to PPCBoot as part of the GTH board
>support on 2001/09/11, and never changed since. Interesting ewnough,
>the GTH board does not use the code - nor does any other board. The
>README says what it is intended to do. The uCode itself is probaly
>obsolete by now as it is at least as old as the code in the CVS.
>
>
I checked the patch I sent for the GTH board.
upatch.c was not included.
You probably just happened to add upatch.c from somewhere
else at the same time.
We have never used microcode patches for GTH.
CVS log:
--------------------------------------------------------------------------
Add cpu/mpc8xx/upatch.c which I forgot to check in.
Major modification for GTH board;
added CONFIG_RESET_TO_RETRY configuration option
--------------------------------------------------------------------------
Regards,
/Thomas
next prev parent reply other threads:[~2005-05-22 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-22 5:55 [U-Boot-Users] Microcode patches for mpc8xx Vladimir A. Gurevich
2005-05-22 8:38 ` Wolfgang Denk
2005-05-22 17:14 ` Thomas Lange [this message]
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=4290BDE8.8020102@corelatus.se \
--to=thomas@corelatus.se \
--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.