Date: Tue, 02 Dec 2014 11:40:58 -0800 From: Rui Paulo <rpaulo@me.com> To: Scott Ellis <scott@jumpnowtek.com> Cc: freebsd-arm@freebsd.org Subject: Re: Output of gpioctl Message-ID: <DEFBE974-848E-4B82-B54E-9C023E0541A9@me.com> In-Reply-To: <1417532962961-5970143.post@n5.nabble.com> References: <1417532962961-5970143.post@n5.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 2, 2014, at 07:09, Scott Ellis <scott@jumpnowtek.com> wrote: >=20 > I submitted a bug report for gpioctl. >=20 > = http://freebsd.1045724.n5.nabble.com/Bug-195330-New-Reduce-gpioctl-output-= td5968221.html >=20 > At least I consider it a bug, but I haven't seen any response, so > maybe it is not. >=20 > 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? >=20 > 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. I think this was some leftover debugging code. I've considered removing = it yesterday when I converted it to use gpio(3). I think it's time to = do it now. Thanks, -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DEFBE974-848E-4B82-B54E-9C023E0541A9>