From: Prabhakar Kushwaha <prabhakar@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/4] powerpc/85xx:Update NOR code base to support debugger
Date: Tue, 13 Mar 2012 10:58:24 +0530 [thread overview]
Message-ID: <4F5EDAF8.1060608@freescale.com> (raw)
In-Reply-To: <20120307120544.104FF202C7F@gemini.denx.de>
Hi Wolfgang,
On Wednesday 07 March 2012 05:35 PM, Wolfgang Denk wrote:
> Dear Prabhakar Kushwaha,
>
> In message<4F56DEB0.6060500@freescale.com> you wrote:
>>>> + _mas0 = MAS0_TLBSEL(1) |
>>>> + MAS0_ESEL(CONFIG_DEBUGGER_TEMP_TLB);
>>> You are using an undocumented CONFIG_ option here.
>> This CONFIG_ is defined as part of documentation patch sent in this series
> CONFIG_ options must be documented in the README.
Sure
>>>> +#if defined(CONFIG_E500_V1_V2)&& !defined(CONFIG_SYS_RAMBOOT)
>>> What if no such debug support is needed, and code size hurts?
>> sure it will. I agree with you.
>> But this piece of code overcome debug restriction of e500 and e500v2
>> cores and I think fixing restriction is a good way to go.
> What do we do to disable this code if no debug support is needed, and
> the code size is considered critical?
i will put this piece of code under #if defined
(CONFIG_DEBUGGER_TEMP_TLB).
This piece of code will only be enabled when someone wants debugging
here. And the requirement is temporary TLB.
>>>> +#define CONFIG_DEBUGGER_TEMP_TLB 3
>>> Undocumented!
>>>
>> This CONFIG_ is defined as part of documentation patch sent in this series
> This is not sufficient, see above.
i will add the description.
Regards,
Prabhakar
prev parent reply other threads:[~2012-03-13 5:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 8:54 [U-Boot] [PATCH 3/4] powerpc/85xx:Update NOR code base to support debugger Prabhakar Kushwaha
2012-03-06 14:45 ` Wolfgang Denk
2012-03-07 4:06 ` Prabhakar Kushwaha
2012-03-07 12:05 ` Wolfgang Denk
2012-03-13 5:28 ` 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=4F5EDAF8.1060608@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 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.