All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Michael Welling <mwelling@emacinc.com>
Cc: linux-omap@vger.kernel.org,
	Benoit Cousson <bcousson@baylibre.com>,
	paul@pwsan.com
Subject: Re: AM3517 fails to boot 3.16-rc5 device tree kernel
Date: Mon, 21 Jul 2014 00:17:23 -0700	[thread overview]
Message-ID: <20140721071723.GO18374@atomide.com> (raw)
In-Reply-To: <20140718150253.GA27360@sysresccd>

* Michael Welling <mwelling@emacinc.com> [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@atomide.com> 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

  reply	other threads:[~2014-07-21  7:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 23:40 AM3517 fails to boot 3.16-rc5 device tree kernel mwelling
2014-07-18  6:38 ` Tony Lindgren
2014-07-18 14:40   ` Michael Welling
2014-07-18 15:02     ` Michael Welling
2014-07-21  7:17       ` Tony Lindgren [this message]
2014-07-18 16:13     ` Michael Welling
2014-07-21  7:19       ` Tony Lindgren
2014-07-21  7:09     ` Tony Lindgren
2014-07-21 16:38       ` Michael Welling
2014-07-22  0:15         ` Michael Welling
2014-07-22  6:20           ` Tony Lindgren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140721071723.GO18374@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mwelling@emacinc.com \
    --cc=paul@pwsan.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.