All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7 0/5] Add support for Thumb-1 builds
Date: Tue, 10 Nov 2015 15:02:42 +0100	[thread overview]
Message-ID: <20151110150242.065bb7a7@lilith> (raw)
In-Reply-To: <1445616403-12119-1-git-send-email-albert.u.boot@aribaud.net>

Hello Albert,

On Fri, 23 Oct 2015 18:06:38 +0200, Albert ARIBAUD
<albert.u.boot@aribaud.net> wrote:
> This series implements essential changes for thumb-1 support and
> activates thumb-1 build for openrd and tricorder as a proof of
> concept as well as a fix to bring the image sizes of openrd and
> tricorder targets back under an acceptable limit.
> 
> For other targets, some additional files might need to be forced to
> ARM building, notably architecture-specific instances of lowlevel_init.S
> or of cpu.c. This should be handled on a case-by-case basis.
> 
> This series has two unfixed checkpatch diagnostics:
> 
> warning: arch/arm/mach-kirkwood/Kconfig,7:
> please write a paragraph that describes the config symbol fully
> 
> (no option in this Kconfig has help info)
> 
> check: board/Marvell/openrd/openrd.c,42: Avoid CamelCase: <MPP6_SYSRST_OUTn>
> 
> (this is actually not an OpenRD problem and will be fixed
> in another patch)
> 
> IMPORTANT NOTE:
> 
> The whole set has been build-tested across all ARM targets
> and no build regression was detected -- actually, the series
> does fix the x600 board which otherwise fails assembling an
> mcr instruction.
> 
> Patch 1 has been confirmed to be binary-invariant.
> 
> Patch 2 has been build- and run-tested on ED Mini V2 (switched
> temporarily to Thumb build) and confirmed to be binary-invariant
> for non-thumb target Wireless Space.
> 
> Patches 3 through 6 have been build-tested BUT HAVE NOT BEEN
> RUN-TESTED so far.
> 
> I will test on OpenRD (client) before the end of the merge
> window, but:
> 
> *********************************************************
> Open-RD and Tricorder owners, PLEASE run-test this series
> and report on the mailing list whether the target works.
> *********************************************************

Tests on OpenRD-Client uncovered an issue with commit 5ba534d2 (which
introduced board_init_f_mem for crt0.S) and gcc 5.2.1. Because of
this, the series was not applied so far, and a fix to 5ba534d2 was
posted, on which I intended to have the series depend (and I have
verified that with the fix, the series boots fine on OpenRD-Client).

However, there is already at least one board broken by 5ba534d2
(cgtqmx6eval, see <http://patchwork.ozlabs.org/patch/542266/>) for
which a revert was posted.

Since there is already breakage in u-boot/master, and since there will
be a fix to 5ba534d2 eventually, and since this Thumb-1 series has
lingered for long enough:

Applied to u-boot-arm/master.

Amicalement,
-- 
Albert.

      parent reply	other threads:[~2015-11-10 14:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 16:06 [U-Boot] [PATCH v7 0/5] Add support for Thumb-1 builds Albert ARIBAUD
2015-10-23 16:06 ` [U-Boot] [PATCH v7 1/5] stm32f429-discovery: add CONFIG_SYS_THUMB_BUILD Albert ARIBAUD
2015-10-23 16:06 ` [U-Boot] [PATCH v7 2/5] arm: support Thumb-1 with CONFIG_SYS_THUMB_BUILD Albert ARIBAUD
2015-10-23 16:06 ` [U-Boot] [PATCH v7 3/5] tricorder: switch to CONFIG_SYS_THUMB_BUILD Albert ARIBAUD
2015-10-23 16:06 ` [U-Boot] [PATCH v7 4/5] kirkwood: support CONFIG_SYS_THUMB_BUILD Albert ARIBAUD
2015-10-23 16:06 ` [U-Boot] [PATCH v7 5/5] Revive OpenRD targets Albert ARIBAUD
2015-11-10 14:02 ` Albert ARIBAUD [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=20151110150242.065bb7a7@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 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.