From: cyril@ti•com (Cyril Chemparathy)
To: linux-arm-kernel@lists•infradead.org
Subject: Forced HW_BREAKPOINT
Date: Wed, 01 Dec 2010 15:14:19 -0500 [thread overview]
Message-ID: <4CF6AC9B.9060500@ti.com> (raw)
In-Reply-To: <004f01cb917d$c04b4910$40e1db30$@deacon@arm.com>
Hi Will,
On 12/01/2010 12:32 PM, Will Deacon wrote:
> Cyril,
>
>> This was without a debugger connected. It is possible that I have
>> missed some top level debug enable in the SoC (haven't traced through
>> the entire logic yet).
>
> Please can you try this patch?
>
[...]
>
>
> This should cause the hw_breakpoint stuff to give up if monitor-mode
> cannot be enabled.
Could we also scale down the WARN_ONs in enable_monitor_mode?
Regards
Cyril.
next prev parent reply other threads:[~2010-12-01 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 23:56 Forced HW_BREAKPOINT Cyril Chemparathy
2010-12-01 9:54 ` Will Deacon
2010-12-01 16:17 ` Cyril Chemparathy
2010-12-01 16:28 ` Will Deacon
2010-12-01 16:48 ` Cyril Chemparathy
2010-12-01 17:32 ` Will Deacon
2010-12-01 20:14 ` Cyril Chemparathy [this message]
2010-12-02 9:37 ` Will Deacon
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=4CF6AC9B.9060500@ti.com \
--to=cyril@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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