From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mx28 spl power cpu clock configuration
Date: Wed, 25 Jan 2012 17:50:39 +0100 [thread overview]
Message-ID: <201201251750.39571.marek.vasut@gmail.com> (raw)
In-Reply-To: <6EA3E0BCC03CC34B89B01BD57ECBC718F27241@POBOX.postoffice.danego.net>
> Hi Fabio,
>
> > Could you please post a patch with your proposed change so that we can
> > test it?
>
> I was hoping for a suggestion from you, as you know this SoC far better
> than me. Currently I am trying different solutions. Even though they
> prevent the system from hanging up, they still don't enable me to step
> through the code.
From your previous email, it looked like that was proper solution. You can still
send a patch so we can test and proceed further in sync.
> And since therey's no problem with normal operation, I
> think they aren't worth anything unless they fix instruction stepping.
What do you mean?
>
> But as Marek, says: Instruction stepping this section can fail for another
> reason.
I never said such sentence.
M
>
> Cheers,
>
> Robert.
next prev parent reply other threads:[~2012-01-25 16:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 14:40 [U-Boot] mx28 spl power cpu clock configuration Robert Deliën
2012-01-25 15:04 ` Marek Vasut
2012-01-25 15:38 ` Fabio Estevam
2012-01-25 16:36 ` Robert Deliën
2012-01-25 16:50 ` Marek Vasut [this message]
2012-01-25 17:01 ` Robert Deliën
2012-01-25 17:12 ` Marek Vasut
2012-01-25 17:26 ` Robert Deliën
2012-01-25 17:32 ` Marek Vasut
2012-01-26 11:44 ` Robert Deliën
2012-01-30 20:31 ` Fabio Estevam
2012-01-30 21:53 ` Marek Vasut
2012-01-30 22:17 ` Fabio Estevam
2012-01-30 23:26 ` Marek Vasut
2012-01-30 22:09 ` Robert Deliën
2012-01-26 18:32 ` Marek Vasut
2012-01-27 0:11 ` Fabio Estevam
2012-01-27 0:47 ` Marek Vasut
2012-01-27 8:40 ` Robert Deliën
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=201201251750.39571.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.de \
/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.