Hi,

Le 31/08/2013 21:44, Andreas Färber a écrit :
> Am 31.08.2013 07:46, schrieb Andreas Färber:
>> Unfortunately copypac'ed kernel-f+s failed for Factory although it
>> succeeded for 12.2, so I'm guessing this is a binutils/gcc issue:
>>
>> https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:armStone/kernel-f+s
>>
>> [  443s]   AS      arch/arm/kernel/debug.o
>> [  443s] arch/arm/kernel/debug.S: Assembler messages:
>> [  443s] arch/arm/kernel/debug.S:161: Error: ARM register expected --
>> `ldr r2,[ r3,#(0x08)]'
>> [  443s] arch/arm/kernel/debug.S:161: Error: ARM register expected --
>> `ldr r2,[ r3,#(0x18)]'
>> [  443s] arch/arm/kernel/debug.S:161: Error: ARM register expected --
>> `ldr r2,[ r3,#(0x10)]'
>> [  443s] arch/arm/kernel/debug.S:163: Error: ARM register expected --
>> `ldr r2,[ r3,#(0x08)]'
>> [  443s] arch/arm/kernel/debug.S:163: Error: ARM register expected --
>> `ldr r2,[ r3,#(0x18)]'
>> [  443s] arch/arm/kernel/debug.S:163: Error: ARM register expected --
>> `ldr r2,[ r3,#(0x10)]'
>> [  443s] make[1]: *** [arch/arm/kernel/debug.o] Error 1
>> [  443s] make: *** [arch/arm/kernel] Error 2
> I've found a patch to backport, fixing the build. Apparently newer gas
> versions trip over the whitespace after '['. Doh. ;)
>
> However the newly built kernel complains about an unsatisfied
> kernel-uname-r = 3.3.7-F+S and, when ignored, does not boot:

Could you explain the "complain" with a full log, please?

>
>
> Loading file "/boot/zImage" from mmc device 0:1 (xxa1)
> 2861728 bytes read
> ## Booting kernel from zImage at 40800000
>    XIP Kernel Image ... OK
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
>
>
> The openSUSE:12.2:ARM:Contrib:Armstone kernel-f+s still boots okay.
>
> Is there anything I can try other than forward-porting the diff against
> upstream v3.3.7 to a version known working with our binutils/gcc?

Did you check console args (device and speed) that u-boot passed to the kernel?


Guillaume

-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to