From: Michael Eager <eager@eagerm.com>
To: Ajit Kumar Agarwal <ajit.kumar.agarwal@xilinx.com>,
Michael Eager <eager@eagercon.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Joel Brobecker <brobecker@adacore.com>
Cc: Vinod Kathail <vinodk@xilinx.com>,
Vidhumouli Hunsigida <vidhum@xilinx.com>,
Nagaraju Mekala <nmekala@xilinx.com>
Subject: Re: [Patch, microblaze]: Add slr and shr regs and little-endian breakpoint
Date: Wed, 21 May 2014 07:47:00 -0000 [thread overview]
Message-ID: <537C5A25.9000003@eagerm.com> (raw)
In-Reply-To: <dfcc599b-b040-446d-bd46-723b67dbf286@BL2FFO11FD042.protection.gbl>
On 05/20/14 23:20, Ajit Kumar Agarwal wrote:
>
>
> On 05/20/14 09:25, Ajit Kumar Agarwal wrote:
>> Hello Joel:
>>
>> I have split the patches as you have recommended and the following is the first of the patch.
>>
>> [Patch, microblaze]: Add slr and shr regs and little-endian breakpoint
>
>>> What is the relationship between adding slr/shr registers and little-endian breapoints?
>
> The shr/slr registers and little endian breakpoints are related as it fixed the common problem of Packet
> Transfer error when connecting to the target remote host through tar remote in gdb for microblaze.
What "common" problem? How do either of these changes related
to a packet transfer error?
These changes don't appear related. Split independent changes in to separate patches.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2014-05-21 7:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 16:25 Ajit Kumar Agarwal
2014-05-20 21:14 ` Michael Eager
2014-05-21 6:20 ` Ajit Kumar Agarwal
2014-05-21 7:47 ` Michael Eager [this message]
2014-05-21 12:55 ` Ajit Kumar Agarwal
2014-05-21 13:45 ` Joel Brobecker
2014-05-22 17:58 ` Ajit Kumar Agarwal
2014-05-22 19:44 ` Michael Eager
2014-05-23 4:17 ` Ajit Kumar Agarwal
2014-05-23 5:57 ` Eli Zaretskii
2014-05-23 7:21 ` Michael Eager
2014-05-23 7:35 ` Eli Zaretskii
2014-05-21 13:41 ` Ajit Kumar Agarwal
2014-05-21 14:06 ` Pedro Alves
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=537C5A25.9000003@eagerm.com \
--to=eager@eagerm.com \
--cc=ajit.kumar.agarwal@xilinx.com \
--cc=brobecker@adacore.com \
--cc=eager@eagercon.com \
--cc=gdb-patches@sourceware.org \
--cc=nmekala@xilinx.com \
--cc=vidhum@xilinx.com \
--cc=vinodk@xilinx.com \
/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