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: Thu, 23 Jan 2014 11:13:01 -0700 [thread overview]
Message-ID: <52E15BAD.1020400@coloradoengineeringinc.com> (raw)
In-Reply-To: <20140122090644.33C0138220A@gemini.denx.de>
Hi Wolfgang,
Thanks for your reply. My responses are inline below.
On 1/22/2014 2:06 AM, Wolfgang Denk wrote:
> Dear Danny Gale,
>
> In message <52DF18B3.1080904@coloradoengineeringinc.com> you wrote:
>> 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?
> Becuase it simply works :-)
>
>> Can it be updated to e6500?
> Yes - if you add support for 64 bit configurations in general, and
> for powerpc64 in particular.
I don't even have a sense for what would be involved here. How
fundamentally would the U-Boot code need to change?
>> 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:
> Not out of the box.
>
>
> What is your actual reason for wanting to run a 64 bit boot loader?
My reason for wanting to run 64-bit is that this system has 12 GB of
RAM. Will 32-bit U-Boot be able to access and test more than 4 GB of RAM?
Thanks again,
Danny
next prev parent reply other threads:[~2014-01-23 18:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 1:02 [U-Boot] T4QDS e6500 core and U-Boot 64-bit Danny Gale
2014-01-22 9:06 ` Wolfgang Denk
2014-01-23 18:13 ` Danny Gale [this message]
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=52E15BAD.1020400@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).