From owner-freebsd-arm@FreeBSD.ORG Wed Feb 25 13:52:40 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8FC91264 for ; Wed, 25 Feb 2015 13:52:40 +0000 (UTC) Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 23794AD0 for ; Wed, 25 Feb 2015 13:52:40 +0000 (UTC) Received: by wesw55 with SMTP id w55so3741236wes.5 for ; Wed, 25 Feb 2015 05:52:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=i05bADMJaCMI8sNzZfTlO5Ecr0YiCPlWZCLXKFF8bXM=; b=Ot3la61nBeIdLYFKhGQlolpQWvaPw8XTT1hXeCjqjSGPolgUv4ZMuMvMhAR2TjYMeL OGWemptaI7U0C/JnroomWY6FP3qlNhYGlZf4jhkBZ9cVnkqg8y5zjRQAlXEoPJqU9Fea LtAsUDiVtYgmpcihxdZ5CboEQd20Exnjzj2l74fylfRClPt5qaRQYc7v6QcF0aRpEoel UBY5ji5NyWDRkp2L985AH2lFrTpw/7tVRSqFCa2Bd1V1vQjS72HNi3EwoqGJbBzitOvf fWuchvgW3t0Qhl8JoPaB3MnDe90451UDRu+HrFEHB1zEdyGEoo1nq3rFvOlubyesbtDn 8dfg== MIME-Version: 1.0 X-Received: by 10.180.8.98 with SMTP id q2mr39126223wia.80.1424872358497; Wed, 25 Feb 2015 05:52:38 -0800 (PST) Received: by 10.180.195.99 with HTTP; Wed, 25 Feb 2015 05:52:38 -0800 (PST) In-Reply-To: <54ECB24E.3030802@telting.org> References: <54ECB24E.3030802@telting.org> Date: Wed, 25 Feb 2015 10:52:38 -0300 Message-ID: Subject: Re: Beaglebone Implemented Features so far? From: Luiz Otavio O Souza To: Chris Telting Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-arm@freebsd.org" 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: Wed, 25 Feb 2015 13:52:40 -0000 On 24 February 2015 at 14:18, Chris Telting wrote: > Just wondering what the current state for the Beaglebone features are. > > GPIO is working. > > Interrupts on Input. Anyone working on this? Hi, The interrupt support for kernel devices was committed in r276207. You need a device driver that attaches directly to gpiobus to use GPIO interrupts ATM. Here is an example of such driver: https://people.freebsd.org/~loos/gpiointr.diff Userland notification of GPIO interrupt events should be available soon too. > > PWM and ADC. I find it funky that they are accessed though sysctl rather > than a device file and library like GPIO. Yes, I've plans to integrated these devices into GPIO framework, but I also have a few things to finish before I can look into that. > > Hardware watchdog? From what I can tell the ti_wdt0 exists but I don't see > any way to turn it on and control it. Check the watchdog(8) man page, I haven't tried myself but it seems to work. > > PRU's. Libpru is shaping up. PASM for assembly is in ports. > > i2c seems like it should work but so far it's a bust for me. I've seen > mention of people saying they have it working. I2C works fine, it is used to access the onboard PMIC and HDMI framer and I also have used the i2c to access a few other external devices (RTC, GPIO expanders, thermometers). > > SPI? CAM? No SPI support ATM, but it is not hard. > > Changing Pin Modes? It is specified on DTS data and cannot be changed at runtime. > > What about functioning as a USB client? > Not sure about this one. HTH, Luiz