[U-Boot] Regarding 8641D u-boot

Hi kumar, The CONFIG_PHYS_64BIT was not defined on the header file of HPCN but extended address translation was enabled on the start.S irrespective of the MPC8641D_hpcn compilation option why?.
Regards, T.
**************** CAUTION - Disclaimer *****************This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, retention, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Also, email is susceptible to data corruption, interception, tampering, unauthorized amendment and viruses. We only send and receive emails on the basis that we are not liable for any such corruption, interception, tampering, amendment or viruses or any consequence thereof. *********** End of Disclaimer ***********DataPatterns ITS Group**********

On Aug 18, 2009, at 5:12 AM, Thirumalai wrote:
Hi kumar, The CONFIG_PHYS_64BIT was not defined on the header file of HPCN but extended address translation was enabled on the start.S irrespective of the MPC8641D_hpcn compilation option why?.
Regards, T.
Are you running into an issue with this? It could be to allow an OS to have 36-bit addressing w/o u-boot having to deal with it.
- k

On Aug 18, 2009, at 9:14 AM, Kumar Gala wrote:
On Aug 18, 2009, at 5:12 AM, Thirumalai wrote:
Hi kumar, The CONFIG_PHYS_64BIT was not defined on the header file of HPCN but extended address translation was enabled on the start.S irrespective of the MPC8641D_hpcn compilation option why?.
Regards, T.
Are you running into an issue with this? It could be to allow an OS to have 36-bit addressing w/o u-boot having to deal with it.
That's always been there (since the original board port), and it shouldn't cause a problem (or any performance issues), AFAIK.
Cheers, Becky
participants (3)
-
Becky Bruce
-
Kumar Gala
-
Thirumalai