Searched hist:"80870 e2a664e277df0b6c0604bc4c5591aebde67" (Results 1 – 4 of 4) sorted by relevance
/openbmc/u-boot/configs/ |
H A D | tools-only_defconfig | 80870e2a664e277df0b6c0604bc4c5591aebde67 Fri Dec 07 18:00:41 CST 2018 Otavio Salvador <otavio@ossystems.com.br> tools: add a generic config for native tools building
The motivation for this is to allow distributions to distribute all possible tools in a generic way, avoiding the need of specific tools building for each machine.
Especially on OpenEmbedded / Yocto Project ecosystem, it is very common each BSP to end providing their specific tools when they need to generate images for some SoC (e.g MX23 / MX28 in meta-freescale case).
Using this, we can package the tools doing:
$: make tools-only_defconfig $: make tools-only
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> [trini: Add MAINTAINERS entry for myself, add to .travis.yml, make U-Boot itself buildable to not trip up other frameworks] Signed-off-by: Tom Rini <trini@konsulko.com>
|
/openbmc/u-boot/ |
H A D | .travis.yml | 80870e2a664e277df0b6c0604bc4c5591aebde67 Fri Dec 07 18:00:41 CST 2018 Otavio Salvador <otavio@ossystems.com.br> tools: add a generic config for native tools building
The motivation for this is to allow distributions to distribute all possible tools in a generic way, avoiding the need of specific tools building for each machine.
Especially on OpenEmbedded / Yocto Project ecosystem, it is very common each BSP to end providing their specific tools when they need to generate images for some SoC (e.g MX23 / MX28 in meta-freescale case).
Using this, we can package the tools doing:
$: make tools-only_defconfig $: make tools-only
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> [trini: Add MAINTAINERS entry for myself, add to .travis.yml, make U-Boot itself buildable to not trip up other frameworks] Signed-off-by: Tom Rini <trini@konsulko.com>
|
H A D | MAINTAINERS | 80870e2a664e277df0b6c0604bc4c5591aebde67 Fri Dec 07 18:00:41 CST 2018 Otavio Salvador <otavio@ossystems.com.br> tools: add a generic config for native tools building
The motivation for this is to allow distributions to distribute all possible tools in a generic way, avoiding the need of specific tools building for each machine.
Especially on OpenEmbedded / Yocto Project ecosystem, it is very common each BSP to end providing their specific tools when they need to generate images for some SoC (e.g MX23 / MX28 in meta-freescale case).
Using this, we can package the tools doing:
$: make tools-only_defconfig $: make tools-only
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> [trini: Add MAINTAINERS entry for myself, add to .travis.yml, make U-Boot itself buildable to not trip up other frameworks] Signed-off-by: Tom Rini <trini@konsulko.com>
|
/openbmc/u-boot/tools/ |
H A D | Makefile | 80870e2a664e277df0b6c0604bc4c5591aebde67 Fri Dec 07 18:00:41 CST 2018 Otavio Salvador <otavio@ossystems.com.br> tools: add a generic config for native tools building
The motivation for this is to allow distributions to distribute all possible tools in a generic way, avoiding the need of specific tools building for each machine.
Especially on OpenEmbedded / Yocto Project ecosystem, it is very common each BSP to end providing their specific tools when they need to generate images for some SoC (e.g MX23 / MX28 in meta-freescale case).
Using this, we can package the tools doing:
$: make tools-only_defconfig $: make tools-only
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> [trini: Add MAINTAINERS entry for myself, add to .travis.yml, make U-Boot itself buildable to not trip up other frameworks] Signed-off-by: Tom Rini <trini@konsulko.com>
|