u-boot-utils and UBOOT_MACHINE?

u-boot-utils and UBOOT_MACHINE?

[Steffen Sledz]

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

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@DResearch.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058

Re: u-boot-utils and UBOOT_MACHINE?

[Martyn Welch]

On 09/03/11 10:42, Steffen Sledz wrote:
> 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.
> 

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.

> 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?).

> and package build should go into machine specific workdir. Right?
> 

I think they are generic, though I'm no expert.

Martyn

-- 
Martyn Welch (Principal Software Engineer) | Registered in England and
GE Intelligent Platforms                   | Wales (3828642) at 100
T +44(0)127322748                          | Barbirolli Square, Manchester,
E martyn.welch@ge.com                      | M2 3AB  VAT:GB 927559189

Re: u-boot-utils and UBOOT_MACHINE?

[Tom Rini]

On 03/09/2011 03:42 AM, Steffen Sledz wrote:
> 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?

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.

-- 
Tom Rini
Mentor Graphics Corporation