public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ARM]: File type for u-boot elf file
Date: Thu, 24 Feb 2011 12:28:38 +0100	[thread overview]
Message-ID: <4D6640E6.5050901@free.fr> (raw)
In-Reply-To: <AANLkTin3mULSrF658688egJqJw7NqFWepR3Sm804dwCB@mail.gmail.com>

Le 24/02/2011 12:08, sughosh ganu a ?crit :
> hi Albert,
>
> On Thu, Feb 24, 2011 at 4:27 PM, Albert ARIBAUD <albert.aribaud@free.fr
> <mailto:albert.aribaud@free.fr>> 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.

  reply	other threads:[~2011-02-24 11:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 10:01 [U-Boot] [ARM]: File type for u-boot elf file sughosh ganu
2011-02-24 10:57 ` Albert ARIBAUD
2011-02-24 11:08   ` sughosh ganu
2011-02-24 11:28     ` Albert ARIBAUD [this message]
2011-02-24 12:29       ` sughosh ganu
2011-02-24 13:26         ` Detlev Zundel
2011-02-25  7:18           ` Albert ARIBAUD
2011-02-25 13:41             ` Ben Gardiner
2011-02-25 14:55               ` sughosh ganu
2011-02-25 17:26                 ` Albert ARIBAUD
2011-02-27 16:32                   ` Wolfgang Denk
2011-02-28  1:49                     ` Andrew Dyer
2011-02-28  6:35                       ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2011-12-05  9:19 rojan
2011-12-05 16:12 ` 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=4D6640E6.5050901@free.fr \
    --to=albert.aribaud@free.fr \
    --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