From owner-freebsd-arm@freebsd.org Mon Mar 18 20:57:33 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3D077154DDAA for ; Mon, 18 Mar 2019 20:57:33 +0000 (UTC) (envelope-from kayasaman@optiplex-networks.com) Received: from x-ray.optiplex-networks.com (mail.optiplex-networks.com [212.159.80.20]) (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 EAA457633E for ; Mon, 18 Mar 2019 20:57:31 +0000 (UTC) (envelope-from kayasaman@optiplex-networks.com) Received: from localhost (localhost [127.0.0.1]) by x-ray.optiplex-networks.com (Postfix) with ESMTP id 25DD772235D for ; Mon, 18 Mar 2019 20:57:29 +0000 (GMT) Received: from x-ray.optiplex-networks.com ([127.0.0.1]) by localhost (x-ray.optiplex-networks.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id SplFYIh63c5K for ; Mon, 18 Mar 2019 20:57:28 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by x-ray.optiplex-networks.com (Postfix) with ESMTP id D3DDE722DCE for ; Mon, 18 Mar 2019 20:57:28 +0000 (GMT) X-Virus-Scanned: amavisd-new at x-ray.optiplex-networks.com Received: from x-ray.optiplex-networks.com ([127.0.0.1]) by localhost (x-ray.optiplex-networks.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id rId2fBpPsJeY for ; Mon, 18 Mar 2019 20:57:28 +0000 (GMT) Received: from x220.optiplex-networks.com (unknown [192.168.0.167]) by x-ray.optiplex-networks.com (Postfix) with ESMTPSA id B2EF672235D for ; Mon, 18 Mar 2019 20:57:28 +0000 (GMT) Subject: Re: Options for FBSD support with LCD device - new project To: freebsd-arm@freebsd.org References: <8df902f6-20a3-31c4-71ac-91f5d5fdf50d@optiplex-networks.com> <0ecf23e129ca7ac6a92a01bbb34c03f1ac8c6dc8.camel@freebsd.org> <89f5b8d1ab0614ac8d88b5d5f1afc63e640c3c17.camel@freebsd.org> <4EB5C6C1-7DB9-4DEE-BB23-CD1259581271@jeditekunum.com> <004ddba628b94b80845d8e509ddcb648d21fd6c9.camel@freebsd.org> From: Kaya Saman Message-ID: <35b3045f-817c-5645-d78b-f20b08671850@optiplex-networks.com> Date: Mon, 18 Mar 2019 20:57:28 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: EAA457633E X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of kayasaman@optiplex-networks.com designates 212.159.80.20 as permitted sender) smtp.mailfrom=kayasaman@optiplex-networks.com X-Spamd-Result: default: False [-2.44 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_DN_NONE(0.00)[]; MX_GOOD(-0.01)[cached: mail.optiplex-networks.com]; NEURAL_HAM_SHORT(-0.27)[-0.265,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6871, ipnet:212.159.64.0/18, country:GB]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.86)[-0.855,0]; RCVD_COUNT_FIVE(0.00)[6]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.99)[-0.989,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[optiplex-networks.com]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-0.02)[country: GB(-0.09)] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Mar 2019 20:57:33 -0000 >>> I'm not sure what would give you that impression about i2c and >>> spi. I >>> belive they're well-supported on virtually every arm SOC we have >>> any >>> support for at all (except maybe amlogic/odroid and exynos, both of >>> which are rapidly bitrootting from neglect). We have command-line >>> tools to read and write data to i2c and spi devices from userland, >>> as >>> well as programmatic interfaces using ioctl() for higher- >>> performance >>> needs like a rasterized spi display. >>> >>> I'm the person who does most of the i2c and spi driver work for all >>> of >>> freebsd (not just arm), and it's something we use heavily in our >>> products at $work, so I tend to stay on top of it. >>> >>> To enable i2c or spi on any given platform, you usually do have to >>> touch some FDT code along the way. That's because almost always, >>> the >>> pins used by i2c or spi can be used for other things as well, so >>> the >>> default config (which we get by importing fdt source code from >>> linux) >>> usually isn't set up to enable those devices. >>> >>> To enable them you typically have to write and compile a small dts >>> overlay and set a variable in /boot/loader.conf to have that >>> overlay >>> loaded at boot time. None of that is hard, but there is quite a >>> bit to >>> explain, more than I can do right here in this email in the middle >>> of a >>> $work day. I guess maybe I should write a wiki page for it. >>> >>> -- Ian >> Finding this thread: https://forum.pine64.org/showthread.php?tid=6232 It seems that there is an official image for pine64 platform: http://ftp.freebsd.org/pub/FreeBSD/releases/arm64/aarch64/ISO-IMAGES/12.0/ Would anyone recommend the Pine64? Also which model as there are several: http://wiki.pine64.org/index.php/Main_Page#PINE64_Devices I could go with A64 or H64, though I wonder if there is a mode basic model out there? I don't need 4k or even HD graphics, or 'desktop' related stuff. A serial console would be fine or even vga just as long as the board is stable and robust and won't crash or hang often. Regards, Kaya