From: Dirk Behme <dirk.behme@googlemail.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: "Saint-Etienne, Eric" <e-saint-etienne@ti.com>,
linux-omap-open-source@linux.omap.com
Subject: Re: early printk
Date: Thu, 18 Jan 2007 19:06:02 +0100 [thread overview]
Message-ID: <45AFB70A.4010006@googlemail.com> (raw)
In-Reply-To: <EA12F909C0431D458B9D18A176BEE4A50969C4F1@dlee02.ent.ti.com>
Woodruff, Richard wrote:
>>>Did someone already released an early-printk patch?
>>
>>Do you mean something other than low level printk?
>>
>>Low level printk should work, see CONFIG_DEBUG_LL and
>>CONFIG_OMAP_LL_DEBUG_UART1 (or 2 or 3).
>
>
> Seems like there has been some noise around some RT'ish changes + Timers
> breaking some early printk's on the other lists. I've not tried a build
> recently to see if it affects OMAP at all.
At least on OSK (OMAP1) CONFIG_DEBUG_LL works with recent
git. Have no OMAP2 to test though.
Dirk
next prev parent reply other threads:[~2007-01-18 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070118101336.18C6B80778@linux.omap.com>
2007-01-18 10:58 ` early printk Saint-Etienne, Eric
2007-01-18 17:07 ` Tony Lindgren
2007-01-18 17:25 ` Woodruff, Richard
2007-01-18 18:06 ` Dirk Behme [this message]
2007-01-21 0:30 ` Saint-Etienne, Eric
2007-01-21 16:32 ` Dirk Behme
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=45AFB70A.4010006@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=e-saint-etienne@ti.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=r-woodruff2@ti.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