From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Thu, 24 Feb 2011 12:28:38 +0100 Subject: [U-Boot] [ARM]: File type for u-boot elf file In-Reply-To: References: <4D66399C.9010201@free.fr> Message-ID: <4D6640E6.5050901@free.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Le 24/02/2011 12:08, sughosh ganu a ?crit : > hi Albert, > > On Thu, Feb 24, 2011 at 4:27 PM, Albert ARIBAUD > wrote: > > Hi Sughosh, > > Le 24/02/2011 11:01, sughosh ganu a ?crit : > > Can you please tell me what could have caused this change. I > compiled > u-boot for a powerpc board, and found that the file type in that > case is > 'ELF Executable'. Is there any specific reason why the file type has > changed for ARM, as powerpc also supports relocation. > > > You have already answered your own question: the move to relocatable > executable caused the change you see. > > > Yes, this is true, what i wanted to understand was the reason why the > 'Type' field is different for ARM now, compared to the u-boot elf image > for powerpc. Not sure if i am missing something, but powerpc also > supports relocation, so what is the reason for the difference in the > two image types. Prior to relocation, we used to get the file type as > 'Executable', same as powerpc. PPC and ARM have different architectures, different toolchains, different methods for relocation -- that explains the different ELF type. > I suspect the utility freaks out because it thinks the ELF cannot be > made into a binary like it would previously, but actually the binary > generation process did not change when we refactored the relocation > -- maybe the utility would work on our relocatable ELFs with just > the check for ELF type bypassed. > > Yes, even i think that would be the case, but i guess that would call > for changes in the utility. Perhaps someone from TI can look into this. Isn't there some official support channel? > -sughosh Amicalement, -- Albert.