From owner-freebsd-ports@FreeBSD.ORG Thu Nov 21 21:21:27 2013 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AF17ACC8 for ; Thu, 21 Nov 2013 21:21:27 +0000 (UTC) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id 8946B2753 for ; Thu, 21 Nov 2013 21:21:27 +0000 (UTC) Received: by be-well.ilk.org (Postfix, from userid 1147) id B5DD233C25; Thu, 21 Nov 2013 16:21:20 -0500 (EST) From: Lowell Gilbert To: Alexander Leidinger Subject: Re: Porting a software which uses INP_GPIO? References: <20131121214359.000006f6@unknown> Date: Thu, 21 Nov 2013 16:21:20 -0500 In-Reply-To: <20131121214359.000006f6@unknown> (Alexander Leidinger's message of "Thu, 21 Nov 2013 21:43:59 +0100") Message-ID: <44bo1d5u3z.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: ports@FreeBSD.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: ports@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Nov 2013 21:21:27 -0000 Alexander Leidinger writes: > I try to compile a software on FreeBSD which wants to use INP_GPIO, > OUTP_GPIO and some oder *GPIO* things. > > A quick googling shows me some raspberry pi sites. Is this something > linux-specific (so that I can forget this software on FreeBSD as long > as we don't gain something similar)? > > Searching for gpio in names of ports didn't show a hit and in the > basesystem includes I can't find it either. GPIO is a way to do pin assignments for a chip package at run-time. I use it on embedded platforms all the time, but it isn't normally available on a PC. There's a gpioctl(1) that should be able to set the a pin for input or output, as those flags indicate, or programmatically I guess it would be GPIO_PIN_INPUT or GPIO_PIN_OUTPUT in /usr/include/sys/gpio.h but again, you need to have the hardware for it.