From: Teresa Remmet <t.remmet@phytec.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: AM335x NAND boot on next
Date: Mon, 17 Dec 2018 15:02:17 +0100 [thread overview]
Message-ID: <1545055337.6213.18.camel@phytec.de> (raw)
In-Reply-To: <20181217111407.bsdwqy2lqfinwj2p@pengutronix.de>
Hello Sascha,
Am Montag, den 17.12.2018, 12:14 +0100 schrieb Sascha Hauer:
> Hi Teresa,
>
> On Mon, Dec 17, 2018 at 11:54:30AM +0100, Teresa Remmet wrote:
> >
> > Hello Sascha,
> >
> > I watend to test the gpmc driver changes for our am335x boards
> > using
> > latest next. I noticed that booting from nand is not working
> > correct
> > any more. The MLO can not correctly obtain the image size of the
> > barebox image.
> Ups, right. Try the following.
Yes, this helps. Thanks.
>
> While you are testing this board anyway could you see if the NAND
> generally still works on AM33xx? There are sitting some changes to
> the
> NAND driver in next.
I'll have a look at it. Noticed also two other things with the AM35xx
patch stack. I will send patches for this.
Teresa
>
> Sascha
>
> -----------------------8<-----------------------------
>
> From 197806965fe26a444d40791fde5acff7eb4cd805 Mon Sep 17 00:00:00
> 2001
> From: Sascha Hauer <s.hauer@pengutronix.de>
> Date: Mon, 17 Dec 2018 12:09:23 +0100
> Subject: [PATCH] Images: Add image size to built images
>
> This brings back the image size written into the built images which
> got
> lost in the conversion to using piggydata in the PBL images.
>
> Fixes: 5a1a5ed253 ("ARM: images: use piggydata")
>
> Reported-by: Teresa Remmet <t.remmet@phytec.de>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
> images/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/images/Makefile b/images/Makefile
> index 4c6d486f08..41509aa957 100644
> --- a/images/Makefile
> +++ b/images/Makefile
> @@ -66,6 +66,7 @@ $(obj)/%.pbl: $(pbl-lds) $(barebox-pbl-common)
> $(obj)/piggy.o FORCE
>
> $(obj)/%.pblb: $(obj)/%.pbl FORCE
> $(call if_changed,objcopy_bin,$(*F))
> + $(Q)$(objtree)/scripts/fix_size -f $@
>
> $(obj)/%.s: $(obj)/% FORCE
> $(call if_changed,disasm)
> --
> 2.19.1
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-12-17 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 10:54 AM335x NAND boot on next Teresa Remmet
2018-12-17 11:14 ` Sascha Hauer
2018-12-17 14:02 ` Teresa Remmet [this message]
2018-12-18 7:44 ` Sascha Hauer
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=1545055337.6213.18.camel@phytec.de \
--to=t.remmet@phytec.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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.