Home
last modified time | relevance | path

Searched hist:d2b12a5767ec762f92a7c308a562472e23b5347e (Results 1 – 3 of 3) sorted by relevance

/openbmc/u-boot/board/imgtec/boston/
H A Ddt.cd2b12a5767ec762f92a7c308a562472e23b5347e Sun Apr 30 14:22:42 CDT 2017 Paul Burton <paul.burton@imgtec.com> boston: Setup memory ranges in FDT provided to Linux

The boston memory map isn't suited to the simple "all memory starting
from 0" approach that the MIPS arch_fixup_fdt() implementation takes.
Instead we need to indicate the first 256MiB of DDR from 0 and the rest
from 0x90000000. Implement ft_board_setup to do that.

Signed-off-by: Paul Burton <paul.burton@imgtec.com>
Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
H A DMakefilediff d2b12a5767ec762f92a7c308a562472e23b5347e Sun Apr 30 14:22:42 CDT 2017 Paul Burton <paul.burton@imgtec.com> boston: Setup memory ranges in FDT provided to Linux

The boston memory map isn't suited to the simple "all memory starting
from 0" approach that the MIPS arch_fixup_fdt() implementation takes.
Instead we need to indicate the first 256MiB of DDR from 0 and the rest
from 0x90000000. Implement ft_board_setup to do that.

Signed-off-by: Paul Burton <paul.burton@imgtec.com>
Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
/openbmc/u-boot/arch/mips/
H A DKconfigdiff d2b12a5767ec762f92a7c308a562472e23b5347e Sun Apr 30 14:22:42 CDT 2017 Paul Burton <paul.burton@imgtec.com> boston: Setup memory ranges in FDT provided to Linux

The boston memory map isn't suited to the simple "all memory starting
from 0" approach that the MIPS arch_fixup_fdt() implementation takes.
Instead we need to indicate the first 256MiB of DDR from 0 and the rest
from 0x90000000. Implement ft_board_setup to do that.

Signed-off-by: Paul Burton <paul.burton@imgtec.com>
Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>