public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: OMAP <Linux-omap-open-source@linux.omap.com>
Subject: Re: Recent git kernels and OSK
Date: Wed, 04 Oct 2006 11:03:54 +0200	[thread overview]
Message-ID: <452378FA.9050604@gmail.com> (raw)
In-Reply-To: <452280A5.5080805@gmail.com>

Dirk Behme wrote:
>> Just checked it. Seems that recent git on OSK is really broken. 
>> Enabling lowlevel debug last thing I get is kernel command line output 
>> [3]. On my last working kernel next output would be clock stuff [2]
>  
>> Any ideas?
> 
> Seems to me that it hangs in arch/arm/mach-omap1/clock.c in 
> omap1_clk_init in

As already mentioned in my last mail, this seems to be 
related to broken low level debug.

Doing some more debugging (with low level debug disabled 
now) shows that at least until "ARM: OMAP: DSPGW: mailbox 
log cleanup" [1] everything is okay. Then, with all changes 
including "ARM: OMAP: DSPGW: Peripheral (kfunc) control" [2] 
it seems to be broken.

So maybe DSPGW changes cause the trouble on OSK. Can anybody 
with DSPGW knowledge re-check this on OSK?

Many thanks,

Dirk

[1]
http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=commit;h=0992816784c16d294b884c15fde6fe469a18a01f

[2]
http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=commit;h=0a1de60c0d0f0c9f634a8673a1918f716c2cdcad

  reply	other threads:[~2006-10-04  9:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-02 22:35 Recent git kernels and OSK Philip Balister
2006-10-02 23:29 ` David Brownell
2006-10-03 13:55 ` Dirk Behme
2006-10-03 15:24   ` Dirk Behme
2006-10-04  9:03     ` Dirk Behme [this message]
     [not found]       ` <4523892B.3000505@balister.org>
2006-10-04 13:27         ` Dirk Behme
2006-10-06  9:58       ` 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=452378FA.9050604@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