Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Terry Guo <gnu.terry@gmail.com>
Cc: gdb-patches@sourceware.org, Ilija Kocho <ilijak@siva.com.mk>,
	 Terry Guo <terry.guo@arm.com>
Subject: Re: [patch] Add support for VFP d16 layout for Cortex-M4
Date: Thu, 19 Apr 2012 16:09:00 -0000	[thread overview]
Message-ID: <4F9035F4.7060101@eCosCentric.com> (raw)
In-Reply-To: <CAMCN_BipY7U4jKzGmXegn2+ViSn-MuoUeomFJZp8TCwZJWa22A@mail.gmail.com>

On 19/04/12 16:45, Terry Guo wrote:
> 
> I support this patch and your idea that using g_packet_guess is
> smarter and more flexible. I will try your patch out when I am at
> office tomorrow. What kind of board and gdb stub are you using?
> Currently I only have a STM32F4 board in hand but couldn't find a
> suitable gdb stub to access its FPU registers. Such functionality in
> OpenOCD is still in development. Do you have any recommendations on
> gdb stub for M4 board?

It is currently work in progress in eCos, but as yet uncommitted (far more
info and history than you need to know is here:
<http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001524>). Most
development is taking place on a Freescale Kinetis board, primarily by
Ilija Kocho, with me interfering along the way ;-). The eCos changes still
need to be reviewed before they're committed.

STM32F4 is likely to follow very soon after. Ironically, it's not likely
to be committed until we have some confidence that what goes into GDB will
match up with what the stub is doing! We wouldn't want to commit something
that has to change in an incompatible way.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
  **   Visit us at NEW:UK - the UK Embedded & Electronics Exhibition  **
  **   ARM Partner Pavilion/Stand #114. 18-19 April. Birmingham NEC   **
------["Si fractum non sit, noli id reficere"]------       Opinions==mine


  reply	other threads:[~2012-04-19 15:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 15:13 Jonathan Larmour
2012-04-19 15:58 ` Terry Guo
2012-04-19 16:09   ` Jonathan Larmour [this message]
2012-04-19 16:38     ` Terry Guo
2012-04-19 17:30       ` Jonathan Larmour
2012-04-20  7:51     ` Ilija Kocho
2012-04-20  8:31       ` Terry Guo
2012-04-20  8:54         ` Ilija Kocho
2012-04-20 11:44 ` Pedro Alves
2012-04-20 12:43 ` Pedro Alves
2012-04-20 13:20   ` Terry Guo
2012-04-20 13:22     ` Pedro Alves
2012-04-24  2:49   ` Jonathan Larmour
2012-04-26 20:28     ` Tom Tromey
2012-04-26 23:40       ` Jonathan Larmour
2012-04-27 15:55         ` Tom Tromey
2012-04-26  7:35 ` Sergio Durigan Junior
2012-04-26 15:07   ` Jonathan Larmour
2012-04-26 15:20     ` Pedro Alves
2012-04-26 15:29       ` Jonathan Larmour

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=4F9035F4.7060101@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gnu.terry@gmail.com \
    --cc=ilijak@siva.com.mk \
    --cc=terry.guo@arm.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