public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Anton Gerasimov <tossel@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] zynq: Kconfig: extend the bootstrap malloc() pool
Date: Fri, 21 Dec 2018 11:39:52 +0100	[thread overview]
Message-ID: <2eafeb8a-8715-1516-7d79-929cdbd42a0f@gmail.com> (raw)
In-Reply-To: <530817ee-8b6f-6bb4-9400-cd71bd9d992a@xilinx.com>

> I have not a problem with this change but it has to be done based on
> more information. It means you should look what requires that memory
> and if make sense that these components need it at that time.

Thank you for  the advice, that was quite fruitful. So most of the
heap (0x5f4 of 0x600) before the relocation is being consumed in
device_bind_common function which binds device tree entries to
the drivers.

If I remove 'u-boot,dm-pre-alloc' from uart0 node, that is not
being used as far as I can see, it drops to 0x5a0, which lets the board
boot, but still looks pretty tight. So maybe it's worth extending the heap
anyway unless you need more information to take the decision.

Thanks,
Anton

  reply	other threads:[~2018-12-21 10:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20 21:57 [U-Boot] [PATCH 0/1] Extend malloc() pool for Zynq devices Anton Gerasimov
2018-12-20 21:57 ` [U-Boot] [PATCH 1/1] zynq: Kconfig: extend the bootstrap malloc() pool Anton Gerasimov
2018-12-21  7:14   ` Michal Simek
2018-12-21 10:39     ` Anton Gerasimov [this message]
2019-01-03  8:31       ` Michal Simek
2019-01-20 11:29         ` Anton Gerasimov
2019-01-22 12:01           ` Michal Simek
2018-12-24  1:29     ` [U-Boot] [PATCHv2] " Anton Gerasimov

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=2eafeb8a-8715-1516-7d79-929cdbd42a0f@gmail.com \
    --to=tossel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox