public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: David Gibson <david@gibson•dropbear.id.au>
To: Ralph Blach <rblach@intrex•net>
Cc: Hollis Blanchard <hollis@austin•ibm.com>,
	embedded list <linuxppc-embedded@lists•linuxppc.org>
Subject: Re: DBCR0 reset?
Date: Wed, 30 Oct 2002 14:15:55 +1100	[thread overview]
Message-ID: <20021030031555.GM15643@zax> (raw)
In-Reply-To: <3DBF0764.10808@intrex.net>


On Tue, Oct 29, 2002 at 05:10:44PM -0500, Ralph Blach wrote:
> Hollis,
>
> The OS does this.  I send you the info on how to disable it tommorrow.

Please send it to the list as well - I've encountered this problem as
well.  Although it usually doesn't happen quite this quickly.

> Hollis Blanchard wrote:
> >Has anyone had problems with hardware breakpoints from external
> >debuggers? I'm using RISCWatch, which sets DBCR0 and IAC1 for me (yes
> >I've verified that). I'm then using 'echo > /proc/sys' to invoke my
> >code. However by the time I get to my sysctl proc handler, DBCR0 has
> >been reset from 0x80810000 to 0x00010000, hence IAC1 is ignored.
> >
> >I don't see much use of DBCR0, other than initialization and then save
> >during exception prologs and then restore during task restore. Can
> >anyone point me to where it might be reset?
> >
> >-Hollis

--
David Gibson			| For every complex problem there is a
david@gibson•dropbear.id.au	| solution which is simple, neat and
				| wrong.
http://www.ozlabs.org/people/dgibson

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-10-30  3:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-29 19:18 DBCR0 reset? Hollis Blanchard
2002-10-29 22:10 ` Ralph Blach
2002-10-30  3:15   ` David Gibson [this message]
2002-10-30 19:52 ` Matt Porter

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=20021030031555.GM15643@zax \
    --to=david@gibson$(echo .)dropbear.id.au \
    --cc=hollis@austin$(echo .)ibm.com \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    --cc=rblach@intrex$(echo .)net \
    /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