From: Mike Frysinger <vapier@gentoo.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Andrew Stubbs <ams@codesourcery.com>,
toolchain-devel@blackfin.uclinux.org,
Daniel Jacobowitz <dan@codesourcery.com>
Subject: Re: [PATCH v2] gdbserver: bfin: new port
Date: Tue, 14 Dec 2010 17:48:00 -0000 [thread overview]
Message-ID: <201012141247.12591.vapier@gentoo.org> (raw)
In-Reply-To: <201012141739.52716.pedro@codesourcery.com>
[-- Attachment #1: Type: Text/Plain, Size: 1452 bytes --]
On Tuesday, December 14, 2010 12:39:27 Pedro Alves wrote:
> On Tuesday 14 December 2010 16:57:48, Mike Frysinger wrote:
> > thinking about it more, the gdb port atm doesnt support FDPIC. so if the
> > only contentious point of the gdbserver code is the FDPIC handling, then
> > i can simply drop that and revisit when the Blackfin/FDPIC core code is
> > merged.
>
> I think that's the best approach. Would it be easy to split
> the linux bits out of gdb/bfin-tdep.c into gdb/bfin-linux-tdep.c?
> You could even push the bare metal (bfin-elf?) bits first without
> any linux bits as a first step.
i imagine for someone who is a gdb expert, this would be trivial. but it
would require a bit of research on my side, so i'd prefer to not do this
initially. the code Joel is OK with supports both Blackfin bare metal and
Blackfin Linux/FLAT.
i'll open a tracker item to get this stuff eventually split out, but i dont
see it being done in a time frame that is before the gdb-7.3 release which i
really want to be a part of.
> Please also get rid of gdb/config/bfin/bfin.mt -- .mt files have
> long since been eliminated from gdb, the code that would go there you
> already have in configure.tgt.
i couldnt find documentation on this file (or mts in general) so i was
hesitant to touch it. the only thing we have in there is to set the TDEPFILES
variable, but i guess that too is no longer used anywhere ?
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-12-14 17:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 9:29 [PATCH v2] gdb: " Mike Frysinger
2010-12-09 9:31 ` [PATCH v2] gdbserver: " Mike Frysinger
2010-12-13 18:44 ` Pedro Alves
2010-12-13 19:24 ` Mike Frysinger
2010-12-14 9:37 ` Andrew Stubbs
2010-12-14 15:10 ` Mike Frysinger
2010-12-14 16:31 ` Pedro Alves
2010-12-14 16:58 ` Mike Frysinger
2010-12-14 17:16 ` Andrew Stubbs
2010-12-14 17:26 ` Mike Frysinger
2010-12-15 11:54 ` Andrew Stubbs
2010-12-15 12:55 ` [toolchain-devel] " Mike Frysinger
2010-12-15 13:17 ` Andrew Stubbs
2010-12-14 17:40 ` Pedro Alves
2010-12-14 17:48 ` Mike Frysinger [this message]
2010-12-14 18:06 ` Pedro Alves
2010-12-14 18:21 ` Mike Frysinger
2010-12-15 16:54 ` Mike Frysinger
2010-12-14 6:03 ` [PATCH v2] gdb: " Joel Brobecker
2010-12-14 16:14 ` Mike Frysinger
2010-12-14 20:43 ` [PATCH v3] " Mike Frysinger
2010-12-14 21:31 ` Pedro Alves
2010-12-14 22:01 ` Mike Frysinger
2010-12-15 13:02 ` Mike Frysinger
2010-12-15 16:53 ` Pedro Alves
2010-12-15 17:08 ` Mike Frysinger
2010-12-15 18:01 ` Pedro Alves
2010-12-15 18:38 ` Mike Frysinger
2010-12-15 18:42 ` Pedro Alves
2010-12-15 18:16 ` Mike Frysinger
2010-12-15 18:25 ` Pedro Alves
2010-12-14 21:48 ` [PATCH v3] gdbserver: " Mike Frysinger
2010-12-14 23:03 ` Ralf Corsepius
2010-12-15 0:15 ` Mike Frysinger
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=201012141247.12591.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=ams@codesourcery.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=toolchain-devel@blackfin.uclinux.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