Re: AM3517 fails to boot 3.16-rc5 device tree kernel

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

 



* Michael Welling <mwelling@xxxxxxxxxxx> [140718 08:05]:
> On Fri, Jul 18, 2014 at 09:40:48AM -0500, Michael Welling wrote:
> > On Fri, Jul 18, 2014 at 1:38 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote:
> > >
> > > Can you please enable debug_ll + earlyprintk and pass also earlyprintk
> > > in the kernel cmdline?
> > I will try this.
> 
> Adding the earlyprintk did not work. It still hangs without any
> messages.

If you have it enabled for the wrong UART it will always hang..
Maybe check you have the right port? 

> > > Hmm maybe double check your're booting device tree based kernel
> > > instead of legacy machine ID based kernel? The legacy booting should
> > > still work just fine and no changes has been made to it, but it will
> > > get removed shortly.
> 
> How do you determine which you are booting?

Looking at the dmesg, the earliest point you'll see it is from
"Machine model: " line, that's most likely different than for
legacy booting :)

And later on you'll see some DT only drivers get initialized
properly like pinctrl-single:

pinctrl-single 48002030.pinmux: 284 pins at pa fa002030 size 568
...

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux