public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagerm.com>
To: Ajit Kumar Agarwal <ajit.kumar.agarwal@xilinx.com>,
	 Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	 Michael Eager <eager@eagercon.com>,
	Vinod Kathail <vinodk@xilinx.com>,
	 Vidhumouli Hunsigida <vidhum@xilinx.com>,
	Nagaraju Mekala <nmekala@xilinx.com>
Subject: Re: [Patch, microblaze]: Fix for remote G Packet message too long error for baremetal.
Date: Sun, 20 Jul 2014 12:57:00 -0000	[thread overview]
Message-ID: <53CB1392.4060206@eagerm.com> (raw)
In-Reply-To: <48d1f24b-3924-44d4-85e3-a25ae7012647@BY2FFO11FD048.protection.gbl>

On 07/01/14 12:36, Ajit Kumar Agarwal wrote:
> Hello Pedro:
>
> Please find the updated patch. Incorporated review comments.
>
>      [Patch, microblaze]: Fix for remote G Packet message too long error for baremetal.
>
>      Prior to version MicroBlaze v8.10.a,EDK 13.1, XMD's gdbserver stub returned 57
>      registers in response to GDB's G request. Starting with version MicroBlaze
>      v8.10.a, EDK 13.1, XMD added the slr and shr register, for a count of 59
>      registers. This patch adds these registers to the expected G response. This patch
>      fixes the above problem for baremetal and also supports the backward compatibility.
>
>      ChangeLog:
>      2014-07-02  Ajit Agarwal  <ajitkum@xilinx.com>
>
>          * microblaze-tdep.c (microblaze_register_names): Add
>          the rshr and rslr register names.
>          (microblaze_gdbarch_init): Use of tdesc_has_registers.
>          Use of tdesc_find_feature. Use of tdesc_data_alloc.
>          Use of tdesc_numbered_register. Use of
>          microblaze_register_g_packet_guesses. Use of
>          tdesc_use_registers. Use of set_gdbarch_register_type.
>          (microblaze_register_g_packet_guesses): New.
>          * microblaze-tdep.h (microblaze_reg_num): Add
>          field MICROBLAZE_SLR_REGNUM MICROBLAZE_SHR_REGNUM
>          MICROBLAZE_NUM_REGS and MICROBLAZE_NUM_CORE_REGS.
>          (microblaze_frame_cache): Use of MICROBLAZE_NUM_REGS.
>          * features/microblaze-core.xml: New file.
>          * features/microblaze-stack-protect.xml: New file.
>          * features/microblaze-with-stack-protect.c: New file.
>          * features/microblaze-with-stack-protect.xml: New file.
>          * features/microblaze.xml: New file.
>          * features/microblaze.c: New file.
>          * features/Makefile (microblaze-with-stack-protect): Add
>          microblaze-with-stack-protect microblaze and
>          microblaze-expedite.
>          * regformats/microblaze-with-stack-protect.dat: New file.
>          * regformats/microblaze.dat: New file.
>          * doc/gdb.texinfo (MicroBlaze Features): New.
                                                     ^^^
                                          changed to Added.

Patch has trailing whitespace.

Committed 164224e9 without trailing whitespace.


-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077

  reply	other threads:[~2014-07-20  0:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12  8:56 Ajit Kumar Agarwal
2014-06-12 14:52 ` Michael Eager
2014-06-17 11:17 ` Pedro Alves
2014-06-18 11:06   ` Ajit Kumar Agarwal
2014-06-18 14:58     ` Michael Eager
2014-06-18 15:10     ` Pedro Alves
2014-06-18 15:30       ` Pedro Alves
2014-06-18 15:40       ` Ajit Kumar Agarwal
2014-06-18 15:54         ` Pedro Alves
2014-06-18 15:57           ` Ajit Kumar Agarwal
2014-06-18 19:56           ` Ajit Kumar Agarwal
2014-06-23 13:18             ` Pedro Alves
2014-06-23 19:36               ` Ajit Kumar Agarwal
2014-06-24  9:13                 ` Pedro Alves
2014-06-24 10:28                   ` Ajit Kumar Agarwal
2014-06-24 12:06                     ` Pedro Alves
2014-06-24 12:31                       ` Ajit Kumar Agarwal
2014-06-24 12:46                         ` Pedro Alves
2014-06-24 13:27                           ` Ajit Kumar Agarwal
2014-06-30 10:32                           ` Ajit Kumar Agarwal
2014-06-30 10:55                             ` Pedro Alves
2014-06-30 11:13                               ` Ajit Kumar Agarwal
2014-06-30 11:23                                 ` Pedro Alves
2014-06-30 16:29                                   ` Ajit Kumar Agarwal
2014-07-01 19:36                                   ` Ajit Kumar Agarwal
2014-07-20 12:57                                     ` Michael Eager [this message]
2014-06-30 14:47                             ` Michael Eager
2014-07-01 16:07                               ` Ajit Kumar Agarwal
2014-07-01 16:46                                 ` Michael Eager
2014-07-02 10:40                                   ` Ajit Kumar Agarwal
2014-06-24 14:11                       ` Michael Eager
2014-06-25 13:00                         ` Ajit Kumar Agarwal
2014-06-25 14:09                         ` 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=53CB1392.4060206@eagerm.com \
    --to=eager@eagerm.com \
    --cc=ajit.kumar.agarwal@xilinx.com \
    --cc=eager@eagercon.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nmekala@xilinx.com \
    --cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).