All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jagan Teki <jagannadh.teki@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH for 2018.03] sunxi: README.sunxi64: Add hint about non-debug ATF
Date: Thu, 22 Feb 2018 13:35:50 +0530	[thread overview]
Message-ID: <CAD6G_RQpJ3XbkovwsM+7Q7H-RSTzT9RjcXZwR2dposkQcas=xA@mail.gmail.com> (raw)
In-Reply-To: <20180222015027.25585-1-andre.przywara@arm.com>

On Thu, Feb 22, 2018 at 7:20 AM, Andre Przywara <andre.przywara@arm.com> wrote:
> As we are running into issues where the final U-Boot FIT image file is
> exceeding our size limit, add a hint to the README.sunxi64 file
> to point out the possibility of building non-debug versions of the ATF
> binary. This is about 12KB smaller than the standard debug build, and
> so again allows successful U-Boot builds for many boards with the
> Allwinner H5 SoC.
> Please note that under normal circumstances the debug build is still
> recommended, as it gives valuable clues in case something goes wrong in
> the ATF.

So for H5 we can't able to use debug (:

>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> ---
> Hi,
>
> as the level of desperation about Allwinner 64-bit FIT image sizes rises,
> we are getting more into the slightly cheaty section with our mitigations.
> However as my previous attempts in fixing this issue were not that warmly
> welcomed, I now suggest this rather pragmatic solution, which avoids hacking
> U-Boot badly. This fixes the various H5 builds for me.
>
> Cheers,
> Andre.
>
>  board/sunxi/README.sunxi64 | 6 ++++++
>  1 file changed, 6 insertions(+)
>
> diff --git a/board/sunxi/README.sunxi64 b/board/sunxi/README.sunxi64
> index c492f749b8..eefa5001a2 100644
> --- a/board/sunxi/README.sunxi64
> +++ b/board/sunxi/README.sunxi64
> @@ -38,6 +38,12 @@ the root of your U-Boot build directory (or create a symbolic link).
>  $ export BL31=/src/arm-trusted-firmware/build/sun50iw1p1/debug/bl31.bin
>    (adjust the actual path accordingly)
>
> +If you run into size issues with the resulting U-Boot image file, it might
> +help to use a release build, by using "DEBUG=0" when building bl31.bin.

This is something like release build even w/o DEBUG=0 it will build
same is it? In that case we can say not to use DEBUG=1 just make
PLAT=sun50iw1p1 bl31

  reply	other threads:[~2018-02-22  8:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22  1:50 [U-Boot] [PATCH for 2018.03] sunxi: README.sunxi64: Add hint about non-debug ATF Andre Przywara
2018-02-22  8:05 ` Jagan Teki [this message]
2018-02-22  9:03   ` Andre Przywara
2018-02-22  9:56     ` Maxime Ripard

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='CAD6G_RQpJ3XbkovwsM+7Q7H-RSTzT9RjcXZwR2dposkQcas=xA@mail.gmail.com' \
    --to=jagannadh.teki@gmail.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.