public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] rockchip breakage with "spl: Remove overwrite of relocated malloc limit"
Date: Tue, 07 Mar 2017 01:42:32 +0100	[thread overview]
Message-ID: <5416401.pcIAmeSpSx@diego> (raw)

Hi,

I just realized patch b3d2861eb20a ("spl: Remove overwrite of relocated malloc 
limit") introduces breakage in my rk3188 uboot code (and should most likely 
also affect the very similar other rockchip spl boards).

The boards call spl_init in their board_init_f functions because they need the 
spl infrastructure to find and bringup the devicetree stuff and things like 
pinctrl and ram.

With the recent change mentioned above, spl_init fails with
	spl_init() failed: -12
because
	dm_init_and_scan() returned error -12
because
	dm_init() failed: -12
...
because
	Missing uclass for driver root_driver
because
	uclass_add calls calloc, which fails with the -ENOMEM (-12)

I still lack uboot experience to see the correct way forward. Reverting that 
patch of course makes my board start uboot again [and most likely the other 
Rockchip SPLs as well], but there is possibly some better solution
[Or there is simply something very wrong with my rk3188 stuff :-) ].


Heiko

             reply	other threads:[~2017-03-07  0:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07  0:42 Heiko Stübner [this message]
2017-03-07  6:56 ` [U-Boot] rockchip breakage with "spl: Remove overwrite of relocated malloc limit" Kever Yang
2017-03-07 17:01   ` Simon Glass
2017-03-07 18:39     ` Heiko Stübner
2017-03-07 18:45       ` Simon Glass

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=5416401.pcIAmeSpSx@diego \
    --to=heiko@sntech.de \
    --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