From: Prabhakar Kushwaha <prabhakar@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] doc: Add documentation for mpc85xx debugger support
Date: Tue, 13 Mar 2012 12:44:06 +0530 [thread overview]
Message-ID: <4F5EF3BE.1040209@freescale.com> (raw)
In-Reply-To: <20120307123047.6586D202C7F@gemini.denx.de>
Hi Wolfgang,
On Wednesday 07 March 2012 06:00 PM, Wolfgang Denk wrote:
> Dear Prabhakar Kushwaha,
>
> In message<4F572159.9020303@freescale.com> you wrote:
>>> Also, what's the "V1_V2" ? Are there also other systems (say, e500 v3
>>> cores), and are this not affected? We already have CONFIG_E500 and
>>> CONFIG_E500MC so CONFIG_E500_V1_V2 appears to belong to this group,
>>> but if I understand your intentions it does something completely
>>> unrelated.
>> V1_V2 is used because it applied to e500v1 and e500v2 not e500mc
>> processor. So CONFIG_E500MC cant be used. Also I cant use CONFIG_E500 as
>> it refer the entire e500 family which includes e500mc.
> Hm... I am not sure if CONFIG_E500 was supposed to include
> CONFIG_E500MC; it's nowhere documented. Let's assume it is.
>
> What happens if you enable this code on a E500MC system?
>
Debug restrictions are not valid for e500mc system.
At first sight it should not hurt e500mc execution (other than some
seemingly unnecessary steps). However i will check this point.
Regards,
Prabhakar
next prev parent reply other threads:[~2012-03-13 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 8:53 [U-Boot] [PATCH 1/4] doc: Add documentation for mpc85xx debugger support Prabhakar Kushwaha
2012-03-06 14:39 ` Wolfgang Denk
2012-03-07 3:32 ` Prabhakar Kushwaha
[not found] ` <071A08F2C6A57E4E94D980ECA553F874575244@039-SN1MPN1-005.039d.mgd.msft.net>
2012-03-07 6:24 ` Wolfgang Denk
2012-03-07 8:50 ` Prabhakar Kushwaha
2012-03-07 12:30 ` Wolfgang Denk
2012-03-13 7:14 ` Prabhakar Kushwaha [this message]
2012-03-14 9:35 ` Prabhakar Kushwaha
2012-03-14 19:30 ` Scott Wood
2012-03-15 3:51 ` Prabhakar Kushwaha
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=4F5EF3BE.1040209@freescale.com \
--to=prabhakar@freescale.com \
--cc=u-boot@lists.denx.de \
/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