In message <[EMAIL PROTECTED]> you wrote:
> Add support for the recognition of 'powerpc' as an alias for the PowerPC
> architecture type since Linux is already trending in that direction,
> preferring 'powerpc' to 'ppc'.
> 
> Signed-off-by: Grant Erickson <[EMAIL PROTECTED]>
> ---
>  common/image.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/common/image.c b/common/image.c
> index 4a024d4..ecbf9d8 100644
> --- a/common/image.c
> +++ b/common/image.c
> @@ -93,6 +93,7 @@ static table_entry_t uimage_arch[] = {
>       {       IH_ARCH_MIPS64,         "mips64",       "MIPS 64 Bit",  },
>       {       IH_ARCH_NIOS,           "nios",         "NIOS",         },
>       {       IH_ARCH_NIOS2,          "nios2",        "NIOS II",      },
> +     {       IH_ARCH_POWERPC,        "powerpc",      "PowerPC",      },
>       {       IH_ARCH_PPC,            "ppc",          "PowerPC",      },
>       {       IH_ARCH_S390,           "s390",         "IBM S390",     },
>       {       IH_ARCH_SH,             "sh",           "SuperH",       },

Do we really want to do that? At least you have to provide some  user
documentation,  when  to  chose one of the other, and what the diffe-
rence between both is...

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED]
All a hacker needs is a tight PUSHJ, a loose pair of UUOs, and a warm
place to shift.

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
U-Boot-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/u-boot-users

Reply via email to