U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Simple Malloc Breaks omap3_logic
Date: Tue, 14 Feb 2017 16:10:42 -0500	[thread overview]
Message-ID: <20170214211042.GV26129@bill-the-cat> (raw)
In-Reply-To: <CAHCN7xJ52VM6GXVaOQw-YBHn1M32GNjGMMPs47EfNKNZrwH12g@mail.gmail.com>

On Tue, Feb 14, 2017 at 03:03:44PM -0600, Adam Ford wrote:

> Tom,
> 
> I noticed there was an update to the omap3_logic_defconfig to use Simple Malloc
> 
> http://git.denx.de/?p=u-boot.git;a=commit;h=0959649dc6d9e6a371617abd3b03630c5d4d5a72
> 
> 
> I didn't see anything in my inbox indicating the patch, I only noticed
> it because I pulled the latest from the trunk.  Unfortunately, this
> patch breaks the board.
> 
> (ie. MLO doesn't load U-Boot)
> 
> See Log:
> 
> U-Boot SPL 2017.03-rc2-00008-g2ebb842-dirty (Feb 14 2017 - 14:54:59)
> Trying to boot from MMC1
> reading args
> spl_load_image_fat_os: error reading image args, err - -1
> reading u-boot.img
> reading u-boot.img
> 
> (then it just hangs)
> 
> Removing this line from the defconfig returns the board to a functional state.
> 
> Is there an alternative that we can explore to give you what you need?
> 
> I am able to build with gcc version 5.4.0 , but I can help you do some
> testing if you need.

Oh, sorry, I thought I had made sure to copy all of the required logic
to have simple malloc work.  I think it's highly likely I forgot to make
sure that CONFIG_SYS_MALLOC_F_LEN is also set and that's why it all went
south.  Sorry again!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170214/67f7229c/attachment.sig>

  reply	other threads:[~2017-02-14 21:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 21:03 [U-Boot] Simple Malloc Breaks omap3_logic Adam Ford
2017-02-14 21:10 ` Tom Rini [this message]
2017-02-14 21:56   ` Adam Ford
2017-02-14 22:07     ` Tom Rini
2017-02-15 13:23       ` Adam Ford
2017-03-07 22:02         ` Adam Ford
2017-03-07 22:05           ` Tom Rini
2017-03-07 22:23             ` Adam Ford
2017-03-07 22:41               ` Tom Rini
2017-03-08  1:04               ` Tom Rini
2017-03-08  3:31                 ` Adam Ford
2017-03-08 12:11                   ` Tom Rini
2017-03-08 12:13                     ` Tom Rini

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=20170214211042.GV26129@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox