From owner-freebsd-arm@freebsd.org Mon Nov 30 05:30:42 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 36ADD470189 for ; Mon, 30 Nov 2020 05:30:42 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ckv2p11kmz4bFg; Mon, 30 Nov 2020 05:30:42 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from weatherwax.trouble.is (weatherwax.trouble.is [46.235.227.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "weatherwax.trouble.is", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: philip/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id F35162A24E; Mon, 30 Nov 2020 05:30:41 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from rincewind.trouble.is (rincewind.trouble.is [95.216.22.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "rincewind.trouble.is", Issuer "Let's Encrypt Authority X3" (verified OK)) by weatherwax.trouble.is (Postfix) with ESMTPS id 4Ckv2n0wYcz11FG; Mon, 30 Nov 2020 05:30:41 +0000 (UTC) Received: by rincewind.trouble.is (Postfix, authenticated sender philip) id 4Ckv2k4Jjgz5q3C; Mon, 30 Nov 2020 05:30:38 +0000 (UTC) From: "Philip Paeps" To: "Ronald Klop" Cc: "Steve Wills" , "Kurt Jaeger" , freebsd-arm@freebsd.org, "Cluster Administrators" Subject: Re: aarch64 pkg build seems broken/hanging Date: Mon, 30 Nov 2020 13:30:33 +0800 X-Clacks-Overhead: GNU Terry Pratchett X-Mailer: MailMate (1.14r5740) Message-ID: <4F2C84A9-72EF-4041-B28B-CFDF5A10DF80@freebsd.org> In-Reply-To: References: <735767609.10.1597159067683@localhost> <504493339.1.1597829845980@localhost> <1268679721.21.1598955250524@localhost> <2128344036.116.1599572445531@localhost> <93ab93ce-8887-315e-c775-0929c716032a@FreeBSD.org> <20200909142039.GK53210@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2020 05:30:42 -0000 On 2020-11-01 19:28:24 (+0800), Ronald Klop wrote: > On Wed, 09 Sep 2020 16:20:39 +0200, Kurt Jaeger wrote: >>> Sorry, but this is not a portmgr@ issue, this is a clusteradm@ >>> issue. >> >> philip@ (with clusteradm@ hat) checked the issue and explained the >> cause of the problem: >> >> The thunderx hardware currently in use in the cluster is a very early >> version and has stability issues. A replacement is @work. > > I don't want to be pushing the issue, but do you have some information > about the progress of the aarch64 hardware issues? The new aarch64 systems arrived at the data centre on Friday (local time) and were installed and configured in the cluster yesterday (my time). They'll start running builds soon. Packages will start appearing on the mirrors shortly after. Steady progress... Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises From owner-freebsd-arm@freebsd.org Mon Nov 30 15:41:07 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0AA5247FF46 for ; Mon, 30 Nov 2020 15:41:07 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Cl8b66MJpz3p4q; Mon, 30 Nov 2020 15:41:06 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Date: Mon, 30 Nov 2020 16:41:02 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1606750862; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=c8e46RvuuZ+WKcm4ViYaDXf/vT99SXbQYzOK1h6CZ0g=; b=Bu3+G/xsMI0X7ueopTLKiBNmebnr6xvDpzjC20qFEMGW5qU/uRbFUywTBy8SrzUmked0Rj df6ARpxTzRETf1SJELAF4NG9gCd8b82rrHxEFR1r1JhFLlpmXT1AAcD8Kuv65Z4W6biJI4 jfoq211kwkpj/qKPV86M+AXAOnotPd1MGKHn2DVy2iael4IfETvD6HUfLh8JSgB6asKxqz v4p1+yCM4OSV++5hL3V6dL/MU9XeKBykI55F4LTWFZ988Kebd4cMY2ve2ZGM3Kbd3ltWhH 6ItTrcoXti+etf7+NkgwcNq8cjiekWsY+kMQ8C4Jy0rtZk2OODODfcADuGKlqw== From: Ronald Klop To: Philip Paeps Cc: Kurt Jaeger , Cluster Administrators , Steve Wills , freebsd-arm@freebsd.org Message-ID: <1846211902.1.1606750862152@localhost> In-Reply-To: <4F2C84A9-72EF-4041-B28B-CFDF5A10DF80@freebsd.org> References: <735767609.10.1597159067683@localhost> <504493339.1.1597829845980@localhost> <1268679721.21.1598955250524@localhost> <2128344036.116.1599572445531@localhost> <93ab93ce-8887-315e-c775-0929c716032a@FreeBSD.org> <20200909142039.GK53210@home.opsec.eu> <4F2C84A9-72EF-4041-B28B-CFDF5A10DF80@freebsd.org> Subject: Re: aarch64 pkg build seems broken/hanging MIME-Version: 1.0 X-Mailer: Realworks (536.27.b17f9013b53) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4Cl8b66MJpz3p4q X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2020 15:41:07 -0000 Van: Philip Paeps Datum: maandag, 30 november 2020 06:30 Aan: Ronald Klop CC: Steve Wills , Kurt Jaeger , freebsd-arm@freebsd.org, Cluster Administrators Onderwerp: Re: aarch64 pkg build seems broken/hanging > > On 2020-11-01 19:28:24 (+0800), Ronald Klop wrote: > > On Wed, 09 Sep 2020 16:20:39 +0200, Kurt Jaeger wrote: > >>> Sorry, but this is not a portmgr@ issue, this is a clusteradm@ >>> issue. > >> > >> philip@ (with clusteradm@ hat) checked the issue and explained the > >> cause of the problem: > >> > >> The thunderx hardware currently in use in the cluster is a very early > >> version and has stability issues. A replacement is @work. > > > > I don't want to be pushing the issue, but do you have some information > about the progress of the aarch64 hardware issues? > > The new aarch64 systems arrived at the data centre on Friday (local time) and were installed and configured in the cluster yesterday (my time). They'll start running builds soon. Packages will start appearing on the mirrors shortly after. > > Steady progress... > > Philip > > -- > Philip Paeps > Senior Reality Engineer > Alternative Enterprises > > > Great news! Thanks for the update. Do you have some nice details about the new systems? Just for my curiosity. Probably a bit better than the RPI4 I installed to build my packages in the meantime. :-) Regards, Ronald. From owner-freebsd-arm@freebsd.org Mon Nov 30 21:52:23 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D33AD4A95D3 for ; Mon, 30 Nov 2020 21:52:23 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound5a.ore.mailhop.org (outbound5a.ore.mailhop.org [44.233.67.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4ClJqW2fDTz4m20 for ; Mon, 30 Nov 2020 21:52:23 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1606773142; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=PcAt5zLs1Xjd7oMkPlyvZAGGKj/9v08Fq8tDEsN2NYlOAY4C72vBshZudvcklj0EOfWCX4dKXTWAJ b4e4RVYJtoK6xBY4c21h6QTP4f/XhjhySuUGVxONJKowETkSXGVeP601yNy7oUYj3yn231Crwx1aM9 D9F/3h0d3h2ALwog0qh0aN2t2rgXQLKDVjndAWOeyl+VJPbysGEyrDqSOLd4oS+A4G6A+vBcF8j88X DvIARNpy5RoEfE2gfRktnPntqekathv8wZYftXVlt/X5FDhdDux/yiP9VqFn8f4qPxxqm5/aV+sPQK cNRjqUSyv2+esaanf7rwKL4B7qlDB2A== 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=BlqKb8oQ8YrPoiv/kE5ClHZeflc9aSOKPEVyTg4YU+U=; b=tVAxyMp4bW3II0SOOXDcUROWf/1mH67YkqoXEJ0NYKbc0UAnTv74C+norF+V9b068hxd6rj2mp6U+ 7xiCHw0MMUlxTb6Lz7/Bcu4e7rv2rQDmrvGqm93tT3oxzftKq5icYCNeMCAPY+oCOo5qa53t5GUuME dSgBgzELtj9kK9T/5QQ/kyfzE8JkL3VIwjCkM63oQaS8rRZMu1zFcAT+X47NAGfcvtMTvUgFqkGrGJ n7htC3e3OUluq2SeBjTI3myfwABbsEqW7RDBcoaCyeiORqMwWwRhwq3LlWdTsmGFezyI4CrvuhBeW3 F3IeXszmVr1HOJUascYVDyB9Z2QL9ZA== 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=BlqKb8oQ8YrPoiv/kE5ClHZeflc9aSOKPEVyTg4YU+U=; b=KVctnk/fOOBWL4V85ykPC15d/LiF3HnRRrfTg0eMNUzUn/8wMH5u23Pev625CmlN1oxwr0Gl6Ui14 72fzOE806MVZJdmgK2ry86Q8cq3FVUF/dcQDx0huBoTFPcj26bPHBJ5XVPv1bumECB3HgLNb808OLv bD1osASSzg6p8IEOEhKhA5rtEH4IwhhzqKjWuLEk3oVXdpbVImMwfnPxBvJV5Q5Nr+Y1eWY+2RFgra VmKoUtCNPlHvu9xBiofxe7ppTgrGMMeaja4VzsFoyAcBovFzm2WTZVnELR6QVgebT6+kqXtoTNweyJ E/9e8XkBWQcfIPNGcI0L/kt5WU3kojg== X-MHO-RoutePath: aGlwcGll X-MHO-User: 51549ff0-3356-11eb-8b39-614106969e8d 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 (c-67-177-211-60.hsd1.co.comcast.net [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 51549ff0-3356-11eb-8b39-614106969e8d; Mon, 30 Nov 2020 21:52:20 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id 0AULqIwj091917; Mon, 30 Nov 2020 14:52:18 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: User Space GPIO Interrupt programming - GSoC-2018 From: Ian Lepore To: "Dr. Rolf Jansen" Cc: freebsd-arm@freebsd.org Date: Mon, 30 Nov 2020 14:52:18 -0700 In-Reply-To: References: <2B01780F-D367-48A3-A827-B479030A496D@obsigna.com> <8d806302-479c-ca34-3fdb-96d27f40e212@viruzzz.org> <8655AF30-273B-48E7-98CD-007AA1D265F5@obsigna.com> <54ffe2d2-01a2-8b43-94fa-aee4a3f89861@viruzzz.org> <08649892ca2ab434c261d36e0e13ba051086de6f.camel@freebsd.org> <1e6993d43d22d6ce1aa2860a61745356688d1e53.camel@freebsd.org> Content-Type: text/plain; charset="ASCII" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4ClJqW2fDTz4m20 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:16509, ipnet:44.224.0.0/11, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2020 21:52:23 -0000 On Fri, 2020-11-27 at 19:45 -0300, Dr. Rolf Jansen wrote: > Am 27.11.2020 um 15:04 schrieb Ian Lepore : > > On Fri, 2020-11-27 at 10:16 -0700, Ian Lepore wrote: > > > On Fri, 2020-11-27 at 14:28 +0300, Vladimir Goncharov wrote: > > > > Here it is. > > > > There is struct gpioc_event with pin number and bintime which > > > > is send > > > > to userspace. > > > > > > > > Also I'm thinking about to implementation notofication without > > > > extra > > > > reading from socket via struct kevent's extra fields > > > > (fflags/ext[4]), > > > > looks like it is possible. > > > > > > > > > > Please don't top-post on freebsd mailing lists. > > > > > > I think we need a way for the app to choose whether it wants > > > simple > > > reporting of pin number (like the original code) perhaps along > > > with a > > > count, versus requesting detailed per-event data. I'm going to > > > propose > > > something more detailed about this as soon as I get my thoughts > > > all > > > organized. I also want to get the original code and the locking > > > fixes > > > I've done to it into a phab review for people to start looking at > > > before starting to do new major changes to it. > > > > > > Allocating memory in the interrupt handler isn't a good idea, it > > > will > > > just increase latency on processing other pin interrupts and lead > > > to > > > inaccurate timestamps. IMO, it would be better to allocate a > > > fixed > > > array of events; when the app requests detailed event reporting > > > it can > > > request the number of stored events it wants handled and we could > > > allocate all at once based on that. > > > > > > > The gsoc2018 code, with locking and style(9) fixes, is now at: > > > > https://reviews.freebsd.org/D27398 > > I got it working, and as expected, by your comments the level > interrupt mode has been disabled. I am OK with this. Later, I will > add more comments on this in my response to you other e-mail. > > Best regards > > Rolf I've just updated the phabricator review with new code. This adds the detailed versus summary reporting. I decided the detailed reporting should still be the default like it was before, but now it can handle many events between calls to read(), unlike the old code that only stored one pin change event between calls. Now it uses a circular buffer, and there's a new ioctl function for increasing the size of the buffer (or switching to summary reporting mode). I incorporated Christian's test program into the phab review, and added some enhancements to it. It shows how to read and interpret the new detailed and summary structures, how to convert the monotonic clock event timestaps to UTC if needed (*), and how to handle getting multiple event notifications with each read() call (by passing a big buffer and parsing the structs from it after the call). https://reviews.freebsd.org/D27398 (*) The conversion of monotonic to utc time doesn't attempt to deal with the system clock being stepped between the time an event was recorded and when it is printed. In the real world, system time gets stepped when the system boots, not at random while apps are running. -- Ian From owner-freebsd-arm@freebsd.org Mon Nov 30 22:20:38 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6E4AA4AA0AA for ; Mon, 30 Nov 2020 22:20:38 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ClKS62BDtz4p3q; Mon, 30 Nov 2020 22:20:38 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from weatherwax.trouble.is (weatherwax.trouble.is [IPv6:2a00:1098:82:3a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "weatherwax.trouble.is", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: philip/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 278022475; Mon, 30 Nov 2020 22:20:38 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from rincewind.trouble.is (rincewind.trouble.is [95.216.22.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "rincewind.trouble.is", Issuer "Let's Encrypt Authority X3" (verified OK)) by weatherwax.trouble.is (Postfix) with ESMTPS id 4ClKS35GtSz11bL; Mon, 30 Nov 2020 22:20:35 +0000 (UTC) Received: by rincewind.trouble.is (Postfix, authenticated sender philip) id 4ClKS107nkz5qFX; Mon, 30 Nov 2020 22:20:32 +0000 (UTC) From: "Philip Paeps" To: "Ronald Klop" Cc: "Kurt Jaeger" , "Cluster Administrators" , "Steve Wills" , freebsd-arm@freebsd.org Subject: Re: aarch64 pkg build seems broken/hanging Date: Tue, 01 Dec 2020 06:20:26 +0800 X-Clacks-Overhead: GNU Terry Pratchett X-Mailer: MailMate (1.14r5742) Message-ID: <928ED594-4664-489F-B24A-2DB0A4DD7690@freebsd.org> In-Reply-To: <1846211902.1.1606750862152@localhost> References: <735767609.10.1597159067683@localhost> <504493339.1.1597829845980@localhost> <1268679721.21.1598955250524@localhost> <2128344036.116.1599572445531@localhost> <93ab93ce-8887-315e-c775-0929c716032a@FreeBSD.org> <20200909142039.GK53210@home.opsec.eu> <4F2C84A9-72EF-4041-B28B-CFDF5A10DF80@freebsd.org> <1846211902.1.1606750862152@localhost> MIME-Version: 1.0 Content-Type: text/plain; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2020 22:20:38 -0000 On 2020-11-30 23:41:02 (+0800), Ronald Klop wrote: > Philip Paeps wrote: >> The new aarch64 systems arrived at the data centre on Friday (local = >> time) and were installed and configured in the cluster yesterday (my = >> time). They'll start running builds soon. Packages will start = >> appearing on the mirrors shortly after. > > Great news! Thanks for the update. > Do you have some nice details about the new systems? Just for my = > curiosity. Probably a bit better than the RPI4 I installed to build my = > packages in the meantime. :-) The new systems are Ampere eMAG based: 32 cores, 128G memory. They're = currently set up with two spinning rust drives. We'll probably replace = those with four SSDs for better IO. Full specs here: https://amperecomputing.com/wp-content/uploads/2019/04/Lenovo_ThinkSystem= _HR330A_PB_20190409.pdf Philip -- = Philip Paeps Senior Reality Engineer Alternative Enterprises From owner-freebsd-arm@freebsd.org Mon Nov 30 22:46:45 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 06EF94AA649 for ; Mon, 30 Nov 2020 22:46:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ClL2D0Yqlz4rnp for ; Mon, 30 Nov 2020 22:46:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x82f.google.com with SMTP id z3so9538892qtw.9 for ; Mon, 30 Nov 2020 14:46:43 -0800 (PST) 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=HtwLgYowJ4ByVdUNbdKVRJ/v/p4u47Vz10fRoJhy97Q=; b=gsWe/t8msFT7U9sPB68RozcNxqTAUPLy8BSQXmfcUigOWSDIs46Kt9oN/eZFArYHFp fxBHlKdHknxaP/G3s52vVzTAWsHG9X8gCvQMHsvHLcLiDQO5WDXm1WPKfiIJnLZsb0pA xej+hbJ4vsIaqhkR4NSGn/hFCdFUaDC+J9ozvNVuHuWlPPqe1u+41dr5GU553QjwRV6J nBrqgMmGWEMvV5i6I6hT4YvVz3mo247Ll1iKGEQeJe09iL7Cv3ksKkvLXCf1s2GgmxIZ dstlnTaNcCCVN1JH9J0it7D2jLso+T/M/Qu/CjsQAXQZWWWQWl4HqzmeoT08af/JGRaM ceCg== 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=HtwLgYowJ4ByVdUNbdKVRJ/v/p4u47Vz10fRoJhy97Q=; b=acQTP8yQWB5kgupSo5wSwOa7iujuXlvpF1Z32GcxxUh6o1dl9IK4pYkJGewIzYvRml fv6iEDpG+D/vrdIX1Em9Ni53Ueohq5ZCUUAn2jUqXBJygv/7h4CVZ97eNM7ePsG29TFN edXKgbhjOMdFLzWoJorRxJPdDaEtqUb2ESiyb6xzhql82cDKznqNUyby6ksYSBrSN9i5 eZf3lHPglh3hkW0yta8bRDcseyUlYuOtFMfefptVHGtV81j1yCaeJBn+gTkfEHiwcchG 6SjPh2DLdxQJygXL2FLO1m1kM+QKYeLiY+D5rcHcJS6YGYV+Ckqi/GCTrf7etr4+AoGg aEsw== X-Gm-Message-State: AOAM531w9dN3uYFah5FBvrc0cM60Lkw1xL/hJYwKZRmDnaqAmqrgUQHB dcSE5EKA3vc5cyKQrXzWmxl4crSlrwrNkeNdugCaVg== X-Google-Smtp-Source: ABdhPJxzt0AHovUuoLArGuX/tHKObT/cGwWj615Oeh/xY0Ubg5WwpOnpRqHFS4huR+tiym8IxvMO6j5pRA86w8qNPgk= X-Received: by 2002:aed:2946:: with SMTP id s64mr24012227qtd.73.1606776403097; Mon, 30 Nov 2020 14:46:43 -0800 (PST) MIME-Version: 1.0 References: <2B01780F-D367-48A3-A827-B479030A496D@obsigna.com> <8d806302-479c-ca34-3fdb-96d27f40e212@viruzzz.org> <8655AF30-273B-48E7-98CD-007AA1D265F5@obsigna.com> <54ffe2d2-01a2-8b43-94fa-aee4a3f89861@viruzzz.org> <08649892ca2ab434c261d36e0e13ba051086de6f.camel@freebsd.org> <1e6993d43d22d6ce1aa2860a61745356688d1e53.camel@freebsd.org> In-Reply-To: From: Warner Losh Date: Mon, 30 Nov 2020 15:46:32 -0700 Message-ID: Subject: Re: User Space GPIO Interrupt programming - GSoC-2018 To: Ian Lepore Cc: "Dr. Rolf Jansen" , "freebsd-arm@freebsd.org" X-Rspamd-Queue-Id: 4ClL2D0Yqlz4rnp X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=gsWe/t8m; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::82f) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-3.00 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::82f:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-1.00)[-0.995]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::82f:from]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::82f:from]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; MAILMAN_DEST(0.00)[freebsd-arm]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2020 22:46:45 -0000 On Mon, Nov 30, 2020 at 2:52 PM Ian Lepore wrote: > On Fri, 2020-11-27 at 19:45 -0300, Dr. Rolf Jansen wrote: > > Am 27.11.2020 um 15:04 schrieb Ian Lepore : > > > On Fri, 2020-11-27 at 10:16 -0700, Ian Lepore wrote: > > > > On Fri, 2020-11-27 at 14:28 +0300, Vladimir Goncharov wrote: > > > > > Here it is. > > > > > There is struct gpioc_event with pin number and bintime which > > > > > is send > > > > > to userspace. > > > > > > > > > > Also I'm thinking about to implementation notofication without > > > > > extra > > > > > reading from socket via struct kevent's extra fields > > > > > (fflags/ext[4]), > > > > > looks like it is possible. > > > > > > > > > > > > > Please don't top-post on freebsd mailing lists. > > > > > > > > I think we need a way for the app to choose whether it wants > > > > simple > > > > reporting of pin number (like the original code) perhaps along > > > > with a > > > > count, versus requesting detailed per-event data. I'm going to > > > > propose > > > > something more detailed about this as soon as I get my thoughts > > > > all > > > > organized. I also want to get the original code and the locking > > > > fixes > > > > I've done to it into a phab review for people to start looking at > > > > before starting to do new major changes to it. > > > > > > > > Allocating memory in the interrupt handler isn't a good idea, it > > > > will > > > > just increase latency on processing other pin interrupts and lead > > > > to > > > > inaccurate timestamps. IMO, it would be better to allocate a > > > > fixed > > > > array of events; when the app requests detailed event reporting > > > > it can > > > > request the number of stored events it wants handled and we could > > > > allocate all at once based on that. > > > > > > > > > > The gsoc2018 code, with locking and style(9) fixes, is now at: > > > > > > https://reviews.freebsd.org/D27398 > > > > I got it working, and as expected, by your comments the level > > interrupt mode has been disabled. I am OK with this. Later, I will > > add more comments on this in my response to you other e-mail. > > > > Best regards > > > > Rolf > > I've just updated the phabricator review with new code. This adds the > detailed versus summary reporting. I decided the detailed reporting > should still be the default like it was before, but now it can handle > many events between calls to read(), unlike the old code that only > stored one pin change event between calls. Now it uses a circular > buffer, and there's a new ioctl function for increasing the size of the > buffer (or switching to summary reporting mode). > > I incorporated Christian's test program into the phab review, and added > some enhancements to it. It shows how to read and interpret the new > detailed and summary structures, how to convert the monotonic clock > event timestaps to UTC if needed (*), and how to handle getting > multiple event notifications with each read() call (by passing a big > buffer and parsing the structs from it after the call). > > https://reviews.freebsd.org/D27398 > > (*) The conversion of monotonic to utc time doesn't attempt to deal > with the system clock being stepped between the time an event was > recorded and when it is printed. In the real world, system time gets > stepped when the system boots, not at random while apps are running. > Well, ignoring leapseconds don't you mean? :) But I think this is an acceptable limitation... Well done in getting the cob webs dusted off this code and subsequent tweaks... Warner From owner-freebsd-arm@freebsd.org Tue Dec 1 05:15:14 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B915E473556 for ; Tue, 1 Dec 2020 05:15:14 +0000 (UTC) (envelope-from freebsd-rj@obsigna.com) Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [81.169.146.221]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ClVfT42C0z4Tmx; Tue, 1 Dec 2020 05:15:13 +0000 (UTC) (envelope-from freebsd-rj@obsigna.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1606799711; s=strato-dkim-0002; d=obsigna.com; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=XkVBxPQCJ0r/tIjV4rScjTB69Oj1ULn4iktMP73Yc18=; b=AJBodtOqKmYKfXyJ7HfTLOO7Utp3AkRXwZX3ic7LqIOXSvBEvIDG8Ws0pq5ADLVAwm TE4wT+EaNJb0Cw3kXHBcZz2pcaJz0ZcWVC+GZ3qdIc3IDuUqBCxC4ZwVxqWw9wrP2WMj YbP9qF883cMnM/Hy3wW+p+ejd4NyLpF7D92oJbO+cvXHh4Fm9Oj6b0FttBOVKHWA1C8q xQgSFHRd6ZTH8ybM4OQ1wvyBHXCRsFqTA7hfsJUrot1xpJlmTv+a+D+MxdFY+mq869ou EYJkfkexXrRnwbvnIINWVx6jnFYpMxlRGIud9bn/AEdgwl1phpwaJSW10Y3hpzkovbDO Lyjw== X-RZG-AUTH: ":O2kGeEG7b/pS1F2rRHW2isrKl4DV03XBEi+I6ZuztdvN9wS3wFGySS4Lw+ldTBio0dVbInGjc9RnD7rYRqs=" X-RZG-CLASS-ID: mo00 Received: from mail.obsigna.com by smtp.strato.de (RZmta 47.3.3 DYNA|AUTH) with ESMTPSA id U0af7bwB15FAcS1 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Tue, 1 Dec 2020 06:15:10 +0100 (CET) Received: from rolf-mini.obsigna.com (rolf-mini.obsigna.com [192.168.222.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.obsigna.com (Postfix) with ESMTPSA id 0F88E1350F91D; Tue, 1 Dec 2020 02:15:06 -0300 (-03) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.15\)) Subject: Re: User Space GPIO Interrupt programming - GSoC-2018 From: Dr. Rolf Jansen In-Reply-To: Date: Tue, 1 Dec 2020 02:15:06 -0300 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <1470B727-1499-407A-91A4-1745F22A5EC3@obsigna.com> References: <2B01780F-D367-48A3-A827-B479030A496D@obsigna.com> <8d806302-479c-ca34-3fdb-96d27f40e212@viruzzz.org> <8655AF30-273B-48E7-98CD-007AA1D265F5@obsigna.com> <54ffe2d2-01a2-8b43-94fa-aee4a3f89861@viruzzz.org> <08649892ca2ab434c261d36e0e13ba051086de6f.camel@freebsd.org> <1e6993d43d22d6ce1aa2860a61745356688d1e53.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.3445.104.15) X-Rspamd-Queue-Id: 4ClVfT42C0z4Tmx X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=obsigna.com header.s=strato-dkim-0002 header.b=AJBodtOq; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd-rj@obsigna.com designates 81.169.146.221 as permitted sender) smtp.mailfrom=freebsd-rj@obsigna.com X-Spamd-Result: default: False [0.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:81.169.146.128/25]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[obsigna.com:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[81.169.146.221:from]; ASN(0.00)[asn:6724, ipnet:81.169.144.0/22, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[obsigna.com:s=strato-dkim-0002]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[obsigna.com]; NEURAL_SPAM_SHORT(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[81.169.146.221:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[81.169.146.221:from]; FROM_NAME_HAS_TITLE(1.00)[dr]; RWL_MAILSPIKE_POSSIBLE(0.00)[81.169.146.221:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2020 05:15:14 -0000 Am 30.11.2020 um 18:52 schrieb Ian Lepore : > On Fri, 2020-11-27 at 19:45 -0300, Dr. Rolf Jansen wrote: >> Am 27.11.2020 um 15:04 schrieb Ian Lepore : >>> On Fri, 2020-11-27 at 10:16 -0700, Ian Lepore wrote: >>>> On Fri, 2020-11-27 at 14:28 +0300, Vladimir Goncharov wrote: >>>>> Here it is. >>>>> There is struct gpioc_event with pin number and bintime which >>>>> is send >>>>> to userspace. >>>>>=20 >>>>> Also I'm thinking about to implementation notofication without >>>>> extra >>>>> reading from socket via struct kevent's extra fields >>>>> (fflags/ext[4]), >>>>> looks like it is possible. >>>>>=20 >>>>=20 >>>> Please don't top-post on freebsd mailing lists. >>>>=20 >>>> I think we need a way for the app to choose whether it wants >>>> simple >>>> reporting of pin number (like the original code) perhaps along >>>> with a >>>> count, versus requesting detailed per-event data. I'm going to >>>> propose >>>> something more detailed about this as soon as I get my thoughts >>>> all >>>> organized. I also want to get the original code and the locking >>>> fixes >>>> I've done to it into a phab review for people to start looking at >>>> before starting to do new major changes to it. >>>>=20 >>>> Allocating memory in the interrupt handler isn't a good idea, it >>>> will >>>> just increase latency on processing other pin interrupts and lead >>>> to >>>> inaccurate timestamps. IMO, it would be better to allocate a >>>> fixed >>>> array of events; when the app requests detailed event reporting >>>> it can >>>> request the number of stored events it wants handled and we could >>>> allocate all at once based on that. >>>>=20 >>>=20 >>> The gsoc2018 code, with locking and style(9) fixes, is now at: >>>=20 >>> https://reviews.freebsd.org/D27398 >>=20 >> I got it working, and as expected, by your comments the level >> interrupt mode has been disabled. I am OK with this. Later, I will >> add more comments on this in my response to you other e-mail. >>=20 >> Best regards >>=20 >> Rolf >=20 > I've just updated the phabricator review with new code. This adds the > detailed versus summary reporting. I decided the detailed reporting > should still be the default like it was before, but now it can handle > many events between calls to read(), unlike the old code that only > stored one pin change event between calls. Now it uses a circular > buffer, and there's a new ioctl function for increasing the size of = the > buffer (or switching to summary reporting mode). >=20 > I incorporated Christian's test program into the phab review, and = added > some enhancements to it. It shows how to read and interpret the new > detailed and summary structures, how to convert the monotonic clock > event timestaps to UTC if needed (*), and how to handle getting > multiple event notifications with each read() call (by passing a big > buffer and parsing the structs from it after the call). >=20 > https://reviews.freebsd.org/D27398 >=20 > (*) The conversion of monotonic to utc time doesn't attempt to deal > with the system clock being stepped between the time an event was > recorded and when it is printed. In the real world, system time gets > stepped when the system boots, not at random while apps are running. >=20 > -- Ian I just tested it, by utilizing the gpioevent test tool. And everything = is working exactly the way, I need it. For example, on the BBB, I = connected a quite worn-out push button to a GPIO in PU mode and to DGND. = This button is known to bounce heavily. Now with your enhancements and = the new tool which reports the timestamps, I could do debouncing in = software. gpioevents -f /dev/gpioc2 -m r 3 er Again this is a really bad button, however the BBB seems to be able to = pick up the bounces in less than a ms resolution. I don=E2=80=99t need = more. Press: time 1122.784614858 pin 3 state 1 time 1122.786906911 pin 3 state 1 time 1122.787700011 pin 3 state 1 time 1122.787758051 pin 3 state 1 time 1122.788112206 pin 3 state 1 time 1122.788434696 pin 3 state 1 time 1122.788699563 pin 3 state 1 time 1122.788742728 pin 3 state 1 time 1122.788775310 pin 3 state 1 time 1122.788962180 pin 3 state 1 time 1122.789201714 pin 3 state 1 time 1122.789409790 pin 3 state 1 time 1122.791530140 pin 3 state 1 time 1122.792603357 pin 3 state 1 time 1122.792638730 pin 3 state 1 time 1122.792694146 pin 3 state 1 time 1122.792759185 pin 3 state 1 time 1122.792782851 pin 3 state 1 time 1122.792858890 pin 3 state 1 time 1122.792903722 pin 3 state 1 time 1122.792926555 pin 3 state 1 time 1122.793038426 pin 3 state 1 time 1122.793119549 pin 3 state 1 time 1122.793301335 pin 3 state 1 time 1122.793501662 pin 3 state 1 time 1122.793565368 pin 3 state 1 time 1122.793608283 pin 3 state 1 time 1122.793768903 pin 3 state 1 time 1122.794032353 pin 3 state 1 time 1122.797496036 pin 3 state 1 time 1122.797512911 pin 3 state 1 Release time 1122.933694459 pin 3 state 1 time 1122.933713000 pin 3 state 1 time 1122.933749748 pin 3 state 1 What is the expected significant time resolution. 9 digits suggests that = it is nanoseconds, however, I tend to believe, that it is perhaps = microseconds (6 digits after the dp), isn=E2=80=99t it? Please let me know, if you want me to test anything else. Please inform me once all this becomes committed to head, then I can = remove the patched files and svn-update the sources for the custom = kernel. Thank you very much. Best regards Rolf From owner-freebsd-arm@freebsd.org Tue Dec 1 07:45:35 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 17F764A17FB for ; Tue, 1 Dec 2020 07:45:35 +0000 (UTC) (envelope-from qroxana@mail.ru) Received: from smtp29.i.mail.ru (smtp29.i.mail.ru [94.100.177.89]) (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 4ClYzx67bzz4v6g for ; Tue, 1 Dec 2020 07:45:33 +0000 (UTC) (envelope-from qroxana@mail.ru) Received: by smtp29.i.mail.ru with esmtpa (envelope-from ) id 1kk0Lp-0008FM-69 for freebsd-arm@freebsd.org; Tue, 01 Dec 2020 10:45:30 +0300 Date: Tue, 01 Dec 2020 07:45:18 +0000 From: qroxana To: freebsd-arm@freebsd.org Subject: No network for if_dwc since r367940 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: X-7564579A: 78E4E2B564C1792B X-77F55803: 4F1203BC0FB41BD999A8EEC2DADA0D0797AD2D10E554DBA553D00663DF1C0F1C182A05F538085040DA7BC02EC4E7D93DFE5A4421BBB096C5B39D8053748A8F806AC6BF71844596CE X-7FA49CB5: FF5795518A3D127A4AD6D5ED66289B5278DA827A17800CE78E8764B5BC580342EA1F7E6F0F101C67BD4B6F7A4D31EC0BCC500DACC3FED6E28638F802B75D45FF8AA50765F79006379BF04B24BEB7B2D58638F802B75D45FF5571747095F342E8C7A0BC55FA0FE5FC4468282DA432827DC0A1268E22334B9009EFDB93A51A245D389733CBF5DBD5E913377AFFFEAFD269176DF2183F8FC7C09E967FC778BD48978941B15DA834481FCF19DD082D7633A0E7DDDDC251EA7DABA471835C12D1D977725E5C173C3A84C3CA5A41EBD8A3A0199FA2833FD35BB23DF004C9065253843090DCD38970440CD17B076A6E789B0E975F5C1EE8F4F765FC253BC1F96265356C3AA81AA40904B5D9CF19DD082D7633A0446828A5085A663B3AA81AA40904B5D940F5DB26CE7A012638CEA0499A91EADFBA3038C0950A5D36D5E8D9A59859A8B66E033549EF6A7EB276E601842F6C81A1F004C90652538430CDF3594A7B9BE05A93EC92FD9297F6718AA50765F7900637C5A177B1F5F43195A7F4EDE966BC389F395957E7521B51C24C7702A67D5C33162DBA43225CD8A89F27FFC8DC967EC12D57739F23D657EF2BB5C8C57E37DE458B4C7702A67D5C3316FA3894348FB808DBE07E89C85EBFA3A8574AF45C6390F7469DAA53EE0834AAEE X-C1DE0DAB: C20DE7B7AB408E4181F030C43753B8186998911F362727C414F749A5E30D975C28BBABB5229571E6A443152A980848C1E2AB2BC456DBAD9D9C2B6934AE262D3EE7EAB7254005DCED9280816B844F2FC71E0A4E2319210D9B64D260DF9561598FCFFBF5018520E3988DC63EAE0DBA7CFC X-C8649E89: 4E36BF7865823D7055A7F0CF078B5EC41A2EA1C61B5C2F0191CA530AB3532F93D4812162932E004D37995CB284F4C3B0E20B2CA3BB566162DC975A7FBE8349C9 X-D57D3AED: 3ZO7eAau8CL7WIMRKs4sN3D3tLDjz0dLbV79QFUyzQ2Ujvy7cMT6pYYqY16iZVKkSc3dCLJ7zSJH7+u4VD18S7Vl4ZUrpaVfd2+vE6kuoey4m4VkSEu530nj6fImhcD4MUrOEAnl0W826KZ9Q+tr5ycPtXkTV4k65bRjmOUUP8cvGozZ33TWg5HZplvhhXbhDGzqmQDTd6OAevLeAnq3Ra9uf7zvY2zzsIhlcp/Y7m53TZgf2aB4JOg4gkr2biojbL9S8ysBdXh5l9o3ihzol4jfBRs0nFjm X-Magic: 96F223A640BC474A707BB03B8E9097E731010E71879BAE935FC319F19CD5AA4CCDE73A114744BA6C X-Mailru-Sender: A8F90F45CB8D80DBDC835F8A9775B8B1642FBB5938264F174D817A486AB2DF7AD732100F3E2561A89BBFFF7D229A147FFDD1F2F6C9B53D730D187FEF3E0D57C1D08349341B303650BDF7E317B72FD726EC982BF62A43B37A04568DD965327F405FEEDEB644C299C0ED14614B50AE0675 X-Mras: Ok X-SRW: A87A55C12133CE1587FD5D6AC9C9A777C363C2D52A20EC246F4C7978FBC05543 X-Rspamd-Queue-Id: 4ClYzx67bzz4v6g X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.10 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[94.100.177.89:from]; R_DKIM_ALLOW(-0.20)[mail.ru:s=mail3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[mail.ru:dkim]; FREEMAIL_FROM(0.00)[mail.ru]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[94.100.177.89:from:127.0.2.255]; R_SPF_ALLOW(-0.20)[+ip4:94.100.176.0/20]; DKIM_TRACE(0.00)[mail.ru:+]; DMARC_POLICY_ALLOW(-0.50)[mail.ru,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[mail.ru]; ASN(0.00)[asn:47764, ipnet:94.100.176.0/20, country:RU]; MAILMAN_DEST(0.00)[freebsd-arm]; RCVD_IN_DNSWL_LOW(-0.10)[94.100.177.89:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2020 07:45:35 -0000 It looks like the network is broken since r367940 on Allwinner A20 boards, dwc0 is up but it's not able to reach the network. Thanks. From owner-freebsd-arm@freebsd.org Tue Dec 1 09:26:27 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 24D3E4A30E7 for ; Tue, 1 Dec 2020 09:26:27 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ClcDK4m0mz3G03 for ; Tue, 1 Dec 2020 09:26:24 +0000 (UTC) (envelope-from manu@bidouilliste.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1606814782; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vp3hiPljpTXEYABj3zF74Vm735xTuCF/SJpXZ9BP6Jw=; b=aJdiiHEQs5cbxuvNvGZuCbL6Xok400fxCKjAbo8Uczt/ydi+Cr+WBsBm19wL4x1LCXC4Yc 4893OUvMEUcvmlgA1RVVboGBpug1F8SqVoSJHyrKi865/vrOptY3g7EN7ZJtIl9Z0H4Sx7 aWeG1tJHoNeuSJNAqFbElJcVeWbczyI= Received: from amy.home (lfbn-idf2-1-288-247.w82-123.abo.wanadoo.fr [82.123.126.247]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 51b69963 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 1 Dec 2020 09:26:22 +0000 (UTC) Date: Tue, 1 Dec 2020 10:26:22 +0100 From: Emmanuel Vadot To: qroxana Cc: qroxana via freebsd-arm Subject: Re: No network for if_dwc since r367940 Message-Id: <20201201102622.9640527e85e030f0d17b23f9@bidouilliste.com> In-Reply-To: References: 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: 4ClcDK4m0mz3G03 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mx header.b=aJdiiHEQ; dmarc=pass (policy=none) header.from=bidouilliste.com; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.155.74 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[bidouilliste.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[mail.ru]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[212.83.155.74:from]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mx]; FREEFALL_USER(0.00)[manu]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[212.83.155.74:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2020 09:26:27 -0000 Hello, On Tue, 01 Dec 2020 07:45:18 +0000 qroxana via freebsd-arm wrote: > > It looks like the network is broken since r367940 on > Allwinner A20 boards, dwc0 is up but it's not able to > reach the network. Thanks. On which board do you see issue ? I admit that I haven't tested on A20 but I think that I've done what was needed. Anyway, I'll test on a few boards here and fix the issue. -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Tue Dec 1 15:15:38 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9C1494ABF97 for ; Tue, 1 Dec 2020 15:15:38 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound5a.ore.mailhop.org (outbound5a.ore.mailhop.org [44.233.67.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CllzG2X55z3w79 for ; Tue, 1 Dec 2020 15:15:38 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1606835731; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=TIOs/xDSVZMUkHV4zsQhxj3eer2g0pulX5t50m952m/yQdFIcpwpBRDgVkcIBPPMVS3QccMq6bNvf oG7lcoqTD45S1rmIPKv1LglzDeKjWF3QaskL3DZcjJZgJ0eTLY4H98TMRIT+beW+nrJg6KhTsESPzX C7HZfCP0qMr/uBT35pG5fH2nlLepUfsCd2rh3dkxfKohCqbsP+H3jICNHj7Ne6wX50dMCsCXoV0rJ4 1fuiYaHOVsxtcH+bPy5px4BoD9s+53vbfmFji/o69MxlowAK9I5MmViBOH7ehPQnwZor43I0ss0hP9 w3Ao1dYkBNk/2tmyTium9/KT7UOT1Kw== 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=BBfstvED+w15i3shWm7rXzB4JYw8Akiec/aVhGVf+vg=; b=PA78n9smQN10Wfc4F4Vh8GeDNvVFRbZV6025ie0sAIZQ9TXjqvN3EIsKwr2S1eXpcOaPIeheYODon YMIUitFVL61fEI1Ql6+U3JPlD7eqK4iCKIZG86FewSmyyX++m0kaLk5Ym5Ympmpib6IcrE1JgmJzy0 mMyUuhtrH4KLCRy59EyS+RO2C+1gzHLcloG+NNPXAnK3T6ejKHvo8IZ1uSv29LBJWSlSP4WTC2ZQsk nzi8JVhU43gYQIsbYlhDDT/9C+xc8PNh1IGoPBpi+Z3180CEk2u8t4U7daVVseSEd7npQAQooJkraf bKvAGQn+sQeMKUHfinuK/WlamxnWHjQ== 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=BBfstvED+w15i3shWm7rXzB4JYw8Akiec/aVhGVf+vg=; b=fhicbiDvADm7Rok5IrH2GV+3olBI7TxSTyuBg9Ikxs00Kc4W8b1hjY+q+DLOG3xNz9bQK+esCCOC8 OpAoUOujFS825eSqWLaKQaZbUsjMrQLW/uxVu8e9NqExoaRAJ0/VbM3kFodk8R0Sk8E2jlIY+T5KTs OLMyO8snd3Z8wCwWs/7kHPZGYGLGAUvHCLZGTRCj+dqch29FVKWnAxiED+fGiQVtgYRa/41Dj7fmyZ fbOjJuFNRP/1dU0IOiASdmaM8GicOBMq4sYwapsuOl3Ig6BujbbKGi+okAtExrf/k3AC7geejts6CB 5cHStBwtl4zCYmI7mNX8IPZo7jrbTzA== X-MHO-RoutePath: aGlwcGll X-MHO-User: 0bb3cd7c-33e8-11eb-8b39-614106969e8d 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 (c-67-177-211-60.hsd1.co.comcast.net [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 0bb3cd7c-33e8-11eb-8b39-614106969e8d; Tue, 01 Dec 2020 15:15:30 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id 0B1FFS6F094930; Tue, 1 Dec 2020 08:15:28 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: User Space GPIO Interrupt programming - GSoC-2018 From: Ian Lepore To: "Dr. Rolf Jansen" Cc: freebsd-arm@freebsd.org Date: Tue, 01 Dec 2020 08:15:28 -0700 In-Reply-To: <1470B727-1499-407A-91A4-1745F22A5EC3@obsigna.com> References: <2B01780F-D367-48A3-A827-B479030A496D@obsigna.com> <8d806302-479c-ca34-3fdb-96d27f40e212@viruzzz.org> <8655AF30-273B-48E7-98CD-007AA1D265F5@obsigna.com> <54ffe2d2-01a2-8b43-94fa-aee4a3f89861@viruzzz.org> <08649892ca2ab434c261d36e0e13ba051086de6f.camel@freebsd.org> <1e6993d43d22d6ce1aa2860a61745356688d1e53.camel@freebsd.org> <1470B727-1499-407A-91A4-1745F22A5EC3@obsigna.com> Content-Type: text/plain; charset="iso-8859-7" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4CllzG2X55z3w79 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2020 15:15:38 -0000 On Tue, 2020-12-01 at 02:15 -0300, Dr. Rolf Jansen wrote: > Am 30.11.2020 um 18:52 schrieb Ian Lepore : > > [...] > > I've just updated the phabricator review with new code. This adds > > the > > detailed versus summary reporting. I decided the detailed > > reporting > > should still be the default like it was before, but now it can > > handle > > many events between calls to read(), unlike the old code that only > > stored one pin change event between calls. Now it uses a circular > > buffer, and there's a new ioctl function for increasing the size of > > the > > buffer (or switching to summary reporting mode). > > > > I incorporated Christian's test program into the phab review, and > > added > > some enhancements to it. It shows how to read and interpret the > > new > > detailed and summary structures, how to convert the monotonic clock > > event timestaps to UTC if needed (*), and how to handle getting > > multiple event notifications with each read() call (by passing a > > big > > buffer and parsing the structs from it after the call). > > > > https://reviews.freebsd.org/D27398 > > > > (*) The conversion of monotonic to utc time doesn't attempt to deal > > with the system clock being stepped between the time an event was > > recorded and when it is printed. In the real world, system time > > gets > > stepped when the system boots, not at random while apps are > > running. > > > > -- Ian > > I just tested it, by utilizing the gpioevent test tool. And > everything is working exactly the way, I need it. For example, on the > BBB, I connected a quite worn-out push button to a GPIO in PU mode > and to DGND. This button is known to bounce heavily. Now with your > enhancements and the new tool which reports the timestamps, I could > do debouncing in software. > > gpioevents -f /dev/gpioc2 -m r 3 er > > Again this is a really bad button, however the BBB seems to be able > to pick up the bounces in less than a ms resolution. I donąt need > more. > > Press: > time 1122.784614858 pin 3 state 1 > [...] > time 1122.793768903 pin 3 state 1 > time 1122.794032353 pin 3 state 1 > time 1122.797496036 pin 3 state 1 > time 1122.797512911 pin 3 state 1 > > Release > time 1122.933694459 pin 3 state 1 > time 1122.933713000 pin 3 state 1 > time 1122.933749748 pin 3 state 1 > > What is the expected significant time resolution. 9 digits suggests > that it is nanoseconds, however, I tend to believe, that it is > perhaps microseconds (6 digits after the dp), isnąt it? > > Please let me know, if you want me to test anything else. > > Please inform me once all this becomes committed to head, then I can > remove the patched files and svn-update the sources for the custom > kernel. > > Thank you very much. > > Best regards > > Rolf In my testing on an imx6 (1ghz 4-core) I fed it a 10mhz square wave, told it to watch for either edge, and was getting an event every 10 microseconds or so. It does a little better if you're only watching for rising or falling edge, about every 6-7us, because in that case it doesn't have to make an extra call to sample the state of the gpio pin in the interrupt handler. I think the code is ready to commit as soon as the review gets some approval feedback. The one thing that remains to be done is to write a gpioc(4) manpage documenting all this stuff, which I intend to do some time in the next week or two, but I don't think I need to hold up the commit for that. -- Ian From owner-freebsd-arm@freebsd.org Wed Dec 2 01:24:26 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9CE1646D0E8 for ; Wed, 2 Dec 2020 01:24:26 +0000 (UTC) (envelope-from qroxana@mail.ru) Received: from smtp36.i.mail.ru (smtp36.i.mail.ru [94.100.177.96]) (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 4Cm1Tj0Yq4z3kTt for ; Wed, 2 Dec 2020 01:24:24 +0000 (UTC) (envelope-from qroxana@mail.ru) Received: by smtp36.i.mail.ru with esmtpa (envelope-from ) id 1kkGsT-00071U-Ig; Wed, 02 Dec 2020 04:24:18 +0300 Date: Wed, 02 Dec 2020 01:23:55 +0000 From: qroxana To: Emmanuel Vadot Cc: freebsd-arm@freebsd.org Subject: Re: No network for if_dwc since r367940 In-Reply-To: <20201201102622.9640527e85e030f0d17b23f9@bidouilliste.com> (Emmanuel Vadot's message of "Tue, 1 Dec 2020 10:26:22 +0100") References: <20201201102622.9640527e85e030f0d17b23f9@bidouilliste.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: X-7564579A: B8F34718100C35BD X-77F55803: 4F1203BC0FB41BD913934B9F4F7782281C8E716DB8F5B18A662D23FB587804C600894C459B0CD1B9E5324C8A10D63540F2C24E869895FF974E7F1C5D280C0DEC45849E6DFAE0F427 X-7FA49CB5: FF5795518A3D127A4AD6D5ED66289B5278DA827A17800CE7CA8E915ACC910FBDEA1F7E6F0F101C67BD4B6F7A4D31EC0BCC500DACC3FED6E28638F802B75D45FF8AA50765F79006377E85B0EC44E8FD73EA1F7E6F0F101C674E70A05D1297E1BBC6CDE5D1141D2B1CBACDCF07D8AB5685F344C723E6617E1E22C098E3A8F65D319FA2833FD35BB23D9E625A9149C048EE26055571C92BF10FE5D25F19253116ADD2E47CDBA5A96583BD4B6F7A4D31EC0BB23A54CFFDBC96A8389733CBF5DBD5E9D5E8D9A59859A8B6AEEA5BB16A939343CC7F00164DA146DA6F5DAA56C3B73B23D9A76B3E0BEF82613AA81AA40904B5D9A18204E546F3947CA14973FBE0621AE56136E347CC761E074AD6D5ED66289B5218080C068C56568E6136E347CC761E07725E5C173C3A84C38BE533ED6FE4FF6ABA3038C0950A5D36B5C8C57E37DE458BAE10EB31B950A5E667F23339F89546C55F5C1EE8F4F765FC696E4123C2B4120575ECD9A6C639B01BBD4B6F7A4D31EC0BC0CAF46E325F83A522CA9DD8327EE4930A3850AC1BE2E735A3CCBC2573AEBDE1C4224003CC836476C0CAF46E325F83A50BF2EBBBDD9D6B0F05F538519369F3743B503F486389A921A5CC5B56E945C8DA X-C1DE0DAB: 0D63561A33F958A5CDD68F6FE7B917CFA61678FACAA40F0708676DC7F9C3AEA1D59269BC5F550898D99A6476B3ADF6B47008B74DF8BB9EF7333BD3B22AA88B938A852937E12ACA75D299BBC8C521FD19410CA545F18667F91A7EA1CDA0B5A7A0 X-C8649E89: 4E36BF7865823D7055A7F0CF078B5EC4B71F6223395F4EF78A271E751B4E395C7AA74F9F97F6718A3D4948AAEB131ADD594782A1D4D8F880B3AC6C9C8917424E X-D57D3AED: 3ZO7eAau8CL7WIMRKs4sN3D3tLDjz0dLbV79QFUyzQ2Ujvy7cMT6pYYqY16iZVKkSc3dCLJ7zSJH7+u4VD18S7Vl4ZUrpaVfd2+vE6kuoey4m4VkSEu530nj6fImhcD4MUrOEAnl0W826KZ9Q+tr5ycPtXkTV4k65bRjmOUUP8cvGozZ33TWg5HZplvhhXbhDGzqmQDTd6OAevLeAnq3Ra9uf7zvY2zzsIhlcp/Y7m53TZgf2aB4JOg4gkr2biojEErOympIxBE+bEcuYpQxXQ== X-Mailru-Sender: A8F90F45CB8D80DB6783F54E311ED0B3C310792200347240228024FB7D783A8EF7D32DAF7EFE038A9BBFFF7D229A147FFDD1F2F6C9B53D730D187FEF3E0D57C1D08349341B303650BDF7E317B72FD726EC982BF62A43B37A04568DD965327F405FEEDEB644C299C0ED14614B50AE0675 X-Mras: Ok X-Rspamd-Queue-Id: 4Cm1Tj0Yq4z3kTt X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[94.100.177.96:from]; R_DKIM_ALLOW(-0.20)[mail.ru:s=mail3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[mail.ru]; R_SPF_ALLOW(-0.20)[+ip4:94.100.176.0/20]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[94.100.177.96:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[mail.ru:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[94.100.177.96:from]; NEURAL_HAM_SHORT(-1.00)[-0.997]; DMARC_POLICY_ALLOW(-0.50)[mail.ru,reject]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[mail.ru]; ASN(0.00)[asn:47764, ipnet:94.100.176.0/20, country:RU]; MAILMAN_DEST(0.00)[freebsd-arm]; DWL_DNSWL_NONE(0.00)[mail.ru:dkim] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Dec 2020 01:24:26 -0000 On Tue, 1 Dec 2020 10:26:22 +0100, Emmanuel Vadot wrote: > Hello, > > On Tue, 01 Dec 2020 07:45:18 +0000 > qroxana via freebsd-arm wrote: > >> >> It looks like the network is broken since r367940 on >> Allwinner A20 boards, dwc0 is up but it's not able to >> reach the network. Thanks. > > On which board do you see issue ? > I admit that I haven't tested on A20 but I think that I've done what > was needed. > Anyway, I'll test on a few boards here and fix the issue. Hi Emmanuel, It's BananaPi M1/M1+. Thanks. From owner-freebsd-arm@freebsd.org Wed Dec 2 02:32:45 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 60CD246DBEE for ; Wed, 2 Dec 2020 02:32:45 +0000 (UTC) (envelope-from rivers@dignus.com) Received: from dignus.com (adsl-065-013-223-202.sip.rdu.bellsouth.net [65.13.223.202]) (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 4Cm30X3Vwkz3mfn for ; Wed, 2 Dec 2020 02:32:43 +0000 (UTC) (envelope-from rivers@dignus.com) Received: from office.dignus.com (localhost [127.0.0.1]) by dignus.com (8.14.4/8.14.4) with ESMTP id 0B22ZIhK029485; Tue, 1 Dec 2020 21:35:18 -0500 (EST) (envelope-from rivers@office.dignus.com) Received: (from rivers@localhost) by office.dignus.com (8.14.4/8.14.4/Submit) id 0B22ZIT7029484; Tue, 1 Dec 2020 21:35:18 -0500 (EST) (envelope-from rivers) Date: Tue, 1 Dec 2020 21:35:18 -0500 (EST) From: Thomas David Rivers Message-Id: <202012020235.0B22ZIT7029484@office.dignus.com> To: freebsd-arm@freebsd.org, rivers@dignus.com Subject: Just getting started with Rasperry PI 4B, 8GB... X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on office.dignus.com X-Rspamd-Queue-Id: 4Cm30X3Vwkz3mfn X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of rivers@dignus.com has no SPF policy when checking 65.13.223.202) smtp.mailfrom=rivers@dignus.com X-Spamd-Result: default: False [0.40 / 15.00]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[rivers]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[65.13.223.202:from]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; HFILTER_HOSTNAME_4(2.50)[adsl-065-013-223-202.sip.rdu.bellsouth.net]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[dignus.com]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[65.13.223.202:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7018, ipnet:65.13.220.0/22, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Dec 2020 02:32:45 -0000 Hello everyone, I'm looking at getting FreeBSD (a pretty stable version) running on a 4B 8GB... I haven't stumbled over a "how to" write-up, and thought I would sign on to freebsd-arm to see where things stand. I took a gander thru the past 3 months archive postings and I see things might not be working too well in on a Raspberry PI 4B 8GB? But, I'm kinda suddenly swimming-in-the-deep-end here without too much context. I downloaded and imaged the latest (2020-Nov-26) 13.0 image, but it just tells me "This board requires newer software". I haven't gone the UEFI route yet - since I'm just booting an SD card (don't need USB boot from a disk drive.) My PI 4 - 8GB says: Raspberry Pi 4 - 8GB bootloader: c305221a Sep 3 2020 config: 86697050 so the bootloader is pretty new. It's getting Read config.txt bytes 147 hnd 0x000003e3 hash '0370b4dfaea0caaf' recover4.elf not found (6) recovery.elf not found (6) Read start4.elf bytes 2775076 hnd 0x00001ebc hash '0797505a72b169c3' Read fixup4.dat bytes 6193 hnd 0x00001c06 hash '5945fb04d1ba9299' 0x00d03114 0x00000000 0x00000000 start4.elf is not compatible This board requires newer software Get the latest software from https://www.raspberrypi.org/downloads/ ERROR: 00000044 Insert SD-CARD I'm guessing there's some obvious step I'm missing here; so perhaps someone already has a write-up about this I just need to look for, if there are any pointers. Or - do I need to switch to a UEFI boot? Or is a Pi 4B-8GB just not supported yet? - Many thanks! - - Dave Rivers - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com From owner-freebsd-arm@freebsd.org Wed Dec 2 08:27:56 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7E65A474F0D for ; Wed, 2 Dec 2020 08:27:56 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CmBtM3TM3z4XRZ for ; Wed, 2 Dec 2020 08:27:55 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Date: Wed, 2 Dec 2020 09:27:50 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1606897671; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Y+dlGeQpbVTCanSw3lZVunm7LLOq8bUrHNbSwu6uz7M=; b=sD2q759xYD6vijo3o5ZbX94Ceq3t7alyfmTyHoqSGPv8XPyO8DcRQBcyxwLZz4JnWyzDZf 2dLHKroaqJGy6CLdG0vk6bAvVnOIzca0S5/GrQJvGQ2wpG73Kxvtq8sItuzdrMXI7Wwux3 f9IS92g0apTbRhBic3AL4J7GwsNf8W1LpC/HUuTsM5iYgLLewlRZSKx6w2LqDru35PNuKC eO++HcQBXcAsJGwNiQ4pUznLQnjhEtltHp9jzJvkRFfVvp5Uzuh4+8Ow/ZiD1nu1u26dUl V9goMIYN5JzgJks//qX2aBaHsmwcX4MYGnu25UHQpCF7Prc41uxBfNhDyopr/w== From: Ronald Klop To: freebsd-arm@freebsd.org Message-ID: <465104746.2.1606897670954@localhost> In-Reply-To: <202012020235.0B22ZIT7029484@office.dignus.com> References: <202012020235.0B22ZIT7029484@office.dignus.com> Subject: Re: Just getting started with Rasperry PI 4B, 8GB... MIME-Version: 1.0 X-Mailer: Realworks (536.35.d9edab775dd) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4CmBtM3TM3z4XRZ X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=sD2q759x; dmarc=pass (policy=none) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of ronald-lists@klop.ws designates 194.109.157.24 as permitted sender) smtp.mailfrom=ronald-lists@klop.ws X-Spamd-Result: default: False [-3.50 / 15.00]; ARC_NA(0.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[194.109.157.24:from]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; DKIM_TRACE(0.00)[klop.ws:+]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,none]; HAS_X_PRIO_THREE(0.00)[3]; RCVD_IN_DNSWL_NONE(0.00)[194.109.157.24:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; MAILMAN_DEST(0.00)[freebsd-arm] Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Dec 2020 08:27:56 -0000 Just a quick (top-posted) note as I'm going into a meeting. I followed these steps: https://lists.freebsd.org/pipermail/freebsd-arm/2020-November/022701.html But instead of mdconfig I just dd'ed the image and mounted the SD-card to put the right files in the msdos partition. Have fun with it. My RPI4 8GB runs quite fine for about 2 weeks now. Ronald. Van: Thomas David Rivers Datum: woensdag, 2 december 2020 03:35 Aan: freebsd-arm@freebsd.org, rivers@dignus.com Onderwerp: Just getting started with Rasperry PI 4B, 8GB... > > Hello everyone, > > I'm looking at getting FreeBSD (a pretty stable version) running > on a 4B 8GB... I haven't stumbled over a "how to" write-up, and > thought I would sign on to freebsd-arm to see where things stand. > > I took a gander thru the past 3 months archive postings and I see > things might not be working too well in on a Raspberry PI 4B 8GB? > But, I'm kinda suddenly swimming-in-the-deep-end here without > too much context. > > I downloaded and imaged the latest (2020-Nov-26) 13.0 image, > but it just tells me "This board requires newer software". > > I haven't gone the UEFI route yet - since I'm just booting an SD > card (don't need USB boot from a disk drive.) > > My PI 4 - 8GB says: > > Raspberry Pi 4 - 8GB > bootloader: c305221a Sep 3 2020 > config: 86697050 > > so the bootloader is pretty new. > > It's getting > > Read config.txt bytes 147 hnd 0x000003e3 hash '0370b4dfaea0caaf' > recover4.elf not found (6) > recovery.elf not found (6) > Read start4.elf bytes 2775076 hnd 0x00001ebc hash '0797505a72b169c3' > Read fixup4.dat bytes 6193 hnd 0x00001c06 hash '5945fb04d1ba9299' > 0x00d03114 0x00000000 0x00000000 > start4.elf is not compatible > This board requires newer software > Get the latest software from https://www.raspberrypi.org/downloads/ > ERROR: 00000044 > Insert SD-CARD > > > I'm guessing there's some obvious step I'm missing here; so perhaps > someone already has a write-up about this I just need to look for, > if there are any pointers. > > Or - do I need to switch to a UEFI boot? Or is a Pi 4B-8GB just > not supported yet? > > - Many thanks! - > - Dave Rivers - > > -- > rivers@dignus.com Work: (919) 676-0847 > Get your mainframe programming tools at http://www.dignus.com > _______________________________________________ > 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 Dec 3 11:16:35 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E9F7B4A3AC9 for ; Thu, 3 Dec 2020 11:16:35 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CmtZV1hF7z3Qqh for ; Thu, 3 Dec 2020 11:16:33 +0000 (UTC) (envelope-from manu@bidouilliste.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1606994191; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=QOIVlHcQJi1I/mSNGxf14CLzT/idwGTk/tD04jjXpBE=; b=bWjyXRV9ThZYHaeWKD66tjtYO80xAYkxFSvJ1iAUGthnDrYI0m6Zdi8asGGmasY3Dco+ZP E9eaL8Ox5N4YStp4gY25cb3m2s1OFYmbP38P1emlKx6Vmt+tlHJz52Xj1d0xr1/QwiBZUn uU4S1HOTG7NwX1/Mclb72zYA5RJ/8V8= Received: from skull.home.blih.net (lfbn-idf2-1-288-247.w82-123.abo.wanadoo.fr [82.123.126.247]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 161642af (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Thu, 3 Dec 2020 11:16:31 +0000 (UTC) Date: Thu, 3 Dec 2020 12:16:31 +0100 From: Emmanuel Vadot To: qroxana Cc: freebsd-arm@freebsd.org Subject: Re: No network for if_dwc since r367940 Message-Id: <20201203121631.8cc3c4a7cf51d8443df6f58a@bidouilliste.com> In-Reply-To: References: <20201201102622.9640527e85e030f0d17b23f9@bidouilliste.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: 4CmtZV1hF7z3Qqh X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mx header.b=bWjyXRV9; dmarc=pass (policy=none) header.from=bidouilliste.com; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.155.74 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; DKIM_TRACE(0.00)[bidouilliste.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[bidouilliste.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[mail.ru]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[212.83.155.74:from]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mx]; FREEFALL_USER(0.00)[manu]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[212.83.155.74:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Dec 2020 11:16:36 -0000 On Wed, 02 Dec 2020 01:23:55 +0000 qroxana wrote: > On Tue, 1 Dec 2020 10:26:22 +0100, Emmanuel Vadot wrote: > > > Hello, > > > > On Tue, 01 Dec 2020 07:45:18 +0000 > > qroxana via freebsd-arm wrote: > > > >> > >> It looks like the network is broken since r367940 on > >> Allwinner A20 boards, dwc0 is up but it's not able to > >> reach the network. Thanks. > > > > On which board do you see issue ? > > I admit that I haven't tested on A20 but I think that I've done what > > was needed. > > Anyway, I'll test on a few boards here and fix the issue. > > Hi Emmanuel, > > It's BananaPi M1/M1+. Thanks. Fixed in r368299. Sorry for the breakage. -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Sat Dec 5 04:36:03 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7ED5C4B4C16 for ; Sat, 5 Dec 2020 04:36:03 +0000 (UTC) (envelope-from shigeru@os-hackers.jp) Received: from mailssl04.asahi-net.or.jp (mailssl04.asahi-net.or.jp [202.224.55.63]) by mx1.freebsd.org (Postfix) with ESMTP id 4CnxbQ6CJfz4hrc for ; Sat, 5 Dec 2020 04:36:02 +0000 (UTC) (envelope-from shigeru@os-hackers.jp) Received: from localhost (w142149.ppp.asahi-net.or.jp [121.1.142.149]) (Authenticated sender: WJ8S-YMMT) by mailssl04.asahi-net.or.jp (Postfix) with ESMTPSA id 033784005A; Sat, 5 Dec 2020 13:29:35 +0900 (JST) Date: Sat, 05 Dec 2020 13:29:23 +0900 (JST) Message-Id: <20201205.132923.139012603584886684.shigeru@os-hackers.jp> To: ronald-lists@klop.ws Cc: freebsd-arm@freebsd.org Subject: Re: Just getting started with Rasperry PI 4B, 8GB... From: YAMAMOTO Shigeru In-Reply-To: <465104746.2.1606897670954@localhost> References: <202012020235.0B22ZIT7029484@office.dignus.com> <465104746.2.1606897670954@localhost> X-Mailer: Mew version 6.8 on Emacs 27.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4CnxbQ6CJfz4hrc X-Spamd-Bar: +++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=softfail (mx1.freebsd.org: 202.224.55.63 is neither permitted nor denied by domain of shigeru@os-hackers.jp) smtp.mailfrom=shigeru@os-hackers.jp X-Spamd-Result: default: False [5.82 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; GREYLIST(0.00)[pass,body]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[202.224.55.63:from]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[os-hackers.jp]; R_SPF_SOFTFAIL(0.00)[~all:c]; NEURAL_SPAM_MEDIUM(0.82)[0.818]; SPAMHAUS_ZRD(0.00)[202.224.55.63:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; VIOLATED_DIRECT_SPF(3.50)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; RCPT_COUNT_TWO(0.00)[2]; MID_CONTAINS_FROM(1.00)[]; NEURAL_SPAM_LONG(1.00)[1.000]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4685, ipnet:202.224.32.0/19, country:JP]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Dec 2020 04:36:03 -0000 Hi, all. >>>>> "Ronald" == Ronald Klop writes: Ronald> Just a quick (top-posted) note as I'm going into a meeting. I Ronald> followed these steps: Ronald> https://lists.freebsd.org/pipermail/freebsd-arm/2020-November/022701.html I update my document, "How to start FreeBSD Raspberry Pi 4". https://github.com/bsd-hacker/freebsd/wiki/How-to-start-FreeBSD---Raspberry-Pi-4 I test Raspberry Pi 4B, 4G model and 8G model. I think to write 'Booting FreeBSD Raspberry Pi 4B from USB disk'. Thanks, --- YAMAMOTO Shigeru From owner-freebsd-arm@freebsd.org Sat Dec 5 06:57:49 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0A5B0470C21 for ; Sat, 5 Dec 2020 06:57:49 +0000 (UTC) (envelope-from herbert@gojira.at) Received: from mail.bsd4all.net (mail.bsd4all.net [94.130.200.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail.bsd4all.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Cp0l00S1Hz4qVf for ; Sat, 5 Dec 2020 06:57:47 +0000 (UTC) (envelope-from herbert@gojira.at) Date: Sat, 05 Dec 2020 07:57:39 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gojira.at; s=mail202005; t=1607151459; bh=UmANvc6on1+SVSWhsAdv5DE92U5DH7Hb7bEbTfFxALE=; h=Date:Message-ID:From:To:Subject:MIME-Version:Content-Type; b=Gp+z/vTHnZ1qoJWxw1b9mncXCCJC4/Wz1pAF7Sr2QrcCnWkJ9ymI8JdKDFoKyAbul HH+fFY7wYTsHjELvrHSoH/56cc/p4EolziCj3V4HHwkOeM77aNDjVxoxUHclOPmY0z C0Dw1ljd4W/AK8DJXGaF44ksurp6pSz0nTIXdZL3A4BupEiIXDNKUC4lw6dyOy0mlE sDwFuaHuSQ+12mYhv6hOyDjqU+s9YdsOM5Q+eeFLtxaLOEotKzJ2saYPxFUt4GUB6F XdsViLmWjQc87VLEubqwx7ZYM8d6uRjlup42hvXzuHMWAY6Uj7Azjxf+l53i2x8GUa iPhkDnWK6Fd6w== Message-ID: <87czzooi3g.wl-herbert@gojira.at> From: "Herbert J. Skuhra" To: freebsd-arm@freebsd.org Subject: Re: Just getting started with Rasperry PI 4B, 8GB... In-Reply-To: <20201205.132923.139012603584886684.shigeru@os-hackers.jp> References: <202012020235.0B22ZIT7029484@office.dignus.com> <465104746.2.1606897670954@localhost> <20201205.132923.139012603584886684.shigeru@os-hackers.jp> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/28.0 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 4Cp0l00S1Hz4qVf X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gojira.at header.s=mail202005 header.b=Gp+z/vTH; dmarc=none; spf=pass (mx1.freebsd.org: domain of herbert@gojira.at designates 94.130.200.20 as permitted sender) smtp.mailfrom=herbert@gojira.at X-Spamd-Result: default: False [-2.50 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gojira.at:s=mail202005]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:94.130.200.20]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[gojira.at]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[94.130.200.20:from:127.0.2.255]; DKIM_TRACE(0.00)[gojira.at:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MID_CONTAINS_FROM(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[94.130.200.20:from]; ASN(0.00)[asn:24940, ipnet:94.130.0.0/16, country:DE]; MAILMAN_DEST(0.00)[freebsd-arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Dec 2020 06:57:49 -0000 On Sat, 05 Dec 2020 05:29:23 +0100, YAMAMOTO Shigeru wrote: > > I update my document, "How to start FreeBSD Raspberry Pi 4". > https://github.com/bsd-hacker/freebsd/wiki/How-to-start-FreeBSD---Raspberry-Pi-4 > > I test Raspberry Pi 4B, 4G model and 8G model. > > I think to write 'Booting FreeBSD Raspberry Pi 4B from USB disk'. You write: replace firmware 4 GB memory model no more replace fiels. And your dmesg for the 4GB model shows: real memory = 993820672 (947 MB) avail memory = 943075328 (899 MB) So there is obviously something wrong!? I have a the 4GB model and I had to replace some files in /boot/msdosfs when I set it up a few months ago. Unfortunately with newer u-boot.bin from sysutils/u-boot-rpi4 my Raspberry Pi 4B no longer boots from microsd card. Error: Controller timeout mmcsd0: Error indicated: 1 Timeout -- Herbert From owner-freebsd-arm@freebsd.org Sat Dec 5 07:36:30 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5CBB7471A5D for ; Sat, 5 Dec 2020 07:36:30 +0000 (UTC) (envelope-from shigeru@os-hackers.jp) Received: from mailssl03.asahi-net.or.jp (mailssl03.asahi-net.or.jp [202.224.55.62]) by mx1.freebsd.org (Postfix) with ESMTP id 4Cp1bc3x8pz4sSg for ; Sat, 5 Dec 2020 07:36:27 +0000 (UTC) (envelope-from shigeru@os-hackers.jp) Received: from localhost (w142149.ppp.asahi-net.or.jp [121.1.142.149]) (Authenticated sender: WJ8S-YMMT) by mailssl03.asahi-net.or.jp (Postfix) with ESMTPSA id B86884005E; Sat, 5 Dec 2020 16:36:18 +0900 (JST) Date: Sat, 05 Dec 2020 16:35:56 +0900 (JST) Message-Id: <20201205.163556.71110316527016215.shigeru@os-hackers.jp> To: herbert@gojira.at Cc: freebsd-arm@freebsd.org Subject: Re: Just getting started with Rasperry PI 4B, 8GB... From: YAMAMOTO Shigeru In-Reply-To: <87czzooi3g.wl-herbert@gojira.at> References: <465104746.2.1606897670954@localhost> <20201205.132923.139012603584886684.shigeru@os-hackers.jp> <87czzooi3g.wl-herbert@gojira.at> X-Mailer: Mew version 6.8 on Emacs 27.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Cp1bc3x8pz4sSg X-Spamd-Bar: +++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=softfail (mx1.freebsd.org: 202.224.55.62 is neither permitted nor denied by domain of shigeru@os-hackers.jp) smtp.mailfrom=shigeru@os-hackers.jp X-Spamd-Result: default: False [5.80 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[202.224.55.62:from]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; GREYLIST(0.00)[pass,meta]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[os-hackers.jp]; R_SPF_SOFTFAIL(0.00)[~all]; NEURAL_SPAM_MEDIUM(0.80)[0.802]; SPAMHAUS_ZRD(0.00)[202.224.55.62:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; VIOLATED_DIRECT_SPF(3.50)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; MID_CONTAINS_FROM(1.00)[]; NEURAL_SPAM_LONG(1.00)[1.000]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4685, ipnet:202.224.32.0/19, country:JP]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Dec 2020 07:36:30 -0000 >>>>> "Herbert" == Herbert J Skuhra writes: Herbert> On Sat, 05 Dec 2020 05:29:23 +0100, YAMAMOTO Shigeru wrote: >> >> I update my document, "How to start FreeBSD Raspberry Pi 4". >> https://github.com/bsd-hacker/freebsd/wiki/How-to-start-FreeBSD---Raspberry-Pi-4 >> >> I test Raspberry Pi 4B, 4G model and 8G model. >> >> I think to write 'Booting FreeBSD Raspberry Pi 4B from USB disk'. Herbert> You write: Herbert> replace firmware 4 GB memory model Herbert> no more replace fiels. Herbert> And your dmesg for the 4GB model shows: Herbert> real memory = 993820672 (947 MB) avail memory = 943075328 (899 MB) Herbert> So there is obviously something wrong!? Herbert> I have a the 4GB model and I had to replace some files in Herbert> /boot/msdosfs when I set it up a few months ago. Unfortunately with Herbert> newer u-boot.bin from sysutils/u-boot-rpi4 my Raspberry Pi 4B no Herbert> longer boots from microsd card. Error: Herbert> Controller timeout mmcsd0: Error indicated: 1 Timeout unfortunately, need to replace u-boot.bin to detect correct memory size. https://github.com/bsd-hacker/freebsd/wiki/How-to-start-FreeBSD---Raspberry-Pi-4#replace-u-bootbin --- YAMAMOTO Shigeru From owner-freebsd-arm@freebsd.org Sat Dec 5 08:21:00 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CEF334729D9 for ; Sat, 5 Dec 2020 08:21:00 +0000 (UTC) (envelope-from herbert@gojira.at) Received: from mail.bsd4all.net (mail.bsd4all.net [IPv6:2a01:4f8:13b:240c::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail.bsd4all.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Cp2Zz5Fm1z4tnr for ; Sat, 5 Dec 2020 08:20:59 +0000 (UTC) (envelope-from herbert@gojira.at) Date: Sat, 05 Dec 2020 09:20:23 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gojira.at; s=mail202005; t=1607156449; bh=td1O3xlOkafU/pHWK0BDMLitza7VA2ASv/PxA3xEDiU=; h=Date:Message-ID:From:To:Subject:MIME-Version:Content-Type; b=F+6gyXCPaDV79AcEvnD8kwYTR3EdYRr65e0yompfDO+X+j5cZum/EBn69Xh072MLQ TIuV5lOJB099UQWqQFj/1Sw1z2JssfPNUVGsl80c9OGcFkNRa51D4/5nKxsdZEikik nyjbxxgJEj8xtjPegRDnR7nBe9Ro+Ed8Kzy+jQrvS4qcm6GGbw40jU0d+uJijb5o/w GJC8RzAVRcMAyvrZDH0me8ZQDLsypXp3oMyS5ZfwI8uHEAPrVdujf86gpOEQypo5bd u9sExPqW34BgzVgAmf1v5BbqZ5erB1xA/grKyQ0Wzri5bKM5QFVHdmjJFSyhHBKwnx Rmw2ljDgYqUtA== Message-ID: <875z5goe9k.wl-herbert@gojira.at> From: "Herbert J. Skuhra" To: freebsd-arm@freebsd.org Subject: Re: Just getting started with Rasperry PI 4B, 8GB... In-Reply-To: <20201205.163556.71110316527016215.shigeru@os-hackers.jp> References: <465104746.2.1606897670954@localhost> <20201205.132923.139012603584886684.shigeru@os-hackers.jp> <87czzooi3g.wl-herbert@gojira.at> <20201205.163556.71110316527016215.shigeru@os-hackers.jp> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/28.0 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 4Cp2Zz5Fm1z4tnr X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gojira.at header.s=mail202005 header.b=F+6gyXCP; dmarc=none; spf=pass (mx1.freebsd.org: domain of herbert@gojira.at designates 2a01:4f8:13b:240c::25 as permitted sender) smtp.mailfrom=herbert@gojira.at X-Spamd-Result: default: False [-2.50 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gojira.at:s=mail202005]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a01:4f8:13b:240c::25]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[gojira.at]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a01:4f8:13b:240c::25:from:127.0.2.255]; DKIM_TRACE(0.00)[gojira.at:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MID_CONTAINS_FROM(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a01:4f8:13b:240c::25:from]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; MAILMAN_DEST(0.00)[freebsd-arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Dec 2020 08:21:00 -0000 On Sat, 05 Dec 2020 08:35:56 +0100, YAMAMOTO Shigeru wrote: > unfortunately, need to replace u-boot.bin to detect correct memory size. > > https://github.com/bsd-hacker/freebsd/wiki/How-to-start-FreeBSD---Raspberry-Pi-4#replace-u-bootbin Does latest u-boot.bin from sysutils/u-boot-rpi4 work for you? I have no idea why I get a boot error and how to fix it: sdhci_bcm1-slot0: Controller timeout [...] mmcsd0: Error indicated: 1 Timeout Luckily I have a backup of an old version: -rwxr-xr-x 1 root root 506360 May 27 2020 u-boot.bin 7d4502f97416fc5d0b44f34081d8c6b9ff47044f8bb827547b3f1d9525c2d125 u-boot.bin I'll try to replace the microsd card. -- Herbert