All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danny Gale <Daniel.Gale@coloradoengineeringinc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] T4QDS e6500 core and U-Boot 64-bit
Date: Tue, 21 Jan 2014 18:02:43 -0700	[thread overview]
Message-ID: <52DF18B3.1080904@coloradoengineeringinc.com> (raw)

Hi All,

The T4240 on the T4QDS board is a PPC e6500 core (64 bit), but it is 
configured in U-Boot as an e500 core, which is 32 bit. Why is this? Can 
it be updated to e6500?

This leads directly into another question: can U-Boot be compiled and 
run 64-bit? So far, I have been unable to make it work with a 64-bit 
compiler. I'm running into these errors:

cc1: error: -mcall not supported in this configuration
cc1: error: -mrelocatable not supported in this configuration
cc1: error: -meabi not supported in this configuration

Specifying CFLAGS="-meabi -mrelocatable -mcall-sysv" will get through 
make T4240QDS_config without errors, but the above errors show up when 
making the following targets:
 > include/autoconf.mk
 > include/autoconf.mk.dep
 > include/spl-autoconf.mk
 > include/tpl-autoconf.mk

The build then fails, with a call to cross-gcc which does not include 
the specified CFLAGS. Is this a bug in the Makefile, that CFLAGS is not 
being passed to the call to cross-gcc?

Thanks,
Danny

             reply	other threads:[~2014-01-22  1:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22  1:02 Danny Gale [this message]
2014-01-22  9:06 ` [U-Boot] T4QDS e6500 core and U-Boot 64-bit Wolfgang Denk
2014-01-23 18:13   ` Danny Gale
2014-01-23 19:00     ` Scott Wood
2014-01-24 13:45     ` Wolfgang Denk
2014-01-24 20:24       ` Scott Wood
2014-01-25 15:46       ` Timur Tabi
2014-01-25 17:00         ` York Sun

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=52DF18B3.1080904@coloradoengineeringinc.com \
    --to=daniel.gale@coloradoengineeringinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.