ARM: Voipac i.MX25: Support with device tree on v3.8-rc1 or later

ARM: Voipac i.MX25: Support with device tree on v3.8-rc1 or later

[David Linares]

Hi guys,

I have just signed up to this distribution list to try to get some support/understanding of an issue I am having when switching from kernel v3.7.3 to v3.8-rc1.
I am using a Voipac i.MX25 and on v3.7.3, barebox correctly loads the kernel and my board is correctly up and running.
After switching to v3.8-rc1 (in order to get some fixes for a few drivers), barebox doesn't seem to load the kernel anymore, or the kernel initialization doesn't go very far as I don't see any kernel message.
So I had a look at the commits between the two kernel versions and I noticed a commit for iMX25 to use devicetree, so I am pretty sure that would explain my problems at kernel loading time as it is the only commit affecting the boot.
Is there somebody on this mailing list that could help me with devicetree?
At first I would just need to verify that the parameters sent by the bootloader are still correct for devicetree and maybe get a few hints on how to debug this issue and see how far the init has gone.

Thank you very much,
Best regards,
David
 		 	   		  

Re: ARM: Voipac i.MX25: Support with device tree on v3.8-rc1 or later

[Sascha Hauer]

On Sun, Jan 20, 2013 at 12:51:57PM +0000, David Linares wrote:
> 
> Hi guys,
> 
> I have just signed up to this distribution list to try to get some
> support/understanding of an issue I am having when switching from
> kernel v3.7.3 to v3.8-rc1.  I am using a Voipac i.MX25 and on v3.7.3,
> barebox correctly loads the kernel and my board is correctly up and
> running.  After switching to v3.8-rc1 (in order to get some fixes for
> a few drivers), barebox doesn't seem to load the kernel anymore, or
> the kernel initialization doesn't go very far as I don't see any
> kernel message.  So I had a look at the commits between the two kernel
> versions and I noticed a commit for iMX25 to use devicetree, so I am
> pretty sure that would explain my problems at kernel loading time as
> it is the only commit affecting the boot.  Is there somebody on this
> mailing list that could help me with devicetree?  At first I would
> just need to verify that the parameters sent by the bootloader are
> still correct for devicetree and maybe get a few hints on how to debug
> this issue and see how far the init has gone.

You should try git bisect to find the offending commit. Once you found
it it should be easy to track the problem down, or at least refer to the
exact commit breaking it. earlyprintk might also be an option to get
some messaged out of the non booting kernel.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |