From: Mike Frysinger <vapier@gentoo.org>
To: Jie Zhang <jie@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: tests/monitor: set remotetimeout to gdb_load_timeout for remote targets
Date: Mon, 15 Mar 2010 07:16:00 -0000 [thread overview]
Message-ID: <201003150315.51005.vapier@gentoo.org> (raw)
In-Reply-To: <4B9D92CB.5010706@codesourcery.com>
[-- Attachment #1: Type: Text/Plain, Size: 994 bytes --]
On Sunday 14 March 2010 21:52:11 Jie Zhang wrote:
> On 03/15/2010 06:02 AM, Mike Frysinger wrote:
> > From: Jie Zhang<jie@codesourcery.com>
> >
> > Rather than relying on the default remotetimeout value (which might be
> > too small for some slower devices), use the existing gdb_load_timeout
> > config option to set it.
> >
> > Signed-off-by: Jie Zhang<jie@codesourcery.com>
> > Signed-off-by: Mike Frysinger<vapier@gentoo.org>
> > ---
> > 2010-03-14 Jie Zhang<jie@codesourcery.com>
> >
> > * gdb/testsuite/config/monitor.exp (gdb_load): New decimal variable.
> > Save remotetimeout setting in oldremotetimeout. Set remotetimeout to
> > $loadtimeout. Restore when done.
>
> I think this patch is not needed for Blackfin now. I believe any
> testcase in GDB can be loaded via gnICE in seconds now.
yes, your work on the gnICE/gnICE+ means the slow loading is a thing of the
past, but i think your changes here are reasonable and address a real problem
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-03-15 7:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 22:01 Mike Frysinger
2010-03-15 0:42 ` Joel Brobecker
2010-03-15 3:56 ` Jie Zhang
2010-03-15 1:52 ` Jie Zhang
2010-03-15 7:16 ` Mike Frysinger [this message]
2011-06-05 21:34 Mike Frysinger
2011-06-18 22:31 ` 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=201003150315.51005.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=jie@codesourcery.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