From: srikanth krishnakar <skrishnakar@gmail.com>
To: John Linn <John.Linn@xilinx.com>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: Initialize DBCR0 for PPC440 targets
Date: Mon, 25 May 2009 12:21:06 +0530 [thread overview]
Message-ID: <6213bc560905242351r7682dcb2m898beef8b334e010@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40905242339l51ee5656ue388cde6da253287@mail.gmail.com>
Hi John,
I am not finding any conclusion of the plan to add DBCR0
initialization code to head_44x.S after this discussion :
http://www.nabble.com/Question-about-DBCR0-initialization-for-440-td2304904=
4.html#a23049044
Can you please comment ?
Thanks,
-Srikanth Krishnakar
On Mon, May 25, 2009 at 12:09 PM, Grant Likely
<grant.likely@secretlab.ca> wrote:
> On Mon, May 25, 2009 at 12:30 AM, srikanth krishnakar
> <skrishnakar@gmail.com> wrote:
>> Hello Grant,
>>
>> Is there any conclusion of the below discussion:
>>
>> http://www.nabble.com/Question-about-DBCR0-initialization-for-440-td2304=
9044.html
>>
>> Xilinx target (virtex5) hangs (while running GDBServer & KGDB) without
>> the DBCR0 initialization.
>>
>> Can you please comment on this ?
>
> IIRC, John Linn was hacking on a patch. =A0Search the mailing list
> archives for DBCR0.
>
> g.
>
> --
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
>
--=20
"The Good You Do, The Best You GET"
Regards
Srikanth Krishnakar
**********************
next prev parent reply other threads:[~2009-05-25 6:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 13:08 Initialize DBCR0 for PPC440 targets srikanth krishnakar
2009-05-19 23:53 ` David Gibson
2009-05-20 5:50 ` srikanth krishnakar
2009-05-20 6:00 ` David Gibson
2009-05-20 6:14 ` srikanth krishnakar
2009-05-25 7:04 ` Benjamin Herrenschmidt
2009-05-26 2:23 ` David Gibson
2009-05-25 6:30 ` srikanth krishnakar
2009-05-25 6:39 ` Grant Likely
2009-05-25 6:51 ` srikanth krishnakar [this message]
2009-05-26 15:11 ` John Linn
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=6213bc560905242351r7682dcb2m898beef8b334e010@mail.gmail.com \
--to=skrishnakar@gmail.com \
--cc=John.Linn@xilinx.com \
--cc=Linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).