From: Kumar Gala <kumar.gala@freescale.com>
To: Corey Minyard <cminyard@mvista.com>
Cc: <linuxppc-dev@lists.linuxppc.org>, Kumar Gala <kumar.gala@motorola.com>
Subject: Re: Patch for debug setcontext
Date: Thu, 29 Jul 2004 14:30:19 -0500 [thread overview]
Message-ID: <BA214A7E-E195-11D8-8E6C-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <41090F9A.8000901@mvista.com>
On Jul 29, 2004, at 9:54 AM, Corey Minyard wrote:
> Kumar Gala wrote:
>
> > I'm guessing, this should really be #if defined(CONFIG_4xx) ||
> > defined(CONFIG_BOOKE)
> > There are a number of similar cases later in this code as well.
>
> That may be the case, but it is very confusing in entry.S. The dbcr0
> register seems to only be defined on 4xx processor, not on book E.
> Look, for instance, at load_4xx_dbcr0:, it is only defined if 4xx is
> enabled, not if book E is enabled.
Corey,
I think you may have an old linux-2.6 tree. I remember renaming
load_4xx_dbcr0 to just load_dbcr0 because of such issues. Hopefully a
newer tree (one with e500 support, if its going head_e500.S) should be
cleaner. If not, let me know.
- kumar
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-29 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 14:54 Patch for debug setcontext Corey Minyard
2004-07-29 15:58 ` Corey Minyard
2004-07-29 19:30 ` Kumar Gala [this message]
2004-07-30 2:27 ` Corey Minyard
2004-07-30 14:08 ` Kumar Gala
2004-08-06 21:39 ` Patch for debug setcontext, relative to 2.6.8 Corey Minyard
-- strict thread matches above, loose matches on Subject: below --
2004-07-28 4:09 Patch for debug setcontext Corey Minyard
2004-07-28 13:52 ` Kumar Gala
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=BA214A7E-E195-11D8-8E6C-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=cminyard@mvista.com \
--cc=kumar.gala@motorola.com \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.