From: Corey Minyard <cminyard@mvista•com>
To: Kumar Gala <kumar.gala@freescale•com>
Cc: linuxppc-dev@lists•linuxppc.org, Kumar Gala <kumar.gala@motorola•com>
Subject: Re: Patch for debug setcontext
Date: Thu, 29 Jul 2004 21:27:49 -0500 [thread overview]
Message-ID: <4109B225.8020604@mvista.com> (raw)
In-Reply-To: <BA214A7E-E195-11D8-8E6C-000393DBC2E8@freescale.com>
I'm using stock 2.6.7. Is there a different kernel I should be using?
-Corey
Kumar Gala wrote:
>
> 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-30 2:27 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
2004-07-30 2:27 ` Corey Minyard [this message]
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=4109B225.8020604@mvista.com \
--to=cminyard@mvista$(echo .)com \
--cc=kumar.gala@freescale$(echo .)com \
--cc=kumar.gala@motorola$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/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