public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: Paul Walmsley <paul@booyaka.com>
Cc: linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
	beagleboard@googlegroups.com
Subject: Re: Recent OMAP git broken on Beagle
Date: Tue, 13 May 2008 19:37:11 +0200	[thread overview]
Message-ID: <4829D1C7.50200@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0805121427150.25982@utopia.booyaka.com>

Paul Walmsley wrote:
> Hello Dirk,
> 
> On Sat, 10 May 2008, Dirk Behme wrote:
> 
> 
>>-- cut --
>>
>>>git bisect bad
>>
>>757f0b4ad6b0fd4377c2ee512fc595b5778aa3ac is first bad commit
>>commit 757f0b4ad6b0fd4377c2ee512fc595b5778aa3ac
>>Author: Paul Walmsley <paul@pwsan.com>
>>Date:   Fri May 9 14:45:24 2008 -0700
>>
>>    powerdomain: convert pwrdm_mutex to rwsem
> 
> 
> Curious, this boots fine on 3430sdp, and there's nothing in that patch 
> that should affect Beagle in particular.  
> 
> Could you try building cdda2a9adbc5421f4857e0313afc6c189f422e25 and see if 
> that also breaks?  

Hmm, I think cdda2a9a... was the first one working for me:

http://marc.info/?l=linux-omap&m=121040218707239&w=2

I started with  "git bisect good cdda2a9a..."

If you like, I can recheck again. But would be better if anybody else 
could confirm this, just in case I missed anything. Hint, hint ;)

> Of the recent OMAP-specific patches, that's the one 
> that I would suspect.  And if that also breaks, maybe try the one 
> before it, 352b2e24c5cd193a40ae376fec85665f2660aeb1 ?

In a private mail I got:

-- cut --
To add another data point:  on the OMAP3 EVM warm boots fail as 
described, but cold boots complete successfully.
-- cut --

Unfortunately, he couldn't confirm which commit is failing for him yet.

On Beagle we currently boot using bootrom starting from MMC. Like with 
TWL, it seems that the pre-initialization by bootrom has some 
influence on kernel behaviour.

Thanks

Dirk



  reply	other threads:[~2008-05-13 17:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-10  6:49 Recent OMAP git broken on Beagle Dirk Behme
2008-05-10 18:09 ` Tony Lindgren
2008-05-10 19:19   ` Dirk Behme
2008-05-12 20:30     ` Paul Walmsley
2008-05-13 17:37       ` Dirk Behme [this message]
2008-05-13 17:41         ` Paul Walmsley

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=4829D1C7.50200@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --cc=beagleboard@googlegroups.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@booyaka.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