From: Dirk Behme <dirk.behme@googlemail.com>
To: linux-omap-open-source@linux.omap.com
Subject: Re: Git tree updated to 2.6.19-rc2
Date: Fri, 27 Oct 2006 17:30:04 +0200 [thread overview]
Message-ID: <454225FC.8060000@gmail.com> (raw)
In-Reply-To: <20061027125013.GB25245@atomide.com>
tony@atomide.com wrote:
> * Dirk Behme <dirk.behme@googlemail.com> [061024 19:16]:
>
>>Tony Lindgren wrote:
>>
>>>- CONFIG_DEBUG_LL hangs system
>>
>>For reference see
>>
>>http://linux.omap.com/pipermail/linux-omap-open-source/2006-October/008025.html
>>
>>and
>>
>>http://linux.omap.com/pipermail/linux-omap-open-source/2006-October/008054.html
>>
>>for an ugly workaround if you really need it. I really have
>>no clue what is broken here.
>
>
> Sounds like some clock is not enabled somewhere and serial write hangs.
Good idea! I think we had some clock rework meanwhile. Maybe
we have to move a clock enable to some earlier point if
using CONFIG_DEBUG_LL. Any idea which clock is worth looking at?
Best regards
Dirk
next prev parent reply other threads:[~2006-10-27 15:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 20:39 Git tree updated to 2.6.19-rc2 Tony Lindgren
2006-10-24 7:53 ` Komal Shah
2006-10-28 6:31 ` Aic23 NULL pointer exception, was: " Dirk Behme
2006-10-24 11:05 ` [PATCH] ARM: OMAP: Fixup omap-rtc (was: Git tree updated to 2.6.19-rc2) Jonathan McDowell
2006-10-24 17:57 ` David Brownell
2006-10-27 12:45 ` tony
2006-10-27 16:16 ` omap-keypad issues with 2.6.19-rc? Jonathan McDowell
2006-10-27 16:49 ` [PATCH] ARM: OMAP: Fix Amstrad Delta omap-keypad usage Jonathan McDowell
2006-10-24 16:16 ` Git tree updated to 2.6.19-rc2 Dirk Behme
2006-10-27 12:50 ` tony
2006-10-27 15:30 ` Dirk Behme [this message]
2006-10-29 22:09 ` Hiroshi DOYU
2006-10-26 20:22 ` David Brownell
2006-10-27 12:53 ` tony
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=454225FC.8060000@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.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