From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc/t104xrdb, t1040qds : Update FMAN microcode NOR address
Date: Wed, 5 Feb 2014 12:00:41 -0800 [thread overview]
Message-ID: <52F29869.2030105@freescale.com> (raw)
In-Reply-To: <1391580771-12981-1-git-send-email-Priyanka.Jain@freescale.com>
On 02/04/2014 10:12 PM, Priyanka Jain wrote:
> FMAN microcode image address range on NOR flash changed from
> (0xeff00000 to 0xebf1ffff) to (0xeff10000 to 0xeff1ffff)
>
> The change has been done
> - to support FMAN microcode flashing via promjet mechanism as
> promjet uses address based on offsets. Based on this
> address of FMAN microcode flash on promjet flash should be 0x0
> But 0x0 offset is already use for rcw on promjet flash.
> To take care of this limitation FMAN microcode address has been
> changed. Now, FMAN microcode address on promjet flash is 0x10000
>
> - FMAN microcode is of size 64KB so it will fit into
> 0xeff10000 to 0xeff1ffff.
>
NACK.
The tool is not broken. I have made a configuration to use PROMJET to download
all images successfully.
York
prev parent reply other threads:[~2014-02-05 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 6:12 [U-Boot] [PATCH] powerpc/t104xrdb, t1040qds : Update FMAN microcode NOR address Priyanka Jain
2014-02-05 20:00 ` York Sun [this message]
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=52F29869.2030105@freescale.com \
--to=yorksun@freescale.com \
--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