From owner-freebsd-arm@freebsd.org Mon Mar 18 14:07:46 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 DE4BC15405B7 for ; Mon, 18 Mar 2019 14:07:45 +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 70EE78AB6C for ; Mon, 18 Mar 2019 14:07:44 +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 743F5722D4E for ; Mon, 18 Mar 2019 14:07:42 +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 dmf9lEQhFLmE for ; Mon, 18 Mar 2019 14:07:41 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by x-ray.optiplex-networks.com (Postfix) with ESMTP id 55F1A722D05 for ; Mon, 18 Mar 2019 14:07:41 +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 q8_FeyqbOOTx for ; Mon, 18 Mar 2019 14:07:41 +0000 (GMT) Received: from x220.optiplex-networks.com (unknown [192.168.0.167]) by x-ray.optiplex-networks.com (Postfix) with ESMTPSA id 3D60B7222F8 for ; Mon, 18 Mar 2019 14:07:41 +0000 (GMT) To: freebsd-arm@freebsd.org From: Kaya Saman Subject: Options for FBSD support with LCD device - new project Message-ID: Date: Mon, 18 Mar 2019 14:07:41 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 70EE78AB6C 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.61 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[6]; spamhaus_xbl(0.00)[20.80.159.212.g4jphcdwjq2eyvr5ppcbhhxyzq.zen.dq.spamhaus.net]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.99)[-0.988,0]; RCVD_TLS_LAST(0.00)[]; MX_GOOD(-0.01)[mail.optiplex-networks.com]; NEURAL_HAM_SHORT(-0.46)[-0.458,0]; DMARC_NA(0.00)[optiplex-networks.com]; NEURAL_HAM_MEDIUM(-0.83)[-0.835,0]; IP_SCORE(-0.02)[country: GB(-0.09)]; 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)[] 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 14:07:46 -0000 Hi, I am looking for a solution capable of running FreeBSD that I will be able to add an LCD or OLED display to. The project spec is fairly simple: - Use an embedded SoC solution - Fit inside a DIN enclosure eg. https://eng.italtronic.com/products/embedded_box_en/ - Have an LCD or OLED display with or without keypad eg. https://www.crystalfontz.com/product/cfa633rdiks-rs232-alphanumeric-lcd-display-16x2#undefined Currently I am thinking about an Odroid C1+ with a Crystalfontz display as they are well supported by Lcdproc. Already I have gone through: https://wiki.freebsd.org/FreeBSD/arm/Odroid-C1 https://www.freebsd.org/platforms/arm.html https://wiki.freebsd.org/FreeBSD/arm but just wanted to see if anyone has any experience with this type of setup or could offer some advice? I guess connection to the LCD would be another question as the most common two options would be GPIO or USB. In the case of GPIO is there a way to simulate an serial connection or are there better supported boards with serial or usb headers on them already? There are LCD modules made specifically for these boards which do sit on top of the GPIO however, do these work with Lcdproc? http://www.lcdproc.org/hardware.php3 Thanks. Kaya From owner-freebsd-arm@freebsd.org Mon Mar 18 14:41:54 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 589FA1541638 for ; Mon, 18 Mar 2019 14:41:54 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1695C8BE98 for ; Mon, 18 Mar 2019 14:41:53 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: by mail-wm1-x330.google.com with SMTP id t124so13050081wma.4 for ; Mon, 18 Mar 2019 07:41:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=mE0W71fEqi6R+GlgbZGI2dZpCLH1PccJQwv3NBVfvXA=; b=ey2/ih7ELvc19eDO2X8uU5qoQmoqWXUuAtwkq0j6dWAdnVu6qmTxre0tv/hP0tSayV RDrMu4oB6TaZnViqPd5NKWYs1Etz60sWzlHbZSdi98wWSLv57QblIFJFLK7hAqEqy3ly ZbZjeXZebKNs2fbHmhThTKtMnv6nAFPWoZ0oCCL8rzqyR1umUxhd8AdMe/Z5UUdf+9Ql ofA8cRARAxtA7OI7UJbLzgKEVsPhm452+u32gZNDS9LDGXgWen9R5C3xMTwWIadmk18e +f7xvG26jDFX7z/SPJg3GoMFbufeDxCrRlTPnxlYS1zSr2Al2abvZFNnKfRDeF6VgBmC 82Zw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=mE0W71fEqi6R+GlgbZGI2dZpCLH1PccJQwv3NBVfvXA=; b=BPbZXXfnMfVvM0qB/pL3so8yeydsXS2++y439ea1DzY4JuhtXBda72cgO81YedNZRK VdGaRUCCn70wNIXLcEOutKPSEv0N9XJbO7F9f4vS+HsJ30o2LizqNKvs6IHTLPxeO8qh zNW1+LdzkyEmlDME2D6Y3X6xEFeWvazd9XEuIA6WksHr7LubrVvOiL5wrQUUl8T6BeKd ZNyF+qlRobQay4kGd1mJywq47Kpsth9puPmH39z9o/2I03bg2bOsg3s+c/KTz09MtZkA +f1DydbVJY3C4hZ4b8167dCJB/hxFF6NuVE+ojB8B3K0NwZu2nn7HFOkFPb5fAKF3xrA GaMg== X-Gm-Message-State: APjAAAWwwLKZ1bTvLAnXw5uKWaL+W5t5/ACQnqJ+TGpcXWvQWWdax44j tA5/c1UYuDqtbtJ+I5EJ/wGo7No/yGGrGuT3HTCPV184PB5LHg== X-Google-Smtp-Source: APXvYqxfV5We4yIlVGUSQe2WYTPlKqKcPeDuYE/H87oCHxmZlhH3wD9qVacJjPBHZpga9C3wsvZCKtzo0Np+FLxXxZw= X-Received: by 2002:a1c:9694:: with SMTP id y142mr11098861wmd.98.1552920111783; Mon, 18 Mar 2019 07:41:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Michael Zhilin Date: Mon, 18 Mar 2019 17:41:39 +0300 Message-ID: Subject: Re: Options for FBSD support with LCD device - new project To: Kaya Saman , "freebsd-arm@freebsd.org" , Mori Hiroki X-Rspamd-Queue-Id: 1695C8BE98 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=ey2/ih7E; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mizhka@gmail.com designates 2a00:1450:4864:20::330 as permitted sender) smtp.mailfrom=mizhka@gmail.com X-Spamd-Result: default: False [-6.75 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.97)[-0.971,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[0.3.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.77)[ip: (-9.32), ipnet: 2a00:1450::/32(-2.36), asn: 15169(-2.09), country: US(-0.07)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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 14:41:54 -0000 Hi, I'm not sure it's exact you're looking for, but here is link: https://qiita.com/yamori813/items/ae66330ccbf6fe6bd5ab Platform is MIPS32/Atheros. It has LCD and keypad. Details: ask Hiroki Mori please. Thanks! On Mon, Mar 18, 2019 at 5:08 PM Kaya Saman wrote: > > Hi, > > > I am looking for a solution capable of running FreeBSD that I will be > able to add an LCD or OLED display to. > > > The project spec is fairly simple: > > - Use an embedded SoC solution > > - Fit inside a DIN enclosure eg. > https://eng.italtronic.com/products/embedded_box_en/ > > - Have an LCD or OLED display with or without keypad eg. > > https://www.crystalfontz.com/product/cfa633rdiks-rs232-alphanumeric-lcd-display-16x2#undefined > > > > Currently I am thinking about an Odroid C1+ with a Crystalfontz display > as they are well supported by Lcdproc. > > Already I have gone through: > > https://wiki.freebsd.org/FreeBSD/arm/Odroid-C1 > > https://www.freebsd.org/platforms/arm.html > > https://wiki.freebsd.org/FreeBSD/arm > > > but just wanted to see if anyone has any experience with this type of > setup or could offer some advice? > > > I guess connection to the LCD would be another question as the most > common two options would be GPIO or USB. In the case of GPIO is there a > way to simulate an serial connection or are there better supported > boards with serial or usb headers on them already? > > There are LCD modules made specifically for these boards which do sit on > top of the GPIO however, do these work with Lcdproc? > http://www.lcdproc.org/hardware.php3 > > > Thanks. > > > Kaya > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Mon Mar 18 15:56:38 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 750F41544F2B for ; Mon, 18 Mar 2019 15:56:38 +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 16D638F204 for ; Mon, 18 Mar 2019 15:56:36 +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 3CC20722420; Mon, 18 Mar 2019 15:56:34 +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 CrklaHk2b3i9; Mon, 18 Mar 2019 15:56:33 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by x-ray.optiplex-networks.com (Postfix) with ESMTP id 53C97722DD9; Mon, 18 Mar 2019 15:56:33 +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 MGQ078wuI-NQ; Mon, 18 Mar 2019 15:56:33 +0000 (GMT) Received: from x220.optiplex-networks.com (unknown [192.168.0.167]) by x-ray.optiplex-networks.com (Postfix) with ESMTPSA id 1DFE8722420; Mon, 18 Mar 2019 15:56:33 +0000 (GMT) Subject: Re: Options for FBSD support with LCD device - new project To: Michael Zhilin , "freebsd-arm@freebsd.org" , Mori Hiroki References: From: Kaya Saman Message-ID: <8df902f6-20a3-31c4-71ac-91f5d5fdf50d@optiplex-networks.com> Date: Mon, 18 Mar 2019 15:56:33 +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-Language: en-US X-Rspamd-Queue-Id: 16D638F204 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.40 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_COUNT_FIVE(0.00)[6]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-0.99)[-0.990,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[optiplex-networks.com]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mail.optiplex-networks.com]; NEURAL_HAM_SHORT(-0.25)[-0.249,0]; NEURAL_HAM_MEDIUM(-0.83)[-0.832,0]; IP_SCORE(-0.02)[country: GB(-0.09)]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:6871, ipnet:212.159.64.0/18, country:GB]; MID_RHS_MATCH_FROM(0.00)[] Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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 15:56:38 -0000 Many thanks Michael! I have also found this guide too: https://www.rototron.info/lcdproc-tutorial-for-raspberry-pi/ It goes through the GPIO connection using a Raspberry Pi and a CF HD44780 compatible display. This should also work in a similar fashion with the Odroid. Regards, Kaya On 3/18/19 2:41 PM, Michael Zhilin wrote: > Hi, > > I'm not sure it's exact you're looking for, but here is link: > https://qiita.com/yamori813/items/ae66330ccbf6fe6bd5ab > > Platform is MIPS32/Atheros. It has LCD and keypad. > Details: ask Hiroki Mori please. > > Thanks! > > On Mon, Mar 18, 2019 at 5:08 PM Kaya Saman > > wrote: > > > Hi, > > > I am looking for a solution capable of running FreeBSD that I will be > able to add an LCD or OLED display to. > > > The project spec is fairly simple: > > - Use an embedded SoC solution > > - Fit inside a DIN enclosure eg. > https://eng.italtronic.com/products/embedded_box_en/ > > - Have an LCD or OLED display with or without keypad eg. > https://www.crystalfontz.com/product/cfa633rdiks-rs232-alphanumeric-lcd-display-16x2#undefined > > > > > Currently I am thinking about an Odroid C1+ with a Crystalfontz > display > as they are well supported by Lcdproc. > > Already I have gone through: > > https://wiki.freebsd.org/FreeBSD/arm/Odroid-C1 > > https://www.freebsd.org/platforms/arm.html > > https://wiki.freebsd.org/FreeBSD/arm > > > but just wanted to see if anyone has any experience with this type of > setup or could offer some advice? > > > I guess connection to the LCD would be another question as the most > common two options would be GPIO or USB. In the case of GPIO is > there a > way to simulate an serial connection or are there better supported > boards with serial or usb headers on them already? > > There are LCD modules made specifically for these boards which do > sit on > top of the GPIO however, do these work with Lcdproc? > http://www.lcdproc.org/hardware.php3 > > > Thanks. > > > Kaya > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to > "freebsd-arm-unsubscribe@freebsd.org > " > From owner-freebsd-arm@freebsd.org Mon Mar 18 16:08:02 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 1BF7E1545861 for ; Mon, 18 Mar 2019 16:08:02 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2m.ore.mailhop.org (outbound2m.ore.mailhop.org [54.149.155.156]) (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 446C68FB19 for ; Mon, 18 Mar 2019 16:08:01 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1552925274; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=XWe4xFIBMQLchsXuH+B7Qxi0u9LbK67TKuCP1lKHadVwhWP7T0zzacqIRUvkcJYh2lUx1Bj56Dry3 fNzI2jPOt8xIt3jjL0iBuRvxhxf+UK1N7Tkgde+khUOpVUj0RCA8wpCgWLmqGjskpkR3JdVuZ7QaU5 491vqZbC8ewPBUkeodwKpZ/S/4pGNa8WFXaqnfBgqFiCLWGlpm8eefeS/kyNHhWt53D0lEACEJ6tP9 3vIoDwS7VpCB9Waan+VkGPV6DE0mo6MXT9UfPhn+6d73qu8IqDsBFjQz/fFAoaskeHJG41a22FU61c +bO5WmHS0SZfuhNpLSBJuP6emlhq8cA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=FU+ie8xVlwRsgy/QM4kNRX+0MI7LVLyRPIenXi004wA=; b=RK3s8Xy+aQxPpghHbacLlI7PJ+rrTHDALJA3hQvKsNdq5XT0m9X+kp8ZN9Xpe97uazm54onfvhWBO ZxY+YkxZc5hk1JsxvQBmkDfkteUTKI2GFaQNOqvrnrEiB8aKmLRbLF5frJFdPY7gVevbsQc4Hp3M/k hhF3m4V2pebPTdvqCl55dAMwxPgQ09ggMnKZrcTWO/ATUtHTLi8Cn/gb+we3CjlOReRlYZ2QCz63U4 IErD/iRO+FexSxfAA6vgcBq2+6nV2MRYWi4EfRYqxrpOb5cvMprNFp3KVMsA7Em0S+/UkbZ1l1QX7H bP89IFcFqZi5blNOJZo8+LqUANXwW2g== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=FU+ie8xVlwRsgy/QM4kNRX+0MI7LVLyRPIenXi004wA=; b=Vtp5+yzeoqtFxQl1wSFUmokBRctrsoZ5TH4L0jvPwA9Dxto7Tcwz0oh9cl9GGGdCKS4dKnF8QcdXQ ipK3NLFytXpjoOGzUT7k5HsZI+14bMOjleyWzr0PjgPX/G5Bz8fWTB7Sr68NWBxuOn9/vEwt9JsZls d7wvxglUrE6YfwzY6n4VMvLQE2ZU/Qj4G216NiBHX1dc5jA+Ye4dL3oeuVjue2tYL94PImVUvamgVB VXxoYfx4mhiAvMAacvmynbXbhenhRe5ks2eBW4v//wTUNQkoVAIHL/Nc0hvsqb92V/fKLvrVMgX690 sUDVrmnoq+dsOuR97rouIdmZDEl0TgA== X-MHO-RoutePath: aGlwcGll X-MHO-User: fafc110a-4997-11e9-befd-af03bedce89f X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id fafc110a-4997-11e9-befd-af03bedce89f; Mon, 18 Mar 2019 16:07:52 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x2IG7o0m062413; Mon, 18 Mar 2019 10:07:50 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <0ecf23e129ca7ac6a92a01bbb34c03f1ac8c6dc8.camel@freebsd.org> Subject: Re: Options for FBSD support with LCD device - new project From: Ian Lepore To: Kaya Saman , Michael Zhilin , "freebsd-arm@freebsd.org" , Mori Hiroki Date: Mon, 18 Mar 2019 10:07:50 -0600 In-Reply-To: <8df902f6-20a3-31c4-71ac-91f5d5fdf50d@optiplex-networks.com> References: <8df902f6-20a3-31c4-71ac-91f5d5fdf50d@optiplex-networks.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 446C68FB19 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.984,0]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US] 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 16:08:02 -0000 On Mon, 2019-03-18 at 15:56 +0000, Kaya Saman wrote: > Many thanks Michael! > > > I have also found this guide too: > https://www.rototron.info/lcdproc-tutorial-for-raspberry-pi/ > > > It goes through the GPIO connection using a Raspberry Pi and a CF > HD44780 compatible display. This should also work in a similar > fashion > with the Odroid. > Before you go too far down this path, you should probably be aware that odroid isn't really supported on freebsd. There was some initial work done to support the original C1, but it was basically a drive-by commit which hasn't been actively supported since then. You should consider some well-supported board, something based on an Allwinner or imx6 SOC would be a good candidate. Gpio sounds like about the worst way to connect a display. Something based on i2c or SPI would be a much better choice. Usually the so- called "usb" solutions are really just forms of i2c or SPI being bit- banged by an FTDI chip. Not a horrible solution, but probably not quite as efficient as native i2c or spi. -- Ian From owner-freebsd-arm@freebsd.org Mon Mar 18 17:34:24 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 549A21548167 for ; Mon, 18 Mar 2019 17:34:24 +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 15BA76C52F; Mon, 18 Mar 2019 17:34:22 +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 7C47D72235D; Mon, 18 Mar 2019 17:34:19 +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 tFDApk5FbRDw; Mon, 18 Mar 2019 17:34:19 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by x-ray.optiplex-networks.com (Postfix) with ESMTP id 32CA1722972; Mon, 18 Mar 2019 17:34:19 +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 fozQ6vSeBA_7; Mon, 18 Mar 2019 17:34:19 +0000 (GMT) Received: from x220.optiplex-networks.com (unknown [192.168.0.167]) by x-ray.optiplex-networks.com (Postfix) with ESMTPSA id 1649F72235D; Mon, 18 Mar 2019 17:34:19 +0000 (GMT) Subject: Re: Options for FBSD support with LCD device - new project To: Ian Lepore , "freebsd-arm@freebsd.org" References: <8df902f6-20a3-31c4-71ac-91f5d5fdf50d@optiplex-networks.com> <0ecf23e129ca7ac6a92a01bbb34c03f1ac8c6dc8.camel@freebsd.org> From: Kaya Saman Message-ID: Date: Mon, 18 Mar 2019 17:34:18 +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: <0ecf23e129ca7ac6a92a01bbb34c03f1ac8c6dc8.camel@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 15BA76C52F 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.08 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_COUNT_FIVE(0.00)[6]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[optiplex-networks.com]; NEURAL_HAM_LONG(-0.99)[-0.990,0]; IP_SCORE(-0.02)[country: GB(-0.09)]; MX_GOOD(-0.01)[cached: mail.optiplex-networks.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.14)[-0.140,0]; NEURAL_HAM_MEDIUM(-0.63)[-0.626,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)[] 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 17:34:24 -0000 On 3/18/19 4:07 PM, Ian Lepore wrote: > On Mon, 2019-03-18 at 15:56 +0000, Kaya Saman wrote: >> Many thanks Michael! >> >> >> I have also found this guide too: >> https://www.rototron.info/lcdproc-tutorial-for-raspberry-pi/ >> >> >> It goes through the GPIO connection using a Raspberry Pi and a CF >> HD44780 compatible display. This should also work in a similar >> fashion >> with the Odroid. >> > Before you go too far down this path, you should probably be aware that > odroid isn't really supported on freebsd. There was some initial work > done to support the original C1, but it was basically a drive-by commit > which hasn't been actively supported since then. > > You should consider some well-supported board, something based on an > Allwinner or imx6 SOC would be a good candidate. > > Gpio sounds like about the worst way to connect a display. Something > based on i2c or SPI would be a much better choice. Usually the so- > called "usb" solutions are really just forms of i2c or SPI being bit- > banged by an FTDI chip. Not a horrible solution, but probably not > quite as efficient as native i2c or spi. > > -- Ian > > That was great advise! Thanks Ian :-) Looking at the FreeBSD support for these types of boards, it seems the most common devices are either the Raspberry Pi family and the Beagleboard Black and Green. It looks like both Raspberry Pi 2B and the Beaglebone Black have good support with FreeBSD and both offer SPI headers. I am not sure about the state of the Pi3 as the information comes up with unknown. I'm just reading through the wiki page for the BB Black: https://wiki.freebsd.org/FreeBSD/arm/BeagleBoneBlack right now trying to get a better understanding of things in general. It might be a good option as it sounds fairly easy to deploy FBSD on it. Regards, Kaya From owner-freebsd-arm@freebsd.org Mon Mar 18 18:15:04 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 BC3B3154931E for ; Mon, 18 Mar 2019 18:15:03 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound3d.ore.mailhop.org (outbound3d.ore.mailhop.org [54.186.57.195]) (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 C321D6DDF6 for ; Mon, 18 Mar 2019 18:15:02 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1552931932; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=QWLSyUQdulqOwPIFC45jybJdlfmYkowzXYJYG6iXzLydISxYsfXqrKZYRzWqTgn01OAQUNGWCoYOt 83WitGw4Z+igBPDG7kuBbKqquZipmUqI7SyW0U5VhOJnGWIvwTvufruO5zm5sUNKFpGmZxpQmiBZ/H L+fBj2WaXV5O7mcVo6a4gPau9FN7s0i1FUU4HdQHO1TV/bD28AiJtic2lD5dE2W7BvZC1dLPR6J5CY 8owtl/u4Yvkd0DpsCUD9xKmptKWH97MjPJUek6ISTllKiduI0FtPSw+V/YA2TQhO35iScUUEmLV6AL zP+HKh++H/vV66hZjTlbdC7ji/vbTtw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=OIET5aTYfmcOfVrg8pL5PpIGVFf6yK8QbXoMOkIQwBE=; b=eQCdmpsWJ0CrP9iwB2NpZVTLeMAQyG4QQmYVsoYkWI1UQTQ3GnVbsn3HxUKCtJ67lorD2D4Cl6M+E 0rUnC7RW4SGYsxRrvO41jdnRNT8ePgaJvq3ukkq7wB7bce+AwzIU6FsDeNjcUkpY09D8ZUqXl+8qst NdWPFh9Enij/hVPq+EawQmI1UAbY0RVp7CSYmSuSNvGYDQkAm2Y4Xbg0j9innPQHtLmIIVbAQ5GPRM eC4CGydbWMnlG9wvGbTLP+aGZc/i/m43djynWnRjDNPu1EjjVHN/PRVGqMcH+qN+mPgAwwdj6h7bjJ vtRZVIb2+MdlCheWFMrWIj59gEvSKIQ== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=OIET5aTYfmcOfVrg8pL5PpIGVFf6yK8QbXoMOkIQwBE=; b=lZPzzn3z7E+yRXVU1F4zJDLHtyUv5gsEHuEha+CjTQk8ju0heKhPMXfjR46SF03cDd58Qb7/w21ig 66kSpKKdb4jDoAyqD2Lif3SRTTdVAKR5KJ5lvzYONb1cvm1439X3lzF34fuuVtWl4Bqo0eP65dylyk jO+mS8yrDW+h3DzEGVb4gNKk2y9ZX8HGT/88npy8zM9UeNNIZoMMdkVMC955yTcxtnVl7d4PSCC3zD j859RaFbDAqNHO1vaAL9MJMOVGOtU5VCENyeKIkL2OhfHTjcCKb25mAtac4R2Api0J5TCinpRGxjU8 Jxg+1FNHwggeO8zCBZIPFDVHE9jYzIA== X-MHO-RoutePath: aGlwcGll X-MHO-User: 7be18f7e-49a7-11e9-9bb1-1f29e4676f89 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 7be18f7e-49a7-11e9-9bb1-1f29e4676f89; Mon, 18 Mar 2019 17:58:50 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x2IHwnlD062806; Mon, 18 Mar 2019 11:58:49 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <89f5b8d1ab0614ac8d88b5d5f1afc63e640c3c17.camel@freebsd.org> Subject: Re: Options for FBSD support with LCD device - new project From: Ian Lepore To: Kaya Saman , "freebsd-arm@freebsd.org" Date: Mon, 18 Mar 2019 11:58:49 -0600 In-Reply-To: References: <8df902f6-20a3-31c4-71ac-91f5d5fdf50d@optiplex-networks.com> <0ecf23e129ca7ac6a92a01bbb34c03f1ac8c6dc8.camel@freebsd.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: C321D6DDF6 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.990,0]; ASN(0.00)[asn:16509, ipnet:54.186.0.0/15, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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 18:15:04 -0000 On Mon, 2019-03-18 at 17:34 +0000, Kaya Saman wrote: > On 3/18/19 4:07 PM, Ian Lepore wrote: > > On Mon, 2019-03-18 at 15:56 +0000, Kaya Saman wrote: > > > Many thanks Michael! > > > > > > > > > I have also found this guide too: > > > https://www.rototron.info/lcdproc-tutorial-for-raspberry-pi/ > > > > > > > > > It goes through the GPIO connection using a Raspberry Pi and a CF > > > HD44780 compatible display. This should also work in a similar > > > fashion > > > with the Odroid. > > > > > > > Before you go too far down this path, you should probably be aware > > that > > odroid isn't really supported on freebsd. There was some initial > > work > > done to support the original C1, but it was basically a drive-by > > commit > > which hasn't been actively supported since then. > > > > You should consider some well-supported board, something based on > > an > > Allwinner or imx6 SOC would be a good candidate. > > > > Gpio sounds like about the worst way to connect a > > display. Something > > based on i2c or SPI would be a much better choice. Usually the so- > > called "usb" solutions are really just forms of i2c or SPI being > > bit- > > banged by an FTDI chip. Not a horrible solution, but probably not > > quite as efficient as native i2c or spi. > > > > -- Ian > > > > > > That was great advise! Thanks Ian :-) > > > Looking at the FreeBSD support for these types of boards, it seems > the > most common devices are either the Raspberry Pi family and the > Beagleboard Black and Green. > > > It looks like both Raspberry Pi 2B and the Beaglebone Black have > good > support with FreeBSD and both offer SPI headers. I am not sure about > the > state of the Pi3 as the information comes up with unknown. > > > I'm just reading through the wiki page for the BB Black: > https://wiki.freebsd.org/FreeBSD/arm/BeagleBoneBlack right now trying > to > get a better understanding of things in general. It might be a good > option as it sounds fairly easy to deploy FBSD on it. > > > Regards, > > > Kaya > I would never recommend that anybody use any flavor of rpi for any purpose at all. The hardware sucks, and the support is minimal, because all of us developers hate working on it (because it sucks so much). The BB isn't too bad, it's just ancient and crippled -- single core at low clock speeds. Really, an Allwinnner-based board is your best bet. I'll let the various users and supporters of the AW stuff recommend specific models (I don't have any AW hardware, I have all I can do supporting imx6 these days). The stuff you'll find on the wiki is mostly ancient news that hasn't been updated in years. -- Ian From owner-freebsd-arm@freebsd.org Mon Mar 18 18:59:27 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 A70E6154AA29 for ; Mon, 18 Mar 2019 18:59:27 +0000 (UTC) (envelope-from jedi@jeditekunum.com) Received: from a2i644.smtp2go.com (a2i644.smtp2go.com [103.47.206.132]) (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 0AB5071327 for ; Mon, 18 Mar 2019 18:59:15 +0000 (UTC) (envelope-from jedi@jeditekunum.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpservice.net; s=m4fue0.a1-4.dyn; x=1552936456; h=Feedback-ID: X-Smtpcorp-Track:To:Date:Subject:Message-Id:From:Reply-To:Sender: List-Unsubscribe; bh=2+ACoO+fKVPM0QVG/beYEFX1AksichKhQNX0jzo3feU=; b=xsm+K1sH JspK4HTZ/5s2+KZU5L4p9ugiYcQ9yjeQARlFHq1WU6TvxgGf1xgJe9GtSqg6Or2srFV6TJVOce2cW TwYVRfdvRz4AI9EmTGFB9y8deXpXSLSHg98YYiXur7VmrDS3bR6suxldbSNJStw4tUPFP/t7mzjJ3 TghFo6E5vla31vDa3Lj7B7xk/i7cSIDgaLYIykW6z5YaIktt+cDuy6lMTV6bMxSZMN7ugIgLK/K46 eWvJA449QeUyvPNhewnno5FK0JKffHUSBtQs+rYqdEuCgg+qEhpNm8TH9yT7iC27mWImO6ODDNHga 41FtjVeL63i+Jl9LTYgRiyENvA==; Received: from [10.66.228.43] (helo=SmtpCorp) by smtpcorp.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from ) id 1h5xTV-ED4uHo-N7; Mon, 18 Mar 2019 18:59:05 +0000 Received: from [10.162.213.37] (helo=takodana.opaxus.net) by smtpcorp.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from ) id 1h5xTV-wSEX6G-7N; Mon, 18 Mar 2019 18:59:05 +0000 Received: from [10.0.10.1] (174-20-17-78.mpls.qwest.net [174.20.17.78]) by takodana.opaxus.net (Postfix) with ESMTPSA id DEF8B26622; Mon, 18 Mar 2019 13:59:03 -0500 (CDT) From: Jedi Tek'Unum Message-Id: <4EB5C6C1-7DB9-4DEE-BB23-CD1259581271@jeditekunum.com> Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Options for FBSD support with LCD device - new project Date: Mon, 18 Mar 2019 13:59:02 -0500 In-Reply-To: <89f5b8d1ab0614ac8d88b5d5f1afc63e640c3c17.camel@freebsd.org> Cc: ian@freebsd.org To: freebsd-arm@freebsd.org References: <8df902f6-20a3-31c4-71ac-91f5d5fdf50d@optiplex-networks.com> <0ecf23e129ca7ac6a92a01bbb34c03f1ac8c6dc8.camel@freebsd.org> <89f5b8d1ab0614ac8d88b5d5f1afc63e640c3c17.camel@freebsd.org> X-Mailer: Apple Mail (2.3445.9.1) X-Smtpcorp-Track: 1h5xTVwSEb6G7N.M6p40mb_P Feedback-ID: 207158m:207158azGM_-I:207158sDWsPdZzId X-Report-Abuse: Please forward a copy of this message, including all headers, to X-Rspamd-Queue-Id: 0AB5071327 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=smtpservice.net header.s=m4fue0.a1-4.dyn header.b=xsm+K1sH X-Spamd-Result: default: False [-2.73 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; MX_INVALID(0.50)[greylisted]; MV_CASE(0.50)[]; TO_DN_NONE(0.00)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; URI_COUNT_ODD(1.00)[3]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[smtpservice.net:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_MED(-0.20)[132.206.47.103.list.dnswl.org : 127.0.3.2]; NEURAL_HAM_SHORT(-0.96)[-0.965,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; IP_SCORE(-0.77)[asn: 1299(-3.85), country: EU(-0.00)]; ASN(0.00)[asn:1299, ipnet:103.47.204.0/22, country:EU]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[smtpservice.net:s=m4fue0.a1-4.dyn]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[jeditekunum.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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 18:59:27 -0000 I=E2=80=99ve been lurking here for some time. Long time (commercial) = unix expert. Not much FBSD. I=E2=80=99m running Linux right now on NanoPi NEO (Allwinner H3) and NEO = 2 (Allwinner H5). Not because I love Linux (I don=E2=80=99t) but because = it works out of the box including I2C. I=E2=80=99d really like to use = FBSD on them. I hope that they will reach the same maturity as BB soon. Perhaps I=E2=80=99m wrong but my impression following this list and = searching around is that I2C and SPI are not =E2=80=9Cout of the box=E2=80= =9D with FBSD on these platforms. I=E2=80=99m not all that familiar with FDT. I=E2=80=99d like to learn = how to master it. If I understood it better I could probably bring = anything I needed to life. BUT, that is back burner to actually = completing the projects I=E2=80=99m trying to complete (where I just = need I2C access from user land). I really need those things to just work = out of the box for now - or have clear instructions on how to enable. In short I can=E2=80=99t use FBSD yet because it doesn=E2=80=99t appear = ready for these kinds of apps on these devices. I greatly appreciate all = the effort that has and is going on to get there. If I had the knowledge = I=E2=80=99d love to help, but I don=E2=80=99t currently. Perhaps I=E2=80=99ve just not searched and read enough to find the jewel = document that explains all the FDT magic in sufficient detail. By that I = mean *current* FDT magic (which is another confusing aspect as things = seem to be in flux). Any advice on these matters greatly appreciated. > On Mar 18, 2019, at 12:58 PM, Ian Lepore wrote: > I would never recommend that anybody use any flavor of rpi for any > purpose at all. The hardware sucks, and the support is minimal, > because all of us developers hate working on it (because it sucks so > much). >=20 > The BB isn't too bad, it's just ancient and crippled -- single core at > low clock speeds. >=20 > Really, an Allwinnner-based board is your best bet. I'll let the > various users and supporters of the AW stuff recommend specific models > (I don't have any AW hardware, I have all I can do supporting imx6 > these days). >=20 > The stuff you'll find on the wiki is mostly ancient news that hasn't > been updated in years. >=20 > -- Ian >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm = > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org = " From owner-freebsd-arm@freebsd.org Mon Mar 18 19:13:58 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 C0246154AEC9 for ; Mon, 18 Mar 2019 19:13:57 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2m.ore.mailhop.org (outbound2m.ore.mailhop.org [54.149.155.156]) (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 ECCDE71BEC for ; Mon, 18 Mar 2019 19:13:56 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1552936435; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=XXFfd9eDMaPgMMqvTpXNWHBB2Yqsn/ldklBnzd+o3/vpUAAR0PrfQDgstjDjks8wVRI1E1VcBQawH m39wSxwUARFi/mRMDNxuDELALGUi1siOoraTicl3BWwUISBQ1rWkiPRbdnwvto2tf/pF52lwsz45tJ 1JU/C00EM5UBWMNzQTlA/B5VL6AGCwAyIqqytmNp8ikjdAg1oQezW1JZtBr8E+ceqTaHAammAIickx 7VHmhju9zSrYmc/x0Qg74zL3NSM2J9mz9ajcrMeaaWAdaDkVEBRCCRF5SxeGmwxDfB6DYBUdbDkEh5 zPgg7IaXAZyUohfNgAs9S8x/D7btcwA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=KDjECLaTlDr5sQnbJ0eqB6sbsblkYNHE8PivkB5poyA=; b=gxoUB02sX0vUOLllWogQZ/TjqrDNKaleABSphjr927uowuGzbb12d3tcdOYKfoDYxGvh+siiIOkWx qDvJqj1eUMyjpwhqPz5/TWO304hPZYoh34fasjPK1/erbymmBn1C437dF6RB9JAF7AKYoTj1Bh2Ncl exjCyX9b2vtKtMr65iLag5DExGO4qEForCOx6QE/sVaW4XHxAd4icwcDN34xqWHm0OU/NAM79f5a5A 9jQ9mtih9n5jUsz/YAebLEFd8yRTD4b7r+BXDDptNXo2IzwHfltdIjD2Mh0A1xLNyRqu2luhu0i0ye CAEPyqRX+/VXVooicuTIfMQQlqxI02g== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=KDjECLaTlDr5sQnbJ0eqB6sbsblkYNHE8PivkB5poyA=; b=CY4WG70AVkf7Pd8weRC7ZWOPz+wMR1EWYzRMC3K0DaLQTeIdFm2BLBY4Z+Ls9Fgz+k2IBoUWD0SsK 6yZS0Q4K8/Np0FdTTbotEWleDWAKWUdtHFDIhcDTYfBL8m594HKa8eWj+El4cyPSVSGmUak15oZgPZ knZAPbI8IRO1XJKmLqLi8dfGJf/mYxzjKlBygD2Ga50u6DqBkshLBB1Vr6yM5+AUBwmx385J1ClFF9 ABcFbAUhORnmDRJfiCTAzLl8kM8yEtua1d38W8ydZelsJuL1pmSyNkoNJz8/oyAjTPUiDtOVE1j74k zDswQ0rV5QbtmsSsMCApKdhi9b4+hDQ== X-MHO-RoutePath: aGlwcGll X-MHO-User: f82a7bdb-49b1-11e9-befd-af03bedce89f X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id f82a7bdb-49b1-11e9-befd-af03bedce89f; Mon, 18 Mar 2019 19:13:54 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x2IJDrph062961; Mon, 18 Mar 2019 13:13:53 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <004ddba628b94b80845d8e509ddcb648d21fd6c9.camel@freebsd.org> Subject: Re: Options for FBSD support with LCD device - new project From: Ian Lepore To: "Jedi Tek'Unum" , freebsd-arm@freebsd.org Date: Mon, 18 Mar 2019 13:13:53 -0600 In-Reply-To: <4EB5C6C1-7DB9-4DEE-BB23-CD1259581271@jeditekunum.com> References: <8df902f6-20a3-31c4-71ac-91f5d5fdf50d@optiplex-networks.com> <0ecf23e129ca7ac6a92a01bbb34c03f1ac8c6dc8.camel@freebsd.org> <89f5b8d1ab0614ac8d88b5d5f1afc63e640c3c17.camel@freebsd.org> <4EB5C6C1-7DB9-4DEE-BB23-CD1259581271@jeditekunum.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: ECCDE71BEC X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_SHORT(-0.99)[-0.994,0]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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 19:13:58 -0000 On Mon, 2019-03-18 at 13:59 -0500, Jedi Tek'Unum wrote: > I’ve been lurking here for some time. Long time (commercial) unix > expert. Not much FBSD. > > I’m running Linux right now on NanoPi NEO (Allwinner H3) and NEO 2 > (Allwinner H5). Not because I love Linux (I don’t) but because it > works out of the box including I2C. I’d really like to use FBSD on > them. I hope that they will reach the same maturity as BB soon. > > Perhaps I’m wrong but my impression following this list and searching > around is that I2C and SPI are not “out of the box” with FBSD on > these platforms. > > I’m not all that familiar with FDT. I’d like to learn how to master > it. If I understood it better I could probably bring anything I > needed to life. BUT, that is back burner to actually completing the > projects I’m trying to complete (where I just need I2C access from > user land). I really need those things to just work out of the box > for now - or have clear instructions on how to enable. > > In short I can’t use FBSD yet because it doesn’t appear ready for > these kinds of apps on these devices. I greatly appreciate all the > effort that has and is going on to get there. If I had the knowledge > I’d love to help, but I don’t currently. > > Perhaps I’ve just not searched and read enough to find the jewel > document that explains all the FDT magic in sufficient detail. By > that I mean *current* FDT magic (which is another confusing aspect as > things seem to be in flux). > > Any advice on these matters greatly appreciated. > > 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 From owner-freebsd-arm@freebsd.org Mon Mar 18 19:52:11 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 ACC07154C29B for ; Mon, 18 Mar 2019 19:52:11 +0000 (UTC) (envelope-from jedi@jeditekunum.com) Received: from a2i644.smtp2go.com (a2i644.smtp2go.com [103.47.206.132]) (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 5A23373677 for ; Mon, 18 Mar 2019 19:52:10 +0000 (UTC) (envelope-from jedi@jeditekunum.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpservice.net; s=m4fue0.a1-4.dyn; x=1552939630; h=Feedback-ID: X-Smtpcorp-Track:To:Date:Subject:Message-Id:From:Reply-To:Sender: List-Unsubscribe; bh=iGkepK9wgMns/3O6qUAXfzqrR+P/iB5Y4oRLF9Sd1Ps=; b=2gHwT1QI Anq5xFtQxQrRgpJmlzIOGClEahdmTAWC6F/Y3s4hKXOi7q+ttC4X11DZoVWK5NZXIx0/2UB7xJNsP fJ9+DQ6Tteh3kCpIDQwLwn8/zZ7CUhdInUJqKRKi5NTpvdfebsGdeWMDWglzAz3lzrhlGj58t0TNW jG9Tu7qX4VAVMl6HWecQNh+BRoKhBQlxKNGoTmgpDiJISEcOyhWCJWsbAeS/iPasypbVLy3M1AqZC 0UJYG93QPwbh4zs3ZMTIWw5KKShd9XrPg/Yu3R6RWHTvRCtUUMITS3iSG3IWJmURC9rU5w1HGLnA3 iBg0qgxlyrkJC8fOwZEYp3I06A==; Received: from [10.173.255.233] (helo=SmtpCorp) by smtpcorp.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from ) id 1h5yIl-ED4wyy-4l; Mon, 18 Mar 2019 19:52:03 +0000 Received: from [10.162.213.37] (helo=takodana.opaxus.net) by smtpcorp.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from ) id 1h5yIk-IbZvem-K2; Mon, 18 Mar 2019 19:52:02 +0000 Received: from [10.0.10.1] (174-20-17-78.mpls.qwest.net [174.20.17.78]) by takodana.opaxus.net (Postfix) with ESMTPSA id C2A332662C; Mon, 18 Mar 2019 14:52:00 -0500 (CDT) From: Jedi Tek'Unum Message-Id: Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Options for FBSD support with LCD device - new project Date: Mon, 18 Mar 2019 14:51:59 -0500 In-Reply-To: <004ddba628b94b80845d8e509ddcb648d21fd6c9.camel@freebsd.org> Cc: freebsd-arm@freebsd.org To: Ian Lepore 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> X-Mailer: Apple Mail (2.3445.9.1) X-Smtpcorp-Track: 1h5ymkmPZv-XK2.M7PM4p7fk Feedback-ID: 207158m:207158azGM_-I:207158sDWsPdZzId X-Report-Abuse: Please forward a copy of this message, including all headers, to X-Rspamd-Queue-Id: 5A23373677 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=smtpservice.net header.s=m4fue0.a1-4.dyn header.b=2gHwT1QI X-Spamd-Result: default: False [-3.59 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[smtpservice.net:s=m4fue0.a1-4.dyn]; MX_INVALID(0.50)[cached]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[jeditekunum.com]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[smtpservice.net:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_MED(-0.20)[132.206.47.103.list.dnswl.org : 127.0.3.2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_SPF_NA(0.00)[]; NEURAL_HAM_SHORT(-0.84)[-0.836,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; IP_SCORE(-0.76)[asn: 1299(-3.77), country: EU(-0.00)]; ASN(0.00)[asn:1299, ipnet:103.47.204.0/22, country:EU]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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 19:52:11 -0000 My impression wasn=E2=80=99t that support wasn=E2=80=99t there - but = =E2=80=9Cout of the box=E2=80=9D configuration wasn=E2=80=99t there. In = comparison, I didn=E2=80=99t have to do anything to get I2C enabled in = the binary distribution of Linux that comes through the manufacturer. Its the enabling part that isn=E2=80=99t obvious to most people IMO. Documentation/wiki is great. But even better would be all the enabling = overlays already in place and the entries in loader.conf already there = and commented out. It would be so much easier to go to a =E2=80=9Ccommon = place=E2=80=9D (loader.conf), skim through the notes, find the thing = that one wants, and then just uncomment the referenced line! (Or any = other similarly easy method.) For FBSD to get a better foothold in this space it needs to be better = documented. For example, the wiki for NEO2 = is a = step-by-step guide for how to acquire and configure Linux for it. > On Mar 18, 2019, at 2:13 PM, Ian Lepore wrote: >=20 > On Mon, 2019-03-18 at 13:59 -0500, Jedi Tek'Unum wrote: >> I=E2=80=99ve been lurking here for some time. Long time (commercial) = unix >> expert. Not much FBSD. >>=20 >> I=E2=80=99m running Linux right now on NanoPi NEO (Allwinner H3) and = NEO 2 >> (Allwinner H5). Not because I love Linux (I don=E2=80=99t) but = because it >> works out of the box including I2C. I=E2=80=99d really like to use = FBSD on >> them. I hope that they will reach the same maturity as BB soon. >>=20 >> Perhaps I=E2=80=99m wrong but my impression following this list and = searching >> around is that I2C and SPI are not =E2=80=9Cout of the box=E2=80=9D = with FBSD on >> these platforms. >>=20 >> I=E2=80=99m not all that familiar with FDT. I=E2=80=99d like to learn = how to master >> it. If I understood it better I could probably bring anything I >> needed to life. BUT, that is back burner to actually completing the >> projects I=E2=80=99m trying to complete (where I just need I2C access = from >> user land). I really need those things to just work out of the box >> for now - or have clear instructions on how to enable. >>=20 >> In short I can=E2=80=99t use FBSD yet because it doesn=E2=80=99t = appear ready for >> these kinds of apps on these devices. I greatly appreciate all the >> effort that has and is going on to get there. If I had the knowledge >> I=E2=80=99d love to help, but I don=E2=80=99t currently. >>=20 >> Perhaps I=E2=80=99ve just not searched and read enough to find the = jewel >> document that explains all the FDT magic in sufficient detail. By >> that I mean *current* FDT magic (which is another confusing aspect as >> things seem to be in flux). >>=20 >> Any advice on these matters greatly appreciated. >>=20 >>=20 >=20 > 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. >=20 > 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. >=20 > 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. >=20 > 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. >=20 > -- Ian From owner-freebsd-arm@freebsd.org Mon Mar 18 19:57:24 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 5357B154C53B for ; Mon, 18 Mar 2019 19:57:24 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound3d.ore.mailhop.org (outbound3d.ore.mailhop.org [54.186.57.195]) (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 934D573A2B for ; Mon, 18 Mar 2019 19:57:23 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1552939041; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=O2MxHP8ExQ9wa43W3t5bAVZjkUGV5OpfsyAL2JQusDbNi/CGoVrWREKdiFaEOXgHOC8GD5UnOQWQz Iwkv5afr2fcw2sjNcjVxNtRYa7V2NPNSBg+Tk5z0owrIeM8OXlxCDKr2FK/jPSa3Q7bidbCHVCJ7Ir 0urXTZ6HjqLs7L2fvzL3sZ1m+bJv6OFfuE38KXjpODXmlwqLu7bfdqhpM15Rxp7SB3lFUxQ6Iwjd2N R8WCUxkZZSUExv88CD9j6uHbvDMxKqUbJg5cQSUFO2k29fLCqTva+j7PRIRrT70VtZtshNiPnbEQAi J0EGGUVzKfqlZ7rbhtc8ZytlcejS0/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=Z2qUCLVZI2eGZb7F+epRRYyIzl6v7qMCuThYW3dJWG8=; b=kW7SLRO1rL7pkqh5XjBccYJhBKdOP3GszlRH+nTj4DNJOqtHOWbAdOtbUf5Me99Z4Xd+CygFlXZO6 G6M63zIhcAoSybfhGENBoVhHu5EjkFg9d1kFKcf1FD8KFAwxN4UaRY5s6WJfJYCOnKWtwKjnNqhTY9 pqM9ynuBchOU7qDIt7E+x1p/ESySTEcP+dgoYeFHmq/uaVCQd+Q9CY0+c2cA3W9icaKbaH7+wm6t7c NV10gGJcUi3p2D0rp2gXaCTj2MWk5SSXsUuuGaVhACnZw1hwH7Jl4U+JBLGH3x3Z9YxvEzzrzsgG2X DhpLa/a376i/d+JmEDlNu0w7n9BEK6g== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=Z2qUCLVZI2eGZb7F+epRRYyIzl6v7qMCuThYW3dJWG8=; b=cTqp/Qdc9eclLMtJftx+2MgTcvZemi0vIi+xMt4JaeO6D+kaGZpDPAVYDnB2zE78YbdxpEsBVm6nw mfvaQUyD5o9RzoH+hxZ+5Ds4Ssllo7fwPF9rHiBHgDaRmJCWtfOr8dO6xW6Io+DvgJJ4IU6ScB9YpT SXf8HjgLBnep8vFtumnlwi3KU68giqwXy/bz66x1PMgF66KsPSNDpirFtYs6hoJ14yUHSlIPvVLBUy UcJq2Y74hhQiDYASr680lu4tFemwU1+zBP2/5y36KWFxVsyR9oJypTPRwgNHkMLuoz5EMDqWPbaPxs edzUBoEsn3xZEYggSB16mGdBkHuFiuA== X-MHO-RoutePath: aGlwcGll X-MHO-User: 096bac3d-49b8-11e9-9bb1-1f29e4676f89 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 096bac3d-49b8-11e9-9bb1-1f29e4676f89; Mon, 18 Mar 2019 19:57:20 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x2IJvIum063085; Mon, 18 Mar 2019 13:57:18 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: Options for FBSD support with LCD device - new project From: Ian Lepore To: "Jedi Tek'Unum" Cc: freebsd-arm@freebsd.org Date: Mon, 18 Mar 2019 13:57:18 -0600 In-Reply-To: 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> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 934D573A2B X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.99)[-0.991,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:16509, ipnet:54.186.0.0/15, country:US] 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 19:57:24 -0000 On Mon, 2019-03-18 at 14:51 -0500, Jedi Tek'Unum wrote: > My impression wasn’t that support wasn’t there - but “out of the box” > configuration wasn’t there. In comparison, I didn’t have to do > anything to get I2C enabled in the binary distribution of Linux that > comes through the manufacturer. > > Its the enabling part that isn’t obvious to most people IMO. > > Documentation/wiki is great. But even better would be all the > enabling overlays already in place and the entries in loader.conf > already there and commented out. It would be so much easier to go to > a “common place” (loader.conf), skim through the notes, find the > thing that one wants, and then just uncomment the referenced line! > (Or any other similarly easy method.) > > > For FBSD to get a better foothold in this space it needs to be better > documented. For example, the wiki for NEO2 < > http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO2> is a step-by- > step guide for how to acquire and configure Linux for it. > > On one of my imx6 boards I have 5 SPI devices. Each device can use 3 or 4 different sets of pins for clock, data-in, and data-out. Plus, each can use literally any number of whatever gpio pins they want as chip selects. Even limiting the chipsels to a handfull, there would literally be thousands of possible combinations of devices and pin configurations, each one needing to be a separate overlay. Maybe you have experience primarily with rpi or some similarly crippled devices that only offer one or two choices? BTW, bottom-posting replies is the norm on freebsd mailing lists. -- Ian > > On Mar 18, 2019, at 2:13 PM, Ian Lepore wrote: > > > > On Mon, 2019-03-18 at 13:59 -0500, Jedi Tek'Unum wrote: > > > I’ve been lurking here for some time. Long time (commercial) unix > > > expert. Not much FBSD. > > > > > > I’m running Linux right now on NanoPi NEO (Allwinner H3) and NEO > > > 2 > > > (Allwinner H5). Not because I love Linux (I don’t) but because it > > > works out of the box including I2C. I’d really like to use FBSD > > > on > > > them. I hope that they will reach the same maturity as BB soon. > > > > > > Perhaps I’m wrong but my impression following this list and > > > searching > > > around is that I2C and SPI are not “out of the box” with FBSD on > > > these platforms. > > > > > > I’m not all that familiar with FDT. I’d like to learn how to > > > master > > > it. If I understood it better I could probably bring anything I > > > needed to life. BUT, that is back burner to actually completing > > > the > > > projects I’m trying to complete (where I just need I2C access > > > from > > > user land). I really need those things to just work out of the > > > box > > > for now - or have clear instructions on how to enable. > > > > > > In short I can’t use FBSD yet because it doesn’t appear ready for > > > these kinds of apps on these devices. I greatly appreciate all > > > the > > > effort that has and is going on to get there. If I had the > > > knowledge > > > I’d love to help, but I don’t currently. > > > > > > Perhaps I’ve just not searched and read enough to find the jewel > > > document that explains all the FDT magic in sufficient detail. By > > > that I mean *current* FDT magic (which is another confusing > > > aspect as > > > things seem to be in flux). > > > > > > Any advice on these matters greatly appreciated. > > > > > > > > > > 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 > > 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 From owner-freebsd-arm@freebsd.org Mon Mar 18 23:10:39 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 85B8C15504F2 for ; Mon, 18 Mar 2019 23:10:39 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 31E1B83210; Mon, 18 Mar 2019 23:10:36 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id f75c5c96; Tue, 19 Mar 2019 00:10:28 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=g3QgachmmoAIjHL58FHix8nbozY=; b=EL7ZYaponoiw1RtBlGj5lrk3jI6w tUK3puZT/jWZL7gY4CCwyW+31rxKgLHiSEXinOMFM7uwrU1OX3K/87jV3a2dOssK d+dA6WM7Zo5YNPbRBDNyd468WQMyQiInWbMcx5DrXF3U4M0SxGoH4GbZv193jr5I 1U9HEg3v16HsPxs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=q9lUoh/6RvKTD32Xew+5g2mDn3+dOUf3GSBoRXOOio1LEwSDqjuR61IQ NwJRfpalos8ZgYzwko3IhiCxBRY1dTrsqaowP6SeCoa6YKTGVFK9sQJWtAvWExx/ CUl6CxGrCdBs802IgStLJcPqSv+2CkqzyYxfnVQEh9ceSNiTv9I= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 81dddef9 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Tue, 19 Mar 2019 00:10:28 +0100 (CET) Date: Tue, 19 Mar 2019 00:10:28 +0100 From: Emmanuel Vadot To: Ian Lepore Cc: Kaya Saman , Michael Zhilin , "freebsd-arm@freebsd.org" , Mori Hiroki Subject: Re: Options for FBSD support with LCD device - new project Message-Id: <20190319001028.8dedeb356095de425f2a35e5@bidouilliste.com> In-Reply-To: <0ecf23e129ca7ac6a92a01bbb34c03f1ac8c6dc8.camel@freebsd.org> References: <8df902f6-20a3-31c4-71ac-91f5d5fdf50d@optiplex-networks.com> <0ecf23e129ca7ac6a92a01bbb34c03f1ac8c6dc8.camel@freebsd.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 31E1B83210 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mail header.b=EL7ZYapo; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.177.182 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [0.49 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mail]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:212.83.177.182/32]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bidouilliste.com]; NEURAL_HAM_LONG(-0.73)[-0.727,0]; NEURAL_SPAM_MEDIUM(0.22)[0.224,0]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.54)[0.540,0]; DKIM_TRACE(0.00)[bidouilliste.com:+]; MX_GOOD(-0.01)[mx-backup.blih.net,mail.blih.net]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(0.36)[ip: (-1.10), ipnet: 212.83.160.0/19(3.18), asn: 12876(-0.26), country: FR(-0.01)]; ASN(0.00)[asn:12876, ipnet:212.83.160.0/19, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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 23:10:39 -0000 On Mon, 18 Mar 2019 10:07:50 -0600 Ian Lepore wrote: > On Mon, 2019-03-18 at 15:56 +0000, Kaya Saman wrote: > > Many thanks Michael! > > > > > > I have also found this guide too: > > https://www.rototron.info/lcdproc-tutorial-for-raspberry-pi/ > > > > > > It goes through the GPIO connection using a Raspberry Pi and a CF > > HD44780 compatible display. This should also work in a similar > > fashion > > with the Odroid. > > > > Before you go too far down this path, you should probably be aware that > odroid isn't really supported on freebsd. There was some initial work > done to support the original C1, but it was basically a drive-by commit > which hasn't been actively supported since then. > > You should consider some well-supported board, something based on an > Allwinner or imx6 SOC would be a good candidate. > > Gpio sounds like about the worst way to connect a display. Something > based on i2c or SPI would be a much better choice. Usually the so- > called "usb" solutions are really just forms of i2c or SPI being bit- > banged by an FTDI chip. Not a horrible solution, but probably not > quite as efficient as native i2c or spi. For an hd44780 based display GPIO is easy and ok, also now (and probably for the last 10-15 years) you can find modules using this controller with an i2c/spi uC to talk to them more easily. > -- Ian > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Mar 18 23:16:44 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 DC6761550759 for ; Mon, 18 Mar 2019 23:16:43 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CD989834BD for ; Mon, 18 Mar 2019 23:16:42 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 42faba37; Tue, 19 Mar 2019 00:16:41 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=QeLlJ9Og6RtPho+vt3URnntV3/s=; b=M7CNpdAp+TfoRHD0zwsZaooEwL3r 0JZ7rH7Y3PVgHILFVgH3R3EBRz/A43xI1LYkUpcsLPt2qDM195TL5y1lw6MPl+mj Lz3z1SrBLSeoi08xAKbEjBHTlo1TvEl1NaDrzvzRG2Ar6Meq9Tgh54EyVh74eQ0E pR6RFCNPp8z/IMQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=S/j81S20FFPms93yUypVPBdBKnMV/JGlBRKEg57iwf37HAtRq3SwQpDx ktEk1ZKP6GcPbr9KRQxqVV7TzRnrINXdePbbYUZW+lortRPgTjQvHNZH97/0Djdf LOMqQTzhwk/9EbXcbZuD6jFyiouK09KaN6rRXpME+X1iHB3wMnw= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id dc9fb9f0 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Tue, 19 Mar 2019 00:16:40 +0100 (CET) Date: Tue, 19 Mar 2019 00:16:40 +0100 From: Emmanuel Vadot To: Kaya Saman Cc: freebsd-arm@freebsd.org Subject: Re: Options for FBSD support with LCD device - new project Message-Id: <20190319001640.57831a1953ae6c8d2168faa0@bidouilliste.com> In-Reply-To: <35b3045f-817c-5645-d78b-f20b08671850@optiplex-networks.com> 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> <35b3045f-817c-5645-d78b-f20b08671850@optiplex-networks.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: CD989834BD X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mail header.b=M7CNpdAp; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.177.182 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [0.48 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mail]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:212.83.177.182/32]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bidouilliste.com]; NEURAL_HAM_LONG(-0.75)[-0.748,0]; NEURAL_SPAM_MEDIUM(0.17)[0.174,0]; NEURAL_SPAM_SHORT(0.60)[0.605,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; RCPT_COUNT_TWO(0.00)[2]; MX_GOOD(-0.01)[cached: mx-backup.blih.net]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(0.36)[ip: (-1.08), ipnet: 212.83.160.0/19(3.17), asn: 12876(-0.26), country: FR(-0.01)]; ASN(0.00)[asn:12876, ipnet:212.83.160.0/19, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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 23:16:44 -0000 On Mon, 18 Mar 2019 20:57:28 +0000 Kaya Saman wrote: > > > >>> 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. Go for the Pine64-LTS then, H6 (The SoC on Pine H64) isn't supported right now. It should be easy to add support for it but I have no hardware and no time for this now. > > Regards, > > > Kaya > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Mar 18 23:31:23 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 1A5D71550B96 for ; Mon, 18 Mar 2019 23:31:23 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 85CAB83C33 for ; Mon, 18 Mar 2019 23:31:20 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id x2INPYKd007404 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 19 Mar 2019 00:25:34 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1552951535; bh=K7d38FpJ2YpIzATZA/arjwLyQoX/IWO6K6dlOt5g4gY=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=W3/shCZ2VzRwiRpiMGyehRi+FAEJ3UmTq3OIIL5WaorhPqqSH3gB0XDEEct4azhhI 0YeQBLmwkhhFR5PCiFUAmIQRTebDQrWpBP+B7imug3O0xsdWHMzX4qwPHCl6/MHeIi 0UAK3bpePYpw3xGqdFIPXmiwjn7nZ5Emr6vYEH10= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id x2INPVtc098885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Mar 2019 00:25:31 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id x2INPVo6036435; Tue, 19 Mar 2019 00:25:31 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id x2INPULo036434; Tue, 19 Mar 2019 00:25:30 +0100 (CET) (envelope-from ticso) Date: Tue, 19 Mar 2019 00:25:30 +0100 From: Bernd Walter To: Kaya Saman Cc: freebsd-arm@freebsd.org Subject: Re: Options for FBSD support with LCD device - new project Message-ID: <20190318232530.GE57400@cicely7.cicely.de> Reply-To: ticso@cicely.de 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> <35b3045f-817c-5645-d78b-f20b08671850@optiplex-networks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <35b3045f-817c-5645-d78b-f20b08671850@optiplex-networks.com> X-Operating-System: FreeBSD cicely7.cicely.de 12.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-Rspamd-Queue-Id: 85CAB83C33 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cicely.de header.s=default header.b=W3/shCZ2 X-Spamd-Result: default: False [-1.37 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[ticso@cicely.de]; R_DKIM_ALLOW(-0.20)[cicely.de:s=default]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-0.98)[-0.977,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cicely.de]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; NEURAL_SPAM_SHORT(0.10)[0.104,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[cicely.de:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[3.99.149.195.list.dnswl.org : 127.0.20.0]; MX_GOOD(-0.01)[mx1.bwct.de]; NEURAL_HAM_MEDIUM(-0.69)[-0.690,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:21461, ipnet:195.149.99.0/24, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.00)[country: DE(-0.01)] 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 23:31:23 -0000 On Mon, Mar 18, 2019 at 08:57:28PM +0000, Kaya Saman wrote: > > > >>>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 The Pine64 is an excellent board, but so far I've only used it with serial console. The Pinebook, which is based on very similar hardware, however works nicely with it's screen, but not done any X tests yet, only console. If you want a smallscreen, which just works with FreeBSD then you should try this one: https://www.waveshare.com/3.5inch-HDMI-LCD.htm I've tested it with FreeBSD in text mode. The touchscreen is based on an XP2046 chip, which (AFAIK) we don't support, but it shouldn't be difficult to write a driver for it. It is an HDMI display and should work on other boards as well, but it is mechanically designed to hook up to an Raspberry with a special HDMI interconnect PCB. I also had to define config.txt entries for many of their HDMI displays, which is raspberry specific. If you are located in Germany, you can buy it from me, I'm a distributor of Waveshare. That said, I can't suggest all of the Waveshare components for use with FreeBSD. Especially the touchscreen support experience is mixed, some work out of the box with wmt(4), some don't. The SPI based displays work by running HDMI as dummy output in a specific resolution and then regularily grab the fbdev data and push it the the SPI display. It should be possible to write software for that, maybe even in userland, but getting the display initialisation right requires some research. On the display module they use shift registers to the parallel data input of the panel. They also have XP2046 base touch chips. > 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. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Tue Mar 19 00:00:59 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 A26C61551313 for ; Tue, 19 Mar 2019 00:00:59 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh505-vm9.bullet.mail.kks.yahoo.co.jp (nh505-vm9.bullet.mail.kks.yahoo.co.jp [183.79.57.111]) by mx1.freebsd.org (Postfix) with SMTP id 9E2C88499A for ; Tue, 19 Mar 2019 00:00:56 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [183.79.100.141] by nh505.bullet.mail.kks.yahoo.co.jp with NNFMP; 18 Mar 2019 23:58:32 -0000 Received: from [183.79.100.136] by t504.bullet.mail.kks.yahoo.co.jp with NNFMP; 18 Mar 2019 23:58:32 -0000 Received: from [127.0.0.1] by omp505.mail.kks.yahoo.co.jp with NNFMP; 18 Mar 2019 23:58:32 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 449686.84606.bm@omp505.mail.kks.yahoo.co.jp X-YMail-OSG: Gxay9d4VM1kM.jjyqirMEW6B0mQUX44sGzNZg2rP5Ry3hrKmE4kyd11ctfgBFK0 kUjGxkxErDjIiKDK8nJ7NpxigwreTY_7Pc7k55SPXRmV5DTzurmD4iavA.HsfpdBeFwIVK_mPwtZ 4uo86qWoui5hxjw7sOZTZejc6DeImcd0I3l7Ix_EoGtHnJYt0OBm8f9IdlZO4y70XHf0Kg08t.uW aePEagtwgMXVt3a6HHokLcMr5ZmNUxZZ.yDfiaPykR7uM5RHBgVDNqmvz5B1NE1_WhzD0OmV.ugX XHmg9lIwHAbTvYTHDLHRf2H.N33K0P9HfWYpLbmq21VsM2G1blSRi5tYoVsbV_lAG_9QCTf68LdH EnoMjQgdE7CMikHRaxg4w.xhmW9AaOLIcd2RgPs7vddd9wlumTFDmMK2tIxIkQSkyUGoRvEByEqB FCcPMra7S0zdCPVS5r1FkVrmNo6H6XrOgNBs0R9i48yWOgW7hsgMaZLCR2Sn9rZ3KLtkbqFd7ftO C.Z1kqLasfukPn0Op.VbBw9oNLWE0ODLZzqv9gqeZxJ_PXYIfMbUcXYyPUrt.INlJFsKkQepvRK3 UqMgp49pXpclR2lViZBHJiP_6ClGm.I6.09AuX.2zAQhYGn4e Received: from jws700006.mail.kks.yahoo.co.jp by sendmailws515.mail.kks.yahoo.co.jp; Tue, 19 Mar 2019 08:58:31 +0000; 1552953511.896 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1552953512; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:To:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; bh=Yc5P0uXGwZZfsYlKG2o6WLZwGupRaxj9xaq5E+uHD0Y=; b=clSU41bSc1HZQ2QCkmRPflbrUgwxQlm6R3rzG1iP8c5ZAO00bHJ/FK6JeVm92lMO wuqu4D1FuIHEamQzvZBS9z9SeorJVY5y7GhXNwM7QUWdOEjPZp0tJDEbx+Fi8tWHyeD 9xO1zTmFMbak8HamaL2MSSVknk4B1hjVhWgGGLCQ= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:Message-ID:In-Reply-To:References:MIME-Version:Content-Type:Content-Transfer-Encoding; b=YyCpDZbDr8SzMkUltudYVQtAx+62a8QlXr8Csk/VI4yoh4mjfCDzZn8dd0+tybKR Z2jO6aaSQoJY2rMbOpfCIl36Ig3OFpWDG24/IaODh2VzbFkDjRH6NkVAX8hL+jcAFQW cM3S8yv38KHpSYxNlY+ZFz9iUS7VzvjFup1E6vlM=; Date: Tue, 19 Mar 2019 08:58:31 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki To: Kaya Saman , Michael Zhilin , "freebsd-arm@freebsd.org" Message-ID: <162282840.119257.1552953511241.JavaMail.yahoo@mail.yahoo.co.jp> In-Reply-To: <8df902f6-20a3-31c4-71ac-91f5d5fdf50d@optiplex-networks.com> References: <8df902f6-20a3-31c4-71ac-91f5d5fdf50d@optiplex-networks.com> Subject: Re: Options for FBSD support with LCD device - new project MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 9E2C88499A X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.co.jp header.s=yj20110701 header.b=clSU41bS; dmarc=pass (policy=none) header.from=yahoo.co.jp; spf=pass (mx1.freebsd.org: domain of yamori813@yahoo.co.jp designates 183.79.57.111 as permitted sender) smtp.mailfrom=yamori813@yahoo.co.jp X-Spamd-Result: default: False [1.62 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[yamori813@yahoo.co.jp]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:183.79.56.0/23]; FREEMAIL_FROM(0.00)[yahoo.co.jp]; MX_GOOD(-0.01)[cached: mx3.mail.yahoo.co.jp]; DKIM_TRACE(0.00)[yahoo.co.jp:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.co.jp,none]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.co.jp]; ASN(0.00)[asn:24572, ipnet:183.79.0.0/16, country:JP]; IP_SCORE(0.89)[ipnet: 183.79.0.0/16(2.52), asn: 24572(2.02), country: JP(-0.07)]; DWL_DNSWL_NONE(0.00)[yahoo.co.jp.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.co.jp:s=yj20110701]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; REPLYTO_EQ_FROM(0.00)[]; NEURAL_HAM_LONG(-0.13)[-0.126,0]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[yahoo.co.jp]; NEURAL_SPAM_MEDIUM(0.91)[0.912,0]; NEURAL_SPAM_SHORT(0.85)[0.847,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[111.57.79.183.list.dnswl.org : 127.0.5.0] 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: Tue, 19 Mar 2019 00:00:59 -0000 Hi ----- Original Message ----- >From: Kaya Saman >To: Michael Zhilin ; "freebsd-arm@freebsd.org" ; Mori Hiroki =20 >Date: 2019/3/19, Tue 00:56 >Subject: Re: Options for FBSD support with LCD device - new project >=20 > >Many thanks Michael! > > >I have also found this guide too: https://www.rototron.info/lcdproc-tutori= al-for-raspberry-pi/ > > >It goes through the GPIO connection using a Raspberry Pi and a CF HD44780 = compatible display. This should also work in a similar fashion with the Odr= oid. > > My other solution for LCD is use FTDI USB module and HD44780. Sorry only Japanese. https://qiita.com/yamori813/items/bc2bebdf06517023e721 This is mruby and cairo library and libftdi. I try only on mips. Hiroki Mori > >Regards, > > >Kaya > > >On 3/18/19 2:41 PM, Michael Zhilin wrote: > >Hi, >> >> >>I'm not sure it's exact you're looking for, but here is link: >>https://qiita.com/yamori813/items/ae66330ccbf6fe6bd5ab >> >> >>Platform is MIPS32/Atheros. It has LCD and keypad.=20 >> >>Details: ask Hiroki Mori please. >> >> >>Thanks! >> >> >>On Mon, Mar 18, 2019 at 5:08 PM Kaya Saman wrote: >> >> >>>Hi, >>> >>> >>>I am looking for a solution capable of running FreeBSD that I =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0will be=20 >>>able to add an LCD or OLED display to. >>> >>> >>>The project spec is fairly simple: >>> >>>- Use an embedded SoC solution >>> >>>- Fit inside a DIN enclosure eg.=20 >>>https://eng.italtronic.com/products/embedded_box_en/ >>> >>>- Have an LCD or OLED display with or without keypad eg.=20 >>>https://www.crystalfontz.com/product/cfa633rdiks-rs232-alphanumeric-lcd-= display-16x2#undefined >>> >>> >>> >>>Currently I am thinking about an Odroid C1+ with a =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Crystalfontz di= splay=20 >>>as they are well supported by Lcdproc. >>> >>>Already I have gone through: >>> >>>https://wiki.freebsd.org/FreeBSD/arm/Odroid-C1 >>> >>>https://www.freebsd.org/platforms/arm.html >>> >>>https://wiki.freebsd.org/FreeBSD/arm >>> >>> >>>but just wanted to see if anyone has any experience with this =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0type of=20 >>>setup or could offer some advice? >>> >>> >>>I guess connection to the LCD would be another question as the =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0most=20 >>>common two options would be GPIO or USB. In the case of GPIO =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0is there a=20 >>>way to simulate an serial connection or are there better =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0supported=20 >>>boards with serial or usb headers on them already? >>> >>>There are LCD modules made specifically for these boards which =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0do sit on=20 >>>top of the GPIO however, do these work with Lcdproc?=20 >>>http://www.lcdproc.org/hardware.php3 >>> >>> >>>Thanks. >>> >>> >>>Kaya >>> >>>_______________________________________________ >>>freebsd-arm@freebsd.org mailing list >>>https://lists.freebsd.org/mailman/listinfo/freebsd-arm >>>To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >>> > > From owner-freebsd-arm@freebsd.org Tue Mar 19 00:01:26 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 AED9115514A7 for ; Tue, 19 Mar 2019 00:01:26 +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 3A99284AF4 for ; Tue, 19 Mar 2019 00:01:25 +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 CBC8B722DBE; Tue, 19 Mar 2019 00:01:22 +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 CKsn2BCptu9s; Tue, 19 Mar 2019 00:01:22 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by x-ray.optiplex-networks.com (Postfix) with ESMTP id 76C8D722DB7; Tue, 19 Mar 2019 00:01:22 +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 2V2icngh8j7F; Tue, 19 Mar 2019 00:01:22 +0000 (GMT) Received: from x220.optiplex-networks.com (unknown [192.168.0.167]) by x-ray.optiplex-networks.com (Postfix) with ESMTPSA id 561FC7226C3; Tue, 19 Mar 2019 00:01:22 +0000 (GMT) Subject: Re: Options for FBSD support with LCD device - new project To: ticso@cicely.de Cc: 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> <35b3045f-817c-5645-d78b-f20b08671850@optiplex-networks.com> <20190318232530.GE57400@cicely7.cicely.de> From: Kaya Saman Message-ID: Date: Tue, 19 Mar 2019 00:01:22 +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: <20190318232530.GE57400@cicely7.cicely.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 3A99284AF4 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 [-3.68 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[6]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[optiplex-networks.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mail.optiplex-networks.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.68)[-0.683,0]; RCVD_TLS_LAST(0.00)[]; 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)[]; IP_SCORE(-0.69)[asn: 6871(-3.34), 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: Tue, 19 Mar 2019 00:01:27 -0000 On 3/18/19 11:25 PM, Bernd Walter wrote: > On Mon, Mar 18, 2019 at 08:57:28PM +0000, Kaya Saman wrote: >> >> >>>>> 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 > The Pine64 is an excellent board, but so far I've only used it with serial > console. > The Pinebook, which is based on very similar hardware, however works nicely > with it's screen, but not done any X tests yet, only console. > > If you want a smallscreen, which just works with FreeBSD then you should > try this one: > https://www.waveshare.com/3.5inch-HDMI-LCD.htm > I've tested it with FreeBSD in text mode. > The touchscreen is based on an XP2046 chip, which (AFAIK) we don't support, > but it shouldn't be difficult to write a driver for it. > It is an HDMI display and should work on other boards as well, but it is > mechanically designed to hook up to an Raspberry with a special HDMI > interconnect PCB. > I also had to define config.txt entries for many of their HDMI displays, which > is raspberry specific. > If you are located in Germany, you can buy it from me, I'm a distributor of > Waveshare. > That said, I can't suggest all of the Waveshare components for use with FreeBSD. > Especially the touchscreen support experience is mixed, some work out of the box > with wmt(4), some don't. > > The SPI based displays work by running HDMI as dummy output in a specific > resolution and then regularily grab the fbdev data and push it the the SPI > display. > It should be possible to write software for that, maybe even in userland, but > getting the display initialisation right requires some research. > On the display module they use shift registers to the parallel data input of > the panel. > They also have XP2046 base touch chips. > That's fantastic! I will probably need the serial console more then the HDMI display though I do want to add a character based LCD such the Crystalfontz I referenced earlier in this thread as an example. Though it looks like there are some alternatives on the site you mentioned too: https://www.waveshare.com/product/modules/oleds-lcds.htm So I think that your reply and Emmanuel's response have clarified things a lot for me and the Pine64-LTS is the one to choose. Looking through the RPi header documentation or the Pine64: http://synfare.com/599N105E/hwdocs/pine64/index.html I should even be able to add a DB9 connector for UART serial rs232c access for terminal emulators like minicom,tip etc. Now I just need to find a DIN NS35 enclosure for it (or make one) and then I can begin my project :-) :-) I'm getting excited now as this is going to be a lot of fun! Thanks everyone for all the responses. Kaya From owner-freebsd-arm@freebsd.org Tue Mar 19 00:09:23 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 3E82B1551A3C for ; Tue, 19 Mar 2019 00:09:23 +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 41609852F5 for ; Tue, 19 Mar 2019 00:09:22 +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 932E1722DB7; Tue, 19 Mar 2019 00:09:19 +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 tdqSwMZF8yHz; Tue, 19 Mar 2019 00:09:17 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by x-ray.optiplex-networks.com (Postfix) with ESMTP id 95504722DBE; Tue, 19 Mar 2019 00:09:17 +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 eIVCFh7Ej2fA; Tue, 19 Mar 2019 00:09:17 +0000 (GMT) Received: from x220.optiplex-networks.com (unknown [192.168.0.167]) by x-ray.optiplex-networks.com (Postfix) with ESMTPSA id 75EA2722DB7; Tue, 19 Mar 2019 00:09:17 +0000 (GMT) Subject: Re: Options for FBSD support with LCD device - new project To: Mori Hiroki , Michael Zhilin , "freebsd-arm@freebsd.org" References: <8df902f6-20a3-31c4-71ac-91f5d5fdf50d@optiplex-networks.com> <162282840.119257.1552953511241.JavaMail.yahoo@mail.yahoo.co.jp> From: Kaya Saman Message-ID: <7a7de300-a2e7-02cc-7981-e62e90307368@optiplex-networks.com> Date: Tue, 19 Mar 2019 00:09:17 +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: <162282840.119257.1552953511241.JavaMail.yahoo@mail.yahoo.co.jp> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 41609852F5 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 [-3.82 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_COUNT_FIVE(0.00)[6]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[optiplex-networks.com]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mail.optiplex-networks.com]; NEURAL_HAM_SHORT(-0.82)[-0.815,0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-0.70)[asn: 6871(-3.41), country: GB(-0.09)]; FREEMAIL_TO(0.00)[yahoo.co.jp]; 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)[] 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: Tue, 19 Mar 2019 00:09:23 -0000 On 3/18/19 11:58 PM, Mori Hiroki wrote: > > Hi > > ----- Original Message ----- >> From: Kaya Saman >> To: Michael Zhilin ; "freebsd-arm@freebsd.org" ; Mori Hiroki >> Date: 2019/3/19, Tue 00:56 >> Subject: Re: Options for FBSD support with LCD device - new project >> >> >> Many thanks Michael! >> >> >> I have also found this guide too: https://www.rototron.info/lcdproc-tutorial-for-raspberry-pi/ >> >> >> It goes through the GPIO connection using a Raspberry Pi and a CF HD44780 compatible display. This should also work in a similar fashion with the Odroid. >> >> > > My other solution for LCD is use FTDI USB module and HD44780. > > Sorry only Japanese. > > > https://qiita.com/yamori813/items/bc2bebdf06517023e721 > > This is mruby and cairo library and libftdi. > > > I try only on mips. > > > Hiroki Mori > > Thanks Hiroki-san! There are many ways to connect an LCD display. Since now I know what board I will go for; the Pine64-LTS, I will look at using the SPI interface on the GPIO RPi header. I have used quite a few displays on x86 hardware connected to USB or Serial headers so it should be fine. Best Regards, Kaya From owner-freebsd-arm@freebsd.org Tue Mar 19 00:41:54 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 6A0F8152C2E3 for ; Tue, 19 Mar 2019 00:41:54 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BC46D86D0A for ; Tue, 19 Mar 2019 00:41:52 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id x2J0fmpZ009955 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 19 Mar 2019 01:41:50 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1552956110; bh=mB79Dr9vrd9Vsp10HgA2rAbX9B5qOzwYMBiVeoe1MXA=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=kBeSpHS5Jy7PFl3eLoVZ3aGl+VkLKRfzgsA/0WhTrOkDEL4Wj+1hl+iG+AXtt9JVn zEuvXRKt+pVll0+C2BJqe6BFkWOhxEjsFDJXMMZ5PUye7CnE0e+rmIez+K7btdBc6s Hq3OelO6eli/lCnofkn0WW4QsWc/K6I7ZpMnKTgg= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id x2J0fka4001099 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Mar 2019 01:41:46 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id x2J0fjIQ036764; Tue, 19 Mar 2019 01:41:45 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id x2J0fje2036763; Tue, 19 Mar 2019 01:41:45 +0100 (CET) (envelope-from ticso) Date: Tue, 19 Mar 2019 01:41:45 +0100 From: Bernd Walter To: Kaya Saman Cc: ticso@cicely.de, freebsd-arm@freebsd.org Subject: Re: Options for FBSD support with LCD device - new project Message-ID: <20190319004145.GF57400@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <0ecf23e129ca7ac6a92a01bbb34c03f1ac8c6dc8.camel@freebsd.org> <89f5b8d1ab0614ac8d88b5d5f1afc63e640c3c17.camel@freebsd.org> <4EB5C6C1-7DB9-4DEE-BB23-CD1259581271@jeditekunum.com> <004ddba628b94b80845d8e509ddcb648d21fd6c9.camel@freebsd.org> <35b3045f-817c-5645-d78b-f20b08671850@optiplex-networks.com> <20190318232530.GE57400@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 12.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-Rspamd-Queue-Id: BC46D86D0A X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cicely.de header.s=default header.b=kBeSpHS5 X-Spamd-Result: default: False [-1.38 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[ticso@cicely.de]; R_DKIM_ALLOW(-0.20)[cicely.de:s=default]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-0.98)[-0.978,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cicely.de]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.10)[0.096,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[cicely.de:+]; MX_GOOD(-0.01)[cached: mx1.bwct.de]; RCVD_IN_DNSWL_NONE(0.00)[3.99.149.195.list.dnswl.org : 127.0.20.0]; NEURAL_HAM_MEDIUM(-0.68)[-0.682,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:21461, ipnet:195.149.99.0/24, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.00)[country: DE(-0.01)] 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: Tue, 19 Mar 2019 00:41:54 -0000 On Tue, Mar 19, 2019 at 12:01:22AM +0000, Kaya Saman wrote: > > On 3/18/19 11:25 PM, Bernd Walter wrote: > >On Mon, Mar 18, 2019 at 08:57:28PM +0000, Kaya Saman wrote: > >> > >> > >>>>>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 > >The Pine64 is an excellent board, but so far I've only used it with serial > >console. > >The Pinebook, which is based on very similar hardware, however works nicely > >with it's screen, but not done any X tests yet, only console. > > > >If you want a smallscreen, which just works with FreeBSD then you should > >try this one: > >https://www.waveshare.com/3.5inch-HDMI-LCD.htm > >I've tested it with FreeBSD in text mode. > >The touchscreen is based on an XP2046 chip, which (AFAIK) we don't support, > >but it shouldn't be difficult to write a driver for it. > >It is an HDMI display and should work on other boards as well, but it is > >mechanically designed to hook up to an Raspberry with a special HDMI > >interconnect PCB. > >I also had to define config.txt entries for many of their HDMI displays, > >which > >is raspberry specific. > >If you are located in Germany, you can buy it from me, I'm a distributor of > >Waveshare. > >That said, I can't suggest all of the Waveshare components for use with > >FreeBSD. > >Especially the touchscreen support experience is mixed, some work out of > >the box > >with wmt(4), some don't. > > > >The SPI based displays work by running HDMI as dummy output in a specific > >resolution and then regularily grab the fbdev data and push it the the SPI > >display. > >It should be possible to write software for that, maybe even in userland, > >but > >getting the display initialisation right requires some research. > >On the display module they use shift registers to the parallel data input > >of > >the panel. > >They also have XP2046 base touch chips. > > > > That's fantastic! I will probably need the serial console more then the > HDMI display though I do want to add a character based LCD such the > Crystalfontz I referenced earlier in this thread as an example. Though > it looks like there are some alternatives on the site you mentioned too: > https://www.waveshare.com/product/modules/oleds-lcds.htm > > > So I think that your reply and Emmanuel's response have clarified things > a lot for me and the Pine64-LTS is the one to choose. > > > Looking through the RPi header documentation or the Pine64: > http://synfare.com/599N105E/hwdocs/pine64/index.html I should even be > able to add a DB9 connector for UART serial rs232c access for terminal > emulators like minicom,tip etc. If you go for DB9, then don't forget that you need propper RS232 transceiver to get the +- signals. The console is 3.3V TTL only. Also for the PINE64-LTS, the console is on the EXP connector, no idea if the RPi compatible header has the same signals or not. > Now I just need to find a DIN NS35 enclosure for it (or make one) and > then I can begin my project :-) :-) > > > I'm getting excited now as this is going to be a lot of fun! > -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Tue Mar 19 00:55:22 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 A9837152C93F for ; Tue, 19 Mar 2019 00:55:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 437038794D for ; Tue, 19 Mar 2019 00:55:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7001D460E for ; Tue, 19 Mar 2019 00:55:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x2J0tLkI056610 for ; Tue, 19 Mar 2019 00:55:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x2J0tLYK056609 for freebsd-arm@FreeBSD.org; Tue, 19 Mar 2019 00:55:21 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 236624] Beaglebone Black: cpsw device does not load on FreeBSD 13.0-CURRENT Date: Tue, 19 Mar 2019 00:55:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gndaryee@uwaterloo.ca X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Tue, 19 Mar 2019 00:55:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236624 Bug ID: 236624 Summary: Beaglebone Black: cpsw device does not load on FreeBSD 13.0-CURRENT Product: Base System Version: CURRENT Hardware: arm OS: Any Status: New Severity: Affects Some People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: gndaryee@uwaterloo.ca As per: https://lists.freebsd.org/pipermail/freebsd-arm/2019-February/019420.html The cpsw device doesn't load from the FDT which causes panics when trying to boot over NFS. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Tue Mar 19 06:28:45 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 C6F9E15435ED for ; Tue, 19 Mar 2019 06:28:44 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A4B136E69B; Tue, 19 Mar 2019 06:28:34 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cs.huji.ac.il; s=57791128; h=References:To:Cc:In-Reply-To:Date:Subject:Mime-Version:Content-Type:Message-Id:From; bh=aqbzxiFGr4s8ugPN5JPAguosYUkrlRI4s/KojvvrgXQ=; b=llfbroalIZhokUHuIZPnOLR8uOSnMJaj2kY5adG2zJjh6zIDjlSTBdun/i297RmeLAsmObEVFWkFMb/4sDCWZ4VAyotdMrYQtcTPygfLa3GQLA3LFhUhXhPB37PuBGFgXEl5BTc94hO77TjlQYq9pzlIFu9XQ6dmz/GI+bKOqU3QiU/JtjkyOmjGj4hvTh7o+t+4uOcvZ4X2JjKD3b2S4EC8/y65Pwvt1DSglXS/z0yzAALEj/2nc/SBrmN8iqXPhN5vcK76pbxzsCOvq14nU15sEJAkQ+SZFX1p6xC5/Zhm24tgt0G3TidjQ6JXHcbHKA5tD6PE9/+sXfU8Y21J+g==; Received: from bach.cs.huji.ac.il ([132.65.80.20]) by kabab.cs.huji.ac.il with esmtp id 1h68Eb-000INN-75; Tue, 19 Mar 2019 08:28:25 +0200 From: Daniel Braniss Message-Id: Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Options for FBSD support with LCD device - new project Date: Tue, 19 Mar 2019 08:28:24 +0200 In-Reply-To: <004ddba628b94b80845d8e509ddcb648d21fd6c9.camel@freebsd.org> Cc: Jedi Tek'Unum , freebsd-arm@freebsd.org To: Ian Lepore 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> X-Mailer: Apple Mail (2.3445.9.1) X-Rspamd-Queue-Id: A4B136E69B X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cs.huji.ac.il header.s=57791128 header.b=llfbroal X-Spamd-Result: default: False [-2.30 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.987,0]; R_DKIM_ALLOW(-0.20)[cs.huji.ac.il:s=57791128]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[huji.ac.il]; TO_DN_SOME(0.00)[]; URI_COUNT_ODD(1.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[cs.huji.ac.il:+]; MX_GOOD(-0.01)[kabab.cs.huji.ac.il,post.cs.huji.ac.il]; RCVD_IN_DNSWL_NONE(0.00)[210.116.65.132.list.dnswl.org : 127.0.10.0]; NEURAL_HAM_SHORT(-0.70)[-0.703,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:378, ipnet:132.64.0.0/13, country:EU]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.80)[ipnet: 132.64.0.0/13(-2.23), asn: 378(-1.78), country: EU(-0.00)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Tue, 19 Mar 2019 06:28:45 -0000 > On 18 Mar 2019, at 21:13, Ian Lepore wrote: >=20 > On Mon, 2019-03-18 at 13:59 -0500, Jedi Tek'Unum wrote: >> I=E2=80=99ve been lurking here for some time. Long time (commercial) = unix >> expert. Not much FBSD. >>=20 >> I=E2=80=99m running Linux right now on NanoPi NEO (Allwinner H3) and = NEO 2 >> (Allwinner H5). Not because I love Linux (I don=E2=80=99t) but = because it >> works out of the box including I2C. I=E2=80=99d really like to use = FBSD on >> them. I hope that they will reach the same maturity as BB soon. >>=20 >> Perhaps I=E2=80=99m wrong but my impression following this list and = searching >> around is that I2C and SPI are not =E2=80=9Cout of the box=E2=80=9D = with FBSD on >> these platforms. >>=20 >> I=E2=80=99m not all that familiar with FDT. I=E2=80=99d like to learn = how to master >> it. If I understood it better I could probably bring anything I >> needed to life. BUT, that is back burner to actually completing the >> projects I=E2=80=99m trying to complete (where I just need I2C access = from >> user land). I really need those things to just work out of the box >> for now - or have clear instructions on how to enable. >>=20 >> In short I can=E2=80=99t use FBSD yet because it doesn=E2=80=99t = appear ready for >> these kinds of apps on these devices. I greatly appreciate all the >> effort that has and is going on to get there. If I had the knowledge >> I=E2=80=99d love to help, but I don=E2=80=99t currently. >>=20 >> Perhaps I=E2=80=99ve just not searched and read enough to find the = jewel >> document that explains all the FDT magic in sufficient detail. By >> that I mean *current* FDT magic (which is another confusing aspect as >> things seem to be in flux). >>=20 >> Any advice on these matters greatly appreciated. >>=20 >>=20 >=20 > 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. >=20 > 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. I have several allwinner SoC, mainly from FriendlyArm, and neither i2c = or SPI work. I have a hacked i2c that mostly works, but hangs sometimes :-), mainly timing issues of which I have no idea how to fix. I=E2=80=99m willing to help here but my knowledge of the twsi tends to = zero. hint hint =E2=80=A6 cheers, danny >=20 > 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. >=20 > 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. >=20 > -- Ian >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm = > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org = " From owner-freebsd-arm@freebsd.org Tue Mar 19 14:27:03 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 8AEAD155243E for ; Tue, 19 Mar 2019 14:27:03 +0000 (UTC) (envelope-from jedi@jeditekunum.com) Received: from a2i644.smtp2go.com (a2i644.smtp2go.com [103.47.206.132]) (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 D27B5871CC for ; Tue, 19 Mar 2019 14:26:52 +0000 (UTC) (envelope-from jedi@jeditekunum.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpservice.net; s=m4fue0.a1-4.dyn; x=1553006512; h=Feedback-ID: X-Smtpcorp-Track:To:Date:Subject:Message-Id:From:Reply-To:Sender: List-Unsubscribe; bh=luryk9BjLdRvzCOJhoZsthCboZOTELMgexWzyPm+jeU=; b=hVGCv2Fr nasDhDyoAQNbm+Tjy8//fbI9e0yTu4SzxW9BAJqnt6NKbfluk99bkA/NBIR7sn+hC0guSQgg4jAxu p7trmxe5KzAMjgl6RrUmzZn/TC4jCY2/0qvwCFZiffD9GClTLNa2NywUxyNFrvtvUsFglQCH1FW++ J0/IPAWzX9lVqGmEEaCZQ7LamniYMHlX+QvTXJrWSHWBOoeXh3M3OY+8mpPVYWq+erhglsK5gUoPf k0eE7+dEGI+hqXotgxTMIHHWv0jrtFoivh+YqptzbfO9qRLu6gpdO2DvPYdpNHfcbC6NGbX16fzyA g/3bVh/SV4q4nQkJ+mhDrts9ng==; Received: from [10.66.228.43] (helo=SmtpCorp) by smtpcorp.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from ) id 1h6FhV-ED4wZr-HM; Tue, 19 Mar 2019 14:26:45 +0000 Received: from [10.162.213.37] (helo=takodana.opaxus.net) by smtpcorp.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from ) id 1h6FhV-wSEVbL-1I; Tue, 19 Mar 2019 14:26:45 +0000 Received: from [10.0.10.1] (174-20-17-78.mpls.qwest.net [174.20.17.78]) by takodana.opaxus.net (Postfix) with ESMTPSA id A82AB266F0; Tue, 19 Mar 2019 09:26:43 -0500 (CDT) From: Jedi Tek'Unum Message-Id: Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Options for FBSD support with LCD device - new project Date: Tue, 19 Mar 2019 09:26:42 -0500 In-Reply-To: Cc: freebsd-arm@freebsd.org To: Ian Lepore 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> X-Mailer: Apple Mail (2.3445.9.1) X-Smtpcorp-Track: 1h6FhVwSEVPL1m.kLwk1YOlC Feedback-ID: 207158m:207158azGM_-I:207158sDWsPdZzId X-Report-Abuse: Please forward a copy of this message, including all headers, to X-Rspamd-Queue-Id: D27B5871CC X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=smtpservice.net header.s=m4fue0.a1-4.dyn header.b=hVGCv2Fr X-Spamd-Result: default: False [-3.65 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[smtpservice.net:s=m4fue0.a1-4.dyn]; MX_INVALID(0.50)[greylisted]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[jeditekunum.com]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[smtpservice.net:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_MED(-0.20)[132.206.47.103.list.dnswl.org : 127.0.3.2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_SPF_NA(0.00)[]; NEURAL_HAM_SHORT(-0.92)[-0.916,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; IP_SCORE(-0.74)[asn: 1299(-3.69), country: EU(-0.00)]; ASN(0.00)[asn:1299, ipnet:103.47.204.0/22, country:EU]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Tue, 19 Mar 2019 14:27:03 -0000 On Mar 18, 2019, at 2:57 PM, Ian Lepore wrote: >=20 > On Mon, 2019-03-18 at 14:51 -0500, Jedi Tek'Unum wrote: >> My impression wasn=E2=80=99t that support wasn=E2=80=99t there - but = =E2=80=9Cout of the box=E2=80=9D >> configuration wasn=E2=80=99t there. In comparison, I didn=E2=80=99t = have to do >> anything to get I2C enabled in the binary distribution of Linux that >> comes through the manufacturer. >>=20 >> Its the enabling part that isn=E2=80=99t obvious to most people IMO. >>=20 >> Documentation/wiki is great. But even better would be all the >> enabling overlays already in place and the entries in loader.conf >> already there and commented out. It would be so much easier to go to >> a =E2=80=9Ccommon place=E2=80=9D (loader.conf), skim through the = notes, find the >> thing that one wants, and then just uncomment the referenced line! >> (Or any other similarly easy method.) >>=20 >>=20 >> For FBSD to get a better foothold in this space it needs to be better >> documented. For example, the wiki for NEO2 < >> http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO2> is a step-by- >> step guide for how to acquire and configure Linux for it. >>=20 >>=20 >=20 > On one of my imx6 boards I have 5 SPI devices. Each device can use 3 > or 4 different sets of pins for clock, data-in, and data-out. Plus, > each can use literally any number of whatever gpio pins they want as > chip selects. Even limiting the chipsels to a handfull, there would > literally be thousands of possible combinations of devices and pin > configurations, each one needing to be a separate overlay. >=20 > Maybe you have experience primarily with rpi or some similarly = crippled > devices that only offer one or two choices? If memory serves correctly, there are only 2 I2C devices on the H3/H5 = and the NanoPi NEO/2 implementations only externalize 1. There is only 1 = SPI AFAIK. I wouldn=E2=80=99t call that crippled. I chose this platform exactly = because of its characteristics - small, fast, cheap. It fits the project = I=E2=80=99m using it for perfectly. In fact, I can see uses for even = smaller (see Giant Board ). I = understand other projects may have different requirements and would = drive one towards different solutions - and require more of the various = interfaces. But they aren=E2=80=99t going to be typical of hobbyist = projects. Maybe I should pose the question in another way. What is the philosophy = for choosing GPIO as default for all the pins? These boards have a very = limited number of pins and my preference would be that the broadest = range of interface types would be the default. There are 2 UARTs exposed = so I would have picked 1 to be enabled by default. After that, with I2C = and SPI enabled, there are still 6 GPIO available. For a tiny board like = this that seems to be reasonable. If people have a need for slightly = more GPIO then I would expect they would be the ones configuring = overlays. Apparently the developers of the Linux packages for these boards have = chosen the diverse approach (=E2=80=9CFriendlyCore=E2=80=9D based on = UbuntuCore Xenial). IMHO, most =E2=80=9Chobbyists=E2=80=9D would prefer the diversity = approach. I=E2=80=99m completely capable of becoming an expert in FBSD = and this sort of configuration stuff yet it isn=E2=80=99t a priority for = me - I just want to use it like any other hobbyist. The way things are = now pushes this type of user away from FBSD. If there is some philosophical perspective against the diversity = approach then the next best thing is to have documentation that clearly = and simply tells people how to enable the other functionality. Finally, I think there is an opportunity to grow FBSD in the hobbyist = world of these small products. We are past the point where people can = have a real operating system running on systems at Arduino size and = cost. Linux has been aggressively deployed there but I can say from = experience that it ain=E2=80=99t pretty - I won=E2=80=99t say more as = everyone reading this has a clear understanding of why that is. From owner-freebsd-arm@freebsd.org Tue Mar 19 14:55:51 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 383601553075 for ; Tue, 19 Mar 2019 14:55:51 +0000 (UTC) (envelope-from karl@denninger.net) Received: from colo1.denninger.net (colo1.denninger.net [104.236.120.189]) (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 4F22488904 for ; Tue, 19 Mar 2019 14:55:50 +0000 (UTC) (envelope-from karl@denninger.net) Received: from denninger.net (ip68-1-57-197.pn.at.cox.net [68.1.57.197]) by colo1.denninger.net (Postfix) with ESMTP id B546F21108C for ; Tue, 19 Mar 2019 10:55:13 -0400 (EDT) Received: from [192.168.10.26] (D16.Denninger.Net [192.168.10.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by denninger.net (Postfix) with ESMTPSA id E0F16C95F for ; Tue, 19 Mar 2019 09:55:12 -0500 (CDT) Subject: Re: Options for FBSD support with LCD device - new project [[Maybe related: I2c issues on the Pi2]] 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: Karl Denninger Openpgp: preference=signencrypt Autocrypt: addr=karl@denninger.net; prefer-encrypt=mutual; keydata= mQINBFIX1zsBEADRcJfsQUl9oFeoMfLPJ1kql+3sIaYx0MfJAUhV9LnbWxr0fsWCskM1O4cV tHm5dqPkuPM4Ztc0jLotD1i9ubWvCHOlkLGxFOL+pFbjA+XZ7VKsC/xWmhMwJ3cM8HavK2OV SzEWQ/AEYtMi04IzGSwsxh/5/5R0mPHrsIomV5SbuiI0vjLuDj7fo6146AABI1ULzge4hBYW i/SHrqUrLORmUNBs6bxek79/B0Dzk5cIktD3LOfbT9EAa5J/osVkstMBhToJgQttaMIGv8SG CzpR/HwEokE+7DP+k2mLHnLj6H3kfugOF9pJH8Za4yFmw//s9cPXV8WwtZ2SKfVzn1unpKqf wmJ1PwJoom/d4fGvQDkgkGKRa6RGC6tPmXnqnx+YX4iCOdFfbP8L9rmk2sewDDVzHDU3I3ZZ 8hFIjMYM/QXXYszRatK0LCV0QPZuF7LCf4uQVKw1/oyJInsnH7+6a3c0h21x+CmSja9QJ+y0 yzgEN/nM89d6YTakfR+1xkYgodVmMy/bS8kmXbUUZG/CyeqCqc95RUySjKT2ECrf9GhhoQkl +D8n2MsrAUSMGB4GQSN+TIq9OBTpNuvATGSRuF9wnQcs1iSry+JNCpfRTyWp83uCNApe6oHU EET4Et6KDO3AvjvBMAX0TInTRGW2SQlJMuFKpc7Dg7tHK8zzqQARAQABtCNLYXJsIERlbm5p bmdlciA8a2FybEBkZW5uaW5nZXIubmV0PokCPAQTAQIAJgUCUhfXOwIbIwUJCWYBgAYLCQgH AwIEFQIIAwQWAgMBAh4BAheAAAoJEG6/sivc5s0PLxQP/i6x/QFx9G4Cw7C+LthhLXIm7NSH AtNbz2UjySEx2qkoQQjtsK6mcpEEaky4ky6t8gz0/SifIfJmSmyAx0UhUQ0WBv1vAXwtNrQQ jJd9Bj6l4c2083WaXyHPjt2u2Na6YFowyb4SaQb83hu/Zs25vkPQYJVVE0JX409MFVPUa6E3 zFbd1OTr3T4yNUy4gNeQZfzDqDS8slbIks2sXeoJrZ6qqXVI0ionoivOlaN4T6Q0UYyXtigj dQvvhMt0aNowKFjRqrmSDRpdz+o6yg7Mp7qEZ1V6EZk8KqQTH6htpCTQ8i79ttK4LG6bstSF Re6Fwq52nbrcANrcdmtZXqjo+SGbUqJ8b1ggrxAsJ5MEhRh2peKrCgI/TjQo+ZxfnqEoR4AI 46Cyiz+/lcVvlvmf2iPifS3EEdaH3Itfwt7MxFm6mQORYs6skHDw3tOYB2/AdCW6eRVYs2hB RMAG4uwApZfZDKgRoE95PJmQjeTBiGmRPcsQZtNESe7I7EjHtCDLwtJqvD4HkDDQwpzreT6W XkyIJ7ns7zDfA1E+AQhFR6rsTFGgQZRZKsVeov3SbhYKkCnVDCvb/PKQCAGkSZM9SvYG5Yax 8CMry3AefKktf9fqBFg8pWqtVxDwJr56dhi0GHXRu3jVI995rMGo1fLUG5fSxiZ8L5sAtokh 9WFmQpyl Message-ID: Date: Tue, 19 Mar 2019 09:55:12 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms030807010106010901060906" X-Rspamd-Queue-Id: 4F22488904 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.46 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_ATTACHMENT(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; MX_GOOD(-0.01)[px.denninger.net]; NEURAL_HAM_SHORT(-0.93)[-0.934,0]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-2.32)[ip: (-9.88), ipnet: 104.236.64.0/18(-3.82), asn: 14061(2.17), country: US(-0.07)]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:14061, ipnet:104.236.64.0/18, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:+]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[197.57.1.68.zen.spamhaus.org : 127.0.0.11]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; SIGNED_SMIME(-2.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[denninger.net]; R_SPF_NA(0.00)[] X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Tue, 19 Mar 2019 14:55:51 -0000 This is a cryptographically signed message in MIME format. --------------ms030807010106010901060906 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 3/19/2019 09:26, Jedi Tek'Unum wrote: > On Mar 18, 2019, at 2:57 PM, Ian Lepore wrote: >> On Mon, 2019-03-18 at 14:51 -0500, Jedi Tek'Unum wrote: >>> My impression wasn=E2=80=99t that support wasn=E2=80=99t there - but = =E2=80=9Cout of the box=E2=80=9D >>> configuration wasn=E2=80=99t there. In comparison, I didn=E2=80=99t h= ave to do >>> anything to get I2C enabled in the binary distribution of Linux that >>> comes through the manufacturer. >>> >>> Its the enabling part that isn=E2=80=99t obvious to most people IMO. >>> >>> Documentation/wiki is great. But even better would be all the >>> enabling overlays already in place and the entries in loader.conf >>> already there and commented out. It would be so much easier to go to >>> a =E2=80=9Ccommon place=E2=80=9D (loader.conf), skim through the note= s, find the >>> thing that one wants, and then just uncomment the referenced line! >>> (Or any other similarly easy method.) >>> >>> >>> For FBSD to get a better foothold in this space it needs to be better= >>> documented. For example, the wiki for NEO2 < >>> http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO2> is a step-by-= >>> step guide for how to acquire and configure Linux for it. >>> >>> >> On one of my imx6 boards I have 5 SPI devices. Each device can use 3 >> or 4 different sets of pins for clock, data-in, and data-out. Plus, >> each can use literally any number of whatever gpio pins they want as >> chip selects. Even limiting the chipsels to a handfull, there would >> literally be thousands of possible combinations of devices and pin >> configurations, each one needing to be a separate overlay. >> >> Maybe you have experience primarily with rpi or some similarly cripple= d >> devices that only offer one or two choices? > If memory serves correctly, there are only 2 I2C devices on the H3/H5 a= nd the NanoPi NEO/2 implementations only externalize 1. There is only 1 S= PI AFAIK. > > I wouldn=E2=80=99t call that crippled. I chose this platform exactly be= cause of its characteristics - small, fast, cheap. It fits the project I=E2= =80=99m using it for perfectly. In fact, I can see uses for even smaller = (see Giant Board ). I understand othe= r projects may have different requirements and would drive one towards di= fferent solutions - and require more of the various interfaces. But they = aren=E2=80=99t going to be typical of hobbyist projects. > > Maybe I should pose the question in another way. What is the philosophy= for choosing GPIO as default for all the pins? These boards have a very = limited number of pins and my preference would be that the broadest range= of interface types would be the default. There are 2 UARTs exposed so I = would have picked 1 to be enabled by default. After that, with I2C and SP= I enabled, there are still 6 GPIO available. For a tiny board like this t= hat seems to be reasonable. If people have a need for slightly more GPIO = then I would expect they would be the ones configuring overlays. > > Apparently the developers of the Linux packages for these boards have c= hosen the diverse approach (=E2=80=9CFriendlyCore=E2=80=9D based on Ubunt= uCore Xenial). > > IMHO, most =E2=80=9Chobbyists=E2=80=9D would prefer the diversity appro= ach. I=E2=80=99m completely capable of becoming an expert in FBSD and thi= s sort of configuration stuff yet it isn=E2=80=99t a priority for me - I = just want to use it like any other hobbyist. The way things are now pushe= s this type of user away from FBSD. > > If there is some philosophical perspective against the diversity approa= ch then the next best thing is to have documentation that clearly and sim= ply tells people how to enable the other functionality. > > Finally, I think there is an opportunity to grow FBSD in the hobbyist w= orld of these small products. We are past the point where people can have= a real operating system running on systems at Arduino size and cost. Lin= ux has been aggressively deployed there but I can say from experience tha= t it ain=E2=80=99t pretty - I won=E2=80=99t say more as everyone reading = this has a clear understanding of why that is. I'm currently working an issue similar to this, but one that rates "highly annoying" right now rather than "catastrophically bad." The environment is a RPI2 which has GPIO and I2c configured; GPIO to drive outputs, I2c is used to read analog channels. On 11.0 this code ran perfectly well. On 12-STABLE )FreeBSD 12.0-STABLE r344818 GENERIC) =C2=A0it also runs well *BUT* generates a huge number of console messages= about spurious interrupts: intc0: Spurious interrupt detected local_intc0: Spurious interrupt detected intc0: Spurious interrupt detected intc0: Spurious interrupt detected local_intc0: Spurious interrupt detected local_intc0: Spurious interrupt detected =2E... The issue is coming from the i2c side as I have another one of these that has no I2c defined in the configuration (but is running identical code) and no messages. Something is indeed generating an /insane /number of interrupts on one of the channels: Interrupts 530k total =C2=A01159 local_intc 494k local_intc =C2=A08047 local_intc For obvious reasons I'd like to track this down (it's also generating a load average of 1.0, where it should be 0.1 or thereabouts) but I'm not sure where to start looking. config.txt looks like this: root@Pool-MCP:/mnt # cat config.txt init_uart_clock=3D3000000 enable_uart=3D1 kernel=3Du-boot.bin kernel7=3Du-boot.bin dtoverlay=3Dmmc #audio_pwm_mode=3D2 dtparam=3Di2c_arm=3Don The only "change" from what is in the default is the i2c_arm=3Don line. The "something" appears to be the i2c code, *or* it's something that's gone wrong in the DTS changes that are in the newer way of building the boot area (where the grab is of the "standard" versions from ports and then just copied over.) I suspect this would bite you equally hard if you had a RTC configured on I2c as well..... Killing the process that has the I2c interface open (so the I2c interface is not in active use, but is configured of course) does *not* stop the insane interrupt storm. --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms030807010106010901060906 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC DdgwggagMIIEiKADAgECAhMA5EiKghDOXrvfxYxjITXYDdhIMA0GCSqGSIb3DQEBCwUAMIGL MQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UEBwwJTmljZXZpbGxlMRkw FwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5c3RlbXMgQ0ExITAf BgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQTAeFw0xNzA4MTcxNjQyMTdaFw0yNzA4 MTUxNjQyMTdaMHsxCzAJBgNVBAYTAlVTMRAwDgYDVQQIDAdGbG9yaWRhMRkwFwYDVQQKDBBD dWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5c3RlbXMgQ0ExJTAjBgNVBAMMHEN1 ZGEgU3lzdGVtcyBMTEMgMjAxNyBJbnQgQ0EwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIK AoICAQC1aJotNUI+W4jP7xQDO8L/b4XiF4Rss9O0B+3vMH7Njk85fZ052QhZpMVlpaaO+sCI KqG3oNEbuOHzJB/NDJFnqh7ijBwhdWutdsq23Ux6TvxgakyMPpT6TRNEJzcBVQA0kpby1DVD 0EKSK/FrWWBiFmSxg7qUfmIq/mMzgE6epHktyRM3OGq3dbRdOUgfumWrqHXOrdJz06xE9NzY vc9toqZnd79FUtE/nSZVm1VS3Grq7RKV65onvX3QOW4W1ldEHwggaZxgWGNiR/D4eosAGFxn uYeWlKEC70c99Mp1giWux+7ur6hc2E+AaTGh+fGeijO5q40OGd+dNMgK8Es0nDRw81lRcl24 SWUEky9y8DArgIFlRd6d3ZYwgc1DMTWkTavx3ZpASp5TWih6yI8ACwboTvlUYeooMsPtNa9E 6UQ1nt7VEi5syjxnDltbEFoLYcXBcqhRhFETJe9CdenItAHAtOya3w5+fmC2j/xJz29og1KH YqWHlo3Kswi9G77an+zh6nWkMuHs+03DU8DaOEWzZEav3lVD4u76bKRDTbhh0bMAk4eXriGL h4MUoX3Imfcr6JoyheVrAdHDL/BixbMH1UUspeRuqQMQ5b2T6pabXP0oOB4FqldWiDgJBGRd zWLgCYG8wPGJGYgHibl5rFiI5Ix3FQncipc6SdUzOQIDAQABo4IBCjCCAQYwHQYDVR0OBBYE FF3AXsKnjdPND5+bxVECGKtc047PMIHABgNVHSMEgbgwgbWAFBu1oRhUMNEzjODolDka5k4Q EDBioYGRpIGOMIGLMQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UEBwwJ TmljZXZpbGxlMRkwFwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5 c3RlbXMgQ0ExITAfBgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQYIJAKxAy1WBo2kY MBIGA1UdEwEB/wQIMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgGGMA0GCSqGSIb3DQEBCwUAA4IC AQCB5686UCBVIT52jO3sz9pKuhxuC2npi8ZvoBwt/IH9piPA15/CGF1XeXUdu2qmhOjHkVLN gO7XB1G8CuluxofOIUce0aZGyB+vZ1ylHXlMeB0R82f5dz3/T7RQso55Y2Vog2Zb7PYTC5B9 oNy3ylsnNLzanYlcW3AAfzZcbxYuAdnuq0Im3EpGm8DoItUcf1pDezugKm/yKtNtY6sDyENj tExZ377cYA3IdIwqn1Mh4OAT/Rmh8au2rZAo0+bMYBy9C11Ex0hQ8zWcvPZBDn4v4RtO8g+K uQZQcJnO09LJNtw94W3d2mj4a7XrsKMnZKvm6W9BJIQ4Nmht4wXAtPQ1xA+QpxPTmsGAU0Cv HmqVC7XC3qxFhaOrD2dsvOAK6Sn3MEpH/YrfYCX7a7cz5zW3DsJQ6o3pYfnnQz+hnwLlz4MK 17NIA0WOdAF9IbtQqarf44+PEyUbKtz1r0KGeGLs+VGdd2FLA0e7yuzxJDYcaBTVwqaHhU2/ Fna/jGU7BhrKHtJbb/XlLeFJ24yvuiYKpYWQSSyZu1R/gvZjHeGb344jGBsZdCDrdxtQQcVA 6OxsMAPSUPMrlg9LWELEEYnVulQJerWxpUecGH92O06wwmPgykkz//UmmgjVSh7ErNvL0lUY UMfunYVO/O5hwhW+P4gviCXzBFeTtDZH259O7TCCBzAwggUYoAMCAQICEwCg0WvVwekjGFiO 62SckFwepz0wDQYJKoZIhvcNAQELBQAwezELMAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3Jp ZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBMTEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBD QTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExMQyAyMDE3IEludCBDQTAeFw0xNzA4MTcyMTIx MjBaFw0yMjA4MTYyMTIxMjBaMFcxCzAJBgNVBAYTAlVTMRAwDgYDVQQIDAdGbG9yaWRhMRkw FwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRswGQYDVQQDDBJrYXJsQGRlbm5pbmdlci5uZXQw ggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQC+HVSyxVtJhy3Ohs+PAGRuO//Dha9A 16l5FPATr6wude9zjX5f2lrkRyU8vhCXTZW7WbvWZKpcZ8r0dtZmiK9uF58Ec6hhvfkxJzbg 96WHBw5Fumd5ahZzuCJDtCAWW8R7/KN+zwzQf1+B3MVLmbaXAFBuKzySKhKMcHbK3/wjUYTg y+3UK6v2SBrowvkUBC+jxNg3Wy12GsTXcUS/8FYIXgVVPgfZZrbJJb5HWOQpvvhILpPCD3xs YJFNKEPltXKWHT7Qtc2HNqikgNwj8oqOb+PeZGMiWapsatKm8mxuOOGOEBhAoTVTwUHlMNTg 6QUCJtuWFCK38qOCyk9Haj+86lUU8RG6FkRXWgMbNQm1mWREQhw3axgGLSntjjnznJr5vsvX SYR6c+XKLd5KQZcS6LL8FHYNjqVKHBYM+hDnrTZMqa20JLAF1YagutDiMRURU23iWS7bA9tM cXcqkclTSDtFtxahRifXRI7Epq2GSKuEXe/1Tfb5CE8QsbCpGsfSwv2tZ/SpqVG08MdRiXxN 5tmZiQWo15IyWoeKOXl/hKxA9KPuDHngXX022b1ly+5ZOZbxBAZZMod4y4b4FiRUhRI97r9l CxsP/EPHuuTIZ82BYhrhbtab8HuRo2ofne2TfAWY2BlA7ExM8XShMd9bRPZrNTokPQPUCWCg CdIATQIDAQABo4IBzzCCAcswPAYIKwYBBQUHAQEEMDAuMCwGCCsGAQUFBzABhiBodHRwOi8v b2NzcC5jdWRhc3lzdGVtcy5uZXQ6ODg4ODAJBgNVHRMEAjAAMBEGCWCGSAGG+EIBAQQEAwIF oDAOBgNVHQ8BAf8EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMDMGCWCG SAGG+EIBDQQmFiRPcGVuU1NMIEdlbmVyYXRlZCBDbGllbnQgQ2VydGlmaWNhdGUwHQYDVR0O BBYEFLElmNWeVgsBPe7O8NiBzjvjYnpRMIHKBgNVHSMEgcIwgb+AFF3AXsKnjdPND5+bxVEC GKtc047PoYGRpIGOMIGLMQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UE BwwJTmljZXZpbGxlMRkwFwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRh IFN5c3RlbXMgQ0ExITAfBgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQYITAORIioIQ zl6738WMYyE12A3YSDAdBgNVHREEFjAUgRJrYXJsQGRlbm5pbmdlci5uZXQwDQYJKoZIhvcN AQELBQADggIBAJXboPFBMLMtaiUt4KEtJCXlHO/3ZzIUIw/eobWFMdhe7M4+0u3te0sr77QR dcPKR0UeHffvpth2Mb3h28WfN0FmJmLwJk+pOx4u6uO3O0E1jNXoKh8fVcL4KU79oEQyYkbu 2HwbXBU9HbldPOOZDnPLi0whi/sbFHdyd4/w/NmnPgzAsQNZ2BYT9uBNr+jZw4SsluQzXG1X lFL/qCBoi1N2mqKPIepfGYF6drbr1RnXEJJsuD+NILLooTNf7PMgHPZ4VSWQXLNeFfygoOOK FiO0qfxPKpDMA+FHa8yNjAJZAgdJX5Mm1kbqipvb+r/H1UAmrzGMbhmf1gConsT5f8KU4n3Q IM2sOpTQe7BoVKlQM/fpQi6aBzu67M1iF1WtODpa5QUPvj1etaK+R3eYBzi4DIbCIWst8MdA 1+fEeKJFvMEZQONpkCwrJ+tJEuGQmjoQZgK1HeloepF0WDcviiho5FlgtAij+iBPtwMuuLiL shAXA5afMX1hYM4l11JXntle12EQFP1r6wOUkpOdxceCcMVDEJBBCHW2ZmdEaXgAm1VU+fnQ qS/wNw/S0X3RJT1qjr5uVlp2Y0auG/eG0jy6TT0KzTJeR9tLSDXprYkN2l/Qf7/nT6Q03qyE QnnKiBXWAZXveafyU/zYa7t3PTWFQGgWoC4w6XqgPo4KV44OMYIFBzCCBQMCAQEwgZIwezEL MAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBM TEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExM QyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTANBglghkgBZQMEAgMFAKCCAkUw GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTkwMzE5MTQ1NTEy WjBPBgkqhkiG9w0BCQQxQgRAZhHM+ATgZDKxNMRf3Y/gWykxPKsom0+JhgmnTXxlJuPfnXCj WvKNWQXBHf0ztuNRwoLYDoYVazZroSxJFNjVGzBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFl AwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3 DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGjBgkrBgEEAYI3EAQxgZUwgZIwezEL MAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBM TEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExM QyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTCBpQYLKoZIhvcNAQkQAgsxgZWg gZIwezELMAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lz dGVtcyBMTEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0 ZW1zIExMQyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTANBgkqhkiG9w0BAQEF AASCAgAUg97vj5TSZ1LIz1rxePHbxd3bLS8iKrdgMFPDo5J2mRnk7MBdK9Tew7q/6bEMFGe/ 2bj1kqyZrAfgWm8SYGniUdNfnXZZYApFvra/J2z0Qa7cI7g7Rxy20zZTI7h5Oyi3Qom7NUap hYSzDy9ViSy2rfPHVurX2Zew3CCicz9IyBfFLRsSW5aaqSEIkyltUMtrIPkXQcc2erGoajoh P78eeC8FZ6OmVkZtPp2z3JEbgnMm3lXGCTOFqxKVrNgnC2sA7X5po//xsI/97uUNyhrzBjoN nFGUkzLlrJfDfm23ETleU64Kzv3kpiS2lPBgSjof2x2hrjizEsW7Szpmf1g1bhVdLeoVuzKX 09uMupnE5aRrFfK++ma5cNhKkb2TK6OhlLB7Os0BWh5T1K9h8UvFGq6+cmL/yb+cZO/e5lB9 UGo0cRVbmWSZp/ooESNU0rhOT189BoD1jm7rgU6Gi3/WbWGI+WNF9n3JzN+niItctNJQmzEq vq8KULxNxeLPEdWnp1/z7VRZo7J58umR4z6YubyqqBK3Vlz9tFYvGBM7qs5I+DuyAcyCGq7x 8IKiYXHqVhQsQVCCVFrrLz2R3io+KrSokodXdtnzNbu7yQkxIIGL21qA40eMr/qCzvAn6rYC tRyWpBGvj00u7GSeyzNOlkJys5R6fARmayTylgHKWgAAAAAAAA== --------------ms030807010106010901060906-- From owner-freebsd-arm@freebsd.org Tue Mar 19 16:05:22 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 C6C84155457E for ; Tue, 19 Mar 2019 16:05:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 50D6F8AEAB for ; Tue, 19 Mar 2019 16:05:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 86533CC10 for ; Tue, 19 Mar 2019 16:05:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x2JG5LqS055289 for ; Tue, 19 Mar 2019 16:05:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x2JG5LxL055288 for freebsd-arm@FreeBSD.org; Tue, 19 Mar 2019 16:05:21 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 236639] Beaglebone Black: Misaligned cache warning until kernel is loaded (FreeBSD 13.0-CURRENT) Date: Tue, 19 Mar 2019 16:05:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gndaryee@uwaterloo.ca X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Tue, 19 Mar 2019 16:05:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236639 Bug ID: 236639 Summary: Beaglebone Black: Misaligned cache warning until kernel is loaded (FreeBSD 13.0-CURRENT) Product: Base System Version: CURRENT Hardware: arm OS: Any Status: New Severity: Affects Some People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: gndaryee@uwaterloo.ca Created attachment 202982 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D202982&action= =3Dedit Log from loader.efi up until /boot/kernel/kernel is loaded. The warning: `CACHE: Misaligned operation at range [#####, #####]` is print= ed repeatedly after booting "loader.efi" (downloaded via DHCP along with built FreeBSD DTBs). Full logs are included. After discussions on IRC, it was determined that: "the CACHE warnings from u-boot are due to some local variable in our ip stack in loader that aren't aligned" --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Tue Mar 19 16:14:34 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 D094C15548F5 for ; Tue, 19 Mar 2019 16:14:33 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8E2A28B4EE for ; Tue, 19 Mar 2019 16:14:32 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id x2JGEQfd036545 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 19 Mar 2019 17:14:27 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1553012068; bh=lybtxszECUf1D8I6KtKG17MIrBS8rBUzoVyQ+xe0rPA=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=BkHJUAd+KF1BBxSR8qAdsk2lH2AGmgouxZAwSGb0/jSlheu3/uoJN/BznJ9znrDfs 6FWIsSpsd01hr8OiqgZO6B95Q1bOP5nXnRKuSjIUCNgIUw1kAWL35imRhaLjlG06qo V6A3vpLA+gxKvQN3cX9BFhwLsoWTwW13J3j5PYys= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id x2JGEOxP030013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Mar 2019 17:14:24 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id x2JGEOuL042318; Tue, 19 Mar 2019 17:14:24 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id x2JGENmi042317; Tue, 19 Mar 2019 17:14:23 +0100 (CET) (envelope-from ticso) Date: Tue, 19 Mar 2019 17:14:23 +0100 From: Bernd Walter To: Karl Denninger Cc: freebsd-arm@freebsd.org Subject: Re: Options for FBSD support with LCD device - new project [[Maybe related: I2c issues on the Pi2]] Message-ID: <20190319161423.GH57400@cicely7.cicely.de> Reply-To: ticso@cicely.de 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> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 12.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-Rspamd-Queue-Id: 8E2A28B4EE X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cicely.de header.s=default header.b=BkHJUAd+ X-Spamd-Result: default: False [-1.77 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[ticso@cicely.de]; R_DKIM_ALLOW(-0.20)[cicely.de:s=default]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-0.98)[-0.983,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cicely.de]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mx1.bwct.de]; DKIM_TRACE(0.00)[cicely.de:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[3.99.149.195.list.dnswl.org : 127.0.20.0]; NEURAL_HAM_MEDIUM(-0.74)[-0.741,0]; R_SPF_NA(0.00)[]; NEURAL_HAM_SHORT(-0.24)[-0.239,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:21461, ipnet:195.149.99.0/24, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.00)[country: DE(-0.01)] 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: Tue, 19 Mar 2019 16:14:34 -0000 On Tue, Mar 19, 2019 at 09:55:12AM -0500, Karl Denninger wrote: > On 3/19/2019 09:26, Jedi Tek'Unum wrote: > > On Mar 18, 2019, at 2:57 PM, Ian Lepore wrote: > >> On Mon, 2019-03-18 at 14:51 -0500, Jedi Tek'Unum wrote: > >>> My impression wasn???t that support wasn???t there - but ???out of the box??? > >>> configuration wasn???t there. In comparison, I didn???t have to do > >>> anything to get I2C enabled in the binary distribution of Linux that > >>> comes through the manufacturer. > >>> > >>> Its the enabling part that isn???t obvious to most people IMO. > >>> > >>> Documentation/wiki is great. But even better would be all the > >>> enabling overlays already in place and the entries in loader.conf > >>> already there and commented out. It would be so much easier to go to > >>> a ???common place??? (loader.conf), skim through the notes, find the > >>> thing that one wants, and then just uncomment the referenced line! > >>> (Or any other similarly easy method.) > >>> > >>> > >>> For FBSD to get a better foothold in this space it needs to be better > >>> documented. For example, the wiki for NEO2 < > >>> http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO2> is a step-by- > >>> step guide for how to acquire and configure Linux for it. > >>> > >>> > >> On one of my imx6 boards I have 5 SPI devices. Each device can use 3 > >> or 4 different sets of pins for clock, data-in, and data-out. Plus, > >> each can use literally any number of whatever gpio pins they want as > >> chip selects. Even limiting the chipsels to a handfull, there would > >> literally be thousands of possible combinations of devices and pin > >> configurations, each one needing to be a separate overlay. > >> > >> Maybe you have experience primarily with rpi or some similarly crippled > >> devices that only offer one or two choices? > > If memory serves correctly, there are only 2 I2C devices on the H3/H5 and the NanoPi NEO/2 implementations only externalize 1. There is only 1 SPI AFAIK. > > > > I wouldn???t call that crippled. I chose this platform exactly because of its characteristics - small, fast, cheap. It fits the project I???m using it for perfectly. In fact, I can see uses for even smaller (see Giant Board ). I understand other projects may have different requirements and would drive one towards different solutions - and require more of the various interfaces. But they aren???t going to be typical of hobbyist projects. > > > > Maybe I should pose the question in another way. What is the philosophy for choosing GPIO as default for all the pins? These boards have a very limited number of pins and my preference would be that the broadest range of interface types would be the default. There are 2 UARTs exposed so I would have picked 1 to be enabled by default. After that, with I2C and SPI enabled, there are still 6 GPIO available. For a tiny board like this that seems to be reasonable. If people have a need for slightly more GPIO then I would expect they would be the ones configuring overlays. > > > > Apparently the developers of the Linux packages for these boards have chosen the diverse approach (???FriendlyCore??? based on UbuntuCore Xenial). > > > > IMHO, most ???hobbyists??? would prefer the diversity approach. I???m completely capable of becoming an expert in FBSD and this sort of configuration stuff yet it isn???t a priority for me - I just want to use it like any other hobbyist. The way things are now pushes this type of user away from FBSD. > > > > If there is some philosophical perspective against the diversity approach then the next best thing is to have documentation that clearly and simply tells people how to enable the other functionality. > > > > Finally, I think there is an opportunity to grow FBSD in the hobbyist world of these small products. We are past the point where people can have a real operating system running on systems at Arduino size and cost. Linux has been aggressively deployed there but I can say from experience that it ain???t pretty - I won???t say more as everyone reading this has a clear understanding of why that is. > > I'm currently working an issue similar to this, but one that rates > "highly annoying" right now rather than "catastrophically bad." > > The environment is a RPI2 which has GPIO and I2c configured; GPIO to > drive outputs, I2c is used to read analog channels. > > On 11.0 this code ran perfectly well. > > On 12-STABLE )FreeBSD 12.0-STABLE r344818 GENERIC) > it also runs well *BUT* generates a huge number of console messages > about spurious interrupts: > > intc0: Spurious interrupt detected > local_intc0: Spurious interrupt detected > intc0: Spurious interrupt detected > intc0: Spurious interrupt detected > local_intc0: Spurious interrupt detected > local_intc0: Spurious interrupt detected > > .... > > The issue is coming from the i2c side as I have another one of these > that has no I2c defined in the configuration (but is running identical > code) and no messages. Interesting. A local Pi1 running 12-RELEASE has the same messages: intc0: Spurious interrupt detected intc0: Spurious interrupt detected intc0: Spurious interrupt detected intc0: Spurious interrupt detected intc0: Spurious interrupt detected intc0: Spurious interrupt detected intc0: Spurious interrupt detected I have an I2C RTC on this machine. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Wed Mar 20 10:24:21 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 C314B154F046 for ; Wed, 20 Mar 2019 10:24:20 +0000 (UTC) (envelope-from mk@semihalf.com) Received: from mail-ed1-x544.google.com (mail-ed1-x544.google.com [IPv6:2a00:1450:4864:20::544]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5264C8F92F for ; Wed, 20 Mar 2019 10:24:19 +0000 (UTC) (envelope-from mk@semihalf.com) Received: by mail-ed1-x544.google.com with SMTP id q3so1511088edg.0 for ; Wed, 20 Mar 2019 03:24:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=zMlyCR0ry6wOsrQ0PEUoHthq3WCsonL14wkJo3H33yA=; b=jlhnMPav7mFLVRR89gIzk2N0jtGXNFpKRq8jgnFTuKNkwfNTj95dTTyb78xbgsHDgT z26oJG/tQ8pti7cHW+K+n6EA0nNfKLshhcW18nRft8flYqFyf8UolEb6a5WVyteptgZ1 8CZWCwzK5XD51Kn10TskU33s9f44rnoHknE/UdOcf4dk7uoOWdU2aLOM4TV6RT6Sz6De SzDvoY54QmWXMlXfIy5z0daU1I3ZMj8J0sDeoEyXLBLDQU7Ddcpf/H9gztHC+VY/1zRQ nV8Y0Hg4E4+/fuEzBTh152qNlWc+DyVrzFNSc3PCRR8AEA90TB/IgawdpQ3t3US8rI7V FbBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=zMlyCR0ry6wOsrQ0PEUoHthq3WCsonL14wkJo3H33yA=; b=Q8hQGZl2dA3PfxJX2lHk0+tOBtwDjMhvqP6/ooP3Fqw+Ytb5rin2cZtgps1RsJqaZW AsFDi8AqIRl4fD7LpOTbUqN4vEIXwJADwEsbBwE/wK+5l0G4hY9Valzm1X8SnJypqVtl 6u5RJOeRacZznrF6Ra2WnHHwz6uRq0WP0l1Nz5wV4BOHquk5ou3Kvj26zueU3XNys/rz AU18dQiMm8r+4y2AZlztKtRwGDVRcuDyLG1cf3PA6chzmLOcY2Va9qbJr7+Gmda9AaH8 eNfRDXaUuOIZzpYiH0DekUp2c9YuA49GTzY1Xd0R8EPU2Yp1Wi2u09f4DGCHSnQfxxMT J1WA== X-Gm-Message-State: APjAAAVZg6tMr33tMJeplosrPGcEKY1uzO8DLDFmlGep5qKRKTgQ/ShM qA1NGAt969fCk1UGTE4vB1HwwWeg0kZ8VgYhqx+9BxH04bk= X-Google-Smtp-Source: APXvYqypAH4471ohlQULJKGD2KehmONMJ3IT05QGlpLGuR9VD2dT4bCr9caUNm2Nm0yPrQ8yf0i8jFkjxAX9AaAZWWE= X-Received: by 2002:a17:906:b291:: with SMTP id q17mr12217700ejz.56.1553077458253; Wed, 20 Mar 2019 03:24:18 -0700 (PDT) MIME-Version: 1.0 References: <79CC79B9-81AF-4563-BABE-429E6A57F476@bmalum.com> <010201686fe5047f-ed14af85-2b25-4480-a62a-a893f062eedd-000000@eu-west-1.amazonses.com> <010201686fe5047f-ed14af85-2b25-4480-a62a-a893f062eedd-000000@eu-west-1.amazo> <1548182399.2864.0@smtp.migadu.com> <1552255580.21373.0@unrelenting.technology> <01000169992ab14c-aa38b2f1-3f57-4805-9d8a-fa92207e4c2d-000000@email.amazonses.com> In-Reply-To: <01000169992ab14c-aa38b2f1-3f57-4805-9d8a-fa92207e4c2d-000000@email.amazonses.com> From: =?UTF-8?Q?Micha=C5=82_Krawczyk?= Date: Wed, 20 Mar 2019 11:24:07 +0100 Message-ID: Subject: Re: ARM Graviton AWS Processor (AMI Image) To: Colin Percival Cc: Marcin Wojtas , Greg V , "Matushevsky, Alexander" , Martin Karrer , =?UTF-8?B?UmFmYcWCIEtvemlr?= , freebsd-arm@freebsd.org, "Tzalik, Guy" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 5264C8F92F X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=semihalf-com.20150623.gappssmtp.com header.s=20150623 header.b=jlhnMPav X-Spamd-Result: default: False [-4.03 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.996,0]; R_DKIM_ALLOW(-0.20)[semihalf-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[semihalf.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[semihalf-com.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[ASPMX2.GOOGLEMAIL.com,ALT2.ASPMX.L.GOOGLE.com,ASPMX.L.GOOGLE.com,ALT1.ASPMX.L.GOOGLE.com,ASPMX3.GOOGLEMAIL.com]; RCPT_COUNT_SEVEN(0.00)[8]; RCVD_IN_DNSWL_NONE(0.00)[4.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; NEURAL_HAM_SHORT(-0.78)[-0.778,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-0.95)[ip: (-0.18), ipnet: 2a00:1450::/32(-2.38), asn: 15169(-2.11), country: US(-0.07)] 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: Wed, 20 Mar 2019 10:24:21 -0000 Hi, we have solution for two of the issues with ENA, The double resource activation can be fixed by this patch: https://reviews.freebsd.org/D19655 And the issue with reloading module/reconfiguring it by using ifconfig can be fixed by using this patch: https://reviews.freebsd.org/D19641 Please check if that fixes it for you. Thanks, Micha=C5=82 =C5=9Br., 20 mar 2019 o 04:35 Colin Percival napisa= =C5=82(a): > > Hi ENA people, > > Any luck figuring out what was going on with the ENA driver here > with interrupt activation? > > Colin Percival > > On 3/11/19 1:35 AM, Marcin Wojtas wrote: > > +FreeBSD ENA maintainers > > > > W dniu pon., 11.03.2019 o 00:40 Greg V > > napisa=C5=82(a): > > > >> > >> On Tue, Jan 22, 2019 at 9:39 PM, Greg V > >> wrote: > >>> On Mon, Jan 21, 2019 at 1:11 PM, Martin Karrer > >>> wrote: > >>>> My question is if there are any plans yet to support the Graviton > >>>> ARM instances of AWS? > >>>> > >>>> We have a heavy load on FreeBSD and would also use the ARM > >>>> instances. Are there any other interested parties? > >>> > >>> I have tried this. It should work very well in theory, e.g. the > >>> network card driver (if_ena) compiles with no changes for aarch64, > >>> and in fact NetBSD has ported this driver and is up and running on > >>> these instances: https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4= 623 > >>> > >>> But my result with FreeBSD was: nothing on the console after > >>> loader.efi hands control to the kernel. > >>> [=E2=80=A6] > >> > >> Hello everyone, big update: > >> > >> FreeBSD/aarch64 on Amazon EC2 a1 (AWS Graviton) instances WORKS! > >> > >> https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4813 > >> > >> And you can try it (well, my -CURRENT build, NO WARRANTY etc) right no= w: > >> > >> ami-0c2829a0b82a62ca6 in eu-west-1 (Ireland) > >> > >> ----- > >> > >> So, what I had to do / what should be done / how others can help get > >> this into a finished state: > >> > >> 1. Serial console: > >> - I fixed it: https://reviews.freebsd.org/D19507 > >> - (I learned some things about UARTs and their support in FreeBSD, > >> should write a blog post about that) > >> > >> 2. aarch64 build configuration: > >> - if_ena network driver module should be enabled: > >> https://reviews.freebsd.org/D18372 > >> - NVMe driver should be enabled in the GENERIC kernel config (devic= e > >> nvme, device nvd) > >> - BTW, why not also go with hw.nvme.use_nvd=3D"0" by default on > >> aarch64, IIRC that was done on powerpc64 > >> > >> 3. VM image build system: > >> - GPT+EFI should be used (amd64 was GPT with no EFI, and aarch64 wa= s > >> MBR with EFI (???)): https://reviews.freebsd.org/D18371 > >> - bsdec2-image-upload --arm64 flag should be supported: included > >> above ^^ > >> - ec2.conf: amazon-ssm-agent shouldn't be installed when building > >> for aarch64 TARGET, since that's written in Go, and Go isn't ported to > >> FreeBSD/aarch64 yet: > >> > >> https://github.com/myfreeweb/freebsd/commit/5b530ebf7385d8320b9076cf84= f50aad01689bc > >> (untested patch, I actually used an interactive shell in between the > >> image build commands) > >> - qemu-aarch64-static should be used for preinstalling pkgs when > >> chrooting into the image: rough version included above ^^ > >> > >> 4. ENA (Elastic Network Adapter) driver: > >> - it works > >> - except there's something funky with interrupt activation, and it > >> hits panic("Attempt to double activation of resource id: %u\n", res_id= ) > >> (for the management IRQ) on boot, so I applied the obvious silly > >> workaround of "don't panic": > >> > >> https://github.com/myfreeweb/freebsd/commit/a7e7c6e48cdbdb0fdc6c4e0ba6= 3392262938e62c > >> - but still, it doesn't properly reactivate interrupts (and the box > >> becomes unreachable over the net) after going down and up again =E2=80= =94 > >> guess what does that on boot? dhclient applying the big jumbo MTU =E2= =80=94 > >> so I set dhclient.conf to reject MTU changes: > >> > >> https://github.com/myfreeweb/freebsd/commit/03ec4d417b0b4252285baaf4e2= 94cc6d8c870f7f > >> > >> > >> Would be great if someone familiar with interrupts and stuff could hel= p > >> debug the ena driver and make it work without these hacks :) > -- > Colin Percival > Security Officer Emeritus, FreeBSD | The power to serve > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoi= d From owner-freebsd-arm@freebsd.org Wed Mar 20 11:17:19 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 B8A4015507DB for ; Wed, 20 Mar 2019 11:17:19 +0000 (UTC) (envelope-from 010201699ad1ceb2-b60498e4-cd21-4ff2-8f89-beb8cacb59ff-000000@eu-west-1.amazonses.com) Received: from a4-6.smtp-out.eu-west-1.amazonses.com (a4-6.smtp-out.eu-west-1.amazonses.com [54.240.4.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F279918A9 for ; Wed, 20 Mar 2019 11:17:17 +0000 (UTC) (envelope-from 010201699ad1ceb2-b60498e4-cd21-4ff2-8f89-beb8cacb59ff-000000@eu-west-1.amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=uwfrvhlat3drqdfg3hx77nynjjjdh6z6; d=sitaridev.co.za; t=1553080635; h=Message-ID:Date:Subject:From:Reply-To:To:MIME-Version:Content-Type:List-Unsubscribe:List-Id; bh=TDuiPcoVv8jDGXoHAzN9oJpxvsHrpKciaW1TkkUXb9Q=; b=iBLPZCG4jf+3evZBm37U5gG2r0zJ9pDCLDe7l3QhUtaGHgDYzID7Rd02j20zsoxO LAhnA0o7TALTx0cBM2gS86m908PzrqttqBG+yXvzy4Rvqy0gPkPbdY4OX5xAuD7mZEO Wv0buChdFsM23z7WZEahP2I8qz5Ga7vRvmBX5UhQ= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ihchhvubuqgjsxyuhssfvqohv7z3u4hn; d=amazonses.com; t=1553080635; h=Message-ID:Date:Subject:From:Reply-To:To:MIME-Version:Content-Type:List-Unsubscribe:List-Id:Feedback-ID; bh=TDuiPcoVv8jDGXoHAzN9oJpxvsHrpKciaW1TkkUXb9Q=; b=bXI+5PZgBQWHJfNJqr05wV07US6eQ3ohi3rX9JzSr7LanQILgDrp2/6BVnptlQer S0TA+1WJAWyXO4Tnu+njc84McR+a6XEX2QI0cYeXko/2BbqrL/SXyVkj6tCLb3/sgCF ZHz0LiVAdrRXOqDPeK6uw40gByo51YSSg1NUpE0s= Message-ID: <010201699ad1ceb2-b60498e4-cd21-4ff2-8f89-beb8cacb59ff-000000@eu-west-1.amazonses.com> Date: Wed, 20 Mar 2019 11:17:15 +0000 Subject: News Letter | Designer Apartments | Secure Estate Living | The Boulevard From: Sitari Country Estate | Somerset West Reply-To: Sitari Country Estate | Somerset West To: "freebsd-arm@freebsd.org" MIME-Version: 1.0 X-Sender: schelderberg@sitaridev.co.za X-Report-Abuse: Please report abuse for this campaign here: http://leopardmail.co.za/campaigns/kk547pghswebd/report-abuse/pw058x59yb143/lp84242dqnbe5 X-Receiver: freebsd-arm@freebsd.org X-Jgoy-Tracking-Did: 0 X-Jgoy-Subscriber-Uid: lp84242dqnbe5 X-Jgoy-Mailer: SwiftMailer - 5.4.x X-Jgoy-EBS: http://leopardmail.co.za/lists/block-address X-Jgoy-Delivery-Sid: 11 X-Jgoy-Customer-Uid: wh555e142oa00 X-Jgoy-Customer-Gid: 3 X-Jgoy-Campaign-Uid: kk547pghswebd Precedence: bulk Feedback-ID: 1.eu-west-1.uvn48qXFNfbBCSq27QjYopu03+ZevnFjz7NsiwWAkk8=:AmazonSES X-SES-Outgoing: 2019.03.20-54.240.4.6 X-Rspamd-Queue-Id: 9F279918A9 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=sitaridev.co.za header.s=uwfrvhlat3drqdfg3hx77nynjjjdh6z6 header.b=iBLPZCG4; dkim=pass header.d=amazonses.com header.s=ihchhvubuqgjsxyuhssfvqohv7z3u4hn header.b=bXI+5PZg; spf=pass (mx1.freebsd.org: domain of 010201699ad1ceb2-b60498e4-cd21-4ff2-8f89-beb8cacb59ff-000000@eu-west-1.amazonses.com designates 54.240.4.6 as permitted sender) smtp.mailfrom=010201699ad1ceb2-b60498e4-cd21-4ff2-8f89-beb8cacb59ff-000000@eu-west-1.amazonses.com X-Spamd-Result: default: False [-6.55 / 15.00]; HAS_REPLYTO(0.00)[property@sitaridev.co.za]; R_SPF_ALLOW(-0.20)[+ip4:54.240.0.0/18]; REPLYTO_DN_EQ_FROM_DN(0.00)[]; MX_GOOD(-0.01)[feedback-smtp.eu-west-1.amazonses.com,feedback-smtp.eu-west-1.amazonses.com,feedback-smtp.eu-west-1.amazonses.com]; DKIM_TRACE(0.00)[sitaridev.co.za:+,amazonses.com:+]; NEURAL_HAM_SHORT(-0.98)[-0.976,0]; MAILLIST(-0.10)[generic]; FORGED_SENDER(0.00)[schelderberg@sitaridev.co.za,010201699ad1ceb2-b60498e4-cd21-4ff2-8f89-beb8cacb59ff-000000@eu-west-1.amazonses.com]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+,1:+]; IP_SCORE(-3.00)[ip: (-9.22), ipnet: 54.240.0.0/21(-4.41), asn: 16509(-1.32), country: US(-0.07)]; ASN(0.00)[asn:16509, ipnet:54.240.0.0/21, country:US]; FROM_NEQ_ENVFROM(0.00)[schelderberg@sitaridev.co.za,010201699ad1ceb2-b60498e4-cd21-4ff2-8f89-beb8cacb59ff-000000@eu-west-1.amazonses.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[sitaridev.co.za:s=uwfrvhlat3drqdfg3hx77nynjjjdh6z6,amazonses.com:s=ihchhvubuqgjsxyuhssfvqohv7z3u4hn]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PRECEDENCE_BULK(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[sitaridev.co.za]; REPLYTO_DOM_EQ_FROM_DOM(0.00)[]; HAS_LIST_UNSUB(-0.01)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MANY_INVISIBLE_PARTS(0.05)[1]; RCVD_IN_DNSWL_NONE(0.00)[6.4.240.54.list.dnswl.org : 127.0.15.0]; TO_DN_EQ_ADDR_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[]; FORGED_SENDER_MAILLIST(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Mar 2019 11:17:20 -0000 News Letter | Designer Apartments | Secure Estate Living | The Boulevard= NEW DEVELOPMENT =E2=80=A2 HELDERBERG THE BOULEVARD PREMIUM APARTMENT= S =C2=A0 Move Into an Impeccably Designed Apartment With Every Detail= Considered =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Discover an Apar= tment Like No Other Now Selling from R 1 395 000 (Includes Transfer Dut= y) =C2=A0 =C2=A0 CALL ME BACK http://leopardmail.co.za/campaigns/kk= 547pghswebd/track-url/lp84242dqnbe5/baed8443b250867638ec47f4d83e46e51f2597e= e =C2=A0 GET SALES PACK =C2=A0 =C2=A0 =C2=A0 =C2=A0 VISIT WEB= SITE http://leopardmail.co.za/campaigns/kk547pghswebd/track-url/lp84242dq= nbe5/9095e7399a22d0a4343ccc16eb5cdbcdc68ef918 =C2=A0 =C2=A0 Click her= e if you're not able to view this mailer http://leopardmail.co.za/campaig= ns/kk547pghswebd/track-url/lp84242dqnbe5/6ee0313e33e33e8de06f4a4710f2f0560a= e95106 This email was sent to freebsd-arm@freebsd.org on=C2=A003/20/2019= Unsubscribe http://leopardmail.co.za/lists/pw058x59yb143/unsubscribe/l= p84242dqnbe5/kk547pghswebd ~ Report email as unsolicited http://leopard= mail.co.za/campaigns/kk547pghswebd/track-url/lp84242dqnbe5/4fa4f4b405039ccb= c67efff5262168434b1cbb68 Sitari Country Estate 5th Floor, Madison Squar= e 4 Howick Slot Bellville Western Cape 7570 South Africa Leopard Mail= is an email-marketing service that serves companies of all shapes and si= zes. With several users/companies sending campaigns to hundreds of mill= ions of recipients, we're bound to get abuse reports.=C2=A0 We take abuse= reports seriously, if you believe a customer is sending unsolicited and = or spam email, please report abuse immediately HERE http://leopardmail.co= .za/campaigns/kk547pghswebd/track-url/lp84242dqnbe5/4fa4f4b405039ccbc67efff= 5262168434b1cbb68 =C2=A0 From owner-freebsd-arm@freebsd.org Wed Mar 20 14:56:28 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 B78B5155613B for ; Wed, 20 Mar 2019 14:56:28 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound3d.ore.mailhop.org (outbound3d.ore.mailhop.org [54.186.57.195]) (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 069D56AB79 for ; Wed, 20 Mar 2019 14:56:27 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1553093780; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=ew/KfstEXgrerBzVMs9Y864fcg6uEIpDgNPnQDPGZbV2rl3chK28/LjcuwBDf+pQaR/6RKmZKP3MG Vxo3zEq1OtYeQ6u2X8Ek0+XeSaxNLvOdoU2JpTaww6AcV+Yiak3vb+YPZv5W//9h2EyAYWuu4bSjup y9j9ex6EzR2cD1KwUqegvJjrSNWiPXiuoVVnOn35BvMnDvOunVIA+hA/YoQURmv0OygK/M7j1ImPAe 9ttbmTnmKaGcdy3+bdEtFhtRYCBKzAPLC7+LkAML7+ibgy2FfPXN3cWV8ehBFAubcXRb172sAdWAd2 oB9S1ie7ZEXmDKdhGN+TLsFBXdSgdew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=umDdha8I2PWegq9PrZAT6n8RLb01rRD1Kd459rIAVGw=; b=sfXFttFYK6SeSpMbwqUk95x1gdul8pcRnyttM/086xyheW1K1n85Zks17pUft+t6v6OpdRvvBYapT GdLRBY/kiKDlGp8n612eWZmDQTfYjSeCOK9AKIvKDRP1rDc0pe/mrArpEvnW5mZiK9JnmJKJ/zoMcD dd/H9ers1SENisH1cDWMW+yG3wlqRV/H1tXCDO+8NFoZBd3OQjV2ANfPiVuHSKem2qxobIvRc6Vpf2 pg9cnbBvGMIrneGCPcGCsA3AEra1V3gEHNG+dEkPF1NlRONXHgdCM6z9S1x9VQ4PXl4C4Rho5gXWvW QwhpjS9ZGAY4MXmrjY4+2fWqQsETCvQ== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=umDdha8I2PWegq9PrZAT6n8RLb01rRD1Kd459rIAVGw=; b=bWTWyE5G+k7bmfKKu0FcQBnhq1QadHQhrUr1U+EkgVE2pBlMc8R8Fo48lhVyMx3wFc8fbfn723659 fZDpHq6RfaFSqXHXnvhe0xV2ICUrwMKdLj0ZNiQiInIHRQ4Uram5LJ+5q9+nJdCyARXLhjUZVeeQB8 WM2FXXSBvUMnGU4kbDpLzFznu6sVeCRZ9i/s+2K1PDlHtISVYApC2XBdXcyuHUEiRjoExYj14QXPhd BgcTt5N5pt55dcnfQ/uqu6Rs5atS/0MZqhzYdPs/yxMl65PbbIG4p4T85YpsEhs684SjgvBBPk5tFC /9eau2N+gAtM2wKvjurHL72K3WL8wQA== X-MHO-RoutePath: aGlwcGll X-MHO-User: 51077c7e-4b20-11e9-9bb1-1f29e4676f89 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 51077c7e-4b20-11e9-9bb1-1f29e4676f89; Wed, 20 Mar 2019 14:56:19 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x2KEuHkb069099; Wed, 20 Mar 2019 08:56:17 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <17133d06965e61e7e835c5ea7d69ca9762efad7d.camel@freebsd.org> Subject: Re: Options for FBSD support with LCD device - new project From: Ian Lepore To: "Jedi Tek'Unum" Cc: freebsd-arm@freebsd.org Date: Wed, 20 Mar 2019 08:56:17 -0600 In-Reply-To: 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> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 069D56AB79 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.988,0]; ASN(0.00)[asn:16509, ipnet:54.186.0.0/15, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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: Wed, 20 Mar 2019 14:56:29 -0000 On Tue, 2019-03-19 at 09:26 -0500, Jedi Tek'Unum wrote: > On Mar 18, 2019, at 2:57 PM, Ian Lepore wrote: > > > > On Mon, 2019-03-18 at 14:51 -0500, Jedi Tek'Unum wrote: > > > My impression wasn’t that support wasn’t there - but “out of the > > > box” > > > configuration wasn’t there. In comparison, I didn’t have to do > > > anything to get I2C enabled in the binary distribution of Linux > > > that > > > comes through the manufacturer. > > > > > > Its the enabling part that isn’t obvious to most people IMO. > > > > > > Documentation/wiki is great. But even better would be all the > > > enabling overlays already in place and the entries in loader.conf > > > already there and commented out. It would be so much easier to go > > > to > > > a “common place” (loader.conf), skim through the notes, find the > > > thing that one wants, and then just uncomment the referenced > > > line! > > > (Or any other similarly easy method.) > > > > > > > > > For FBSD to get a better foothold in this space it needs to be > > > better > > > documented. For example, the wiki for NEO2 < > > > http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO2>; is a > > > step-by- > > > step guide for how to acquire and configure Linux for it. > > > > > > > > > > On one of my imx6 boards I have 5 SPI devices. Each device can use > > 3 > > or 4 different sets of pins for clock, data-in, and data- > > out. Plus, > > each can use literally any number of whatever gpio pins they want > > as > > chip selects. Even limiting the chipsels to a handfull, there > > would > > literally be thousands of possible combinations of devices and pin > > configurations, each one needing to be a separate overlay. > > > > Maybe you have experience primarily with rpi or some similarly > > crippled > > devices that only offer one or two choices? > > If memory serves correctly, there are only 2 I2C devices on the H3/H5 > and the NanoPi NEO/2 implementations only externalize 1. There is > only 1 SPI AFAIK. > > I wouldn’t call that crippled. I chose this platform exactly because > of its characteristics - small, fast, cheap. It fits the project I’m > using it for perfectly. In fact, I can see uses for even smaller (see > Giant Board ). I understand other > projects may have different requirements and would drive one towards > different solutions - and require more of the various interfaces. But > they aren’t going to be typical of hobbyist projects. > > Maybe I should pose the question in another way. What is the > philosophy for choosing GPIO as default for all the pins? These > boards have a very limited number of pins and my preference would be > that the broadest range of interface types would be the default. > There are 2 UARTs exposed so I would have picked 1 to be enabled by > default. After that, with I2C and SPI enabled, there are still 6 GPIO > available. For a tiny board like this that seems to be reasonable. If > people have a need for slightly more GPIO then I would expect they > would be the ones configuring overlays. > > Apparently the developers of the Linux packages for these boards have > chosen the diverse approach (“FriendlyCore” based on UbuntuCore > Xenial). > > IMHO, most “hobbyists” would prefer the diversity approach. I’m > completely capable of becoming an expert in FBSD and this sort of > configuration stuff yet it isn’t a priority for me - I just want to > use it like any other hobbyist. The way things are now pushes this > type of user away from FBSD. > > If there is some philosophical perspective against the diversity > approach then the next best thing is to have documentation that > clearly and simply tells people how to enable the other > functionality. > > Finally, I think there is an opportunity to grow FBSD in the hobbyist > world of these small products. We are past the point where people can > have a real operating system running on systems at Arduino size and > cost. Linux has been aggressively deployed there but I can say from > experience that it ain’t pretty - I won’t say more as everyone > reading this has a clear understanding of why that is. > The default pin assignments in the dts are completely controlled by linux, and I think effectively by the actual board vendors who create the dts and submit it to linux. We (freebsd) are just a consumer of the dts info, we have to work with whatever they shove down our throats, and continually re-adapt ourselves whenever they change their minds and make arbitrary incompatible changes from one release to the next (which they definitely do). -- Ian From owner-freebsd-arm@freebsd.org Wed Mar 20 15:00:22 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 52C3C15562D8 for ; Wed, 20 Mar 2019 15:00:22 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound3d.ore.mailhop.org (outbound3d.ore.mailhop.org [54.186.57.195]) (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 B18BF6AD01 for ; Wed, 20 Mar 2019 15:00:21 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1553094020; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=Ep/3/k2fgCY7QzBWix1NGU+Ay+mDf6uR8J04mvgKYNVxLIYYKauC7vzTc4/Xe9QevwVsHgr27B5/I sUnZ1RoyeNFlfRTk1PrecQiO9ZLFVMkLPcdt9mwDMbnmeN0IH6S9ZZ6BwsJqWlfKa+7W8caRxnl27v CEwOYElPoHyjPRCKq6+2UkL3qhnCD6v2F1WXLgwcJbAEOCnjwUYb/CgL8xWV7cQLyjdtG8NhjrpoPE +fqMJCsX4I4beu6r883MX9RHawCpp0QJwU2xBqJmBfmfGIWyQQprf6BZibg0KavVL8uYBklIXRtVpj C/yKYFpXvlWwk134w11r+iKBALYOxeg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=pVVWUh2gpVxCcxhoJpntCTP6X81Kg2CC87sJRoVzT74=; b=CGKoGEV6dmspzlu/XCO2kmRpVM2VPFd8D9WAdd8SCnhMk3VmgCzo1br9gLlETVJFLgTQKkk4+WQ0i 40gCUysTydWwsF0GfS4rF1mJ/+rVOrU5d5kTVsN0rHc1jmOG90Am9VgjZAwMtW7EXIwiXeDdmCOr7v fLUDozcHY80QW4wrVDdoaVcvHjewywNIOkLPsOCvcteE4RrtaH1C/g5djDZxg1w12DYXLYA3i3DQSM tSecGOUxgX02+6zDxUl3RxPou2hy9MOpF7MJXqEgdqR9tJwlQgM7I/f055Bz3LwiKLgf8V2rkaANZQ XonHTbRQhFJRP1r/ea9RW32iRGAeF5w== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=pVVWUh2gpVxCcxhoJpntCTP6X81Kg2CC87sJRoVzT74=; b=JtZi4scarkoh3ZfyNqkLcu/k3jAVkZgEcNEaXIZjJm0tB3uG4r4EEepN32lhHYne1pVH1tsjcbqzF 1uVKk7b6tP7s08FyWANHdV2bGEoanLp9WLYOEc+mCT/ZH6cUEdnRdd+s3G9MDjqeWOQARkLcFalIEM 9Hwj5nw+EhcV9Euc4MuXIs49OOXMl6AIVrnozU73LPCOQMytkuWRJ2Z6MPSpPipCoI8uymFIe4QA06 pMwa2Fohkl7zIJYcb7RrmpYUmRmJ1pqtk12Klob0ib8KbbGj7t20QEwchxA3mAYoYaQ35dn3G7EARf TQtOkGtsqfUGY0T/zsBULtOZ4xD6ZlQ== X-MHO-RoutePath: aGlwcGll X-MHO-User: e02686da-4b20-11e9-9bb1-1f29e4676f89 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id e02686da-4b20-11e9-9bb1-1f29e4676f89; Wed, 20 Mar 2019 15:00:19 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x2KF0Iuv069124; Wed, 20 Mar 2019 09:00:18 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: Options for FBSD support with LCD device - new project [[Maybe related: I2c issues on the Pi2]] From: Ian Lepore To: Karl Denninger , freebsd-arm@freebsd.org Date: Wed, 20 Mar 2019 09:00:17 -0600 In-Reply-To: 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> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: B18BF6AD01 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.995,0]; ASN(0.00)[asn:16509, ipnet:54.186.0.0/15, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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: Wed, 20 Mar 2019 15:00:22 -0000 On Tue, 2019-03-19 at 09:55 -0500, Karl Denninger wrote: > On 3/19/2019 09:26, Jedi Tek'Unum wrote: > > On Mar 18, 2019, at 2:57 PM, Ian Lepore wrote: > > > On Mon, 2019-03-18 at 14:51 -0500, Jedi Tek'Unum wrote: > > > > My impression wasn’t that support wasn’t there - but “out of > > > > the box” > > > > configuration wasn’t there. In comparison, I didn’t have to do > > > > anything to get I2C enabled in the binary distribution of Linux > > > > that > > > > comes through the manufacturer. > > > > > > > > Its the enabling part that isn’t obvious to most people IMO. > > > > > > > > Documentation/wiki is great. But even better would be all the > > > > enabling overlays already in place and the entries in > > > > loader.conf > > > > already there and commented out. It would be so much easier to > > > > go to > > > > a “common place” (loader.conf), skim through the notes, find > > > > the > > > > thing that one wants, and then just uncomment the referenced > > > > line! > > > > (Or any other similarly easy method.) > > > > > > > > > > > > For FBSD to get a better foothold in this space it needs to be > > > > better > > > > documented. For example, the wiki for NEO2 < > > > > http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO2>; is a > > > > step-by- > > > > step guide for how to acquire and configure Linux for it. > > > > > > > > > > > > > > On one of my imx6 boards I have 5 SPI devices. Each device can > > > use 3 > > > or 4 different sets of pins for clock, data-in, and data- > > > out. Plus, > > > each can use literally any number of whatever gpio pins they want > > > as > > > chip selects. Even limiting the chipsels to a handfull, there > > > would > > > literally be thousands of possible combinations of devices and > > > pin > > > configurations, each one needing to be a separate overlay. > > > > > > Maybe you have experience primarily with rpi or some similarly > > > crippled > > > devices that only offer one or two choices? > > > > If memory serves correctly, there are only 2 I2C devices on the > > H3/H5 and the NanoPi NEO/2 implementations only externalize 1. > > There is only 1 SPI AFAIK. > > > > I wouldn’t call that crippled. I chose this platform exactly > > because of its characteristics - small, fast, cheap. It fits the > > project I’m using it for perfectly. In fact, I can see uses for > > even smaller (see Giant Board ) > > . I understand other projects may have different requirements and > > would drive one towards different solutions - and require more of > > the various interfaces. But they aren’t going to be typical of > > hobbyist projects. > > > > Maybe I should pose the question in another way. What is the > > philosophy for choosing GPIO as default for all the pins? These > > boards have a very limited number of pins and my preference would > > be that the broadest range of interface types would be the default. > > There are 2 UARTs exposed so I would have picked 1 to be enabled by > > default. After that, with I2C and SPI enabled, there are still 6 > > GPIO available. For a tiny board like this that seems to be > > reasonable. If people have a need for slightly more GPIO then I > > would expect they would be the ones configuring overlays. > > > > Apparently the developers of the Linux packages for these boards > > have chosen the diverse approach (“FriendlyCore” based on > > UbuntuCore Xenial). > > > > IMHO, most “hobbyists” would prefer the diversity approach. I’m > > completely capable of becoming an expert in FBSD and this sort of > > configuration stuff yet it isn’t a priority for me - I just want to > > use it like any other hobbyist. The way things are now pushes this > > type of user away from FBSD. > > > > If there is some philosophical perspective against the diversity > > approach then the next best thing is to have documentation that > > clearly and simply tells people how to enable the other > > functionality. > > > > Finally, I think there is an opportunity to grow FBSD in the > > hobbyist world of these small products. We are past the point where > > people can have a real operating system running on systems at > > Arduino size and cost. Linux has been aggressively deployed there > > but I can say from experience that it ain’t pretty - I won’t say > > more as everyone reading this has a clear understanding of why that > > is. > > I'm currently working an issue similar to this, but one that rates > "highly annoying" right now rather than "catastrophically bad." > > The environment is a RPI2 which has GPIO and I2c configured; GPIO to > drive outputs, I2c is used to read analog channels. > > On 11.0 this code ran perfectly well. > > On 12-STABLE )FreeBSD 12.0-STABLE r344818 GENERIC) > it also runs well *BUT* generates a huge number of console messages > about spurious interrupts: > > intc0: Spurious interrupt detected > local_intc0: Spurious interrupt detected > intc0: Spurious interrupt detected > intc0: Spurious interrupt detected > local_intc0: Spurious interrupt detected > local_intc0: Spurious interrupt detected > > .... > > The issue is coming from the i2c side as I have another one of these > that has no I2c defined in the configuration (but is running > identical > code) and no messages. > > Something is indeed generating an /insane /number of interrupts on > one > of the channels: > > Interrupts > 530k total > 1159 local_intc > 494k local_intc > 8047 local_intc > > For obvious reasons I'd like to track this down (it's also generating > a > load average of 1.0, where it should be 0.1 or thereabouts) but I'm > not > sure where to start looking. > > config.txt looks like this: > > root@Pool-MCP:/mnt # cat config.txt > init_uart_clock=3000000 > enable_uart=1 > kernel=u-boot.bin > kernel7=u-boot.bin > dtoverlay=mmc > #audio_pwm_mode=2 > dtparam=i2c_arm=on > > The only "change" from what is in the default is the i2c_arm=on line. > > The "something" appears to be the i2c code, *or* it's something > that's > gone wrong in the DTS changes that are in the newer way of building > the > boot area (where the grab is of the "standard" versions from ports > and > then just copied over.) > > I suspect this would bite you equally hard if you had a RTC > configured > on I2c as well..... > > Killing the process that has the I2c interface open (so the I2c > interface is not in active use, but is configured of course) does > *not* > stop the insane interrupt storm. > I'm aware of this (haven't forgotten that you reported it), but I haven't had time to look into it, because of a crazy $work schedule right now. I did some work on the rpi i2c driver last year, so there's a chance I caused this problem. I only have an ancient rpi-b to test with, I wonder if this is a problem that only happens on rpi2 models? -- Ian From owner-freebsd-arm@freebsd.org Wed Mar 20 15:31:16 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 0DC221556EEF for ; Wed, 20 Mar 2019 15:31:16 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1.eu.mailhop.org (outbound1.eu.mailhop.org [52.28.251.132]) (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 23E3D6BE21 for ; Wed, 20 Mar 2019 15:31:14 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1553095868; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=IhIH59l/hTJ1YUHztcA26279nlQw4aFqblivuDXXKZWl1Hf2myLRHuQrzLQOMIc55xjKF2dMQnM7M 6mjO1riVHCF9mxHlaMTW5Gqy8FrvNzK/+cxoq6RmgvvPg+u0qoWTs9zep8/UV+k5IqkMtM1aJC/qtG et7/ZtbteQ10QegFz2CTFPCotZM88L1dF9oi5aoH1w42XIT0SqBIYgew77LHNLf49AiezocBKtnJoR +1ehtiEwQw6qPVjk3YLbEOK8/fZionv+rifR28Z558yf6XwbUNFJWU1kBtygdwWurH4ejmodMB1zNL rxDvd2e3wy7woEqH2C6Q0Ijl18tmxXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=QPtz/BJzt5aZwn3obL4Pu2/T5rbCgRmtDgXGevh8ICo=; b=EtQgeRP1sJvCbU64UBD9GlfEwtqpWZC102SHUTkL4LDgIR56st9nVxH/JGeu0pKOis2bn2QaJN4ae QNP5LGqx6BZ3iJg2/XHV67OQdN/0FMe+xjLzOA93no6n3OGr/jdUxbtFgu+bas/ZFT1ZfVKfV+MFwq J8nLrOST1oEwP1RhmJAGNduNrs9oqOHjviZi95pcJm8PsuIfGGP93o1wECGeU4RIloXPaBB28a3xqL p4ae3FJCV/rOp4BenvZjA3koR4+bAisVg18SbXNsAEC0b9m3755wqKnJTfTWQBfWoSU9cVy/KwC6xS 6fm1RTAAlD7qUeRGrChIe5yqUQUglaw== ARC-Authentication-Results: i=1; outbound3.eu.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=QPtz/BJzt5aZwn3obL4Pu2/T5rbCgRmtDgXGevh8ICo=; b=FU1lS3QxyOXI3QDGggYj+j771xtXYfsS8hEWtMxEOBEtj1O8k/T/gmEPKsfJbJ2ExMs5piPyTFBeD D211/BfExvnh54IN7ZOwrQArMjZw6YOAfqDFcVP56MvVP8Sz7jyISr50JiFwiuU5szYViYX+6+VH2X WVR0bU1RHh7pAUaBzCW8qKRGMwRKEcJKv2gTS0853fV/782F8nclDatBqg3Zp/aKCKskIKbgEzUT9B YSAHoZz0IwskOMGjE1YmyvFdkc0KPfBCsV1GDTAMojYp/UA4ZjQeuRJNkmvyFa6Xvd70mjLEh0cGgt 8KiGokj/+y/qnZDWhzrl5nnAKDacH7g== X-MHO-RoutePath: aGlwcGll X-MHO-User: 2c0e7ad4-4b25-11e9-908b-352056dbf2de X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.eu.mailhop.org (Halon) with ESMTPSA id 2c0e7ad4-4b25-11e9-908b-352056dbf2de; Wed, 20 Mar 2019 15:31:05 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x2KFV28T069180; Wed, 20 Mar 2019 09:31:03 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: allwinner i2c [was: Options for FBSD support with LCD device - new project] From: Ian Lepore To: Daniel Braniss Cc: freebsd-arm@freebsd.org Date: Wed, 20 Mar 2019 09:31:02 -0600 In-Reply-To: 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> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 23E3D6BE21 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.983,0]; ASN(0.00)[asn:16509, ipnet:52.28.0.0/16, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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: Wed, 20 Mar 2019 15:31:16 -0000 On Tue, 2019-03-19 at 08:28 +0200, Daniel Braniss wrote: > I have several allwinner SoC, mainly from FriendlyArm, and neither i2c or SPI work. > I have a hacked i2c that mostly works, but hangs sometimes :-), mainly > timing issues of which I have no idea how to fix. > I’m willing to help here but my knowledge of the twsi tends to zero. > hint hint … > > cheers, > danny Iirc, allwinner requires working i2c even to boot, because the boards have i2c PMIC chips on them. I wonder if it's a case where a few small commands to the pmic work fine but bigger transfers fail? I dunno, anything more you can say about the problem would help. -- Ian From owner-freebsd-arm@freebsd.org Wed Mar 20 15:44:56 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 821AF1557681 for ; Wed, 20 Mar 2019 15:44:56 +0000 (UTC) (envelope-from karl@denninger.net) Received: from colo1.denninger.net (colo1.denninger.net [104.236.120.189]) (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 6F4F96CACB; Wed, 20 Mar 2019 15:44:55 +0000 (UTC) (envelope-from karl@denninger.net) Received: from denninger.net (ip68-1-57-197.pn.at.cox.net [68.1.57.197]) by colo1.denninger.net (Postfix) with ESMTP id 6299F21108C; Wed, 20 Mar 2019 11:44:18 -0400 (EDT) Received: from [192.168.10.27] (D17.Denninger.Net [192.168.10.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by denninger.net (Postfix) with ESMTPSA id D9389130F9; Wed, 20 Mar 2019 10:44:17 -0500 (CDT) Subject: Re: Options for FBSD support with LCD device - new project [[Maybe related: I2c issues on the Pi2]] To: Ian Lepore , 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: Karl Denninger Openpgp: preference=signencrypt Autocrypt: addr=karl@denninger.net; prefer-encrypt=mutual; keydata= mQINBFIX1zsBEADRcJfsQUl9oFeoMfLPJ1kql+3sIaYx0MfJAUhV9LnbWxr0fsWCskM1O4cV tHm5dqPkuPM4Ztc0jLotD1i9ubWvCHOlkLGxFOL+pFbjA+XZ7VKsC/xWmhMwJ3cM8HavK2OV SzEWQ/AEYtMi04IzGSwsxh/5/5R0mPHrsIomV5SbuiI0vjLuDj7fo6146AABI1ULzge4hBYW i/SHrqUrLORmUNBs6bxek79/B0Dzk5cIktD3LOfbT9EAa5J/osVkstMBhToJgQttaMIGv8SG CzpR/HwEokE+7DP+k2mLHnLj6H3kfugOF9pJH8Za4yFmw//s9cPXV8WwtZ2SKfVzn1unpKqf wmJ1PwJoom/d4fGvQDkgkGKRa6RGC6tPmXnqnx+YX4iCOdFfbP8L9rmk2sewDDVzHDU3I3ZZ 8hFIjMYM/QXXYszRatK0LCV0QPZuF7LCf4uQVKw1/oyJInsnH7+6a3c0h21x+CmSja9QJ+y0 yzgEN/nM89d6YTakfR+1xkYgodVmMy/bS8kmXbUUZG/CyeqCqc95RUySjKT2ECrf9GhhoQkl +D8n2MsrAUSMGB4GQSN+TIq9OBTpNuvATGSRuF9wnQcs1iSry+JNCpfRTyWp83uCNApe6oHU EET4Et6KDO3AvjvBMAX0TInTRGW2SQlJMuFKpc7Dg7tHK8zzqQARAQABtCNLYXJsIERlbm5p bmdlciA8a2FybEBkZW5uaW5nZXIubmV0PokCPAQTAQIAJgUCUhfXOwIbIwUJCWYBgAYLCQgH AwIEFQIIAwQWAgMBAh4BAheAAAoJEG6/sivc5s0PLxQP/i6x/QFx9G4Cw7C+LthhLXIm7NSH AtNbz2UjySEx2qkoQQjtsK6mcpEEaky4ky6t8gz0/SifIfJmSmyAx0UhUQ0WBv1vAXwtNrQQ jJd9Bj6l4c2083WaXyHPjt2u2Na6YFowyb4SaQb83hu/Zs25vkPQYJVVE0JX409MFVPUa6E3 zFbd1OTr3T4yNUy4gNeQZfzDqDS8slbIks2sXeoJrZ6qqXVI0ionoivOlaN4T6Q0UYyXtigj dQvvhMt0aNowKFjRqrmSDRpdz+o6yg7Mp7qEZ1V6EZk8KqQTH6htpCTQ8i79ttK4LG6bstSF Re6Fwq52nbrcANrcdmtZXqjo+SGbUqJ8b1ggrxAsJ5MEhRh2peKrCgI/TjQo+ZxfnqEoR4AI 46Cyiz+/lcVvlvmf2iPifS3EEdaH3Itfwt7MxFm6mQORYs6skHDw3tOYB2/AdCW6eRVYs2hB RMAG4uwApZfZDKgRoE95PJmQjeTBiGmRPcsQZtNESe7I7EjHtCDLwtJqvD4HkDDQwpzreT6W XkyIJ7ns7zDfA1E+AQhFR6rsTFGgQZRZKsVeov3SbhYKkCnVDCvb/PKQCAGkSZM9SvYG5Yax 8CMry3AefKktf9fqBFg8pWqtVxDwJr56dhi0GHXRu3jVI995rMGo1fLUG5fSxiZ8L5sAtokh 9WFmQpyl Message-ID: <7058a207-f92f-2997-92a6-9e9c35acb59b@denninger.net> Date: Wed, 20 Mar 2019 10:44:10 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms090107030102050007020009" X-Rspamd-Queue-Id: 6F4F96CACB X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.38 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; SIGNED_SMIME(-2.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ATTACHMENT(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,multipart/alternative,text/plain]; DMARC_NA(0.00)[denninger.net]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; MX_GOOD(-0.01)[px.denninger.net]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.84)[-0.840,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+]; ASN(0.00)[asn:14061, ipnet:104.236.64.0/18, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-2.33)[ip: (-9.88), ipnet: 104.236.64.0/18(-3.83), asn: 14061(2.13), country: US(-0.07)]; RECEIVED_SPAMHAUS_PBL(0.00)[197.57.1.68.zen.spamhaus.org : 127.0.0.11] X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Wed, 20 Mar 2019 15:44:57 -0000 This is a cryptographically signed message in MIME format. --------------ms090107030102050007020009 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 3/20/2019 10:00, Ian Lepore wrote: > On Tue, 2019-03-19 at 09:55 -0500, Karl Denninger wrote: >> On 3/19/2019 09:26, Jedi Tek'Unum wrote: >>> On Mar 18, 2019, at 2:57 PM, Ian Lepore wrote: >>>> On Mon, 2019-03-18 at 14:51 -0500, Jedi Tek'Unum wrote: >>>>> My impression wasn=E2=80=99t that support wasn=E2=80=99t there - bu= t =E2=80=9Cout of >>>>> the box=E2=80=9D >>>>> configuration wasn=E2=80=99t there. In comparison, I didn=E2=80=99t= have to do >>>>> anything to get I2C enabled in the binary distribution of Linux >>>>> that >>>>> comes through the manufacturer. >>>>> >>>>> Its the enabling part that isn=E2=80=99t obvious to most people IMO= =2E >>>>> >>>>> Documentation/wiki is great. But even better would be all the >>>>> enabling overlays already in place and the entries in >>>>> loader.conf >>>>> already there and commented out. It would be so much easier to >>>>> go to >>>>> a =E2=80=9Ccommon place=E2=80=9D (loader.conf), skim through the no= tes, find >>>>> the >>>>> thing that one wants, and then just uncomment the referenced >>>>> line! >>>>> (Or any other similarly easy method.) >>>>> >>>>> >>>>> For FBSD to get a better foothold in this space it needs to be >>>>> better >>>>> documented. For example, the wiki for NEO2 < >>>>> http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO2>; is a >>>>> step-by- >>>>> step guide for how to acquire and configure Linux for it. >>>>> >>>>> >>>> On one of my imx6 boards I have 5 SPI devices. Each device can >>>> use 3 >>>> or 4 different sets of pins for clock, data-in, and data- >>>> out. Plus, >>>> each can use literally any number of whatever gpio pins they want >>>> as >>>> chip selects. Even limiting the chipsels to a handfull, there >>>> would >>>> literally be thousands of possible combinations of devices and >>>> pin >>>> configurations, each one needing to be a separate overlay. >>>> >>>> Maybe you have experience primarily with rpi or some similarly >>>> crippled >>>> devices that only offer one or two choices? >>> If memory serves correctly, there are only 2 I2C devices on the >>> H3/H5 and the NanoPi NEO/2 implementations only externalize 1. >>> There is only 1 SPI AFAIK. >>> >>> I wouldn=E2=80=99t call that crippled. I chose this platform exactly >>> because of its characteristics - small, fast, cheap. It fits the >>> project I=E2=80=99m using it for perfectly. In fact, I can see uses f= or >>> even smaller (see Giant Board ) >>> . I understand other projects may have different requirements and >>> would drive one towards different solutions - and require more of >>> the various interfaces. But they aren=E2=80=99t going to be typical o= f >>> hobbyist projects. >>> >>> Maybe I should pose the question in another way. What is the >>> philosophy for choosing GPIO as default for all the pins? These >>> boards have a very limited number of pins and my preference would >>> be that the broadest range of interface types would be the default. >>> There are 2 UARTs exposed so I would have picked 1 to be enabled by >>> default. After that, with I2C and SPI enabled, there are still 6 >>> GPIO available. For a tiny board like this that seems to be >>> reasonable. If people have a need for slightly more GPIO then I >>> would expect they would be the ones configuring overlays. >>> >>> Apparently the developers of the Linux packages for these boards >>> have chosen the diverse approach (=E2=80=9CFriendlyCore=E2=80=9D base= d on >>> UbuntuCore Xenial). >>> >>> IMHO, most =E2=80=9Chobbyists=E2=80=9D would prefer the diversity app= roach. I=E2=80=99m >>> completely capable of becoming an expert in FBSD and this sort of >>> configuration stuff yet it isn=E2=80=99t a priority for me - I just w= ant to >>> use it like any other hobbyist. The way things are now pushes this >>> type of user away from FBSD. >>> >>> If there is some philosophical perspective against the diversity >>> approach then the next best thing is to have documentation that >>> clearly and simply tells people how to enable the other >>> functionality. >>> >>> Finally, I think there is an opportunity to grow FBSD in the >>> hobbyist world of these small products. We are past the point where >>> people can have a real operating system running on systems at >>> Arduino size and cost. Linux has been aggressively deployed there >>> but I can say from experience that it ain=E2=80=99t pretty - I won=E2= =80=99t say >>> more as everyone reading this has a clear understanding of why that >>> is. >> I'm currently working an issue similar to this, but one that rates >> "highly annoying" right now rather than "catastrophically bad." >> >> The environment is a RPI2 which has GPIO and I2c configured; GPIO to >> drive outputs, I2c is used to read analog channels. >> >> On 11.0 this code ran perfectly well. >> >> On 12-STABLE )FreeBSD 12.0-STABLE r344818 GENERIC) >> it also runs well *BUT* generates a huge number of console messages >> about spurious interrupts: >> >> intc0: Spurious interrupt detected >> local_intc0: Spurious interrupt detected >> intc0: Spurious interrupt detected >> intc0: Spurious interrupt detected >> local_intc0: Spurious interrupt detected >> local_intc0: Spurious interrupt detected >> >> .... >> >> The issue is coming from the i2c side as I have another one of these >> that has no I2c defined in the configuration (but is running >> identical >> code) and no messages. >> >> Something is indeed generating an /insane /number of interrupts on >> one >> of the channels: >> >> Interrupts >> 530k total >> 1159 local_intc >> 494k local_intc >> 8047 local_intc >> >> For obvious reasons I'd like to track this down (it's also generating >> a >> load average of 1.0, where it should be 0.1 or thereabouts) but I'm >> not >> sure where to start looking. >> >> config.txt looks like this: >> >> root@Pool-MCP:/mnt # cat config.txt >> init_uart_clock=3D3000000 >> enable_uart=3D1 >> kernel=3Du-boot.bin >> kernel7=3Du-boot.bin >> dtoverlay=3Dmmc >> #audio_pwm_mode=3D2 >> dtparam=3Di2c_arm=3Don >> >> The only "change" from what is in the default is the i2c_arm=3Don line= =2E >> >> The "something" appears to be the i2c code, *or* it's something >> that's >> gone wrong in the DTS changes that are in the newer way of building >> the >> boot area (where the grab is of the "standard" versions from ports >> and >> then just copied over.) >> >> I suspect this would bite you equally hard if you had a RTC >> configured >> on I2c as well..... >> >> Killing the process that has the I2c interface open (so the I2c >> interface is not in active use, but is configured of course) does >> *not* >> stop the insane interrupt storm. >> > I'm aware of this (haven't forgotten that you reported it), but I > haven't had time to look into it, because of a crazy $work schedule > right now. I did some work on the rpi i2c driver last year, so there's= > a chance I caused this problem. I only have an ancient rpi-b to test > with, I wonder if this is a problem that only happens on rpi2 models? > > -- Ian I don't think so -- there's another report (Bernd Walter on this list) with a Pi1 running 12-Release and an I2c RTC on it getting the same messages (and, I assume, the same insane interrupt counts.) --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms090107030102050007020009 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC DdgwggagMIIEiKADAgECAhMA5EiKghDOXrvfxYxjITXYDdhIMA0GCSqGSIb3DQEBCwUAMIGL MQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UEBwwJTmljZXZpbGxlMRkw FwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5c3RlbXMgQ0ExITAf BgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQTAeFw0xNzA4MTcxNjQyMTdaFw0yNzA4 MTUxNjQyMTdaMHsxCzAJBgNVBAYTAlVTMRAwDgYDVQQIDAdGbG9yaWRhMRkwFwYDVQQKDBBD dWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5c3RlbXMgQ0ExJTAjBgNVBAMMHEN1 ZGEgU3lzdGVtcyBMTEMgMjAxNyBJbnQgQ0EwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIK AoICAQC1aJotNUI+W4jP7xQDO8L/b4XiF4Rss9O0B+3vMH7Njk85fZ052QhZpMVlpaaO+sCI KqG3oNEbuOHzJB/NDJFnqh7ijBwhdWutdsq23Ux6TvxgakyMPpT6TRNEJzcBVQA0kpby1DVD 0EKSK/FrWWBiFmSxg7qUfmIq/mMzgE6epHktyRM3OGq3dbRdOUgfumWrqHXOrdJz06xE9NzY vc9toqZnd79FUtE/nSZVm1VS3Grq7RKV65onvX3QOW4W1ldEHwggaZxgWGNiR/D4eosAGFxn uYeWlKEC70c99Mp1giWux+7ur6hc2E+AaTGh+fGeijO5q40OGd+dNMgK8Es0nDRw81lRcl24 SWUEky9y8DArgIFlRd6d3ZYwgc1DMTWkTavx3ZpASp5TWih6yI8ACwboTvlUYeooMsPtNa9E 6UQ1nt7VEi5syjxnDltbEFoLYcXBcqhRhFETJe9CdenItAHAtOya3w5+fmC2j/xJz29og1KH YqWHlo3Kswi9G77an+zh6nWkMuHs+03DU8DaOEWzZEav3lVD4u76bKRDTbhh0bMAk4eXriGL h4MUoX3Imfcr6JoyheVrAdHDL/BixbMH1UUspeRuqQMQ5b2T6pabXP0oOB4FqldWiDgJBGRd zWLgCYG8wPGJGYgHibl5rFiI5Ix3FQncipc6SdUzOQIDAQABo4IBCjCCAQYwHQYDVR0OBBYE FF3AXsKnjdPND5+bxVECGKtc047PMIHABgNVHSMEgbgwgbWAFBu1oRhUMNEzjODolDka5k4Q EDBioYGRpIGOMIGLMQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UEBwwJ TmljZXZpbGxlMRkwFwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5 c3RlbXMgQ0ExITAfBgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQYIJAKxAy1WBo2kY MBIGA1UdEwEB/wQIMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgGGMA0GCSqGSIb3DQEBCwUAA4IC AQCB5686UCBVIT52jO3sz9pKuhxuC2npi8ZvoBwt/IH9piPA15/CGF1XeXUdu2qmhOjHkVLN gO7XB1G8CuluxofOIUce0aZGyB+vZ1ylHXlMeB0R82f5dz3/T7RQso55Y2Vog2Zb7PYTC5B9 oNy3ylsnNLzanYlcW3AAfzZcbxYuAdnuq0Im3EpGm8DoItUcf1pDezugKm/yKtNtY6sDyENj tExZ377cYA3IdIwqn1Mh4OAT/Rmh8au2rZAo0+bMYBy9C11Ex0hQ8zWcvPZBDn4v4RtO8g+K uQZQcJnO09LJNtw94W3d2mj4a7XrsKMnZKvm6W9BJIQ4Nmht4wXAtPQ1xA+QpxPTmsGAU0Cv HmqVC7XC3qxFhaOrD2dsvOAK6Sn3MEpH/YrfYCX7a7cz5zW3DsJQ6o3pYfnnQz+hnwLlz4MK 17NIA0WOdAF9IbtQqarf44+PEyUbKtz1r0KGeGLs+VGdd2FLA0e7yuzxJDYcaBTVwqaHhU2/ Fna/jGU7BhrKHtJbb/XlLeFJ24yvuiYKpYWQSSyZu1R/gvZjHeGb344jGBsZdCDrdxtQQcVA 6OxsMAPSUPMrlg9LWELEEYnVulQJerWxpUecGH92O06wwmPgykkz//UmmgjVSh7ErNvL0lUY UMfunYVO/O5hwhW+P4gviCXzBFeTtDZH259O7TCCBzAwggUYoAMCAQICEwCg0WvVwekjGFiO 62SckFwepz0wDQYJKoZIhvcNAQELBQAwezELMAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3Jp ZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBMTEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBD QTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExMQyAyMDE3IEludCBDQTAeFw0xNzA4MTcyMTIx MjBaFw0yMjA4MTYyMTIxMjBaMFcxCzAJBgNVBAYTAlVTMRAwDgYDVQQIDAdGbG9yaWRhMRkw FwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRswGQYDVQQDDBJrYXJsQGRlbm5pbmdlci5uZXQw ggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQC+HVSyxVtJhy3Ohs+PAGRuO//Dha9A 16l5FPATr6wude9zjX5f2lrkRyU8vhCXTZW7WbvWZKpcZ8r0dtZmiK9uF58Ec6hhvfkxJzbg 96WHBw5Fumd5ahZzuCJDtCAWW8R7/KN+zwzQf1+B3MVLmbaXAFBuKzySKhKMcHbK3/wjUYTg y+3UK6v2SBrowvkUBC+jxNg3Wy12GsTXcUS/8FYIXgVVPgfZZrbJJb5HWOQpvvhILpPCD3xs YJFNKEPltXKWHT7Qtc2HNqikgNwj8oqOb+PeZGMiWapsatKm8mxuOOGOEBhAoTVTwUHlMNTg 6QUCJtuWFCK38qOCyk9Haj+86lUU8RG6FkRXWgMbNQm1mWREQhw3axgGLSntjjnznJr5vsvX SYR6c+XKLd5KQZcS6LL8FHYNjqVKHBYM+hDnrTZMqa20JLAF1YagutDiMRURU23iWS7bA9tM cXcqkclTSDtFtxahRifXRI7Epq2GSKuEXe/1Tfb5CE8QsbCpGsfSwv2tZ/SpqVG08MdRiXxN 5tmZiQWo15IyWoeKOXl/hKxA9KPuDHngXX022b1ly+5ZOZbxBAZZMod4y4b4FiRUhRI97r9l CxsP/EPHuuTIZ82BYhrhbtab8HuRo2ofne2TfAWY2BlA7ExM8XShMd9bRPZrNTokPQPUCWCg CdIATQIDAQABo4IBzzCCAcswPAYIKwYBBQUHAQEEMDAuMCwGCCsGAQUFBzABhiBodHRwOi8v b2NzcC5jdWRhc3lzdGVtcy5uZXQ6ODg4ODAJBgNVHRMEAjAAMBEGCWCGSAGG+EIBAQQEAwIF oDAOBgNVHQ8BAf8EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMDMGCWCG SAGG+EIBDQQmFiRPcGVuU1NMIEdlbmVyYXRlZCBDbGllbnQgQ2VydGlmaWNhdGUwHQYDVR0O BBYEFLElmNWeVgsBPe7O8NiBzjvjYnpRMIHKBgNVHSMEgcIwgb+AFF3AXsKnjdPND5+bxVEC GKtc047PoYGRpIGOMIGLMQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UE BwwJTmljZXZpbGxlMRkwFwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRh IFN5c3RlbXMgQ0ExITAfBgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQYITAORIioIQ zl6738WMYyE12A3YSDAdBgNVHREEFjAUgRJrYXJsQGRlbm5pbmdlci5uZXQwDQYJKoZIhvcN AQELBQADggIBAJXboPFBMLMtaiUt4KEtJCXlHO/3ZzIUIw/eobWFMdhe7M4+0u3te0sr77QR dcPKR0UeHffvpth2Mb3h28WfN0FmJmLwJk+pOx4u6uO3O0E1jNXoKh8fVcL4KU79oEQyYkbu 2HwbXBU9HbldPOOZDnPLi0whi/sbFHdyd4/w/NmnPgzAsQNZ2BYT9uBNr+jZw4SsluQzXG1X lFL/qCBoi1N2mqKPIepfGYF6drbr1RnXEJJsuD+NILLooTNf7PMgHPZ4VSWQXLNeFfygoOOK FiO0qfxPKpDMA+FHa8yNjAJZAgdJX5Mm1kbqipvb+r/H1UAmrzGMbhmf1gConsT5f8KU4n3Q IM2sOpTQe7BoVKlQM/fpQi6aBzu67M1iF1WtODpa5QUPvj1etaK+R3eYBzi4DIbCIWst8MdA 1+fEeKJFvMEZQONpkCwrJ+tJEuGQmjoQZgK1HeloepF0WDcviiho5FlgtAij+iBPtwMuuLiL shAXA5afMX1hYM4l11JXntle12EQFP1r6wOUkpOdxceCcMVDEJBBCHW2ZmdEaXgAm1VU+fnQ qS/wNw/S0X3RJT1qjr5uVlp2Y0auG/eG0jy6TT0KzTJeR9tLSDXprYkN2l/Qf7/nT6Q03qyE QnnKiBXWAZXveafyU/zYa7t3PTWFQGgWoC4w6XqgPo4KV44OMYIFBzCCBQMCAQEwgZIwezEL MAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBM TEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExM QyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTANBglghkgBZQMEAgMFAKCCAkUw GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTkwMzIwMTU0NDE0 WjBPBgkqhkiG9w0BCQQxQgRAVFFSWRp0UEPlAwZJaZHFvKlFP24DD+yBzNtHgqi2yG7P1Li+ uJXMBj/ZJ4+zpkY+cuAJGJZrW83NyzbVO+qV+TBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFl AwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3 DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGjBgkrBgEEAYI3EAQxgZUwgZIwezEL MAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBM TEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExM QyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTCBpQYLKoZIhvcNAQkQAgsxgZWg gZIwezELMAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lz dGVtcyBMTEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0 ZW1zIExMQyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTANBgkqhkiG9w0BAQEF AASCAgA0dyPfKKziciMq27oPD0lLC5jYmogxczKZORaQzbzzXLz3oEPghF372qx8IOAxNGG0 /8K8OJEQzfTyg3MoFJpfo6ybSsy0f1msYrwSw5QdZ+fMBJpSuVASbMgD3G6ql1U+5g/kCG+w q+buLoiizjt9jRccj8JwflR21Fr+w950kp+E9rFXwwRqFVerj1pK54OcIZB59MietkZzmn2u iChSJTPV4DkCeX1n0Dz/drl/iG4klsE8Fk5fBHWjKa5CtoP3RrePp3+nkXh+8X4ZqJ+KTVrk f+Vt9tsyvp35HJ1h2Z3OGildQHQhGKMrP289bHgdxRqgMMwRFJ+8pu+s6+2EgqYpHDoXzCP5 5G6IjC6y9+m94jisteZfoDHUVjtWr6M0giv4JgfaClCcNc+lKtv7tSjLzoqPmVem7MjFF63q 9afDOsry+XwYF1PNYnjczSbQdfYSfoFpaFxndAC7ekcLKjLs2uqCd1prmakaJlEpQ6a5Nhr7 4ShMLFT3LN6VpuSHYvIClxPWwyeXXe+NrHf4LvDpFCF014ZLykmuOWVQg0Oj9K2oZ4PCeAY8 nybsFhyfKTFt9R8r2fsZ8MCwVOUEGAyp5FVxQ0CiUwhz9x7mwiMWpo4OXojmZ4wkpoziBS8X CCL20vFi3rBVGCBbwp8ySIt/ypGVxOEhlSr2r9yRwwAAAAAAAA== --------------ms090107030102050007020009-- From owner-freebsd-arm@freebsd.org Wed Mar 20 16:15:55 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 7165815583B4 for ; Wed, 20 Mar 2019 16:15:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A60E6DCEA for ; Wed, 20 Mar 2019 16:15:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 5236519F30 for ; Wed, 20 Mar 2019 16:15:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x2KGFsdR002658 for ; Wed, 20 Mar 2019 16:15:54 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x2KGFs39002654 for freebsd-arm@FreeBSD.org; Wed, 20 Mar 2019 16:15:54 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 236375] make -j4 buildworld fails for latest -RELEASE svn on arm64/RPI3 Date: Wed, 20 Mar 2019 16:15:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markj@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution cc bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Wed, 20 Mar 2019 16:15:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236375 Mark Johnston changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Not A Bug CC| |markj@FreeBSD.org Status|New |Closed --- Comment #3 from Mark Johnston --- Indeed, this looks like an OOM kill. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Thu Mar 21 04:05:19 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 15236154CBED for ; Thu, 21 Mar 2019 04:05:19 +0000 (UTC) (envelope-from 010001699e6c9812-a0fc8d06-51d3-4252-ac06-2c1087d2c46f-000000@amazonses.com) Received: from a8-52.smtp-out.amazonses.com (a8-52.smtp-out.amazonses.com [54.240.8.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8D2716BFB6 for ; Thu, 21 Mar 2019 04:05:17 +0000 (UTC) (envelope-from 010001699e6c9812-a0fc8d06-51d3-4252-ac06-2c1087d2c46f-000000@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=vnqrkfnvu6csdl6mwgk5t6ix3nnepx57; d=tarsnap.com; t=1553141111; h=Subject:To:Cc:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; bh=7A5b7nk9wigh6p/oREGTdLpP+CQlzpci0N70YWCBoAI=; b=Ozhkhhvh1v8t2mMSduIa7+7NiFEJ+RCQqDq7N/UJJ/3ZelShb7DxDZA/mRY33//G pS3hE94xC+zVJcIZNmckKS1zCMcofQofR96mQZltke/VGE+aDLFswCN5qQ+hTFyBMBa j8KOAjs2FZKRVJklHBQwMFModBZOp8DA8EKFtT24= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1553141110; h=Subject:To:Cc:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=7A5b7nk9wigh6p/oREGTdLpP+CQlzpci0N70YWCBoAI=; b=JM/ZcpM36M4pb3lL6ZXR/tXALgN4ZWFn9DsDcFdSkBFpLgxwF0ghS0dYG1PQdbHu QsVjbOQKQ7tqYTEEm2BAi5HBFxtYZg5tg/72gDWxsN+3TrHqI6OppXXQD4HuIRvWyKA cEG4cSjp/ZFxaxcw0sXbLl0Fu0mkBpoeIt9nEpQA= Subject: Re: ARM Graviton AWS Processor (AMI Image) To: =?UTF-8?Q?Micha=c5=82_Krawczyk?= Cc: Marcin Wojtas , Greg V , "Matushevsky, Alexander" , Martin Karrer , =?UTF-8?Q?Rafa=c5=82_Kozik?= , freebsd-arm@freebsd.org, "Tzalik, Guy" References: <79CC79B9-81AF-4563-BABE-429E6A57F476@bmalum.com> <010201686fe5047f-ed14af85-2b25-4480-a62a-a893f062eedd-000000@eu-west-1.amazonses.com> <010201686fe5047f-ed14af85-2b25-4480-a62a-a893f062eedd-000000@eu-west-1.amazo> <1548182399.2864.0@smtp.migadu.com> <1552255580.21373.0@unrelenting.technology> <01000169992ab14c-aa38b2f1-3f57-4805-9d8a-fa92207e4c2d-000000@email.amazonses.com> From: Colin Percival Openpgp: preference=signencrypt Autocrypt: addr=cperciva@tarsnap.com; prefer-encrypt=mutual; keydata= mQGhBElrAAcRBACDfDys4ZtK+ErCJ1HAzYeteKpm3OEsvT/49AjUTLihkF79HhIKrCQU+1KC zv7BwHCMLb6hq30As9L7iFKG7n5QFLFC4Te/VcITUnWHMG/c3ViLOfJGvi+9/nOEHaM1dVJY D6tEp5yM1nHmVQpo9932j4KGuGFR0LhOK5IHXOSfGwCgxSFDPdgxe2OEjWxjGgY+oV3EafcD +JROXCTjlcQiG/OguQH4Vks3mhHfFnEppLxTkDuYgHZQiUtpcT9ssH5khgqoTyMar05OUdAj ZIhNbWDh4LgTj+7ZmvLhXT5Zxw8LX9d7T36aTB8XDQSenDqEtinMWOb0TCBBLbsB8EFG1WTT ESbZci9jJS5yhtktuZoY/eM8uXMD/3k4FWFO80VRRkELSp+XSy/VlSQjyi/rhl2nQq/oOA9F oJbDaB0yq9VNhxP+uFBzBWSqeIX0t1ZWLtNfVFr4TRP5hihI5ICrg/0OpqgisKsU2NFe9xyO hyJLYmfD8ebpDJ/9k30C7Iju9pVrwLm1QgS4S2fqJRcR+U4WbjvP7CgStCVDb2xpbiBQZXJj aXZhbCA8Y3BlcmNpdmFAdGFyc25hcC5jb20+iGEEExECACEFAklrALYCGwMHCwkIBwMCAQQV AggDBBYCAwECHgECF4AACgkQOM7KaQxqam6/igCgn+z2k3V5ggNppmWrZstt1U2lugsAoL7L wS9V9yLtil3oWmHtwpUqYruEuQINBElrAAcQCAD3ZLMIsP4CIDoJORg+YY0lqLVBgcnF7pFb 4Uy2+KvdWofN+DKH61rZLjgXXkNE9M4EQC1B4lGttBP8IY2gs41y3AUogGdyFbidq99rCBz7 LTsgARHwFxZoaHmXyiZLEU1QZuMqwPZV1mCviRhN5E3rRqYNXVcrnXAAuhBpvNyj/ntHvcDN 2/m+ochiuBYueU4kX3lHya7sOj+mTsndcWmQ9soOUyr8O0r/BG088bMn4qqtUw4dl5/pglXk jbl7uOOPinKf0WVd2r6M0wLPJCD4NPHrCWRLLLAjwfjrtoSRvXxDbXhCdgGBa72+K8eYLzVs hgq7tJOoBWzjVK6XRxR7AAMGB/9Mo3iJ2DxqDecd02KCB5BsFDICbJGhPltU7FwrtbC7djSb XUrwsEVLHi4st4cbdGNCWCrp0BRezXZKohKnNAPFOTK++ZfgeKxrV2sJod+Q9RILF86tQ4XF 7A7Yme5hy92t/WgiU4vc/fWbgP8gV/19f8nunaT2E9NSa70mZFjZNu4iuwThoUUO5CV3Wo0Y UISsnRK8XD1+LR3A2qVyLiFRwh/miC1hgLFCTGCQ3GLxZeZzIpYSlGdQJ0L5lixW5ZQD9r1I 8i/8zhE6qRFAM0upUMI3Gt1Oq2w03DiXrZU0Fu/R8Rm8rlnkQKA+95mRTUq1xL5P5NZIi4gJ Z569OPMFiEkEGBECAAkFAklrAAcCGwwACgkQOM7KaQxqam41igCfbaldnFTu5uAdrnrghESv EI3CAo8AoLkNMks1pThl2BJNRm4CtTK9xZeH Message-ID: <010001699e6c9812-a0fc8d06-51d3-4252-ac06-2c1087d2c46f-000000@email.amazonses.com> Date: Thu, 21 Mar 2019 04:05:10 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-SES-Outgoing: 2019.03.21-54.240.8.52 Feedback-ID: 1.us-east-1.Lv9FVjaNvvR5llaqfLoOVbo2VxOELl7cjN0AOyXnPlk=:AmazonSES X-Rspamd-Queue-Id: 8D2716BFB6 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tarsnap.com header.s=vnqrkfnvu6csdl6mwgk5t6ix3nnepx57 header.b=Ozhkhhvh; dkim=pass header.d=amazonses.com header.s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw header.b=JM/ZcpM3; spf=pass (mx1.freebsd.org: domain of 010001699e6c9812-a0fc8d06-51d3-4252-ac06-2c1087d2c46f-000000@amazonses.com designates 54.240.8.52 as permitted sender) smtp.mailfrom=010001699e6c9812-a0fc8d06-51d3-4252-ac06-2c1087d2c46f-000000@amazonses.com X-Spamd-Result: default: False [-2.44 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[tarsnap.com:s=vnqrkfnvu6csdl6mwgk5t6ix3nnepx57,amazonses.com:s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:54.240.0.0/18]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[tarsnap.com]; NEURAL_HAM_SHORT(-0.97)[-0.972,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: feedback-smtp.us-east-1.amazonses.com]; DKIM_TRACE(0.00)[tarsnap.com:+,amazonses.com:+]; RCPT_COUNT_SEVEN(0.00)[8]; RCVD_IN_DNSWL_NONE(0.00)[52.8.240.54.list.dnswl.org : 127.0.15.0]; FORGED_SENDER(0.30)[cperciva@tarsnap.com,010001699e6c9812-a0fc8d06-51d3-4252-ac06-2c1087d2c46f-000000@amazonses.com]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-1.76)[ip: (-0.82), ipnet: 54.240.8.0/21(-4.57), asn: 14618(-3.33), country: US(-0.07)]; ASN(0.00)[asn:14618, ipnet:54.240.8.0/21, country:US]; FORGED_MUA_THUNDERBIRD_MSGID_UNKNOWN(2.50)[]; FROM_NEQ_ENVFROM(0.00)[cperciva@tarsnap.com, 010001699e6c9812-a0fc8d06-51d3-4252-ac06-2c1087d2c46f-000000@amazonses.com] 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: Thu, 21 Mar 2019 04:05:19 -0000 Hi Michał, Thanks, those two patches fix both problems. Can you get them into the FreeBSD tree or should I commit them? Colin Percival On 3/20/19 3:24 AM, Michał Krawczyk wrote: > Hi, > > we have solution for two of the issues with ENA, > > The double resource activation can be fixed by this patch: > https://reviews.freebsd.org/D19655 > > And the issue with reloading module/reconfiguring it by using ifconfig > can be fixed by using this patch: > https://reviews.freebsd.org/D19641 > > Please check if that fixes it for you. > > Thanks, > Michał > > > śr., 20 mar 2019 o 04:35 Colin Percival napisał(a): >> >> Hi ENA people, >> >> Any luck figuring out what was going on with the ENA driver here >> with interrupt activation? >> >> Colin Percival >> >> On 3/11/19 1:35 AM, Marcin Wojtas wrote: >>> +FreeBSD ENA maintainers >>> >>> W dniu pon., 11.03.2019 o 00:40 Greg V >>> napisał(a): >>> >>>> >>>> On Tue, Jan 22, 2019 at 9:39 PM, Greg V >>>> wrote: >>>>> On Mon, Jan 21, 2019 at 1:11 PM, Martin Karrer >>>>> wrote: >>>>>> My question is if there are any plans yet to support the Graviton >>>>>> ARM instances of AWS? >>>>>> >>>>>> We have a heavy load on FreeBSD and would also use the ARM >>>>>> instances. Are there any other interested parties? >>>>> >>>>> I have tried this. It should work very well in theory, e.g. the >>>>> network card driver (if_ena) compiles with no changes for aarch64, >>>>> and in fact NetBSD has ported this driver and is up and running on >>>>> these instances: https://dmesgd.nycbug.org/index.cgi?do=view&id=4623 >>>>> >>>>> But my result with FreeBSD was: nothing on the console after >>>>> loader.efi hands control to the kernel. >>>>> […] >>>> >>>> Hello everyone, big update: >>>> >>>> FreeBSD/aarch64 on Amazon EC2 a1 (AWS Graviton) instances WORKS! >>>> >>>> https://dmesgd.nycbug.org/index.cgi?do=view&id=4813 >>>> >>>> And you can try it (well, my -CURRENT build, NO WARRANTY etc) right now: >>>> >>>> ami-0c2829a0b82a62ca6 in eu-west-1 (Ireland) >>>> >>>> ----- >>>> >>>> So, what I had to do / what should be done / how others can help get >>>> this into a finished state: >>>> >>>> 1. Serial console: >>>> - I fixed it: https://reviews.freebsd.org/D19507 >>>> - (I learned some things about UARTs and their support in FreeBSD, >>>> should write a blog post about that) >>>> >>>> 2. aarch64 build configuration: >>>> - if_ena network driver module should be enabled: >>>> https://reviews.freebsd.org/D18372 >>>> - NVMe driver should be enabled in the GENERIC kernel config (device >>>> nvme, device nvd) >>>> - BTW, why not also go with hw.nvme.use_nvd="0" by default on >>>> aarch64, IIRC that was done on powerpc64 >>>> >>>> 3. VM image build system: >>>> - GPT+EFI should be used (amd64 was GPT with no EFI, and aarch64 was >>>> MBR with EFI (???)): https://reviews.freebsd.org/D18371 >>>> - bsdec2-image-upload --arm64 flag should be supported: included >>>> above ^^ >>>> - ec2.conf: amazon-ssm-agent shouldn't be installed when building >>>> for aarch64 TARGET, since that's written in Go, and Go isn't ported to >>>> FreeBSD/aarch64 yet: >>>> >>>> https://github.com/myfreeweb/freebsd/commit/5b530ebf7385d8320b9076cf84f50aad01689bc >>>> (untested patch, I actually used an interactive shell in between the >>>> image build commands) >>>> - qemu-aarch64-static should be used for preinstalling pkgs when >>>> chrooting into the image: rough version included above ^^ >>>> >>>> 4. ENA (Elastic Network Adapter) driver: >>>> - it works >>>> - except there's something funky with interrupt activation, and it >>>> hits panic("Attempt to double activation of resource id: %u\n", res_id) >>>> (for the management IRQ) on boot, so I applied the obvious silly >>>> workaround of "don't panic": >>>> >>>> https://github.com/myfreeweb/freebsd/commit/a7e7c6e48cdbdb0fdc6c4e0ba63392262938e62c >>>> - but still, it doesn't properly reactivate interrupts (and the box >>>> becomes unreachable over the net) after going down and up again — >>>> guess what does that on boot? dhclient applying the big jumbo MTU — >>>> so I set dhclient.conf to reject MTU changes: >>>> >>>> https://github.com/myfreeweb/freebsd/commit/03ec4d417b0b4252285baaf4e294cc6d8c870f7f >>>> >>>> >>>> Would be great if someone familiar with interrupts and stuff could help >>>> debug the ena driver and make it work without these hacks :) >> -- >> Colin Percival >> Security Officer Emeritus, FreeBSD | The power to serve >> Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid > > -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-arm@freebsd.org Thu Mar 21 04:14:18 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 B111F154D1EA for ; Thu, 21 Mar 2019 04:14:18 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-qk1-x741.google.com (mail-qk1-x741.google.com [IPv6:2607:f8b0:4864:20::741]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 091BD6C8B5 for ; Thu, 21 Mar 2019 04:14:16 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-qk1-x741.google.com with SMTP id m65so7967857qkl.11 for ; Wed, 20 Mar 2019 21:14:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+9XiuRL1J5gTcDX493wvr3iNYbNkIhess8f9YUZMSAo=; b=uf/U3LcboQlFQPoN+b9QybPOUyweXDEwsKqV29CNVYBhbepeZVcDucWn7QbYuBoT4X C5m9dAKMjdbj9WLd3GVnltAwRz4lRl+tVXRCUG/Y10PYK7tDafEx7xGoH/P0pDi/QAHB /C2ZABknbLktg2e/PKhp91XT5fBHWWS6NOSgbcHA579MxJ2M6AvHnhJcOU2FmxghjHuS ++03ljHnw/TnJNFw0Fds8Gb1mS+RjCI1SGSTNHUY93SpI0INJLAUxGSEXbGoP2EnKyg6 uzAsYNe7OT1ix7FhpkyK1BwHBQ9bJwb67pQusPNFxlGcoZ0n/l4SPbn2VL5eLv20dNM7 J4zQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+9XiuRL1J5gTcDX493wvr3iNYbNkIhess8f9YUZMSAo=; b=BtE6yhEwFURSLxtVAEGSETgj/F8uEoghvsVIFcOZoecgU2nA4uAuszxq74ytJatGsW IjqZMCG5PotWZzno/O4juT0kq2kLf1G4TbLwldJY0xoJV+sLF5WNQ36qySZ6lP93Urey AkA3GARvJYiJe6yrDWo4jAnQVhHqb/4bltrOLyO+RVozbvz0X32Zhmgkct3LP+Kte62/ +fXowAjtUP9/MElt60VfrqzzhkGM7mQBqcIR/Ua3RkPsckmlCWi0xGfz44tca19uPJwb 1bVEyjkW9U8QNGXdT1G1sjxmqKvFOYVD7AKrepznZI6g/01xIvbxU/qkwRDrrhOaFjBf Mv9A== X-Gm-Message-State: APjAAAU4WoBMuRdFik4RLCtpQgN4tlSoHxuG30ca3XF4Q/t/jlIfgPIA 5XlmRh0B8aR4gmrd9bDRGnO3JQhB7jdTe2oS9k/D2ovJ X-Google-Smtp-Source: APXvYqwlXoIEnb3iSjF9CbPhyu4kkBJDadFF8+lK9V9PCIRnOxgNGK+i1svq4mzC7LXg+25xt9+CWKN8sTjUhGEx+0s= X-Received: by 2002:a37:a4d1:: with SMTP id n200mr1056228qke.62.1553141656340; Wed, 20 Mar 2019 21:14:16 -0700 (PDT) MIME-Version: 1.0 References: <79CC79B9-81AF-4563-BABE-429E6A57F476@bmalum.com> <010201686fe5047f-ed14af85-2b25-4480-a62a-a893f062eedd-000000@eu-west-1.amazonses.com> <010201686fe5047f-ed14af85-2b25-4480-a62a-a893f062eedd-000000@eu-west-1.amazo> <1548182399.2864.0@smtp.migadu.com> <1552255580.21373.0@unrelenting.technology> <01000169992ab14c-aa38b2f1-3f57-4805-9d8a-fa92207e4c2d-000000@email.amazonses.com> <010001699e6c9844-608d29c1-df68-4504-a611-430adf179bec-000000@email.amazonses.com> In-Reply-To: <010001699e6c9844-608d29c1-df68-4504-a611-430adf179bec-000000@email.amazonses.com> From: Marcin Wojtas Date: Thu, 21 Mar 2019 05:14:05 +0100 Message-ID: Subject: Re: ARM Graviton AWS Processor (AMI Image) To: Colin Percival Cc: Greg V , Martin Karrer , "Matushevsky, Alexander" , =?UTF-8?Q?Micha=C5=82_Krawczyk?= , =?UTF-8?B?UmFmYcWCIEtvemlr?= , "Tzalik, Guy" , freebsd-arm@freebsd.org X-Rspamd-Queue-Id: 091BD6C8B5 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=semihalf-com.20150623.gappssmtp.com header.s=20150623 header.b=uf/U3Lcb X-Spamd-Result: default: False [-3.69 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.987,0]; R_DKIM_ALLOW(-0.20)[semihalf-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[semihalf.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: ASPMX2.GOOGLEMAIL.com]; DKIM_TRACE(0.00)[semihalf-com.20150623.gappssmtp.com:+]; RCPT_COUNT_SEVEN(0.00)[8]; RCVD_IN_DNSWL_NONE(0.00)[1.4.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; NEURAL_HAM_SHORT(-0.85)[-0.851,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-0.54)[ip: (2.30), ipnet: 2607:f8b0::/32(-2.81), asn: 15169(-2.12), country: US(-0.07)] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Thu, 21 Mar 2019 04:14:19 -0000 Hi Colin, I will handle those patches, thanks. Best regards, Marcin W dniu czw., 21.03.2019 o 05:05 Colin Percival napisa=C5=82(a): > Hi Micha=C5=82, > > Thanks, those two patches fix both problems. Can you get them into > the FreeBSD tree or should I commit them? > > Colin Percival > > On 3/20/19 3:24 AM, Micha=C5=82 Krawczyk wrote: > > Hi, > > > > we have solution for two of the issues with ENA, > > > > The double resource activation can be fixed by this patch: > > https://reviews.freebsd.org/D19655 > > > > And the issue with reloading module/reconfiguring it by using ifconfig > > can be fixed by using this patch: > > https://reviews.freebsd.org/D19641 > > > > Please check if that fixes it for you. > > > > Thanks, > > Micha=C5=82 > > > > > > =C5=9Br., 20 mar 2019 o 04:35 Colin Percival > napisa=C5=82(a): > >> > >> Hi ENA people, > >> > >> Any luck figuring out what was going on with the ENA driver here > >> with interrupt activation? > >> > >> Colin Percival > >> > >> On 3/11/19 1:35 AM, Marcin Wojtas wrote: > >>> +FreeBSD ENA maintainers > >>> > >>> W dniu pon., 11.03.2019 o 00:40 Greg V > >>> napisa=C5=82(a): > >>> > >>>> > >>>> On Tue, Jan 22, 2019 at 9:39 PM, Greg V > >>>> wrote: > >>>>> On Mon, Jan 21, 2019 at 1:11 PM, Martin Karrer > >>>>> wrote: > >>>>>> My question is if there are any plans yet to support the Graviton > >>>>>> ARM instances of AWS? > >>>>>> > >>>>>> We have a heavy load on FreeBSD and would also use the ARM > >>>>>> instances. Are there any other interested parties? > >>>>> > >>>>> I have tried this. It should work very well in theory, e.g. the > >>>>> network card driver (if_ena) compiles with no changes for aarch64, > >>>>> and in fact NetBSD has ported this driver and is up and running on > >>>>> these instances: https://dmesgd.nycbug.org/index.cgi?do=3Dview&id= =3D4623 > >>>>> > >>>>> But my result with FreeBSD was: nothing on the console after > >>>>> loader.efi hands control to the kernel. > >>>>> [=E2=80=A6] > >>>> > >>>> Hello everyone, big update: > >>>> > >>>> FreeBSD/aarch64 on Amazon EC2 a1 (AWS Graviton) instances WORKS! > >>>> > >>>> https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4813 > >>>> > >>>> And you can try it (well, my -CURRENT build, NO WARRANTY etc) right > now: > >>>> > >>>> ami-0c2829a0b82a62ca6 in eu-west-1 (Ireland) > >>>> > >>>> ----- > >>>> > >>>> So, what I had to do / what should be done / how others can help get > >>>> this into a finished state: > >>>> > >>>> 1. Serial console: > >>>> - I fixed it: https://reviews.freebsd.org/D19507 > >>>> - (I learned some things about UARTs and their support in FreeBSD= , > >>>> should write a blog post about that) > >>>> > >>>> 2. aarch64 build configuration: > >>>> - if_ena network driver module should be enabled: > >>>> https://reviews.freebsd.org/D18372 > >>>> - NVMe driver should be enabled in the GENERIC kernel config > (device > >>>> nvme, device nvd) > >>>> - BTW, why not also go with hw.nvme.use_nvd=3D"0" by default on > >>>> aarch64, IIRC that was done on powerpc64 > >>>> > >>>> 3. VM image build system: > >>>> - GPT+EFI should be used (amd64 was GPT with no EFI, and aarch64 > was > >>>> MBR with EFI (???)): https://reviews.freebsd.org/D18371 > >>>> - bsdec2-image-upload --arm64 flag should be supported: included > >>>> above ^^ > >>>> - ec2.conf: amazon-ssm-agent shouldn't be installed when building > >>>> for aarch64 TARGET, since that's written in Go, and Go isn't ported = to > >>>> FreeBSD/aarch64 yet: > >>>> > >>>> > https://github.com/myfreeweb/freebsd/commit/5b530ebf7385d8320b9076cf84f50= aad01689bc > >>>> (untested patch, I actually used an interactive shell in between the > >>>> image build commands) > >>>> - qemu-aarch64-static should be used for preinstalling pkgs when > >>>> chrooting into the image: rough version included above ^^ > >>>> > >>>> 4. ENA (Elastic Network Adapter) driver: > >>>> - it works > >>>> - except there's something funky with interrupt activation, and i= t > >>>> hits panic("Attempt to double activation of resource id: %u\n", > res_id) > >>>> (for the management IRQ) on boot, so I applied the obvious silly > >>>> workaround of "don't panic": > >>>> > >>>> > https://github.com/myfreeweb/freebsd/commit/a7e7c6e48cdbdb0fdc6c4e0ba6339= 2262938e62c > >>>> - but still, it doesn't properly reactivate interrupts (and the b= ox > >>>> becomes unreachable over the net) after going down and up again =E2= =80=94 > >>>> guess what does that on boot? dhclient applying the big jumbo MTU = =E2=80=94 > >>>> so I set dhclient.conf to reject MTU changes: > >>>> > >>>> > https://github.com/myfreeweb/freebsd/commit/03ec4d417b0b4252285baaf4e294c= c6d8c870f7f > >>>> > >>>> > >>>> Would be great if someone familiar with interrupts and stuff could > help > >>>> debug the ena driver and make it work without these hacks :) > >> -- > >> Colin Percival > >> Security Officer Emeritus, FreeBSD | The power to serve > >> Founder, Tarsnap | www.tarsnap.com | Online backups for the truly > paranoid > > > > > > -- > Colin Percival > Security Officer Emeritus, FreeBSD | The power to serve > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoi= d > From owner-freebsd-arm@freebsd.org Thu Mar 21 10:53:57 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 A4DF3153219E for ; Thu, 21 Mar 2019 10:53:57 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8DA39855AF for ; Thu, 21 Mar 2019 10:53:55 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-qt1-x833.google.com with SMTP id z16so4590564qtn.4 for ; Thu, 21 Mar 2019 03:53:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=QQNDow3+mdTic15Onw8mwEWbydV0qZCk45Ua28oHQdQ=; b=FdFmYoNxXoUuFBmUsAX4xNCi27E5hNZ6bVOyjeBuIXChBxlWN1OquTfvrDmqpCVHK6 dS60DiVXDF3ytjJrPC8N+8Ivoslu2C5Tu19m5ir/tMqSYgWAk0cyq1bDoykqpwKRsU+j R6P15/Tk+ValFRNKvI64ho1l0uYXB3ApcDRjlXGOmEcgeR/0D+aXR9DavC+Plvkn2i6E HS011cIAtEVglYVcBdQzlzfhq6q6ClnqrXsfg0XemT8sPYNlIdyMv9ee7UJgLXqCdF5z C4xAytismk3kykMejMXZPpETRkXmE5q2SJWuQU8yCNQe7iQQhO9ZKb9sKQioWqq4IF+S AnWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=QQNDow3+mdTic15Onw8mwEWbydV0qZCk45Ua28oHQdQ=; b=Zz+IN3+TqI0EZpojMH05xp/OkrSBsU+bjuY8WrA9W6fEu82dAgQ29w8/JaMeDZyK80 U4Foc6eMiGovYM8P3ldAuT6RzeR0XChAmDkQkRtb9LcaqWHfeA4Stz3djDxh3JpH/McP pyI++Mb+PTXJ8iP/Ol/mu9x2kTR7LJy/OAiIfAzDxVahvaLwFvaBEXWCLMFw5Jp8/ngn ikM++6s4JAG+KD7sxiZilDYZF+9L6IeLYxYKa2nxZU6TJO4QaJlSSCipJlnoWfUMyELP j6IFXDvt/K+pCslOZgC+6ZmAYQ1JmrJR3iLGpwzRafRftXQW+ANVSPAEWjfRiskskOd0 8Osg== X-Gm-Message-State: APjAAAXiqwkNCtOKUTR+V8cfOlRKwwoQSmG9Zv+I6V6VuffJtOBXQvl1 wZl11lH28KconZsyFgu2eIg/3P+M5NhddEbouaLiVA== X-Google-Smtp-Source: APXvYqzd5jmfPA2g7Zt08K9m3tI/NNuzUw8ITmTZ/xU5CKruDC6XOYJh3fzVBe3ls9HekZJXXzTGhzZuLL/Je9JH/sc= X-Received: by 2002:a0c:9acc:: with SMTP id k12mr2454506qvf.211.1553165633876; Thu, 21 Mar 2019 03:53:53 -0700 (PDT) MIME-Version: 1.0 References: <79CC79B9-81AF-4563-BABE-429E6A57F476@bmalum.com> <010201686fe5047f-ed14af85-2b25-4480-a62a-a893f062eedd-000000@eu-west-1.amazonses.com> <010201686fe5047f-ed14af85-2b25-4480-a62a-a893f062eedd-000000@eu-west-1.amazo> <1548182399.2864.0@smtp.migadu.com> <1552255580.21373.0@unrelenting.technology> <01000169992ab14c-aa38b2f1-3f57-4805-9d8a-fa92207e4c2d-000000@email.amazonses.com> <010001699e6c9812-a0fc8d06-51d3-4252-ac06-2c1087d2c46f-000000@email.amazonses.com> In-Reply-To: <010001699e6c9812-a0fc8d06-51d3-4252-ac06-2c1087d2c46f-000000@email.amazonses.com> From: Marcin Wojtas Date: Thu, 21 Mar 2019 11:53:41 +0100 Message-ID: Subject: Re: ARM Graviton AWS Processor (AMI Image) To: Colin Percival Cc: =?UTF-8?Q?Micha=C5=82_Krawczyk?= , "Matushevsky, Alexander" , freebsd-arm , "Tzalik, Guy" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 8DA39855AF X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=semihalf-com.20150623.gappssmtp.com header.s=20150623 header.b=FdFmYoNx X-Spamd-Result: default: False [-5.73 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[semihalf-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[semihalf.com]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[semihalf-com.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[ASPMX2.GOOGLEMAIL.com,ALT2.ASPMX.L.GOOGLE.com,ASPMX.L.GOOGLE.com,ALT1.ASPMX.L.GOOGLE.com,ASPMX3.GOOGLEMAIL.com]; RCVD_IN_DNSWL_NONE(0.00)[3.3.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.69)[-0.687,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-2.73)[ip: (-8.65), ipnet: 2607:f8b0::/32(-2.82), asn: 15169(-2.12), country: US(-0.07)] 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: Thu, 21 Mar 2019 10:53:57 -0000 Hi Colin, Fixes pushed: https://svnweb.freebsd.org/base?view=3Drevision&revision=3D345371 https://svnweb.freebsd.org/base?view=3Drevision&revision=3D345373 Best regards, Marcin czw., 21 mar 2019 o 06:05 Colin Percival napisa=C5= =82(a): > > Hi Micha=C5=82, > > Thanks, those two patches fix both problems. Can you get them into > the FreeBSD tree or should I commit them? > > Colin Percival > > On 3/20/19 3:24 AM, Micha=C5=82 Krawczyk wrote: > > Hi, > > > > we have solution for two of the issues with ENA, > > > > The double resource activation can be fixed by this patch: > > https://reviews.freebsd.org/D19655 > > > > And the issue with reloading module/reconfiguring it by using ifconfig > > can be fixed by using this patch: > > https://reviews.freebsd.org/D19641 > > > > Please check if that fixes it for you. > > > > Thanks, > > Micha=C5=82 > > > > > > =C5=9Br., 20 mar 2019 o 04:35 Colin Percival nap= isa=C5=82(a): > >> > >> Hi ENA people, > >> > >> Any luck figuring out what was going on with the ENA driver here > >> with interrupt activation? > >> > >> Colin Percival > >> > >> On 3/11/19 1:35 AM, Marcin Wojtas wrote: > >>> +FreeBSD ENA maintainers > >>> > >>> W dniu pon., 11.03.2019 o 00:40 Greg V > >>> napisa=C5=82(a): > >>> > >>>> > >>>> On Tue, Jan 22, 2019 at 9:39 PM, Greg V > >>>> wrote: > >>>>> On Mon, Jan 21, 2019 at 1:11 PM, Martin Karrer > >>>>> wrote: > >>>>>> My question is if there are any plans yet to support the Graviton > >>>>>> ARM instances of AWS? > >>>>>> > >>>>>> We have a heavy load on FreeBSD and would also use the ARM > >>>>>> instances. Are there any other interested parties? > >>>>> > >>>>> I have tried this. It should work very well in theory, e.g. the > >>>>> network card driver (if_ena) compiles with no changes for aarch64, > >>>>> and in fact NetBSD has ported this driver and is up and running on > >>>>> these instances: https://dmesgd.nycbug.org/index.cgi?do=3Dview&id= =3D4623 > >>>>> > >>>>> But my result with FreeBSD was: nothing on the console after > >>>>> loader.efi hands control to the kernel. > >>>>> [=E2=80=A6] > >>>> > >>>> Hello everyone, big update: > >>>> > >>>> FreeBSD/aarch64 on Amazon EC2 a1 (AWS Graviton) instances WORKS! > >>>> > >>>> https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4813 > >>>> > >>>> And you can try it (well, my -CURRENT build, NO WARRANTY etc) right = now: > >>>> > >>>> ami-0c2829a0b82a62ca6 in eu-west-1 (Ireland) > >>>> > >>>> ----- > >>>> > >>>> So, what I had to do / what should be done / how others can help get > >>>> this into a finished state: > >>>> > >>>> 1. Serial console: > >>>> - I fixed it: https://reviews.freebsd.org/D19507 > >>>> - (I learned some things about UARTs and their support in FreeBSD= , > >>>> should write a blog post about that) > >>>> > >>>> 2. aarch64 build configuration: > >>>> - if_ena network driver module should be enabled: > >>>> https://reviews.freebsd.org/D18372 > >>>> - NVMe driver should be enabled in the GENERIC kernel config (dev= ice > >>>> nvme, device nvd) > >>>> - BTW, why not also go with hw.nvme.use_nvd=3D"0" by default on > >>>> aarch64, IIRC that was done on powerpc64 > >>>> > >>>> 3. VM image build system: > >>>> - GPT+EFI should be used (amd64 was GPT with no EFI, and aarch64 = was > >>>> MBR with EFI (???)): https://reviews.freebsd.org/D18371 > >>>> - bsdec2-image-upload --arm64 flag should be supported: included > >>>> above ^^ > >>>> - ec2.conf: amazon-ssm-agent shouldn't be installed when building > >>>> for aarch64 TARGET, since that's written in Go, and Go isn't ported = to > >>>> FreeBSD/aarch64 yet: > >>>> > >>>> https://github.com/myfreeweb/freebsd/commit/5b530ebf7385d8320b9076cf= 84f50aad01689bc > >>>> (untested patch, I actually used an interactive shell in between the > >>>> image build commands) > >>>> - qemu-aarch64-static should be used for preinstalling pkgs when > >>>> chrooting into the image: rough version included above ^^ > >>>> > >>>> 4. ENA (Elastic Network Adapter) driver: > >>>> - it works > >>>> - except there's something funky with interrupt activation, and i= t > >>>> hits panic("Attempt to double activation of resource id: %u\n", res_= id) > >>>> (for the management IRQ) on boot, so I applied the obvious silly > >>>> workaround of "don't panic": > >>>> > >>>> https://github.com/myfreeweb/freebsd/commit/a7e7c6e48cdbdb0fdc6c4e0b= a63392262938e62c > >>>> - but still, it doesn't properly reactivate interrupts (and the b= ox > >>>> becomes unreachable over the net) after going down and up again =E2= =80=94 > >>>> guess what does that on boot? dhclient applying the big jumbo MTU = =E2=80=94 > >>>> so I set dhclient.conf to reject MTU changes: > >>>> > >>>> https://github.com/myfreeweb/freebsd/commit/03ec4d417b0b4252285baaf4= e294cc6d8c870f7f > >>>> > >>>> > >>>> Would be great if someone familiar with interrupts and stuff could h= elp > >>>> debug the ena driver and make it work without these hacks :) > >> -- > >> Colin Percival > >> Security Officer Emeritus, FreeBSD | The power to serve > >> Founder, Tarsnap | www.tarsnap.com | Online backups for the truly para= noid > > > > > > -- > Colin Percival > Security Officer Emeritus, FreeBSD | The power to serve > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoi= d > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Thu Mar 21 18:34:55 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 AC52C154AE2C for ; Thu, 21 Mar 2019 18:34:55 +0000 (UTC) (envelope-from jedi@jeditekunum.com) Received: from a2i644.smtp2go.com (a2i644.smtp2go.com [103.47.206.132]) (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 074F071298 for ; Thu, 21 Mar 2019 18:34:44 +0000 (UTC) (envelope-from jedi@jeditekunum.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpservice.net; s=m4fue0.a1-4.dyn; x=1553194185; h=Feedback-ID: X-Smtpcorp-Track:To:Date:Subject:Message-Id:From:Reply-To:Sender: List-Unsubscribe; bh=OYfjRsB5yTl0gqeFYBHW5qEY4czUL/lV1ph+cOGSiHw=; b=0RWgCOGq /JfOc7mHGLGJnj84k3VjsF8sY2m4FAnFHDynpZYrnz+WkrVE97YGd1IuhgzO5wsjby2kgKODzZXhW Y6+wORiRPQD/+/wkojHfVcuGXtiX1vVhHpQcIX63FqqK0omCH8/M9nLRQ6SzERuo00zgpPFKq2qCn rQGNnG2wvchCzilHe36hN43ailGvXZL8IQQekKu/QWvvPdEuZY1kwgvWvoendiqA9Yp7YLNx7puOw ubYmOy6H2oFCzqGGKgsJi+uQtQ+w3lrM7GlmEsXv10mC4tE3cqGLb82MXQRfXdQHnhUGLyjUZuqlv qAM+BPjnIwkRe4/7/3vI4Q4o5g==; Received: from [10.173.255.233] (helo=SmtpCorp) by smtpcorp.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from ) id 1h72WH-ED4yjj-Vl; Thu, 21 Mar 2019 18:34:26 +0000 Received: from [10.162.213.37] (helo=takodana.opaxus.net) by smtpcorp.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from ) id 1h72WH-IbZs0d-EL; Thu, 21 Mar 2019 18:34:25 +0000 Received: from [10.0.10.1] (174-20-17-78.mpls.qwest.net [174.20.17.78]) by takodana.opaxus.net (Postfix) with ESMTPSA id E19E62692A; Thu, 21 Mar 2019 13:34:21 -0500 (CDT) From: Jedi Tek'Unum Message-Id: <8AF0CF9D-BD5D-42AC-B1BF-27A056B3D7C2@jeditekunum.com> Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: allwinner i2c [was: Options for FBSD support with LCD device - new project] Date: Thu, 21 Mar 2019 13:34:20 -0500 In-Reply-To: Cc: Daniel Braniss , freebsd-arm@freebsd.org To: Ian Lepore 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> X-Mailer: Apple Mail (2.3445.102.3) X-Smtpcorp-Track: 1h72WHmPZs0dEL.k5kzqkQLi Feedback-ID: 207158m:207158azGM_-I:207158seUxOnWT_Y X-Report-Abuse: Please forward a copy of this message, including all headers, to X-Rspamd-Queue-Id: 074F071298 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=smtpservice.net header.s=m4fue0.a1-4.dyn header.b=0RWgCOGq X-Spamd-Result: default: False [-3.56 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[smtpservice.net:s=m4fue0.a1-4.dyn]; MX_INVALID(0.50)[greylisted]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[jeditekunum.com]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[smtpservice.net:+]; RCVD_IN_DNSWL_MED(-0.20)[132.206.47.103.list.dnswl.org : 127.0.3.2]; NEURAL_HAM_SHORT(-0.84)[-0.839,0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; IP_SCORE(-0.72)[asn: 1299(-3.60), country: EU(-0.00)]; ASN(0.00)[asn:1299, ipnet:103.47.204.0/22, country:EU]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Thu, 21 Mar 2019 18:34:56 -0000 On Mar 20, 2019, at 10:31 AM, Ian Lepore wrote: >=20 > On Tue, 2019-03-19 at 08:28 +0200, Daniel Braniss wrote: >> I have several allwinner SoC, mainly from FriendlyArm, and neither = i2c or SPI work. >> I have a hacked i2c that mostly works, but hangs sometimes :-), = mainly >> timing issues of which I have no idea how to fix. >> I=E2=80=99m willing to help here but my knowledge of the twsi tends = to zero. >> hint hint =E2=80=A6 >>=20 >> cheers, >> danny >=20 > Iirc, allwinner requires working i2c even to boot, because the boards > have i2c PMIC chips on them. I wonder if it's a case where a few = small > commands to the pmic work fine but bigger transfers fail? I dunno, > anything more you can say about the problem would help. My H5 board, a NanoPi NEO 2, running vendor supplied Linux has = /dev/i2c-0 through i2c-3. Only i2c0 is available externally. Detect shows 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- --=20 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --=20 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --=20 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- 3e 3f=20 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --=20 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --=20 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --=20 70: 70 71 -- 73 -- -- -- -- =20 3c is the OLED Hat. The rest are all my boards (73 is mux and the rest = are SX1509s). The only other scan that shows anything is i2c3 device 30. Maybe that is = the PMIC? i2c1 and i2c2 scan very slowly and eventually show nothing. I suppose = they aren=E2=80=99t pulled up. Daniel, I haven=E2=80=99t had any problems with hangs (Linux) but I do = have intermittent troubles that could be due to a variety of things. = I=E2=80=99ve yet to see anything =E2=80=9Crock solid=E2=80=9D about = these boards. From owner-freebsd-arm@freebsd.org Thu Mar 21 18:43:04 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 37CF6154B1D6 for ; Thu, 21 Mar 2019 18:43:04 +0000 (UTC) (envelope-from jedi@jeditekunum.com) Received: from a2i644.smtp2go.com (a2i644.smtp2go.com [103.47.206.132]) (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 5B20671745 for ; Thu, 21 Mar 2019 18:43:03 +0000 (UTC) (envelope-from jedi@jeditekunum.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpservice.net; s=m4fue0.a1-4.dyn; x=1553194683; h=Feedback-ID: X-Smtpcorp-Track:To:Date:Subject:Message-Id:From:Reply-To:Sender: List-Unsubscribe; bh=V9Ay3sQFP6qbqkN3JZkYTXfybhfkTcUBndb9RCnzzX4=; b=kAyPlmoy MqT4yciaIigVvT+oE2LITe1EACDtc7cJr6kmg44ah1M2f4HdFSHdVnbHIRpoq+s8UB1Baz8yy6R4M hMPVq8jwHsU5VVJGrYNyoKuLoDK8eLALPpazNmCgz5sL5r8GSzWklG/C5L9euXBFXI7E7m1vA+S9B nWg1yUzGUIvmzVenWeEEX4UM+TOeDeLMsdQubebEYtBJXD+VcugBBzC7tye96x9sOGe8ly2oJjrgC d9gcAm1AH85l2eog5j3w39M9yHn0o/4RzVU4heEdXZ49/uosBcLKFSSL2SGJnh++rY3hR1Qx3BCp8 t2x/vKJjvEjhpwTV4KuqlCjHBw==; Received: from [10.176.58.103] (helo=SmtpCorp) by smtpcorp.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from ) id 1h72eb-ED4v6G-9q; Thu, 21 Mar 2019 18:43:01 +0000 Received: from [10.162.213.37] (helo=takodana.opaxus.net) by smtpcorp.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from ) id 1h72eZ-9EFN3p-V2; Thu, 21 Mar 2019 18:43:00 +0000 Received: from [10.0.10.1] (174-20-17-78.mpls.qwest.net [174.20.17.78]) by takodana.opaxus.net (Postfix) with ESMTPSA id E75502692C; Thu, 21 Mar 2019 13:42:57 -0500 (CDT) From: Jedi Tek'Unum Message-Id: <84A0566D-4107-4FD5-83E3-858F727A197C@jeditekunum.com> Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: Options for FBSD support with LCD device - new project Date: Thu, 21 Mar 2019 13:42:55 -0500 In-Reply-To: <17133d06965e61e7e835c5ea7d69ca9762efad7d.camel@freebsd.org> Cc: freebsd-arm@freebsd.org To: Ian Lepore 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> <17133d06965e61e7e835c5ea7d69ca9762efad7d.camel@freebsd.org> X-Mailer: Apple Mail (2.3445.102.3) X-Smtpcorp-Track: 1h72-Z9EFN3pV2.k5syfqBfr Feedback-ID: 207158m:207158azGM_-I:207158sDWsPdZzId X-Report-Abuse: Please forward a copy of this message, including all headers, to X-Rspamd-Queue-Id: 5B20671745 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=smtpservice.net header.s=m4fue0.a1-4.dyn header.b=kAyPlmoy X-Spamd-Result: default: False [-3.53 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[smtpservice.net:s=m4fue0.a1-4.dyn]; MX_INVALID(0.50)[cached]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[jeditekunum.com]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[smtpservice.net:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_MED(-0.20)[132.206.47.103.list.dnswl.org : 127.0.3.2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_SPF_NA(0.00)[]; NEURAL_HAM_SHORT(-0.82)[-0.824,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; IP_SCORE(-0.70)[asn: 1299(-3.51), country: EU(-0.00)]; ASN(0.00)[asn:1299, ipnet:103.47.204.0/22, country:EU]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Thu, 21 Mar 2019 18:43:04 -0000 On Mar 20, 2019, at 9:56 AM, Ian Lepore wrote: >=20 > The default pin assignments in the dts are completely controlled by > linux, and I think effectively by the actual board vendors who create > the dts and submit it to linux. We (freebsd) are just a consumer of > the dts info, we have to work with whatever they shove down our > throats, and continually re-adapt ourselves whenever they change their > minds and make arbitrary incompatible changes from one release to the > next (which they definitely do). The problem is =E2=80=9Clinux=E2=80=9D - which one?! As far as I=E2=80=99ve been able to figure out, these boards have not = been propagated into mainline linux. So if you are saying FBSD draws = from mainline linux then you might not be getting the good stuff. There is friendlyarm=E2=80=99s distribution = /boot/sun50i-h5-nanopi-neo2.dtb that decompiled doesn=E2=80=99t look = remotely like anything I=E2=80=99ve seen elsewhere. There is = https://linux-sunxi.org/Main_Page . = There is armbian - some sun50i-h5-i2c*.dts overlays here: = https://github.com/armbian/sunxi-DT-overlays/tree/master/sun50i-h5 = . = Given the moving target of what FDT is, who knows whether these are = remotely useful. Bottom line is we non-experts have next to zero chance getting these = boards working for us with FBSD. From owner-freebsd-arm@freebsd.org Fri Mar 22 10:44:51 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 401C5153FEAF for ; Fri, 22 Mar 2019 10:44:51 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh503-vm10.bullet.mail.kks.yahoo.co.jp (nh503-vm10.bullet.mail.kks.yahoo.co.jp [183.79.56.196]) by mx1.freebsd.org (Postfix) with SMTP id AB18F74C05 for ; Fri, 22 Mar 2019 10:44:39 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [183.79.100.138] by nh503.bullet.mail.kks.yahoo.co.jp with NNFMP; 22 Mar 2019 10:42:23 -0000 Received: from [183.79.101.123] by t501.bullet.mail.kks.yahoo.co.jp with NNFMP; 22 Mar 2019 10:42:23 -0000 Received: from [127.0.0.1] by omp510.mail.kks.yahoo.co.jp with NNFMP; 22 Mar 2019 10:42:23 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 340606.38558.bm@omp510.mail.kks.yahoo.co.jp X-YMail-OSG: seUH7zkVM1muB1.WWUM_7fTFq.EAVqTql8SRW_81UWpdqG0q0PS2_No4jVW6GEq 6tsLHWmrekChEy7BDdAT6Se_LMj8t90F6GUg1RAfz2RkrTL6zs9J_SscgiZJR.97.Tul6WQ0OC4I 5UkCy5Tq2b4M43pJWmNu6T89_5SlYvbz4aF08PpfGMBnNEyRODirxqsM8ChmQpuAM01hF._QRiRm IAnBDneY7f3.3Ocm4L._QPi_Y3zMLEE1f49e6B_Dbi18liOf8HKPop_zZui811bbnkSWnUnDc44k aycuwA7RRgotIDZKXq_AWfWNaXPrAK_c5PhCv3pcG3hN0kMPVRjhEbOEaPT9KIluQ_tPJKmb4Sy5 3hRsGGrG8jmBKvRXZZKIS0BOTNWxdaxJxIyhSK9WPCz..i9A0tMecqilBL3nN3oYcJZKFxFpLClW 2LcpFqZk.BP3khO1Q2aKqwfwo4Nnu0M7iBoZNW.ieQo3Tuu0LXif.pAg3KSggr3tKzZdLKFZZ7AX w609c0fI1kxWfq1WBgVpK4FRxTm7B3vDic7fWR_wB.h1VC4JpnAunT3eIvhDg4DzD3QVhSl8qVm4 wV74GNeqMYj8M.VWQW.LZ0hQzFnleQu94ANw1jANZ Received: from jws700003.mail.kks.yahoo.co.jp by sendmailws518.mail.kks.yahoo.co.jp; Fri, 22 Mar 2019 19:42:22 +0000; 1553251342.835 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1553251343; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:To:Message-ID:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:References; bh=pK+ZaT5qB/26fkU/IjWGgVLzig17MXJWVf82J/+8muI=; b=TKfI572htDSXvcUzWdyg4j0XpLQzB656kcMZRdwBES2Z5A101gW0sVL5zobWQGNz gvLfHIRlTXaG0MLreYGA558U87UwDK0M+53ZslD6PL1Kewyd9ZwGjZ7iFBzzhUWQ2Te LBoShShFe3Q/wHnc1cekXm8iodHXzr0q74gQQZWY= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:References; b=ImL8TtLfNEiUzMeG75/mpEAG2IyQjlFZSiPmLJshZVZmijtMNmi184SXh8nnKxOh uXvbSk9dbUO0jMIIGitsAtoD5wuEzPijByTzpVgaoPAx+AFrp0o+cenJ7rLg+8a8pFe YNruyMP2Heciy75jrXerkqDxzX9UsmqLyv4oZrUM=; Date: Fri, 22 Mar 2019 19:42:22 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki To: "freebsd-arm@freebsd.org" Message-ID: <1252845449.757894.1553251342413.JavaMail.yahoo@mail.yahoo.co.jp> Subject: Re: build error MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable References: <1252845449.757894.1553251342413.JavaMail.yahoo.ref@mail.yahoo.co.jp> X-Rspamd-Queue-Id: AB18F74C05 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.co.jp header.s=yj20110701 header.b=TKfI572h; dmarc=pass (policy=none) header.from=yahoo.co.jp; spf=pass (mx1.freebsd.org: domain of yamori813@yahoo.co.jp designates 183.79.56.196 as permitted sender) smtp.mailfrom=yamori813@yahoo.co.jp X-Spamd-Result: default: False [0.83 / 15.00]; HAS_REPLYTO(0.00)[yamori813@yahoo.co.jp]; R_SPF_ALLOW(-0.20)[+ip4:183.79.56.0/23]; FREEMAIL_FROM(0.00)[yahoo.co.jp]; DKIM_TRACE(0.00)[yahoo.co.jp:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.co.jp,none]; MX_GOOD(-0.01)[mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo. co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.co.jp]; ASN(0.00)[asn:24572, ipnet:183.79.0.0/16, country:JP]; IP_SCORE(0.90)[ipnet: 183.79.0.0/16(2.54), asn: 24572(2.03), country: JP(-0.07)]; DWL_DNSWL_NONE(0.00)[yahoo.co.jp.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.co.jp:s=yj20110701]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; NEURAL_HAM_LONG(-0.59)[-0.591,0]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[yahoo.co.jp]; NEURAL_SPAM_MEDIUM(0.49)[0.488,0]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[196.56.79.183.list.dnswl.org : 127.0.5.0]; TO_DN_EQ_ADDR_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.95)[0.946,0] 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: Fri, 22 Mar 2019 10:44:51 -0000 Hi I have more error by armv5t cross compile at CURRENT. -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- install: target directory `/usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tm= p/usr /home/hiroki/freebsd/arm.arm/tmp/usr/lib/clang/8.0.0/include/' does not exi= st last error still occur. Hiroki Mori ----- Original Message ----- > From: Mori Hiroki > To: "freebsd-arm@freebsd.org" > Cc:=20 > Date: 2019/2/3, Sun 10:52 > Subject: Re: build error >=20 >=20 >=20 > Hi >=20 > This is temporary patch. Please fix correct. >=20 > diff --git a/Makefile.inc1 b/Makefile.inc1 > index e5a062acb64..2b9d81759c5 100644 > --- a/Makefile.inc1 > +++ b/Makefile.inc1 > @@ -1101,6 +1101,8 @@ _includes: > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 @echo=20 > "--------------------------------------------------------------" > =C2=A0# Special handling for SUBDIR_OVERRIDE in buildworld as they most l= ikely need > =C2=A0# headers from default SUBDIR.=C2=A0 Do SUBDIR_OVERRIDE includes la= st. > +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 @mkdir -p ${WORLDTMP}/usr/include/c= ++/v1/experimental > +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 @mkdir -p ${WORLDTMP}/usr/include/c= ++/v1/ext > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ${_+_}cd ${.CURDIR}; ${WMAKE} = SUBDIR_OVERRIDE=3D SHARED=3Dsymlinks =C2=A5 > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 MK_INC= LUDES=3Dyes includes > =C2=A0.if !empty(SUBDIR_OVERRIDE) && make(buildworld) > @@ -2459,6 +2461,7 @@ _ar=3Dusr.bin/ar > =C2=A0.endif >=20 > =C2=A0cross-tools: .MAKE .PHONY > +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 @mkdir -p ${WORLDTMP}/usr/lib/clang= /7.0.1/include/ > =C2=A0.for _tool in =C2=A5 > =C2=A0=C2=A0=C2=A0=C2=A0 ${LOCAL_XTOOL_DIRS} =C2=A5 > =C2=A0=C2=A0=C2=A0=C2=A0 ${_ar} =C2=A5 >=20 >=20 > ----- Original Message ----- >> From: Mori Hiroki >> To: "freebsd-arm@freebsd.org" =20 >> Date: 2019/2/3, Sun 08:56 >> Subject: build error >>=20 >> Hi >> I try to marvell kirkwood. >>=20 >> I have build error on current. >> I use ZRouter build system. But almost FreeBSD cross build system. >>=20 >> If you have advice please let me know. >> Thanks. >> Hiroki Mori >>=20 >> -------------------------------------------------------------- >>>>>=C2=A0 stage 3: cross tools >> -------------------------------------------------------------- >> cd /usr/home/hiroki/freebsd; INSTALL=3D"sh=20 > /usr/home/hiroki/freebsd/tools/install. >> sh"=C2=A0=20 > TOOLS_PREFIX=3D/usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home= /hir >> oki/freebsd/arm.arm/tmp=C2=A0=20 > PATH=3D/usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/ >> usr/home/hiroki/freebsd/arm.arm/tmp/legacy/usr/sbin:/usr/home/hiroki/zob= j/usr/ho >> me/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/arm.arm/tmp/legacy/usr/bin= :/usr/ho >> me/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/arm.a= rm/tmp/l >> egacy/bin:/sbin:/bin:/usr/sbin:/usr/bin=C2=A0=20 > WORLDTMP=3D/usr/home/hiroki/zobj/usr/home >> /hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/arm.arm/tmp=C2=A0 MAKEFLAGS= =3D"-m=20 > /usr/home >> /hiroki/freebsd/tools/build/mk=C2=A0 -D NO_CLEAN -m=20 > /usr/home/hiroki/freebsd/share/mk >> " make=C2=A0 -f Makefile.inc1=C2=A0 DESTDIR=3D=C2=A0=20 > OBJTOP=3D'/usr/home/hiroki/zobj/usr/home/hirok >> i/ZRouter/tmp/usr/home/hiroki/freebsd/arm.arm/tmp/obj-tools'=C2=A0=20 > OBJROOT=3D'${OBJTOP} >> /'=C2=A0 MAKEOBJDIRPREFIX=3D=C2=A0 BOOTSTRAPPING=3D1102000=C2=A0 BWPHASE= =3Dcross-tools=C2=A0=20 > SSP_CFLAGS=3D=C2=A0=20 >> MK_HTML=3Dno NO_LINT=3Dyes MK_MAN=3Dno=C2=A0 -DNO_PIC MK_PROFILE=3Dno -D= NO_SHARED=C2=A0=20 > -DNO_CPU_C >> FLAGS MK_WARNS=3Dno MK_CTF=3Dno=C2=A0 MK_CLANG_EXTRAS=3Dno MK_CLANG_FULL= =3Dno=C2=A0 MK_LLDB=3Dno=20 > MK_ >> RETPOLINE=3Dno MK_TESTS=3Dno=C2=A0 MK_INCLUDES=3Dyes MK_LLVM_TARGET_ALL= =3Dno=C2=A0 TARGET=3Darm=20 > TARG >> ET_ARCH=3Darm=C2=A0 MK_GDB=3Dno MK_TESTS=3Dno cross-tools >> =3D=3D=3D> lib/clang (obj,all,install) >> =3D=3D=3D> lib/clang/libllvm (obj) >> =3D=3D=3D> lib/clang/libclang (obj) >> =3D=3D=3D> lib/clang/headers (obj) >> =3D=3D=3D> lib/clang/libllvm (all) >> =3D=3D=3D> lib/clang/libclang (all) >> =3D=3D=3D> lib/clang/headers (all) >> =3D=3D=3D> lib/clang/libllvm (install) >> =3D=3D=3D> lib/clang/libclang (install) >> =3D=3D=3D> lib/clang/headers (install) >> sh /usr/home/hiroki/freebsd/tools/install.sh=C2=A0 -C -o root -g wheel -= m 444=C2=A0=20 > /usr/h >> ome/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/__clang_cuda_bui= ltin_var >> s.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/__clang_cud= a_c >> math.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/__clang_cud >> a_complex_builtins.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Heade >> rs/__clang_cuda_device_functions.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/c >> lang/lib/Headers/__clang_cuda_intrinsics.h=20 > /usr/home/hiroki/freebsd/contrib/llvm >> /tools/clang/lib/Headers/__clang_cuda_libdevice_declares.h=20 > /usr/home/hiroki/free >> bsd/contrib/llvm/tools/clang/lib/Headers/__clang_cuda_math_forward_decla= res.h=20 > /u >> sr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/__clang_cuda= _runtime >> _wrapper.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/__stdde >> f_max_align_t.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/__ >> wmmintrin_aes.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/__ >> wmmintrin_pclmul.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers >> /adxintrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/altiv >> ec.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/ammintrin.h= / >> usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/arm64intr.h= =20 > /usr/ho >> me/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/arm_acle.h=20 > /usr/home/hiro >> ki/freebsd/contrib/llvm/tools/clang/lib/Headers/armintr.h=20 > /usr/home/hiroki/freeb >> sd/contrib/llvm/tools/clang/lib/Headers/avx2intrin.h=20 > /usr/home/hiroki/freebsd/co >> ntrib/llvm/tools/clang/lib/Headers/avx512bitalgintrin.h=20 > /usr/home/hiroki/freebsd >> /contrib/llvm/tools/clang/lib/Headers/avx512bwintrin.h=20 > /usr/home/hiroki/freebsd/ >> contrib/llvm/tools/clang/lib/Headers/avx512cdintrin.h=20 > /usr/home/hiroki/freebsd/c >> ontrib/llvm/tools/clang/lib/Headers/avx512dqintrin.h=20 > /usr/home/hiroki/freebsd/co >> ntrib/llvm/tools/clang/lib/Headers/avx512erintrin.h=20 > /usr/home/hiroki/freebsd/con >> trib/llvm/tools/clang/lib/Headers/avx512fintrin.h=20 > /usr/home/hiroki/freebsd/contr >> ib/llvm/tools/clang/lib/Headers/avx512ifmaintrin.h=20 > /usr/home/hiroki/freebsd/cont >> rib/llvm/tools/clang/lib/Headers/avx512ifmavlintrin.h=20 > /usr/home/hiroki/freebsd/c >> ontrib/llvm/tools/clang/lib/Headers/avx512pfintrin.h=20 > /usr/home/hiroki/freebsd/co >> ntrib/llvm/tools/clang/lib/Headers/avx512vbmi2intrin.h=20 > /usr/home/hiroki/freebsd/ >> contrib/llvm/tools/clang/lib/Headers/avx512vbmiintrin.h=20 > /usr/home/hiroki/freebsd >> /contrib/llvm/tools/clang/lib/Headers/avx512vbmivlintrin.h=20 > /usr/home/hiroki/free >> bsd/contrib/llvm/tools/clang/lib/Headers/avx512vlbitalgintrin.h=20 > /usr/home/hiroki >> /freebsd/contrib/llvm/tools/clang/lib/Headers/avx512vlbwintrin.h=20 > /usr/home/hirok >> i/freebsd/contrib/llvm/tools/clang/lib/Headers/avx512vlcdintrin.h=20 > /usr/home/hiro >> ki/freebsd/contrib/llvm/tools/clang/lib/Headers/avx512vldqintrin.h=20 > /usr/home/hir >> oki/freebsd/contrib/llvm/tools/clang/lib/Headers/avx512vlintrin.h=20 > /usr/home/hiro >> ki/freebsd/contrib/llvm/tools/clang/lib/Headers/avx512vlvbmi2intrin.h=20 > /usr/home/ >> hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/avx512vlvnniintrin.h= =20 > /usr/ho >> me/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/avx512vnniintrin.= h=20 > /usr/h >> ome/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/avx512vpopcntdqi= ntrin.h=20 >=20 >> /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/avx512vpop= cntdqvli >> ntrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/avxintrin. >> h /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/bmi2intr= in.h=20 > /us >> r/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/bmiintrin.h= =20 > /usr/home >> /hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/cetintrin.h=20 > /usr/home/hirok >> i/freebsd/contrib/llvm/tools/clang/lib/Headers/cldemoteintrin.h=20 > /usr/home/hiroki >> /freebsd/contrib/llvm/tools/clang/lib/Headers/clflushoptintrin.h=20 > /usr/home/hirok >> i/freebsd/contrib/llvm/tools/clang/lib/Headers/clwbintrin.h=20 > /usr/home/hiroki/fre >> ebsd/contrib/llvm/tools/clang/lib/Headers/clzerointrin.h=20 > /usr/home/hiroki/freebs >> d/contrib/llvm/tools/clang/lib/Headers/cpuid.h=20 > /usr/home/hiroki/freebsd/contrib/ >> llvm/tools/clang/lib/Headers/emmintrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/t >> ools/clang/lib/Headers/f16cintrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/ >> clang/lib/Headers/fma4intrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang >> /lib/Headers/fmaintrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/H >> eaders/fxsrintrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Header >> s/gfniintrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/htm >> intrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/htmxlintr >> in.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/ia32intrin.= h=20 >> /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/immintrin.= h=20 > /usr/h >> ome/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/invpcidintrin.h= =20 > /usr/hom >> e/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/lwpintrin.h=20 > /usr/home/hiro >> ki/freebsd/contrib/llvm/tools/clang/lib/Headers/lzcntintrin.h=20 > /usr/home/hiroki/f >> reebsd/contrib/llvm/tools/clang/lib/Headers/mm3dnow.h=20 > /usr/home/hiroki/freebsd/c >> ontrib/llvm/tools/clang/lib/Headers/mm_malloc.h=20 > /usr/home/hiroki/freebsd/contrib >> /llvm/tools/clang/lib/Headers/mmintrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/t >> ools/clang/lib/Headers/module.modulemap=20 > /usr/home/hiroki/freebsd/contrib/llvm/to >> ols/clang/lib/Headers/movdirintrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools >> /clang/lib/Headers/msa.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/H >> eaders/mwaitxintrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Head >> ers/nmmintrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/op >> encl-c.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/pconfigin >> trin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/pkuintrin.h >> =C2=A0/usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/pmmi= ntrin.h=20 > /usr/ >> home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/popcntintrin.h= =20 > /usr/hom >> e/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/prfchwintrin.h=20 > /usr/home/h >> iroki/freebsd/contrib/llvm/tools/clang/lib/Headers/ptwriteintrin.h=20 > /usr/home/hir >> oki/freebsd/contrib/llvm/tools/clang/lib/Headers/rdseedintrin.h=20 > /usr/home/hiroki >> /freebsd/contrib/llvm/tools/clang/lib/Headers/rtmintrin.h=20 > /usr/home/hiroki/freeb >> sd/contrib/llvm/tools/clang/lib/Headers/s390intrin.h=20 > /usr/home/hiroki/freebsd/co >> ntrib/llvm/tools/clang/lib/Headers/sgxintrin.h=20 > /usr/home/hiroki/freebsd/contrib/ >> llvm/tools/clang/lib/Headers/shaintrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/t >> ools/clang/lib/Headers/smmintrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/c >> lang/lib/Headers/tbmintrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/l >> ib/Headers/tmmintrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Hea >> ders/vadefs.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/vaes >> intrin.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/vecintrin >> .h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/vpclmulqdqi= ntri >> n.h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/waitpkgintr= in. >> h=20 > /usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/wbnoinvdint= rin.h >> =C2=A0/usr/home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/wmmi= ntrin.h=20 > /usr/ >> home/hiroki/freebsd/contrib/llvm/tools/clang/lib/Headers/x86intrin.h=20 > /usr/home/h >> iroki/freebsd/contrib/llvm/tools/clang/lib/Headers/xmmintrin.h=20 > /usr/home/hiroki/ >> freebsd/contrib/llvm/tools/clang/lib/Headers/xopintrin.h=20 > /usr/home/hiroki/freebs >> d/contrib/llvm/tools/clang/lib/Headers/xsavecintrin.h=20 > /usr/home/hiroki/freebsd/c >> ontrib/llvm/tools/clang/lib/Headers/xsaveintrin.h=20 > /usr/home/hiroki/freebsd/contr >> ib/llvm/tools/clang/lib/Headers/xsaveoptintrin.h=20 > /usr/home/hiroki/freebsd/contri >> b/llvm/tools/clang/lib/Headers/xsavesintrin.h=20 > /usr/home/hiroki/freebsd/contrib/l >> lvm/tools/clang/lib/Headers/xtestintrin.h arm_fp16.h arm_neon.h=20 > /usr/home/hiroki >> /zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/arm.arm/tmp/us= r/lib/cl >> ang/7.0.1/include/ >> install: target directory=20 > `/usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr >> /home/hiroki/freebsd/arm.arm/tmp/usr/lib/clang/7.0.1/include/' does not= =20 > exist >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to=20 > "freebsd-arm-unsubscribe@freebsd.org" >>=20 >>=20 >> =C2=A0 >=20 From owner-freebsd-arm@freebsd.org Fri Mar 22 11:18:47 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 4CF491540ADF for ; Fri, 22 Mar 2019 11:18:47 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh605-vm3.bullet.mail.ssk.yahoo.co.jp (nh605-vm3.bullet.mail.ssk.yahoo.co.jp [182.22.90.76]) by mx1.freebsd.org (Postfix) with SMTP id 3F0F775930 for ; Fri, 22 Mar 2019 11:18:43 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [182.22.66.105] by nh605.bullet.mail.ssk.yahoo.co.jp with NNFMP; 22 Mar 2019 11:16:06 -0000 Received: from [182.22.91.204] by t603.bullet.mail.ssk.yahoo.co.jp with NNFMP; 22 Mar 2019 11:16:06 -0000 Received: from [127.0.0.1] by omp607.mail.ssk.yahoo.co.jp with NNFMP; 22 Mar 2019 11:16:06 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 563532.740.bm@omp607.mail.ssk.yahoo.co.jp X-YMail-OSG: UGHwGBAVM1mya19T6vN5lL9lcugsedonVYB6fE3q4ph3Z7TdPtezCf9WZKNl3C0 k_T41VD9HgKh0X7KFj1YvWxFvCPmD0eII075k62cbKVKjLJwDrMclOAssCiZl9dRFzxzn_BYau7E TR31Zl_0eXIci5OUgev67E7JfiC1wlhiIEiyRNFUyTNoE4cerDbSKrx42U4NMC3SRErvtup4ZYsy S2Zo4SbggaIYQpAxEKdOpu4pyJsMB946VJRlSv7qLq2sXlprAH3B7Eq_Wd3Oyy8u8A4a8JfAAP9E 3ADnwqceodfwTGypQpLyaa1_SkDvbzPIhKOAAZCbXKKAZqt29JnFZXGRBsNCPfuaheOtJfCmNKYn 6c1noXd1eGt_pJ_haQpWn.T.U_1DmKJ9m07P50TVIPu7tnyX7Jleao1IVETqCUf3lx1sNUrmVoNl VmrTErKjqksILEbsC8mAD8ZsdEN6NFq9SIygL5Zdc1_ugXWVVcMxCM00I00C.Jta2ALALFc7asnz ZQZDhUwLKAX2wKdvYNmRIbdCs64KW4_qKLKWBcPnAlyvX31eMdXz295kYt7VgFq0osYwxIyXChb0 sMutthVwckP7Lz.Ia8tRV_xBpsyNu104DvsHiJPUpZIieqj10q.xK07oAJVJm Received: from jws700007.mail.kks.yahoo.co.jp by sendmailws517.mail.kks.yahoo.co.jp; Fri, 22 Mar 2019 20:16:05 +0000; 1553253365.900 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1553253366; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:To:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; bh=uctrihKYqa0hyQms2f0q61IBGA6xuG85KG0aYOH9qSw=; b=Lj5OKFEB86F6V4PoWC4pvwOYQbEl/fwKX1s80HUS0x1cnzCeKphhhUuVPoTA1s5Z cwhH7ANIjEQfIxn2Rd2IwJMpXNEFB0j5HjeEa5ACIlHJTr7l7HuGjCp+W/4/D4PRODf xH96JaMWa7EL+mw0gSlxq6tH5bd4PNhHUi42Vsek= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:Message-ID:In-Reply-To:References:MIME-Version:Content-Type:Content-Transfer-Encoding; b=oT2T8z56+JIzFMEcvuS1MC6c223HONoMWKAvlCwZzMLkZL1n3ITZsaVk5Vwtsaql e6g11eJBAjn5ZhLgbyPM+6zWHDav744DH/SC4HaiN3HF8GjPatfrkKptPnTGxhbDpXg qa1pruBuaLZMcqbkLngVN6KG0CGfS4DySoF5XUb4=; Date: Fri, 22 Mar 2019 20:16:05 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki To: "freebsd-arm@freebsd.org" Message-ID: <530478235.755585.1553253365514.JavaMail.yahoo@mail.yahoo.co.jp> In-Reply-To: <1252845449.757894.1553251342413.JavaMail.yahoo@mail.yahoo.co.jp> References: <1252845449.757894.1553251342413.JavaMail.yahoo.ref@mail.yahoo.co.jp> <1252845449.757894.1553251342413.JavaMail.yahoo@mail.yahoo.co.jp> Subject: armv5t is fine MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 3F0F775930 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.co.jp header.s=yj20110701 header.b=Lj5OKFEB; dmarc=pass (policy=none) header.from=yahoo.co.jp; spf=pass (mx1.freebsd.org: domain of yamori813@yahoo.co.jp designates 182.22.90.76 as permitted sender) smtp.mailfrom=yamori813@yahoo.co.jp X-Spamd-Result: default: False [0.87 / 15.00]; HAS_REPLYTO(0.00)[yamori813@yahoo.co.jp]; R_SPF_ALLOW(-0.20)[+ip4:182.22.90.0/23]; FREEMAIL_FROM(0.00)[yahoo.co.jp]; DKIM_TRACE(0.00)[yahoo.co.jp:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.co.jp,none]; MX_GOOD(-0.01)[cached: mx3.mail.yahoo.co.jp]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.co.jp]; ASN(0.00)[asn:23816, ipnet:182.22.0.0/17, country:JP]; IP_SCORE(0.93)[ipnet: 182.22.0.0/17(2.63), asn: 23816(2.10), country: JP(-0.07)]; DWL_DNSWL_NONE(0.00)[yahoo.co.jp.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.co.jp:s=yj20110701]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[yahoo.co.jp]; NEURAL_HAM_LONG(-0.55)[-0.554,0]; NEURAL_SPAM_MEDIUM(0.47)[0.475,0]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_SHORT(0.93)[0.933,0]; RCVD_IN_DNSWL_NONE(0.00)[76.90.22.182.list.dnswl.org : 127.0.5.0]; TO_DN_EQ_ADDR_ALL(0.00)[] 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: Fri, 22 Mar 2019 11:18:47 -0000 Hi armv5t is work fine by clang 8.0.0. https://dmesgd.nycbug.org/index.cgi?do=view&id=4830 Thanks Hiroki Mori From owner-freebsd-arm@freebsd.org Sat Mar 23 18:02:26 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 BB42A1558056 for ; Sat, 23 Mar 2019 18:02:26 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh605-vm13.bullet.mail.ssk.yahoo.co.jp (nh605-vm13.bullet.mail.ssk.yahoo.co.jp [182.22.90.86]) by mx1.freebsd.org (Postfix) with SMTP id 570CC74511 for ; Sat, 23 Mar 2019 18:02:14 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [182.22.66.104] by nh605.bullet.mail.ssk.yahoo.co.jp with NNFMP; 23 Mar 2019 17:59:53 -0000 Received: from [182.22.91.206] by t602.bullet.mail.ssk.yahoo.co.jp with NNFMP; 23 Mar 2019 17:59:52 -0000 Received: from [127.0.0.1] by omp609.mail.ssk.yahoo.co.jp with NNFMP; 23 Mar 2019 17:59:52 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 976624.44184.bm@omp609.mail.ssk.yahoo.co.jp X-YMail-OSG: xXVIVR8VM1lQ3Mmh0np3.yQW_KG4AIUR5QHNIeW05D5pVTvJ4RzprWUzXjVj3pM zcJNuU1MDFAkUJ99sAUCp2tovepNZXBdPjCrTP_LE4PLl_ze1MC3.24r3tY89H_CN_mOCfgtb_5p 6mSQixU5F3Fc_Omi8q8CNCXvr4EnnYHL3P5Es4gtQ18PjrEOmC_TvjvUYS0p1gamBQF72AYyDhY8 A4q9DhptC14IDVlLnPd9KqAeC8Z8lXejz4upotZrqmKQ.t2mLwTNgSqpucmOcvLEhKNBB.wMftk8 3YDMetu9Dhgjpe6c5NTVbcPvaq5axexLf0PJKQ8b3K6P8MDN_vUp6TKjv63MyKv563f88OPe.ec6 GXMQLKQlIzb.uNNtIfJjrhbADwmPYHG3qz8rkFatRPz8wxvpl2EUbIOkXjywRgG.czky.PdYyBdt y8JHY1lY_QGWeq7ghr1m7HIlNhMAfVLoW4rNcIuee7Ds.xkTueHmNoxYk_FIQCZeWYO_t5yDsgqR 5_28weOIG8bi22u7Vu6USHX.3Dbl6zaJJ_uCCGNZQEZK36qT2ZArjrOdyiVt_8DnAAA8No7RwQoG jLtGalkhEvjd.PR9fdYs3ktLBYoJZD_nXZciwRQ-- Received: from jws701105.mail.ssk.yahoo.co.jp by sendmailws609.mail.ssk.yahoo.co.jp; Sun, 24 Mar 2019 02:59:52 +0000; 1553363992.470 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1553363992; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:To:Cc:Message-ID:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:References; bh=etcCVS5Kl6UYU+VLU4MQ0xKims5uvNHkmBxJaswdxqE=; b=dGXNVhCSoYE4q5hVvjFUD7/WFfOF6VLOVjgIcgELwHayo/i1g7N3FVWWY7pKmz9k GDSu6bbNFX46yjDK69Tpt1o3KDW53GuDXp0L5CZnAZfbEf13glbeVoliBVSIpApxt9K OhjT1/juQ1ji7BNIOlWnYOh0BrjsTk9vDZGeJwlM= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:Cc:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:References; b=qoSkdK7cmOsHzy2alTrBkpmzxSe3sMK6rHX7Ga4sDalaCkDPgPLCH+/dbrweOz4J 637mCThVYp9DDXVx9Piuy/4jWwp7CaXexIi6dLljy+z4wYvi2Audg0ypUA06WM4vU/m OgbHCCp0sq17u1CgRSP+M84PF8ztUtqxQKfovG68=; Date: Sun, 24 Mar 2019 02:59:51 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki To: "imp@bsdimp.com" Cc: "freebsd-arm@freebsd.org" Message-ID: <188467496.378105.1553363991969.JavaMail.yahoo@mail.yahoo.co.jp> Subject: Ralink armv5t MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit References: <188467496.378105.1553363991969.JavaMail.yahoo.ref@mail.yahoo.co.jp> X-Rspamd-Queue-Id: 570CC74511 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.co.jp header.s=yj20110701 header.b=dGXNVhCS; dmarc=pass (policy=none) header.from=yahoo.co.jp; spf=pass (mx1.freebsd.org: domain of yamori813@yahoo.co.jp designates 182.22.90.86 as permitted sender) smtp.mailfrom=yamori813@yahoo.co.jp X-Spamd-Result: default: False [1.76 / 15.00]; HAS_REPLYTO(0.00)[yamori813@yahoo.co.jp]; R_SPF_ALLOW(-0.20)[+ip4:182.22.90.0/23]; FREEMAIL_FROM(0.00)[yahoo.co.jp]; DKIM_TRACE(0.00)[yahoo.co.jp:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.co.jp,none]; RCPT_COUNT_TWO(0.00)[2]; MX_GOOD(-0.01)[mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo.co.jp, mx2.mail.yahoo.co.jp, mx3.mail.yahoo.co.jp, mx1.mail.yahoo.co.jp, mx5.mail.yahoo. co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.co.jp]; ASN(0.00)[asn:23816, ipnet:182.22.0.0/17, country:JP]; IP_SCORE(0.92)[ipnet: 182.22.0.0/17(2.61), asn: 23816(2.09), country: JP(-0.07)]; DWL_DNSWL_NONE(0.00)[yahoo.co.jp.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.co.jp:s=yj20110701]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; NEURAL_SPAM_SHORT(0.88)[0.877,0]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[yahoo.co.jp]; NEURAL_SPAM_MEDIUM(0.82)[0.823,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.05)[0.047,0]; RCVD_IN_DNSWL_NONE(0.00)[86.90.22.182.list.dnswl.org : 127.0.5.0]; TO_DN_EQ_ADDR_ALL(0.00)[] 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: Sat, 23 Mar 2019 18:02:27 -0000 Hi I give WZR2-G300N to manu yesterday. Also I give WZR2-G300N to hrs and mizhka. Regards Hiroki Mori From owner-freebsd-arm@freebsd.org Sat Mar 23 18:26:52 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 4FF7A1558BE0 for ; Sat, 23 Mar 2019 18:26:52 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 101F37554D for ; Sat, 23 Mar 2019 18:26:50 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x72c.google.com with SMTP id z13so3131984qki.2 for ; Sat, 23 Mar 2019 11:26:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MBD1AlAiC7f/uxAFJWShF/Z+9ewQ32UsoV7/gNsIvdY=; b=ouE15a/iqEW2VpzcsvOAJ1ud81qBJQe4lO+CRSlN+AQeISvdooBSuXZYN0kqXBTxQf 3LwVUpfRu1ECTu1TV6POeq3uzxej+pVJ0B5D1l47uri9q2p2fv2miLbL8alETNaTgOzr mFKm8k4JsTqZlh9S9+Mvj1Z1iuoxZdPQwCXA3cwDbQT/3zdY79zUhffPEFHyUVAQudHE WseDUlpYqlgI5fx/E5qxO2hJmtQfsGZ1C4BCxDsS2Z36tZhzfeuVuiJU+BAP9b9npx+x 6jiV01V+GqxVqKD9IqSHYZzlcTqroZqm3XGKBIKy2YwD+k+RbcD9A94Ib+qaGCUyxqb8 m5tQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MBD1AlAiC7f/uxAFJWShF/Z+9ewQ32UsoV7/gNsIvdY=; b=HwNVePBYhZ8Ra395/0qTV1abAUG9YyrUM07CFw2pL6unB49WDEEjtuBrGAlZ2v2cck 9c+TeuNejhPsGd34HhfR9A9Ah4xo32mmm8ZUpj8MG4AbObsGJ41dZUylTOPOU6Stk1N/ 3IT3nvK9XphAIKoImjAkFmd9uMvQqrMzIiEl/c9zhyIIJivpDCYHPzF7PKM00azzhwke NAoU6PgANizM/zSDwmhUCakE44wOsQqXv842fsSKwhb4WXE6O0nX1KtCEhsRpRS0lkMd l9kSTMml+mpPyXkCFJ+hBHtX3RrHCWlsDG7XDB+Mr7wBfvwLCycQDdcVn9XEn+W2pr/X 6Owg== X-Gm-Message-State: APjAAAVzcRJCAP/DsfBABnU1oDKSgYJVz65rhljDY6E9rhuU2FF3xrR6 SSzWvrisfWyZMCgbw+/OT+1W3M53s1gS1L8wXwfuGSey X-Google-Smtp-Source: APXvYqwRdluBs1gbOxJroLtgxp6p92hGIICmEMgeNOITEo3ymyAjP0OWC6UWlJuEFvKFow6ilSDAgme6uoqK8NvCh/A= X-Received: by 2002:a37:bce:: with SMTP id 197mr13586821qkl.46.1553365610247; Sat, 23 Mar 2019 11:26:50 -0700 (PDT) MIME-Version: 1.0 References: <188467496.378105.1553363991969.JavaMail.yahoo.ref@mail.yahoo.co.jp> <188467496.378105.1553363991969.JavaMail.yahoo@mail.yahoo.co.jp> In-Reply-To: <188467496.378105.1553363991969.JavaMail.yahoo@mail.yahoo.co.jp> From: Warner Losh Date: Sat, 23 Mar 2019 12:26:39 -0600 Message-ID: Subject: Re: Ralink armv5t To: Mori Hiroki Cc: "freebsd-arm@freebsd.org" X-Rspamd-Queue-Id: 101F37554D X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=ouE15a/i X-Spamd-Result: default: False [-5.73 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.87)[-0.871,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[ALT1.aspmx.l.google.com,aspmx.l.google.com,ALT2.aspmx.l.google.com]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[c.2.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; FREEMAIL_TO(0.00)[yahoo.co.jp]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; IP_SCORE(-2.85)[ip: (-9.19), ipnet: 2607:f8b0::/32(-2.85), asn: 15169(-2.13), country: US(-0.07)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Sat, 23 Mar 2019 18:26:52 -0000 I'd love to get my ralink board going... I still haven't been able to get it booting all the way... Do I need to build with ZRouter? Or can I do that with just a plain FreeBSD tree? I've been doing the latter, but I see from your dmesg postings that maybe I should consider the former.... Warner On Sat, Mar 23, 2019 at 11:59 AM Mori Hiroki wrote: > Hi > > I give WZR2-G300N to manu yesterday. > > > Also I give WZR2-G300N to hrs and mizhka. > > Regards > > Hiroki Mori > >