From owner-freebsd-arm@FreeBSD.ORG Tue Dec 2 15:09:29 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BCB4A718 for ; Tue, 2 Dec 2014 15:09:29 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1.freebsd.org (Postfix) with ESMTP id A850E615 for ; Tue, 2 Dec 2014 15:09:29 +0000 (UTC) Received: from msam.nabble.com (unknown [162.253.133.85]) by mwork.nabble.com (Postfix) with ESMTP id CCA49BED912 for ; Tue, 2 Dec 2014 07:09:23 -0800 (PST) Date: Tue, 2 Dec 2014 08:09:22 -0700 (MST) From: Scott Ellis To: freebsd-arm@freebsd.org Message-ID: <1417532962961-5970143.post@n5.nabble.com> Subject: Output of gpioctl MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 15:09:29 -0000 I submitted a bug report for gpioctl. http://freebsd.1045724.n5.nabble.com/Bug-195330-New-Reduce-gpioctl-output-td5968221.html At least I consider it a bug, but I haven't seen any response, so maybe it is not. Is there an example I'm missing where echoing the command line arguments in gpioctl's output is useful when doing a simple read or write? Seems an unnecessarily awkward 'feature' to workaround when used in a script or even just viewing the output until you understand what you are seeing. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Output-of-gpioctl-tp5970143.html Sent from the freebsd-arm mailing list archive at Nabble.com.