From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2202 invoked by alias); 10 Jul 2013 18:10:01 -0000 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 Received: (qmail 2177 invoked by uid 89); 10 Jul 2013 18:09:58 -0000 X-Spam-SWARE-Status: No, score=-6.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Wed, 10 Jul 2013 18:09:57 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r6AI9t2C003155 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 10 Jul 2013 14:09:56 -0400 Received: from barimba (ovpn-113-131.phx2.redhat.com [10.3.113.131]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r6AI9suQ027643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 10 Jul 2013 14:09:55 -0400 From: Tom Tromey To: Yurij Grechishhev Cc: gdb-patches@sourceware.org Subject: Re: Setting parity for remote serial References: Date: Wed, 10 Jul 2013 18:10:00 -0000 In-Reply-To: (Yurij Grechishhev's message of "Wed, 10 Jul 2013 19:17:58 +0400") Message-ID: <87bo6affrh.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-07/txt/msg00290.txt.bz2 >>>>> "Yurij" == Yurij Grechishhev writes: Yurij> GDB doesn't support command to set parity for serial ports. So there Yurij> is a problem to connect target that use "odd" or "even" parity. Yurij> The one way is to set parity before launching gdb (stty for Linux or Yurij> MODE for Windows), but for Windows gdb sets parity to "none" during Yurij> connection. Yurij> I suggest using "set remoteparity " command for this. It looks reasonable to me. There are some formatting issues, but nothing too serious. Do you have a copyright assignment in place? If not, contact me off list and I will get you started on that. This would need at least a ChangeLog entry, documentation patch, and NEWS patch to be complete. A test case would be nice as well, though I can see how it would be hard to make it actually do anything :) Yurij> Do you plan to use "class serial" (set serial ...) for serial settings? Yurij> "set serial parity " is more convenient way. I didn't even know about "set serial". It seems like dead code; but I'd have to dig into the history there to find out. Tom