All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] configs: vf610: increase maximum size and enforce correct limit
Date: Mon, 30 Oct 2017 22:47:56 -0400	[thread overview]
Message-ID: <20171031024756.GD4635@bill-the-cat> (raw)
In-Reply-To: <e6cf519e06614f9bf774d85a4a85f209@agner.ch>

On Mon, Oct 30, 2017 at 09:59:04AM +0100, Stefan Agner wrote:
> Hi Tom, Stefano,
> 
> Any chance to get this still into 2017.11? It allows to use 2017.11 on
> my board...

Stefano, this is your call, thanks!

> 
> --
> Stefan
> 
> On 2017-10-17 13:59, Stefan Agner wrote:
> > From: Stefan Agner <stefan.agner@toradex.com>
> > 
> > On Vybrid SoCs U-Boot gets loaded into GFX SRAM which is 512KiB.
> > Currently 32KiB is reserved for the IMX header. However, this is
> > not reflected in the size limit. In v2017.11-rc2 the actual size
> > limit (512KiB-32KiB) has been reached for Colibri VF61, which
> > lead to a successful build of U-Boot but not a working binary.
> > 
> > The IMX header is much smaller than 32KiB, typically around 1KiB.
> > Decrease the reserved size to 4KiB and specify the correct U-Boot
> > size limit. Apply this new base address and limit for all Vybrid
> > based boards.
> > 
> > Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
> > ---
> > 
> >  include/configs/colibri_vf.h | 4 ++--
> >  include/configs/pcm052.h     | 4 ++--
> >  include/configs/vf610twr.h   | 4 ++--
> >  3 files changed, 6 insertions(+), 6 deletions(-)
> > 
> > diff --git a/include/configs/colibri_vf.h b/include/configs/colibri_vf.h
> > index 8166aa4afb..bf3bbffe24 100644
> > --- a/include/configs/colibri_vf.h
> > +++ b/include/configs/colibri_vf.h
> > @@ -75,8 +75,8 @@
> >  #define CONFIG_FDTADDR			0x84000000
> >  
> >  /* We boot from the gfxRAM area of the OCRAM. */
> > -#define CONFIG_SYS_TEXT_BASE		0x3f408000
> > -#define CONFIG_BOARD_SIZE_LIMIT		524288
> > +#define CONFIG_SYS_TEXT_BASE		0x3f401000
> > +#define CONFIG_BOARD_SIZE_LIMIT		520192
> >  
> >  #define SD_BOOTCMD \
> >  	"sdargs=root=/dev/mmcblk0p2 rw rootwait\0"	\
> > diff --git a/include/configs/pcm052.h b/include/configs/pcm052.h
> > index 8144a83db2..060928bd30 100644
> > --- a/include/configs/pcm052.h
> > +++ b/include/configs/pcm052.h
> > @@ -89,8 +89,8 @@
> >  #define CONFIG_LOADADDR			0x82000000
> >  
> >  /* We boot from the gfxRAM area of the OCRAM. */
> > -#define CONFIG_SYS_TEXT_BASE		0x3f408000
> > -#define CONFIG_BOARD_SIZE_LIMIT		524288
> > +#define CONFIG_SYS_TEXT_BASE		0x3f401000
> > +#define CONFIG_BOARD_SIZE_LIMIT		520192
> >  
> >  /* if no target-specific extra environment settings were defined by the
> >     target, define an empty one */
> > diff --git a/include/configs/vf610twr.h b/include/configs/vf610twr.h
> > index 3430f27c40..ddfcd6f618 100644
> > --- a/include/configs/vf610twr.h
> > +++ b/include/configs/vf610twr.h
> > @@ -79,8 +79,8 @@
> >  #define CONFIG_SYS_LOAD_ADDR		0x82000000
> >  
> >  /* We boot from the gfxRAM area of the OCRAM. */
> > -#define CONFIG_SYS_TEXT_BASE		0x3f408000
> > -#define CONFIG_BOARD_SIZE_LIMIT		524288
> > +#define CONFIG_SYS_TEXT_BASE		0x3f401000
> > +#define CONFIG_BOARD_SIZE_LIMIT		520192
> >  
> >  /*
> >   * We do have 128MB of memory on the Vybrid Tower board. Leave the last
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171030/72b37f2f/attachment.sig>

  reply	other threads:[~2017-10-31  2:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 11:59 [U-Boot] [PATCH] configs: vf610: increase maximum size and enforce correct limit Stefan Agner
2017-10-30  8:59 ` Stefan Agner
2017-10-31  2:47   ` Tom Rini [this message]
2017-10-31  9:59     ` Stefano Babic

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=20171031024756.GD4635@bill-the-cat \
    --to=trini@konsulko.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.