Searched hist:fb3ad9bd923daafed9818c579d841f05c8ecbeb0 (Results 1 – 5 of 5) sorted by relevance
| /rk3399_rockchip-uboot/include/configs/ |
| H A D | ti_omap4_common.h | fb3ad9bd923daafed9818c579d841f05c8ecbeb0 Fri Mar 28 19:03:29 UTC 2014 Tom Rini <trini@ti.com> TI: Add, use a DEFAULT_LINUX_BOOT_ENV environment string
To deal with a reoccurring problem properly we need to specify addresses
for the Linux kernel, Flatted Device Tree and ramdisk that obey the
constraints within the kernel's Documentation/arm/Booting file but also
make sure that we relocate things within a valid address range.
It is possible with these addresses to also set fdt_high and initrd_high
to the value of 0xffffffff. We don't do this by default to allow for
the most likely success of people using custom addresses however.
Signed-off-by: Tom Rini <trini@ti.com>
|
| H A D | ti_omap5_common.h | fb3ad9bd923daafed9818c579d841f05c8ecbeb0 Fri Mar 28 19:03:29 UTC 2014 Tom Rini <trini@ti.com> TI: Add, use a DEFAULT_LINUX_BOOT_ENV environment string
To deal with a reoccurring problem properly we need to specify addresses
for the Linux kernel, Flatted Device Tree and ramdisk that obey the
constraints within the kernel's Documentation/arm/Booting file but also
make sure that we relocate things within a valid address range.
It is possible with these addresses to also set fdt_high and initrd_high
to the value of 0xffffffff. We don't do this by default to allow for
the most likely success of people using custom addresses however.
Signed-off-by: Tom Rini <trini@ti.com>
|
| H A D | ti_armv7_common.h | fb3ad9bd923daafed9818c579d841f05c8ecbeb0 Fri Mar 28 19:03:29 UTC 2014 Tom Rini <trini@ti.com> TI: Add, use a DEFAULT_LINUX_BOOT_ENV environment string
To deal with a reoccurring problem properly we need to specify addresses
for the Linux kernel, Flatted Device Tree and ramdisk that obey the
constraints within the kernel's Documentation/arm/Booting file but also
make sure that we relocate things within a valid address range.
It is possible with these addresses to also set fdt_high and initrd_high
to the value of 0xffffffff. We don't do this by default to allow for
the most likely success of people using custom addresses however.
Signed-off-by: Tom Rini <trini@ti.com>
|
| H A D | am43xx_evm.h | fb3ad9bd923daafed9818c579d841f05c8ecbeb0 Fri Mar 28 19:03:29 UTC 2014 Tom Rini <trini@ti.com> TI: Add, use a DEFAULT_LINUX_BOOT_ENV environment string
To deal with a reoccurring problem properly we need to specify addresses
for the Linux kernel, Flatted Device Tree and ramdisk that obey the
constraints within the kernel's Documentation/arm/Booting file but also
make sure that we relocate things within a valid address range.
It is possible with these addresses to also set fdt_high and initrd_high
to the value of 0xffffffff. We don't do this by default to allow for
the most likely success of people using custom addresses however.
Signed-off-by: Tom Rini <trini@ti.com>
|
| H A D | am335x_evm.h | fb3ad9bd923daafed9818c579d841f05c8ecbeb0 Fri Mar 28 19:03:29 UTC 2014 Tom Rini <trini@ti.com> TI: Add, use a DEFAULT_LINUX_BOOT_ENV environment string
To deal with a reoccurring problem properly we need to specify addresses
for the Linux kernel, Flatted Device Tree and ramdisk that obey the
constraints within the kernel's Documentation/arm/Booting file but also
make sure that we relocate things within a valid address range.
It is possible with these addresses to also set fdt_high and initrd_high
to the value of 0xffffffff. We don't do this by default to allow for
the most likely success of people using custom addresses however.
Signed-off-by: Tom Rini <trini@ti.com>
|