From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22771 invoked by alias); 19 Jan 2011 21:55:05 -0000 Received: (qmail 22763 invoked by uid 22791); 19 Jan 2011 21:55:05 -0000 X-SWARE-Spam-Status: No, hits=-4.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 19 Jan 2011 21:55:00 +0000 Received: from mailhost2.vmware.com (mailhost2.vmware.com [10.16.67.167]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 72E8436006; Wed, 19 Jan 2011 13:54:59 -0800 (PST) Received: from msnyder-server.eng.vmware.com (promd-2s-dhcp138.eng.vmware.com [10.20.124.138]) by mailhost2.vmware.com (Postfix) with ESMTP id 6885C8ED20; Wed, 19 Jan 2011 13:54:59 -0800 (PST) Message-ID: <4D375DB2.1030906@vmware.com> Date: Wed, 19 Jan 2011 21:55:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.24 (X11/20101201) MIME-Version: 1.0 To: Kevin Buettner CC: "gdb-patches@sourceware.org" , Paul Koning Subject: Re: [RFC] configure.tgt: Update mips*-*-* to use remote-mips.o References: <20110119141436.2d8422fe@mesquite.lan> <20110119145041.32229ce7@mesquite.lan> In-Reply-To: <20110119145041.32229ce7@mesquite.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-01/txt/msg00418.txt.bz2 Kevin Buettner wrote: > On Wed, 19 Jan 2011 16:20:50 -0500 > Paul Koning 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. I think mips-*-elf is appropriate.