Port-zaurus archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: ARM ABI changes/combinations

On Aug 26, 2014, at 7:10 PM, Jun Ebihara <jun%soum.co.jp@localhost> wrote:

> From: Jeff Rizzo <riz%NetBSD.org@localhost>
> Subject: Re: ARM ABI changes/combinations (was Re: Preparation for creating 
> netbsd-7 branch)
> Date: Fri, 25 Jul 2014 17:25:26 -0700
>> Index: build.sh
>> ===================================================================
>> RCS file: /cvsroot/src/build.sh,v
>> -MACHINE=zaurus              MACHINE_ARCH=arm        DEFAULT
>> -MACHINE=zaurus              MACHINE_ARCH=earm       ALIAS=ezaurus
>> +MACHINE=zaurus              MACHINE_ARCH=arm        ALIAS=ozaurus
>> +MACHINE=zaurus              MACHINE_ARCH=earm       ALIAS=ezaurus DEFAULT
> Current zaurus port status on my environment;
> - ozaurus bootloader can load ozaurus kernel and boot.
> - ezaurus bootloader can't load ezaurus kernel
> - ozaurus bootloader and ezaurus kernel can load but not boot
>                     ozaurus-kernel  ezaurus-kernel 
> ozaurus bootloader      boot          load and stopped
> ezaurus bootloader     not tested     load fail

The zboot generated by ezaurus or zaurus are binary identical.
So that can't be it.  What does load fail mean?
Does VERBOSE_INIT_ARM reveal anything?

Can I see an ozaurus dmesg?

Home | Main Index | Thread Index | Old Index