From: Prabhakar Kushwaha <prabhakar@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4][v2] doc:Add documentation for e500 external debugger support
Date: Wed, 21 Mar 2012 22:24:16 +0530 [thread overview]
Message-ID: <4F6A07B8.7010502@freescale.com> (raw)
In-Reply-To: <4F6A024B.4030200@freescale.com>
Hi Scott,
Thanks for reviewing it. Please find my reply in-lined.
On Wednesday 21 March 2012 10:01 PM, Scott Wood wrote:
> On 03/20/2012 11:42 PM, Prabhakar Kushwaha wrote:
>> diff --git a/README b/README
>> index 8964672..48e50ed 100644
>> --- a/README
>> +++ b/README
>> @@ -3347,6 +3347,20 @@ Low Level (hardware related) configuration options:
>> be used if available. These functions may be faster under some
>> conditions but may increase the binary size.
>>
>> +E500 (MPC85xx) External Debug Support
>> +-------------------------------------
>> +-CONFIG_E500
>> + Enables BOOKE e500 family.It includes e500, e500v2 e500mc,
>> + e5500 processor etc.
> This is not a debug-specific option. What's wrong with putting both of
> these options under the existing "85xx CPU Options" section?
Yes. Both CONFIG_E500 and CONFIG_SYS_PPC_E500_DEBUG_TLB can be put
under "85xx CPU Options".
I made separate section thinking of CONFIG_SYS_PPC_E500_DEBUG_TLB as it
required for overcoming e500 v1/v2 debugging restriction.
i will send the updated patch.
--Prabhakar
prev parent reply other threads:[~2012-03-21 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 4:42 [U-Boot] [PATCH 1/4][v2] doc:Add documentation for e500 external debugger support Prabhakar Kushwaha
2012-03-21 16:31 ` Scott Wood
2012-03-21 16:54 ` Prabhakar Kushwaha [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=4F6A07B8.7010502@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