From: Grant Likely <grant.likely@secretlab.ca>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, John Linn <John.Linn@xilinx.com>,
Hollis Blanchard <hollisb@us.ibm.com>,
Tirumala Reddy Marri <tmarri@amcc.com>
Subject: Re: Question about DBCR0 initialization for 440
Date: Fri, 17 Apr 2009 13:10:03 -0600 [thread overview]
Message-ID: <fa686aa40904171210y56835f98jfa4f3e08d97930aa@mail.gmail.com> (raw)
In-Reply-To: <1239995087.7210.19.camel@pasglop>
On Fri, Apr 17, 2009 at 1:04 PM, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
> On Fri, 2009-04-17 at 13:07 -0500, Hollis Blanchard wrote:
>> On Friday 17 April 2009 12:22:37 Josh Boyer wrote:
>> > On Fri, Apr 17, 2009 at 11:46 AM, John Linn <John.Linn@xilinx.com> wro=
te:
>> > > Josh, any thoughts on putting this into head_44x.S?
>> >
>> > The code in the fsl file looks like the right solution. =A0I do have a=
n
>> > odd question though, in that it's hard for the
>> > kernel to really know if something like a BDI is running. =A0Namely,
>> > that config option doesn't cover RiscWatch in an obvious manner.
>>
>> Yeah, setting DBCR0 would interfere with all JTAG probes. The ifdef mean=
ds you
>> can't support both a JTAG debugger and hardware breakpoints in the same
>> binary? Now that's an annoying restriction.
>
> Might be worth checking if external debug is enabled, and override it
> only if it's not.
ppc440x5_um.pdf says that both can be enabled.
g.
--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-04-17 19:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 20:33 Question about DBCR0 initialization for 440 John Linn
2009-04-15 16:24 ` Tirumala Reddy Marri
2009-04-17 15:46 ` John Linn
2009-04-17 17:22 ` Josh Boyer
2009-04-17 18:07 ` Hollis Blanchard
2009-04-17 19:04 ` Benjamin Herrenschmidt
2009-04-17 19:10 ` Grant Likely [this message]
2009-04-17 20:30 ` John Linn
2009-04-17 20:35 ` Josh Boyer
2009-04-17 20:41 ` John Linn
2009-04-17 20:54 ` Josh Boyer
2009-04-17 20:50 ` Hollis Blanchard
2009-04-17 20:57 ` John Linn
2009-04-17 18:57 ` Grant Likely
2009-04-17 18:58 ` John Linn
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=fa686aa40904171210y56835f98jfa4f3e08d97930aa@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=John.Linn@xilinx.com \
--cc=benh@kernel.crashing.org \
--cc=hollisb@us.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=tmarri@amcc.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;
as well as URLs for NNTP newsgroup(s).