From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] ARM: mx6: use common CPU errata config options
Date: Fri, 08 Mar 2013 09:12:31 +0100 [thread overview]
Message-ID: <51399D6F.6060808@denx.de> (raw)
In-Reply-To: <5138E848.30706@wwwdotorg.org>
On 07/03/2013 20:19, Stephen Warren wrote:
> On 03/07/2013 10:24 AM, Stefano Babic wrote:
>> On 26/02/2013 23:28, Stephen Warren wrote:
>>> From: Stephen Warren <swarren@nvidia.com>
>>>
>>> Now that U-Boot has common CONFIG_ options to work around some ARM CPU
>>> errata, enable the relevant options on MX6, and remove the custom
>>> lowlevel_init.S, since it's just duplicated code now.
>>>
>>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>>> ---
>>
>> Hi Stephen,
>>
>> applied to u-boot-imx. It is not effective until Alber apply 1/3, but it
>> does not hurt.
>
> If you do that, then won't the imx6-specific WAR code be removed before
> the generic implementation is added, so that there will be a period
> where the WAR won't be enabled?
You're right - there is a period where it is not enabled. I hope it is
quite short, and I will track this patchset to check when flows into
u-boot-arm.
> I suppose if you send your pull request
> after Albert has merged the generic implementation there won't be an
> issue in u-boot-arm, but until u-boot-imx picks up the latest
> u-boot-arm, the issue will exist there.
Right - there is some "grey zone" when a patchset belongs to different
areas. My supposition (please correct if I am wrong) is that this
patchset is ready to be merged and will not require another iteration,
and I do not want to delay it while expecting something from my side.
When Albert will pick it up the rest, everything will be fine.
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2013-03-08 8:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 22:28 [U-Boot] [PATCH 1/3] ARM: implement some Cortex-A9 errata workarounds Stephen Warren
2013-02-26 22:28 ` [U-Boot] [PATCH 2/3] ARM: tegra: enable some CPU " Stephen Warren
2013-03-15 5:59 ` Albert ARIBAUD
2013-02-26 22:28 ` [U-Boot] [PATCH 3/3] ARM: mx6: use common CPU errata config options Stephen Warren
2013-02-27 0:15 ` Fabio Estevam
2013-02-27 2:44 ` Liu Hui-R64343
2013-03-07 17:24 ` Stefano Babic
2013-03-07 19:19 ` Stephen Warren
2013-03-08 8:12 ` Stefano Babic [this message]
2013-02-28 0:30 ` [U-Boot] [PATCH 1/3] ARM: implement some Cortex-A9 errata workarounds Simon Glass
2013-02-28 0:36 ` Stephen Warren
2013-02-28 0:38 ` Simon Glass
2013-02-28 17:08 ` Stephen Warren
2013-03-01 21:53 ` Stephen Warren
2013-03-01 23:02 ` Tom Warren
2013-03-04 16:30 ` Tom Warren
2013-03-04 18:00 ` Albert ARIBAUD
2013-03-04 19:07 ` Tom Warren
2013-03-15 5:58 ` Albert ARIBAUD
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=51399D6F.6060808@denx.de \
--to=sbabic@denx.de \
--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