From: Kevin Hilman <khilman@deeprootsystems.com>
To: Cliff Brake <cliff.brake@gmail.com>
Cc: Nishanth Menon <menon.nishanth@gmail.com>,
Peter Tseng <tsenpet09@gmail.com>,
linux-omap@vger.kernel.org
Subject: Re: omap-pm: omap3_pm_defconfig no longer booting on Overo
Date: Mon, 10 May 2010 09:02:45 -0700 [thread overview]
Message-ID: <87eihjlp7e.fsf@deeprootsystems.com> (raw)
In-Reply-To: <j2lf96d234e1005071502q5a335634jd493a92ee970995b@mail.gmail.com> (Cliff Brake's message of "Fri\, 7 May 2010 18\:02\:40 -0400")
Cliff Brake <cliff.brake@gmail.com> writes:
> On Sat, May 1, 2010 at 11:32 AM, Nishanth Menon
> <menon.nishanth@gmail.com> wrote:
>> DISCLAIMER: I dont have a overo, so no idea if this would work.. but here
>> you go..
>>
>> Attached is a diff which probably will help you with the specific changes
>> needed for making pm boot on overo. hope it helps..
>>
>> a.diff is the change you would probably need for the overo file to fix it up
>> once for all
>>
>> the patch file is cleaning up the unnecessary BUG() in resource34xx.c which
>> caused the lockup -> elegant fix will potentially need more cleaning up..
>> but lets just leave it at the fact that srf is going to go away in a month
>> or so..
>
> Nishanth,
>
> These patches get my overo booting with the PM branch -- can they be
> pushed to the pm branch?
>
Hi Cliff,
The SRF fixup patches are already pushed to the PM branch. This will
at least allow a non-crashing boot on Overo. If you want to enable
DVFS on Overo, someone will have to test and validate Nishanth's other
change on Overo and (re)submit with proper changelog etc.
Thanks,
Kevin
prev parent reply other threads:[~2010-05-10 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 7:24 omap-pm: omap3_pm_defconfig no longer booting on Overo Peter Tseng
2010-04-30 18:54 ` Kevin Hilman
2010-05-01 3:12 ` Peter Tseng
2010-05-01 15:32 ` Nishanth Menon
2010-05-07 22:02 ` Cliff Brake
2010-05-10 16:02 ` 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=87eihjlp7e.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=cliff.brake@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=menon.nishanth@gmail.com \
--cc=tsenpet09@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.