From: Dan Malek <dan@embeddededge.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linux-ppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [Edson.Seabra@cyclades.com: Re: BDI and 85xx]
Date: Mon, 14 Nov 2005 19:27:49 -0500 [thread overview]
Message-ID: <f1398690ca38921aacd6daf98935b5f2@embeddededge.com> (raw)
In-Reply-To: <475D0B8F-FF5A-44DC-9D03-7156AFE2AAB0@kernel.crashing.org>
On Nov 14, 2005, at 5:50 PM, Kumar Gala wrote:
> I'm not 100% sure this is even possible on some of the book-e variants.
I suspect we could if we didn't just keep whacking
the MSR with some constant value :-) What
happens if we just leave DE set all of the time?
I know as part of ptrace, etc. it can get manipulated,
but if we are debugging through COP we shouldn't
get to these software functions.
-- Dan
prev parent reply other threads:[~2005-11-15 0:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 15:20 [Edson.Seabra@cyclades.com: Re: BDI and 85xx] Marcelo Tosatti
2005-11-14 20:45 ` Kumar Gala
2005-11-14 15:53 ` Marcelo Tosatti
2005-11-14 22:43 ` Dan Malek
2005-11-14 22:50 ` Kumar Gala
2005-11-15 0:27 ` Dan Malek [this message]
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=f1398690ca38921aacd6daf98935b5f2@embeddededge.com \
--to=dan@embeddededge.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-embedded@ozlabs.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).