On 11 April 2011 17:20, Jim Huang <jim.hu...@linaro.org> wrote:
> On 11 April 2011 23:14, Patrik Ryd <patrik....@linaro.org> wrote:
>> diff --git a/BoardConfig.mk b/BoardConfig.mk
>> index 5314353..457ab4f 100644
>> --- a/BoardConfig.mk
>> +++ b/BoardConfig.mk
>> @@ -9,7 +9,8 @@ TARGET_NO_KERNEL := false
>> KERNEL_CONFIG := android_omap4_defconfig
>> TARGET_USE_UBOOT := true
>> UBOOT_CONFIG := omap4_panda_config
>> -TARGET_USE_XLOADER := false
>> +TARGET_USE_XLOADER := true
>> +XLOADER_BINARY := device/linaro/pandaboard/MLO.panda
>
> hi Patrik,
>
> Why can't we simply use 'MLO' as the name of first stage boot loader?
I'll change it to MLO. I just got the binary from asac and included it
in the build (we pull down source with repo, but don't build at at the
moment).
I tried to copy it during the build with
PRODUCT_COPY_FILES := \
device/linaro/beagleboard/vold.fstab:system/etc/vold.fstab \
device/linaro/pandaboard/MLO.panda:boot/MBL.panda
in device.mk, but it did not work. Do you have any idea why? I would
prefer to use the standard Android way of doing things instead of
invention my own rules in the build system.
/Patrik
>
> By the way, although we usually call Pandaboard as 'panda', it still
> makes sense to use the fully qualified name, doesn't it?
>
> Regards,
> -jserv
>
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
