public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Bug in malloc()?
Date: Fri, 26 Oct 2007 09:27:04 -0500	[thread overview]
Message-ID: <4721F938.4010701@freescale.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B038A2893@ismail.innsys.innovsys.com>

Rune Torgersen wrote:

> It is excactly what I ran into also.

Something tells me that a lot of 83xx and 82xx platforms are broken.

> Im my case it turns out that the new relocation code fixups does not
> work.
> I could get malloc to work , but then afterwards, none of the command
> line commands would work as they were not properly relocated either.

Just to be clear, backing out f82b3b6304b620ef7e28bfaa1ea887a2ad2fa325
and e9514751cfa5cce61ea699fa0d3eb37898a5eeb5 makes malloc work, but breaks the 
command line?

> I had to disable CONFIG_RELOC_FIXUP_WORKS in include/common.h for my CPU
> to get it to work.

Does disabling that make everything work?

  reply	other threads:[~2007-10-26 14:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 22:35 [U-Boot-Users] Bug in malloc()? Timur Tabi
2007-10-26 11:34 ` Jerry Van Baren
2007-10-26 14:20   ` Rune Torgersen
2007-10-26 14:27     ` Timur Tabi [this message]
2007-10-26 14:41       ` Rune Torgersen
2007-10-26 14:45       ` Rune Torgersen
2007-10-26 15:01         ` Timur Tabi
     [not found]           ` <DCEAAC0833DD314AB0B58112AD99B93B038A2914@ismail.innsys.innovsys.com>
     [not found]             ` <472203F8.3030800@freescale.com>
     [not found]               ` <DCEAAC0833DD314AB0B58112AD99B93B038A292D@ismail.innsys.innovsys.com>
     [not found]                 ` <47220576.2080700@freescale.com>
2007-10-26 15:23                   ` Rune Torgersen
2007-10-26 16:56             ` Timur Tabi
2007-10-26 22:18         ` Timur Tabi
2007-10-26 22:27           ` Grant Likely
2007-10-26 22:33             ` Timur Tabi
2007-10-26 22:36               ` Rune Torgersen
2007-10-26 22:39                 ` Timur Tabi
2007-10-29 20:45                   ` michael.firth at bt.com
2007-10-29 20:53                     ` Grant Likely
2007-10-29 20:55                       ` Timur Tabi
2007-10-29 20:59                         ` Rune Torgersen
2007-10-29 21:19                           ` michael.firth at bt.com
2007-10-29 21:35                             ` Rune Torgersen
2007-10-29 21:39                               ` michael.firth at bt.com
2007-10-29 21:42                                 ` Grant Likely
2007-10-29 21:41                           ` Grant Likely
2007-10-29 21:55                             ` Rune Torgersen
2007-10-26 15:04       ` Rune Torgersen

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=4721F938.4010701@freescale.com \
    --to=timur@freescale.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