From owner-freebsd-arm@freebsd.org Wed Jan 11 02:31:12 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA4CBCAA91A for ; Wed, 11 Jan 2017 02:31:12 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8CE641B7D for ; Wed, 11 Jan 2017 02:31:12 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from [127.0.0.1] (helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cR8gx-000B9w-Ou; Tue, 10 Jan 2017 18:31:12 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id v0B2VAfC042899; Tue, 10 Jan 2017 18:31:10 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Tue, 10 Jan 2017 18:31:10 -0800 From: Oleksandr Tymoshenko To: tech-lists Cc: freebsd-arm@freebsd.org Subject: Re: config.txt on rpi3 and freebsd-12 Message-ID: <20170111023110.GA42860@bluezbox.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD/11.0-RELEASE-p2 (amd64) User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: tech-lists (tech-lists@zyxst.net) wrote: > Hello list, > > I'd like to do the following: > > [1] clock the speed on my rpi3 / turbo mode. Right now it just used > powerd. Am I getting turbo with powerd? dmesg suggests not. > > [2] use a mpeg4 key which I bought for this board from the rpi site. > > I know how to do this in a rpi3 supported linux. My questions are: > > [a] does /efi/config.txt have the same functionality on freebsd-12 as it > does on linux? [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: zyxst.net] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 02:31:12 -0000 tech-lists (tech-lists@zyxst.net) wrote: > Hello list, > > I'd like to do the following: > > [1] clock the speed on my rpi3 / turbo mode. Right now it just used > powerd. Am I getting turbo with powerd? dmesg suggests not. > > [2] use a mpeg4 key which I bought for this board from the rpi site. > > I know how to do this in a rpi3 supported linux. My questions are: > > [a] does /efi/config.txt have the same functionality on freebsd-12 as it > does on linux? Yes, config.txt is handled by VideoCore firmware, so it's OS-independent > [b] Can I expect the mpeg4 key to work? On rpi2 it should work, although I have never tried. On rpi3 it's not going to work because VCHI driver does not work there at the moment. There are several places in the code that assume size of pointer is equal to 32 bit with is not true for ARM64. So it will require some effort to get it right. It's on my TODO list and there is some progress but I can't provide any certain timeframe. -- gonzo