From: Mike Frysinger <vapier@gentoo.org>
To: Ralf Corsepius <ralf.corsepius@rtems.org>
Cc: gdb-patches@sourceware.org, toolchain-devel@blackfin.uclinux.org
Subject: Re: [PATCH v3] gdbserver: bfin: new port
Date: Wed, 15 Dec 2010 00:15:00 -0000 [thread overview]
Message-ID: <201012141914.28474.vapier@gentoo.org> (raw)
In-Reply-To: <4D07F7A5.4000101@rtems.org>
[-- Attachment #1: Type: Text/Plain, Size: 989 bytes --]
On Tuesday, December 14, 2010 18:03:01 Ralf Corsepius wrote:
> On 12/14/2010 10:47 PM, Mike Frysinger wrote:
> > diff --git a/gdb/gdbserver/configure.srv b/gdb/gdbserver/configure.srv
> > index 1e8fa30..ccf8381 100644
> > --- a/gdb/gdbserver/configure.srv
> > +++ b/gdb/gdbserver/configure.srv
> > @@ -67,6 +67,11 @@ case "${target}" in
> >
> > srv_mingw=yes
> > srv_mingwce=yes
> > ;;
> >
> > + bfin-*-*) srv_regobj=reg-bfin.o
> > + srv_tgtobj="linux-low.o linux-bfin-low.o"
> > + srv_linux_usrregs=yes
> > + srv_linux_thread_db=yes
> > + ;;
>
> Is this a generic bfin target or should is a bfin-*linux target.
>
> Seeing linux-*low.o on the right hand side of the case, my feeling is
> the $target should be fbin-*-linux*
we use gdbserver for bfin-uclinux (FLAT) and bfin-linux-uclibc (FDPIC)
targets. looking at the other targets in the configure file, i guess i should
restrict it to bfin-*-*linux* rather than bfin-*.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2010-12-15 0:15 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
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 [this message]
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=201012141914.28474.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=ralf.corsepius@rtems.org \
--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