From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fernando Nasser To: Andrew Cagney Cc: Mark Salter , eliz@is.elta.co.il, gdb-patches@sources.redhat.com Subject: Re: set/show remotestopbits Date: Wed, 26 Sep 2001 13:18:00 -0000 Message-id: <3BB23766.B0B5A854@cygnus.com> References: <200109261227.f8QCRjr27498@deneb.localdomain> <1858-Wed26Sep2001164321+0300-eliz@is.elta.co.il> <200109261502.f8QF23T27912@deneb.localdomain> <3BB209FF.4050407@cygnus.com> <200109261720.f8QHKWK28267@deneb.localdomain> <3BB219B8.2090403@cygnus.com> <3BB23011.50D05907@cygnus.com> <3BB23682.2030805@cygnus.com> X-SW-Source: 2001-09/msg00367.html Andrew Cagney wrote: > > > Anyway, I agree with Andrew's argument that some parameters are > > not necessarily tied to the remote protocol. With that argument in mind, > > the remoteXXXX's cause a little confusion ("remote target" vs. "remote > > target that uses the remote protocol" -- "remote" seems to be > overloaded). > > > > Serial and parallel sound nice. What if we have some things that can > > apply to any "remote" (non-native) target and is not specific to the > > communication link. (I am trying to think of an example -- the name of > > a log file, perhaps? Can you think of some other one?). > > Perhaphs ``set remote ..'' should have been ``set target remote ...'' or > ``set protocol remote ...'' or ``set remote-protocol ...''. (But > remote-protocol is also poorly defined). > > Anyway, the entire syntax will need to be reviewed again soon. At > present GDB assumes a single active target with a single interface. > While it doesn't need to be solved now, we do need to start thinking > about multiple targets with multiple interfaces and how to specify them. > for instance, how to show the serial settings for interface foo. > > I'll add the framework for ``set serial ''' and PR the need to deprecate > ``set remotebaud''. > Great. We will wait for you to do the "kick-off" for the syntax change debate. Regards, Fernando -- Fernando Nasser Red Hat - Toronto E-Mail: fnasser@redhat.com 2323 Yonge Street, Suite #300 Toronto, Ontario M4P 2C9