From: Paul Koning <paul_koning@Dell.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFC] configure.tgt: Update mips*-*-* to use remote-mips.o
Date: Wed, 19 Jan 2011 22:02:00 -0000 [thread overview]
Message-ID: <B441FC53-6518-463F-B9F7-A4569FD9585E@Dell.com> (raw)
In-Reply-To: <20110119145041.32229ce7@mesquite.lan>
On Jan 19, 2011, at 4:50 PM, Kevin Buettner wrote:
> On Wed, 19 Jan 2011 16:20:50 -0500
> Paul Koning <paul_koning@Dell.com> wrote:
>
>> Shouldn't that just be for the MIPS based targets (if there still
>> are any left) that use this protocol?
>
> I want remote-mips.o to be enabled for the various mips*-elf targets.
> Would the patch be more palatable if I were to add a mips*-*-elf pattern
> for this case?
>
>> A lot of them probably just use the standard GDB remote protocol (I
>> know ours does -- NetBSD based).
>
> Keep in mind that adding remote-mips.o doesn't prevent the use of GDB's
> remote serial protocol. The "target remote" command will continue
> to work just as it always has.
>
> Also, I see the pattern "mips*-*-netbsd* | mips*-*-knetbsd*-gnu" in
> configure.tgt. So NetBSD wouldn't be affected by my change anyway.
Ok, that sounds good, thanks much.
paul
prev parent reply other threads:[~2011-01-19 21:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 21:20 Kevin Buettner
2011-01-19 21:39 ` Paul Koning
2011-01-19 21:50 ` Michael Snyder
2011-01-19 21:55 ` Kevin Buettner
2011-01-19 21:55 ` Michael Snyder
2011-01-20 0:55 ` Kevin Buettner
2011-01-20 5:58 ` Michael Snyder
2011-01-20 16:19 ` Ulrich Weigand
2011-01-21 1:14 ` Kevin Buettner
2011-01-21 12:44 ` Ulrich Weigand
2011-01-24 21:52 ` Kevin Buettner
2011-01-24 21:58 ` Joel Brobecker
2011-01-24 23:01 ` Kevin Buettner
2011-01-19 22:02 ` Paul Koning [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=B441FC53-6518-463F-B9F7-A4569FD9585E@Dell.com \
--to=paul_koning@dell.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.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