From: Kevin Hilman <khilman@deeprootsystems.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Low level debugging using CONFIG_EARLY_PRINTK=y, omap-debug branch removed
Date: Thu, 17 Dec 2009 15:38:15 -0800 [thread overview]
Message-ID: <874onp41eg.fsf@deeprootsystems.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0912171603040.12561@utopia.booyaka.com> (Paul Walmsley's message of "Thu\, 17 Dec 2009 16\:04\:17 -0700 \(MST\)")
Paul Walmsley <paul@pwsan.com> writes:
> On Wed, 16 Dec 2009, Shilimkar, Santosh wrote:
>
>> I tried this on couple of boards and at least it doesn't work with the
>> options and mentioned bootargs. The low level debug prints are still not
>> coming on console.
>>
>> I haven't debugged it though.
>
> It works on Beagle, at least. That's the only one that I've tested so
> far.
>
I've been using the earlyprink patch for PM debug on several OMAP3
boards without any problems.
Kevin
prev parent reply other threads:[~2009-12-17 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 0:53 Low level debugging using CONFIG_EARLY_PRINTK=y, omap-debug branch removed Tony Lindgren
2009-12-16 9:07 ` Shilimkar, Santosh
2009-12-17 23:04 ` Paul Walmsley
2009-12-17 23:38 ` Kevin Hilman [this message]
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=874onp41eg.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox