Hello Rudi, On Sat, 21 Nov 2015 08:40:49 +0100 Rudi <[email protected]> wrote:
> Hi, > > is there a known issue with the current 3.4.104 on A10 devices? I gave it a > try on > a Cubieboard using the same config that is O.K. with 3.4.103 and it would not > boot: > > > ## Booting kernel from Legacy Image at 48000000 ... > Image Name: Linux-3.4.104 > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 4086864 Bytes = 3.9 MiB > Load Address: 40008000 > Entry Point: 40008000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > > Starting kernel ... > > > The last message will stay for a few seconds and then the board will reboot > leading > to the same situation. My A20 build (Cubieboard2) does not show this > behaviour. The current https://github.com/linux-sunxi/linux-sunxi/tree/sunxi-3.4 kernel (commit d47d367036be38c5180632ec8a3ad169a4593a88) boots fine on my Cubieboard1 when compiled using sun4i_defconfig. Are you sure that you have not done some silly mistake, like accidentally using a wrong script.bin file or something like this? If you are really sure that you have not done anything wrong, then you can probably provide us with your kernel config, the script.bin file and the "bad" and "good" commit hashes. Or even better, try doing the bisecting job yourself using one of the numerous tutorials from the Internet. Here is one of these tutorials: http://www.metaltoad.com/blog/beginners-guide-git-bisect-process-elimination -- Best regards, Siarhei Siamashka -- 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.
