summaryrefslogtreecommitdiff
path: root/doc/README.dk20k200_std32
diff options
context:
space:
mode:
authorKumar Gala <galak@kernel.crashing.org>2009-06-11 23:42:35 -0500
committerKumar Gala <galak@kernel.crashing.org>2009-06-12 09:15:50 -0500
commite7563aff174f77aa61dab1ef5d9b47bebaa43702 (patch)
treea3ef1e9c1745d417a06328e464446436dd46f2c7 /doc/README.dk20k200_std32
parentd4b130dc80761b430dc5b410159cd158fca1a348 (diff)
downloadu-boot-imx-e7563aff174f77aa61dab1ef5d9b47bebaa43702.zip
u-boot-imx-e7563aff174f77aa61dab1ef5d9b47bebaa43702.tar.gz
u-boot-imx-e7563aff174f77aa61dab1ef5d9b47bebaa43702.tar.bz2
fsl-ddr: Fix handling of >4G of memory when !CONFIG_PHYS_64BIT
The ddr code computes most things as 64-bit quantities and had some places in the middle that it was using phy_addr_t and phys_size_t. Instead we use unsigned long long through out and only at the last stage of setting the LAWs and reporting the amount of memory to the board code do we truncate down to what we can cover via phys_size_t. This has the added benefit that the DDR controller itself is always setup the same way regardless of how much memory we have. Its only the LAW setup that limits what is visible to the system. Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Diffstat (limited to 'doc/README.dk20k200_std32')
0 files changed, 0 insertions, 0 deletions