From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] net/fm: check the old and new Fman microcode locations in NOR flash
Date: Thu, 15 Dec 2011 14:09:33 -0600 [thread overview]
Message-ID: <4EEA53FD.7080703@freescale.com> (raw)
In-Reply-To: <4576048A-3994-49B6-AB43-337DF1271370@freescale.com>
Kumar Gala wrote:
> I see no reason for this patch, if you're flashing a new u-boot flash
> the microcode to the new address as well.
This is useful for people who have not moved the microcode. Are we going to ensure that everyone who updates U-Boot will also move their microcode to the new location? We can always revert this patch after everyone has migrated, if that's really necessary.
You know as well as I do that if don't provide backwards compatibility, someone is going to break and won't know why.
> Don't we already have a
> warning if we don't find the ucode at the expected address.
No. The warning just says that microcode is invalid, not that that it's at the wrong address.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-12-15 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 22:34 [U-Boot] [PATCH 1/2] net/fm: check the old and new Fman microcode locations in NOR flash Timur Tabi
2011-12-14 22:34 ` [U-Boot] [PATCH 2/2] powerpc/85xx: move the Fman microcode from ef000000 to eff40000 Timur Tabi
2011-12-15 20:03 ` [U-Boot] [PATCH 1/2] net/fm: check the old and new Fman microcode locations in NOR flash Kumar Gala
2011-12-15 20:09 ` Timur Tabi [this message]
2011-12-15 20:15 ` Kumar Gala
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=4EEA53FD.7080703@freescale.com \
--to=timur@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 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.