From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Date: Fri, 26 Oct 2007 09:27:04 -0500 Subject: [U-Boot-Users] Bug in malloc()? In-Reply-To: References: <47211A27.1080703@freescale.com> <4721D0BD.4060200@ge.com> Message-ID: <4721F938.4010701@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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?