On Wed, Apr 13, 2011 at 7:35 PM, Alexander Sack wrote:
> I suspect that would mean that a MLO named binary would then be
> installed in the boot/ partition and that should work.
>
guess you meant 'binary named MLO'. yes, this is correct the OMAP boot code
will search for a file named MLO in the
On Tue, Apr 12, 2011 at 9:33 AM, Patrik Ryd wrote:
> On 11 April 2011 17:20, Jim Huang wrote:
>> On 11 April 2011 23:14, Patrik Ryd wrote:
>>> diff --git a/BoardConfig.mk b/BoardConfig.mk
>>> index 5314353..457ab4f 100644
>>> --- a/BoardConfig.mk
>>> +++ b/BoardConfig.mk
>>> @@ -9,7 +9,8 @@ TARG
Just coming in mid stream here...
Did the copy step run? You can build with:
make showcommands
I can investigate a little.
I think the "standard way" would be to put u-boot in
bootable/bootloader and add the appropriate Android.mk files. I'm just
getting to know the Linaro work, so if this isn'
On 11 April 2011 17:20, Jim Huang wrote:
> On 11 April 2011 23:14, Patrik Ryd 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_def
On 11 April 2011 23:14, Patrik Ryd 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
---
BoardConfig.mk |3 ++-
MLO.panda | Bin 0 -> 22072 bytes
2 files changed, 2 insertions(+), 1 deletions(-)
create mode 100644 MLO.panda
diff --git a/BoardConfig.mk b/BoardConfig.mk
index 5314353..457ab4f 100644
--- a/BoardConfig.mk
+++ b/BoardConfig.mk
@@ -9,7 +9,8 @@ TARGET_NO_KERN
