From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/1] fix ARM DCC support for ARMv7 based cores (e.g. CortexA)
Date: Sun, 1 Feb 2015 10:02:47 +0100 [thread overview]
Message-ID: <20150201100247.7cf9f2a0@lilith> (raw)
In-Reply-To: <1422277997-28386-1-git-send-email-alexander.merkle@lauterbach.com>
Hello Alexander,
On Mon, 26 Jan 2015 14:13:16 +0100, Alexander Merkle
<alexander.merkle@lauterbach.com> wrote:
>
> arm_dcc.c supported ARMv4 (ARM7) to ARMv6 (ARM11) correctly. All recent
> CortexA/ARMv7 based cores share the mrc/mcr coprocessor calls of ARMv6.
> Due to the missing #ifdef the ARM7/ARMv4 calls are used as soon as
> CONFIG_CPU_V7 is defined. This results in an undefined instruction exception.
IIUC, the only board that uses ARM DCC serial is the Zynq, and it
gets it to work by #define'ing CONFIG_CPU_V6 in its include config
file despite being ARMv7. Am I right in assuming this #define was
actually a hack to get around the issue you're fixing here, and that it
can and should be removed from the Zinq include? If so, can you please
post a v2 of your patch which does the removal too?
(BTW, no need for a cover letter when there's only one patch in the
"series" IMO)
Amicalement,
--
Albert.
next prev parent reply other threads:[~2015-02-01 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 13:13 [U-Boot] [PATCH 0/1] fix ARM DCC support for ARMv7 based cores (e.g. CortexA) Alexander Merkle
2015-01-26 13:13 ` [U-Boot] [PATCH] " Alexander Merkle
2015-02-01 9:02 ` Albert ARIBAUD [this message]
2015-02-25 6:38 ` [U-Boot] [PATCH 0/1] " 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=20150201100247.7cf9f2a0@lilith \
--to=albert.u.boot@aribaud.net \
--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