linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frank_rowand@mvista.com>
To: Kumar Gala <kumar.gala@motorola.com>
Cc: Dan Malek <dan@embeddededge.com>,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: pt_regs.dbcr0/1
Date: Tue, 04 Jun 2002 15:00:51 -0700	[thread overview]
Message-ID: <3CFD3893.9ECC91D4@mvista.com> (raw)
In-Reply-To: D68E7052-7802-11D6-B64C-003065BFB10E@motorola.com


Kumar Gala wrote:
>
> I am not seeing where the other debug registers that are associated with
> the debug state are being state changed and managed.  For example
> IAC{1-4} [breakpnt], DACs [watchpnts], DVCs are being handled.

The current kernel does not take advantage (use) the hardware breakpoint
and watchpoint registers.  Current jtag based debuggers are capable of
using these registers.  It would be extremely useful to add support
of these resources.

-Frank
--
Frank Rowand <frank_rowand@mvista.com>
MontaVista Software, Inc

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

  reply	other threads:[~2002-06-04 22:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-01  5:08 pt_regs.dbcr0/1 Paul Mackerras
2002-06-03  6:04 ` pt_regs.dbcr0/1 Armin
2002-06-04  1:23 ` pt_regs.dbcr0/1 Dan Malek
2002-06-04  5:02   ` pt_regs.dbcr0/1 Paul Mackerras
2002-06-04 17:22     ` pt_regs.dbcr0/1 Dan Malek
2002-06-04 21:34       ` pt_regs.dbcr0/1 Kumar Gala
2002-06-04 22:00         ` Frank Rowand [this message]
2002-06-04 22:10         ` pt_regs.dbcr0/1 Dan Malek
2002-06-04 21:55 ` pt_regs.dbcr0/1 Frank Rowand
2002-06-04 22:03   ` pt_regs.dbcr0/1 Paul Mackerras

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=3CFD3893.9ECC91D4@mvista.com \
    --to=frank_rowand@mvista.com \
    --cc=dan@embeddededge.com \
    --cc=frowand@mvista.com \
    --cc=kumar.gala@motorola.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=paulus@samba.org \
    /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).