Am Donnerstag, 27. März 2014 19:50:32 UTC+1 schrieb Ezaul Zillmer:
> Ok Muito Obrigado!
> 
> 
> ;)
> 
> Em quinta-feira, 27 de março de 2014 15h19min58s UTC-3, Hans de Goede  
> escreveu:Hi,
> 
> 
> 
> To build this you should do:
> 
> 
> 
> make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- Cubieboard2_config
> 
> make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-
> 
> 
> 
> Regards,
> 
> 
> 
> Hans
> 
> 
> 
> 
> 
> On 03/27/2014 06:33 PM, Ezaul Zillmer wrote:
> 
> > 
> 
> >>
> 
> >> Good Afternoon Doctor Hans 
> 
> >>
> 
> >>  
> 
> > 
> 
> >> Updated my u-boot
> 
> >>
> 
> >>       I wonder how was the logic I tried to compile it like this: 
> 
> >      
> 
> >       ./mkconfig ARCH=arm CPU=armv7 SOC=sunxi BOARD=Cubieboard2 
> 
> > 
> 
> >> make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-
> 
> >>>
> 
> >>
> 
> >>> No dick: (could correct me where I am going wrong! 
> 
> >>
> 
> >>
> 
> >>> Hug Since Thank you much longer
> 
> >>
> 
> >>
> 
> >

Hi Hans,

I tested the new u-boot with your newest kernel (3.14.0-rc8+) on the cubietruck.

I found two issues so far. It seems that only one CPU is initialized correctly:

[    0.049402] /cpus/cpu@0 missing clock-frequency property
[    0.049433] /cpus/cpu@1 missing clock-frequency property
[    0.049447] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.049479] Setting up static identity map for 0x4073f2d0 - 0x4073f368
[    0.058595] CPU1: failed to boot: -38
[    0.058647] Brought up 1 CPUs
[    0.058655] SMP: Total of 1 processors activated.
[    0.058662] CPU: All CPU(s) started in SVC mode.
[    0.059721] devtmpfs: initialized
[    0.064475] VFP support v0.3: implementor 41 architecture 2 part 30 variant 
7 rev 4

Also kvm does not work and there is no /dev/kvm device. 
[    0.176760] kvm [1]: HYP mode not available

Here is the full dmesg output: http://pastebin.com/V72FAzmp

Greetings 
 Markus

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to