Searched hist:"4200 e5aae7c70c728bc9c2e1d8d45223a3f7c614" (Results 1 – 5 of 5) sorted by relevance
| /rk3399_ARM-atf/plat/rockchip/rk3288/ |
| H A D | platform.mk | 4200e5aae7c70c728bc9c2e1d8d45223a3f7c614 Wed Apr 24 18:26:51 UTC 2019 Heiko Stuebner <heiko@sntech.de> rockchip: only include libfdt in non-coreboot cases
While mainline u-boot always expects to submit the devicetree
as platform param, coreboot always uses the existing parameter
structure. As libfdt is somewhat big, it makes sense to limit
its inclusion to where necessary and thus only to non-coreboot
builds.
libfdt itself will get build in all cases, but only the non-
coreboot build will actually reference and thus include it.
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Change-Id: I4c5bc28405a14e6070917e48a526bfe77bab2fb7
|
| /rk3399_ARM-atf/plat/rockchip/rk3328/ |
| H A D | platform.mk | 4200e5aae7c70c728bc9c2e1d8d45223a3f7c614 Wed Apr 24 18:26:51 UTC 2019 Heiko Stuebner <heiko@sntech.de> rockchip: only include libfdt in non-coreboot cases
While mainline u-boot always expects to submit the devicetree
as platform param, coreboot always uses the existing parameter
structure. As libfdt is somewhat big, it makes sense to limit
its inclusion to where necessary and thus only to non-coreboot
builds.
libfdt itself will get build in all cases, but only the non-
coreboot build will actually reference and thus include it.
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Change-Id: I4c5bc28405a14e6070917e48a526bfe77bab2fb7
|
| /rk3399_ARM-atf/plat/rockchip/common/ |
| H A D | params_setup.c | 4200e5aae7c70c728bc9c2e1d8d45223a3f7c614 Wed Apr 24 18:26:51 UTC 2019 Heiko Stuebner <heiko@sntech.de> rockchip: only include libfdt in non-coreboot cases
While mainline u-boot always expects to submit the devicetree
as platform param, coreboot always uses the existing parameter
structure. As libfdt is somewhat big, it makes sense to limit
its inclusion to where necessary and thus only to non-coreboot
builds.
libfdt itself will get build in all cases, but only the non-
coreboot build will actually reference and thus include it.
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Change-Id: I4c5bc28405a14e6070917e48a526bfe77bab2fb7
|
| /rk3399_ARM-atf/plat/rockchip/rk3368/ |
| H A D | platform.mk | 4200e5aae7c70c728bc9c2e1d8d45223a3f7c614 Wed Apr 24 18:26:51 UTC 2019 Heiko Stuebner <heiko@sntech.de> rockchip: only include libfdt in non-coreboot cases
While mainline u-boot always expects to submit the devicetree
as platform param, coreboot always uses the existing parameter
structure. As libfdt is somewhat big, it makes sense to limit
its inclusion to where necessary and thus only to non-coreboot
builds.
libfdt itself will get build in all cases, but only the non-
coreboot build will actually reference and thus include it.
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Change-Id: I4c5bc28405a14e6070917e48a526bfe77bab2fb7
|
| /rk3399_ARM-atf/plat/rockchip/rk3399/ |
| H A D | platform.mk | 4200e5aae7c70c728bc9c2e1d8d45223a3f7c614 Wed Apr 24 18:26:51 UTC 2019 Heiko Stuebner <heiko@sntech.de> rockchip: only include libfdt in non-coreboot cases
While mainline u-boot always expects to submit the devicetree
as platform param, coreboot always uses the existing parameter
structure. As libfdt is somewhat big, it makes sense to limit
its inclusion to where necessary and thus only to non-coreboot
builds.
libfdt itself will get build in all cases, but only the non-
coreboot build will actually reference and thus include it.
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Change-Id: I4c5bc28405a14e6070917e48a526bfe77bab2fb7
|