u-boot-utils and UBOOT_MACHINE?
The current recipe for the u-boot-utils (u-boot-utils_1.2.0.bb) contains this:
------------------->snip<-------------------- do_configure() {
oe_runmake Sandpoint8240_config
} ------------------->snip<--------------------
This seems to be very machine specific.
I'm not a u-boot-tools specialist. If the tools are not machine specific and the above line is just a placeholder, this should be documented.
But if the tools itself are machine specific i believe there should be something like
------------------->snip<--------------------
do_configure() {
oe_runmake ${UBOOT_MACHINE}
}------------------->snip<--------------------
and package build should go into machine specific workdir. Right?
Steffen
Signature · 7 lines
DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, 10319 Berlin, Germany Tel: +49 30 515932-237 mailto:[email protected] Fax: +49 30 515932-299 Geschäftsführer: Dr. Michael Weber, Werner Mögle; Amtsgericht Berlin Charlottenburg; HRB 130120 B; Ust.-IDNr. DE273952058
Quoted 8 lines · Steffen Sledz
The current recipe for the u-boot-utils (u-boot-utils_1.2.0.bb) contains this:
------------------->snip<--------------------
do_configure(){
oe_runmakeSandpoint8240_config
}
------------------->snip<--------------------
Quoted 4 lines
This seems to be very machine specific.
I'm not a u-boot-tools specialist. If the tools are not machine specific and the above line is just a placeholder, this should be documented.
It's been a while since I looked at u-boot-utils, I think the tools are generic but the build scripts need a config to run.
Quoted 8 lines
But if the tools itself are machine specific i believe there should be something like
------------------->snip<--------------------
do_configure() { oe_runmake ${UBOOT_MACHINE} }------------------->snip<--------------------
I guess you mean "oe_runmake ${UBOOT_MACHINE}_config" :-)
I doubt I'm the only one who uses OE to generate Linux images without having a suitable U-Boot machine that could be used to satisfy that. We could put Sandpoint8240 in each such machine conf and document why there. I also assume that there are machine confs that currently lack a UBOOT_MACHINE variable which could cause problems building the U-Boot tools if this change is made, especially for machines that might exist in an overlay (more likely now with OE-core?).
Quoted 2 lines
and package build should go into machine specific workdir. Right?
I think they are generic, though I'm no expert.
Martyn
Signature · 4 lines
Martyn Welch (Principal Software Engineer) | Registered in England and GE Intelligent Platforms | Wales (3828642) at 100 T +44(0)127322748 | Barbirolli Square, Manchester, E [email protected] | M2 3AB VAT:GB 927559189
Quoted 14 lines · Steffen Sledz
The current recipe for the u-boot-utils (u-boot-utils_1.2.0.bb) contains this:
------------------->snip<--------------------
do_configure(){
oe_runmakeSandpoint8240_config
}
------------------->snip<--------------------This seems to be very machine specific.
I'm not a u-boot-tools specialist. If the tools are not machine specific and the above line is just a placeholder, this should be documented.
But if the tools itself are machine specific i believe there should be something like
Quoted 7 lines
------------------->snip<--------------------
do_configure() { oe_runmake ${UBOOT_MACHINE} }------------------->snip<--------------------
and package build should go into machine specific workdir. Right?
So, currently, and modulo the config files that are shipped per-BSP anyhow, the utils that are made are generic. It's possible, but I haven't confirmed, that both this and u-boot-mkimage could just build sans a config target, since it's just building in the tools subdir.
Signature · 2 lines
Tom Rini Mentor Graphics Corporation