From owner-freebsd-arm@freebsd.org Sun Jul 22 08:50:54 2018 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 D00541044D0E for ; Sun, 22 Jul 2018 08:50:53 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (shadow.sentry.org [210.8.237.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "shadow.sentry.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 10D858D716 for ; Sun, 22 Jul 2018 08:50:52 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (localhost [127.0.0.1]) by shadow.sentry.org (8.15.2/8.15.2) with ESMTP id w6M8og9V031661 for ; Sun, 22 Jul 2018 18:50:42 +1000 (AEST) (envelope-from freebsd-arm@sentry.org) Subject: Re: RPI3 swap experiments From: Trev To: freebsd-arm@freebsd.org References: <20180627194217.GA27793@www.zefox.net> <20180628022457.GA30110@www.zefox.net> <7B9D272D-3EDE-46FA-8A1C-AEE65047167C@yahoo.com> <20180628163328.GA33408@www.zefox.net> <51e208b4-9f14-58f7-1e70-6ef8db2c0bed@sentry.org> <20180629155131.GA35717@www.zefox.net> <20180629233937.GC35717@www.zefox.net> <0f137e06-214a-3e8c-a216-f061ec04ac2c@sentry.org> <20180630005145.GA43801@www.zefox.net> <6f3406e2-71f3-d0c2-2b65-703e1a1d3c25@sentry.org> <8e92b2b7-da61-3efb-7231-9fac76b2c1d4@sentry.org> <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> Message-ID: Date: Sun, 22 Jul 2018 18:50:42 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (shadow.sentry.org [0.0.0.0]); Sun, 22 Jul 2018 18:50:42 +1000 (AEST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2018 08:50:54 -0000 Trev wrote on 04/07/2018 07:09: > Ok, the final, final swap experiment. >=20 > I created a 2G swap partition on the SDCard: >=20 > gpart show > =3D>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 63=C2=A0 31116225=C2=A0 mmcsd0=C2=A0= MBR=C2=A0 (15G) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 63=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 2016=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 - free -=C2= =A0 (1.0M) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 2079=C2=A0=C2=A0=C2=A0 102400=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 1=C2=A0 fat32lba=C2=A0 [active]=C2=A0 (50M) > =C2=A0=C2=A0=C2=A0 104479=C2=A0 31011809=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 2=C2=A0 freebsd=C2=A0 (15G) >=20 > =3D>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0=C2=A0 31011809=C2=A0 mmcsd0s= 2=C2=A0 BSD=C2=A0 (15G) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0=C2=A0 25165824=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1=C2=A0 freebsd-ufs=C2=A0 (12G= ) > =C2=A0 25165824=C2=A0=C2=A0 4194304=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 2=C2=A0 freebsd-swap=C2=A0 (2.0G) > =C2=A0 29360128=C2=A0=C2=A0 1651681=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 - free -=C2=A0 (806M) >=20 > and, yes, it still died during make -j4 buildworld: >=20 > Jul=C2=A0 3 22:15:24 rpi3 kernel: pid 57011 (c++), uid 0, was killed: o= ut of=20 > swap space I replaced the SanDisk 16G Ultra (Speed Class 10, UHS Speed Class 1,=20 minimum 10MB/s seq write) used above with a SanDisk 32G Extreme (Speed=20 Class 10, UHS Speed Class 3, minimum 30MB/s seq write) micro-SD card and = now the above configuration survives make -j4 buildworld to end=20 successfully. Twice so far. The configuration is a little different because of the extra space: root@rpi3:~ # gpart show mmcsd0s2 =3D> 0 62229473 mmcsd0s2 BSD (30G) 0 12582912 1 freebsd-ufs (6.0G) [root s2a] 12582912 4194304 2 freebsd-swap (2.0G) [swap s2b] 16777216 12582912 4 freebsd-ufs (6.0G) [home s2d] 29360128 32869345 5 freebsd-ufs (16G) [usr s2e] Note: the SanDisk 32G Extreme I bought at the local (rural) OfficeWorks=20 is "old" stock as it does not have the "application performance class=20 rating" (A1) on it which signifies minimum random read of 1500 IOPS and=20 minimum random write of 500 IOPS. There's also an A2 which signifies=20 minimum random read of 4000 IOPS and minimum random write of 2000 IOPS. Everything subjectively seems snappier. Watching gstat randomly during=20 buildworld I saw no busy percentage greater than 101% and no queue=20 greater than 17, whereas with the Ultra card, I often saw 200-400% with=20 large queues in the 100s. Take the observations in this paragraph with a = grain of evidence-free, anecdotal salt. Trying to determine the real difference between Ultra and Extreme cards=20 was difficult. The best I could come up with were unsupported claims=20 that the Extreme series contain "card controller technology that allows=20 parallel processing of reads and writes" which might just be confusing=20 UHS-I/HC-I (half-duplex) and UHS-II/HC-II (full duplex) bus interfaces. From owner-freebsd-arm@freebsd.org Sun Jul 22 10:00:37 2018 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 38CE010464BC for ; Sun, 22 Jul 2018 10:00:37 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CCF218F367 for ; Sun, 22 Jul 2018 10:00:36 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1fhBAC-0000cE-J1; Sun, 22 Jul 2018 12:00:29 +0200 To: freebsd-arm@freebsd.org, "Nicola Mingotti" Subject: Re: Issues with packages References: <43092f74-f303-35cc-765a-3634f1a90127@gmail.com> Date: Sun, 22 Jul 2018 12:00:32 +0200 MIME-Version: 1.0 From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: ++ X-Spam-Score: 2.0 X-Spam-Status: No, score=2.0 required=5.0 tests=ALL_TRUSTED, BAYES_95, HTML_MESSAGE autolearn=disabled version=3.4.0 X-Scan-Signature: 9fc82074add5d32de548aff89fb3ec1f Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2018 10:00:37 -0000 On Sat, 21 Jul 2018 15:33:59 +0200, Nicola Mingotti wrote: > > > On 07/21/18 12:14, Ronald Klop wrote: >> On Sat, 21 Jul 2018 11:43:00 +0200, Nicola Mingotti >> wrote: >>> >>> Hi all, >>> I am working with FreeBSD-11.1 in BeagleBone Black Rev.C.In the last >>> week I needed to have a webcam streaming from the BBB and i discovered >>> there are some issues with packages. >>> Problem. There are missing popular packages for ARM.For example >>> _ffmpeg_ and _vlc_ but also e.g. _kde..._ >>> I was able to compile the following missing packages from portswithout >>> making any change to the Makefiles.with :#> make -DBATCH install#> >>> make packagefor packages: >>> ------------------------------------------------------------- >>> vlc-2.2.8_6,4.txzffmpeg0-0.7.17_14,1.txzopencv-core-3.4.1_1.txz >>> ffmpeg-4.0.1,1.txzleptonica-1.76.0.txztesseract-3.05.02_1.txz >>> ------------------------------------------------------------- >>> I compiled those packages directly on the BBB with the following >>> caveat.Before running the "make" i was checking all dependenciesof >>> each package in FreshPorts and resolving them one by oneinstalling the >>> relevant *packages*. >>> The reason for this is of course that BBB is very slow, if it hadto >>> recursively compile all stuff it needed for e.g. ffmpg i could never >>> make it. >>> So, if i can compile the packages the central system should also be >>> able to do it. Maybe there are some issues there. >>> Bye >>> >> >> >> I guess BBB is armv6. You can see the build packages here: >> http://pkg.freebsd.org/.Armv6 only has quartely packages. Maybe there >> is a difference in the quarterly packages and a checkout >>of >> /usr/ports which makes vlc, etc. buildable from ports, but is not in >> the quarterly pkgs yet. >> Just an educated guess but I might be wrong. >> There was >> http://portsmon.freebsd.org/portoverview.py?category=multimedia&portname=vlc >> in the past, >>showing why a pkg is not being build, but it is broken >> for a while already. >> Regards,Ronald. > > Thank you for the info Ronald. > > You are correct BBB is ARMv6. (according to uname -p) > Checking http://pkg.freebsd.org/ is actually that, for FreeBSD-11.1 > the directories containing vlc and ffmpeg are: > LATEST --> yes > QUARTERLY ---> no > RELEASE2 --> yes Mind that LATEST is from 2016 (!!) -these are not build due to lack of (fast) resources in armv6-, QUARTERLY from July 2018 (this is actively maintained) and RELEASE_2 from June 2018 (which was apparently a good build in number of packages succeeded and is still quite recent), Packages for armv6 are apparently a bit in a flux. Look here: https://pkg-status.freebsd.org/builds?type=package and search for armv6. It will show that 11.0 pkgs build 23259 pkgs and 11.1 only 542. You can also look here and click 'previous build' to see how much difference there is between different runs of the package building machine. https://pkg-status.freebsd.org/builds/default:quarterly:111armv6:475045:beefy15 Regards, Ronald. > > > So, considering i downloaded the ports with portsnap a few days ago they > shoud be the latest available. > > And my packages must be taken from QUARTERLY, this would make sense, > since i don't see "vlc" and "ffmpeg". > > I have a few newbye question, > -] How do I check from which reposotory/directory my *pkg* is taking the > packages ?-] Is it possible to change it ? > I read around in many man pages but i can't find it. > bye > Nicola > > > ---------------------------- > Dr. Nicola Mingotti > R&D - Borghi Srl > CTO - BondInsider > -------------------------- From owner-freebsd-arm@freebsd.org Sun Jul 22 21:01:20 2018 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 489EC102B13C for ; Sun, 22 Jul 2018 21:01:20 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B665849C7 for ; Sun, 22 Jul 2018 21:01:20 +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 4A13F21D23 for ; Sun, 22 Jul 2018 21:01:19 +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 w6ML1Jjn042887 for ; Sun, 22 Jul 2018 21:01:19 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6ML1JPD042878 for freebsd-arm@FreeBSD.org; Sun, 22 Jul 2018 21:01:19 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201807222101.w6ML1JPD042878@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: freebsd-arm@FreeBSD.org Subject: Problem reports for freebsd-arm@FreeBSD.org that need special attention Date: Sun, 22 Jul 2018 21:01:19 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2018 21:01:20 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 220297 | arch(7) rename arm64 to aarch64 respecting `uname 1 problems total for which you should take action. From owner-freebsd-arm@freebsd.org Mon Jul 23 06:35:13 2018 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 0056C1040B21 for ; Mon, 23 Jul 2018 06:35:13 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6EEE5964B3 for ; Mon, 23 Jul 2018 06:35:12 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w6N6ZRfm045961 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 22 Jul 2018 23:35:28 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w6N6ZR0k045960; Sun, 22 Jul 2018 23:35:27 -0700 (PDT) (envelope-from fbsd) Date: Sun, 22 Jul 2018 23:35:27 -0700 From: bob prohaska To: Trev Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: RPI3 swap experiments Message-ID: <20180723063526.GA45726@www.zefox.net> References: <20180629155131.GA35717@www.zefox.net> <20180629233937.GC35717@www.zefox.net> <0f137e06-214a-3e8c-a216-f061ec04ac2c@sentry.org> <20180630005145.GA43801@www.zefox.net> <6f3406e2-71f3-d0c2-2b65-703e1a1d3c25@sentry.org> <8e92b2b7-da61-3efb-7231-9fac76b2c1d4@sentry.org> <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 06:35:13 -0000 On Sun, Jul 22, 2018 at 06:50:42PM +1000, Trev wrote: > Trev wrote on 04/07/2018 07:09: > > Ok, the final, final swap experiment. > > > > I created a 2G swap partition on the SDCard: > > > > gpart show > > =>?????????? 63?? 31116225?? mmcsd0?? MBR?? (15G) > > ?????????????? 63?????????? 2016?????????????????? - free -?? (1.0M) > > ?????????? 2079?????? 102400???????????? 1?? fat32lba?? [active]?? (50M) > > ?????? 104479?? 31011809???????????? 2?? freebsd?? (15G) > > > > =>???????????? 0?? 31011809?? mmcsd0s2?? BSD?? (15G) > > ???????????????? 0?? 25165824???????????????? 1?? freebsd-ufs?? (12G) > > ?? 25165824???? 4194304???????????????? 2?? freebsd-swap?? (2.0G) > > ?? 29360128???? 1651681?????????????????????? - free -?? (806M) > > > > and, yes, it still died during make -j4 buildworld: > > > > Jul?? 3 22:15:24 rpi3 kernel: pid 57011 (c++), uid 0, was killed: out of > > swap space > > I replaced the SanDisk 16G Ultra (Speed Class 10, UHS Speed Class 1, > minimum 10MB/s seq write) used above with a SanDisk 32G Extreme (Speed > Class 10, UHS Speed Class 3, minimum 30MB/s seq write) micro-SD card and > now the above configuration survives make -j4 buildworld to end > successfully. Twice so far. > > The configuration is a little different because of the extra space: > > root@rpi3:~ # gpart show mmcsd0s2 > => 0 62229473 mmcsd0s2 BSD (30G) > 0 12582912 1 freebsd-ufs (6.0G) [root s2a] > 12582912 4194304 2 freebsd-swap (2.0G) [swap s2b] > 16777216 12582912 4 freebsd-ufs (6.0G) [home s2d] > 29360128 32869345 5 freebsd-ufs (16G) [usr s2e] > > Note: the SanDisk 32G Extreme I bought at the local (rural) OfficeWorks > is "old" stock as it does not have the "application performance class > rating" (A1) on it which signifies minimum random read of 1500 IOPS and > minimum random write of 500 IOPS. There's also an A2 which signifies > minimum random read of 4000 IOPS and minimum random write of 2000 IOPS. > > Everything subjectively seems snappier. Watching gstat randomly during > buildworld I saw no busy percentage greater than 101% and no queue > greater than 17, whereas with the Ultra card, I often saw 200-400% with > large queues in the 100s. Take the observations in this paragraph with a > grain of evidence-free, anecdotal salt. > > Trying to determine the real difference between Ultra and Extreme cards > was difficult. The best I could come up with were unsupported claims > that the Extreme series contain "card controller technology that allows > parallel processing of reads and writes" which might just be confusing > UHS-I/HC-I (half-duplex) and UHS-II/HC-II (full duplex) bus interfaces. > There is some reason to think "newer" Sandisk Extreme devices differ, perhaps in a bad way, from older devices. The older device in my tests is model SDCZ80-064G and is simply labeled USB3.0. The newer, troublesome device is model SDCZ800-064G and is labeled Extreme Go USB 3.1. There are reports that the Extreme Go is slower, advising to buy the older devices if possible. The USB3.1 flash drive is back in test, with the results of a j4 buildworld under r336567 at http://www.zefox.net/~fbsd/rpi3/swaptests/r336567/ The worst case results are still fairly dismal, close to a minute. All the swap was on microSD, so OOMA didn't strike and buildworld completed successfully. Near as I can tell no errors were reported on the console. Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Mon Jul 23 07:08:57 2018 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 92944104153C for ; Mon, 23 Jul 2018 07:08:57 +0000 (UTC) (envelope-from peo@nethead.se) Received: from ns1.nethead.se (ns1.nethead.se [5.150.237.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns1.nethead.se", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C57897282 for ; Mon, 23 Jul 2018 07:08:57 +0000 (UTC) (envelope-from peo@nethead.se) X-Virus-Scanned: amavisd-new at Nethead AB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nethead.se; s=NETHEADSE; t=1532329729; bh=I6ytDwuzFJMdYmNJyBs3GobyEnOKkKMK0QIykKwmp68=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=xvGezVjyH/oYD6yPkzN+p+KYkndr6XNU7DqHb7Ahyl5KbnZ5tere3jn6R9Y+QTGqY +5QOH9SCVfizDQJ410m9vzLrjj3erhmiRnGpEVnvhZfUtv7eYyfQius8wSDJCeRxlL xa9+PJ/Rcnaq0x4mWbjLH3dCF9BHYO18UPo33id8= Subject: Re: rpi3 and Adafruit GPS Hat To: Diane Bruce Cc: freebsd-arm@freebsd.org References: <47f49a55-66b0-1c02-4530-4701a3bd0c43@nethead.se> <20180718170157.GA40221@night.db.net> From: Per olof Ljungmark Message-ID: Date: Mon, 23 Jul 2018 09:08:47 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180718170157.GA40221@night.db.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 07:08:57 -0000 On 07/18/18 19:01, Diane Bruce wrote: > On Wed, Jul 18, 2018 at 05:10:16PM +0200, Per olof Ljungmark wrote: >> Being a complete newbie to arm I thought a nice project would be to >> build a NTP server with the parts in the subject line. >> >> Unfortunately I have almost no idea where to start, it seems FreeBSD for >> arm have shifted around quite a bit, almost none of the googled pages I >> find has relevance, and to add insult to injury, the Pi project >> apparently shifted the serial ports around for the Pi3. >> >> What I need to achieve, >> >> - Stop the kernel to use the uart for console output (I have ethernet >> and HDMI connected) > > No need. > > change your config.txt > > #dtoverlay=pi3-disable-bt > device_tree_address=0x4000 > kernel=u-boot.bin > enable_uart=1 > > This moves the console port to the less capable micro uart port > this will free up the good uart (the pl011 device) as /dev/ttyu0 > > Remove the pi3-disable-dt in config.txt > enable_uart=1 is needed. > >> VERY grateful if someone that knows better can give me a push in the >> right direction for up to date information. > .. > > This is assuming you use FreeBSD-12 (Head of tree) > Yes, 12.0-CURRENT #2 r336461. Unfortunately your advice did not solve the problem, when the hat is attached it sends NMEA sequences to the u-boot loader making it impossible to boot further, just like it is described in this thread: http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-shield-on-a-Raspberry-Pi-td6236680.html From owner-freebsd-arm@freebsd.org Mon Jul 23 07:11:24 2018 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 12BEB1041776 for ; Mon, 23 Jul 2018 07:11:24 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic309-15.consmr.mail.bf2.yahoo.com (sonic309-15.consmr.mail.bf2.yahoo.com [74.6.129.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A95EB974E2 for ; Mon, 23 Jul 2018 07:11:23 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: 6KRgLj8VM1kyAXjZxHFLl2aE6I.oet3CwssrLXwJFk8Mkqcp8OXmGfiRnpWhiOb vRDVnFWxGY1M1.KfF3bmg0143CHHlzAqtPYqCOLH8rUVVfrTd7.ghAiC7b71MLQ1u0jrTY_x2d9Q z.2MOoavz31xG.PXV2qxeuBW1BUaKUhXPds7xkvBLc4V4Yz7M5E.6JcQJHMWAWv.Pk20RqDIkwvX aa0qHgGveTcHn9O6ijUDTd1otw9sZsrfLr5gwejElamNBwtXJ4_L29saj_98xLZSNlggY9IP4aBY q47D0w5rQF2MfLkuLPmWefnTiXp6t7kJbSrEDDlY2ccO0Ed90s9x0ADCXF9Tb_aq9Mfc9pAyxq18 tVoDGjqNSqMbiO2bKTQdLrhNwLbFC8d2Yxtzg683_xsOGYjPp2e5mFPKJBrxlJ00s5eSBITQ4xlE 3kzNQcP4HmBiiZRIYId3vDYpiUqU5_fD1XPsplx1qVNV9alwUmSfnwvGkTqk.TIj5gU4qc8FNBKs aHwK1zNGVDTLBEIjSYYpQQ.EfqV53YYADCYqx9gn4t3x5gQTI.e7Ep91_Ogyok6IoqsnuHLAhS2W cJJdAAPaFytcN3t.9Sz_nQSW0WODdLhbTvsX6v.4vr8YSmtukSuON4NsTgRt523yvE3p2y4TEm2r BVwMbxVSjFLJtvUzNg782Rd1n3SDmsfkqFujud_sdFDBwm2j6pUZL4rfZkbAJPRkTCtNHnolqtpX Eg76LjCMXnfAbKaOvPIWz_gziURuJbc0C9auLcV_h1wJUWeDXHZn5.3Ruigaz9ugkVWjZzJ_pG0q GEUpgEX1.5EcrHy6TzJptAIU4BAkp8B01Gl.ivhiBG3.AsGNODG.WjOZVlebj1Mk5F0gfAbZ1kPH UABYDXRcONYAggqB92cqJ_bHfNTgJP3kLyz9EqdqFLNQB_3BHggm7TDgIZdakEl9RA4QT6vLfyFk AYRftpa6RqO4brsbPrDMte9UawqMhwuOPsvSIbjaRgZQEwmqMR4N.KgUKBCXYPzQEvSqZpRymJCS ek7Ky.jYTB9I- Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.bf2.yahoo.com with HTTP; Mon, 23 Jul 2018 07:11:23 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp419.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 6df567a113bf4bf8f40fe7a235a0dc4a; Mon, 23 Jul 2018 07:11:21 +0000 (UTC) From: Mark Millard Message-Id: Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: RPI3 swap experiments Date: Mon, 23 Jul 2018 00:11:19 -0700 In-Reply-To: <20180723063526.GA45726@www.zefox.net> Cc: Trev , freebsd-arm@freebsd.org To: bob prohaska References: <20180629155131.GA35717@www.zefox.net> <20180629233937.GC35717@www.zefox.net> <0f137e06-214a-3e8c-a216-f061ec04ac2c@sentry.org> <20180630005145.GA43801@www.zefox.net> <6f3406e2-71f3-d0c2-2b65-703e1a1d3c25@sentry.org> <8e92b2b7-da61-3efb-7231-9fac76b2c1d4@sentry.org> <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> <20180723063526.GA45726@www.zefox.net> X-Mailer: Apple Mail (2.3445.9.1) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 07:11:24 -0000 On 2018-Jul-22, at 11:35 PM, bob prohaska wrote: >> . . . > There is some reason to think "newer" Sandisk Extreme devices differ, = perhaps > in a bad way, from older devices. The older device in my tests is = model > SDCZ80-064G and is simply labeled USB3.0. The newer, troublesome = device > is model SDCZ800-064G and is labeled Extreme Go USB 3.1. There are = reports > that the Extreme Go is slower, advising to buy the older devices if = possible. >=20 > The USB3.1 flash drive is back in test, with the results of a j4 = buildworld > under r336567 at > http://www.zefox.net/~fbsd/rpi3/swaptests/r336567/ >=20 > The worst case results are still fairly dismal, close to a minute. All = the > swap was on microSD, so OOMA didn't strike and buildworld completed = successfully. > Near as I can tell no errors were reported on the console. Rebuilds that do not rebuild the llvm materials (clang, lld, lldb, etc.) = are not all that comparable to ones that do. (This is visible in the time differences in = the builds that complete.) The llvm related build activity likely involves most of the = potential swapping, for example. Also: lots of I/O. There can be two rebuilds of some of the llvm material. One stage with = such is the cross-compiler: --- buildworld --- make[1]: "/usr/src/Makefile.inc1" line 341: SYSTEM_COMPILER: Determined = that CC=3Dcc matches the source tree. Not bootstrapping a = cross-compiler. make[1]: "/usr/src/Makefile.inc1" line 346: SYSTEM_LINKER: Determined = that LD=3Dld matches the source tree. Not bootstrapping a cross-linker. (it was not rebuilt in the example). The other involves the build of the = system llvm materials for use in the (potentially) installed system, such as the system's clang. Taking an environment that worked for lack of llvm related rebuilds may = not well indicate the result for rebuilds that would try to rebuild the llvm = related materials. It is something to consider in what builds are compared, how they are compared, and what one infers from comparisons. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Mon Jul 23 08:39:28 2018 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 0A81C1043861 for ; Mon, 23 Jul 2018 08:39:28 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8FEFD71EB0 for ; Mon, 23 Jul 2018 08:39:27 +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 D386827DA6 for ; Mon, 23 Jul 2018 08:39:26 +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 w6N8dQjP068410 for ; Mon, 23 Jul 2018 08:39:26 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6N8dQtQ068409 for freebsd-arm@FreeBSD.org; Mon, 23 Jul 2018 08:39:26 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 229976] Make it easier to disable the serial console on arm Date: Mon, 23 Jul 2018 08:39:26 +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 Only Me X-Bugzilla-Who: peo@nethead.se 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.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 08:39:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229976 Bug ID: 229976 Summary: Make it easier to disable the serial console on arm Product: Base System Version: CURRENT Hardware: arm OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: peo@nethead.se The serial console is enabled by default on ARM for obvious reasons. However, if you need the uart for other tasks, it is very complicated to disable the serial console when it is hardwired in more than one place. I wish we could have something similar to Linux where you can just edit config.txt and cmdline.txt to achieve this. This thread pretty much sums it up: http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-shield-on-a-Ra= spberry-Pi-td6236680.html --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Mon Jul 23 08:47:07 2018 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 EEFF41043BCF for ; Mon, 23 Jul 2018 08:47:06 +0000 (UTC) (envelope-from dave@dogwood.com) Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 806DD72396 for ; Mon, 23 Jul 2018 08:47:06 +0000 (UTC) (envelope-from dave@dogwood.com) Received: by mail-oi0-x236.google.com with SMTP id k12-v6so31851415oiw.8 for ; Mon, 23 Jul 2018 01:47:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dogwood.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iIbxfEcJaJN6J3tKXvXyU0q3NSx4PMzipmp/QLWQox4=; b=kBKiVKaM2KBF/1aM0zZn57OlWClc5vno9+vV/aNl/s9iH5NupAQV7ix7hmfA68SkDf AwxIz+fUDhkVLe6wEFJ9LxfON73bFGfp+q17cPeK/IyVnofqxb0+gR1aeymcXeR8nnWe B9h78WrXjJZMG5AWUTyeaEfkG0Hk4JCWMPicw= 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=iIbxfEcJaJN6J3tKXvXyU0q3NSx4PMzipmp/QLWQox4=; b=unTlq556e5151VxUB9vpcvYHW6PgRduZ8hUsLfWQzIIDuEoREbQOFJuw7OjuJjEqps HYJhy/EFCtYvUkqcEFkY1B6BIGnNAtj7xZsSrp46FojJP+VQ8UngolL/W8ctyqr0aUeD C9m6Ock0pMl3jL+At4ex66HbIdzyv5/BhP8sSZwA3mRgM1rTHmLITnzmQEV2KblsR9cy aALifXD3GItzEY51QP94PhzUFMh+h2r/Vu8YYBEsU1vz7Npf5hZ4GaZ0O0b1l2HJGY7Q BuKDi82DFRkiqXkDBzZcVMt141rQPPL1tAN9gePijs4KNL4ruvf9EMHafYRZWTCno0uT Rx9A== X-Gm-Message-State: AOUpUlE08pXhu31skY+ZJOq3gZgT67Gh1oEFA4M5K/ecqGNRtsp3GJo+ NfOh0M2s5WhFVUbH+JkZThFhVOcXEdEUuxA0xUbhZKn0 X-Google-Smtp-Source: AAOMgpdKjzcVP76yJWp6pxQybhssmLLrJcbK9H47AyR0NP3/An7O9ER0yBDfmkQOjG0EOsQ5jAwJcdXujerhI0kk3zI= X-Received: by 2002:aca:e2d3:: with SMTP id z202-v6mr8166604oig.121.1532335624210; Mon, 23 Jul 2018 01:47:04 -0700 (PDT) MIME-Version: 1.0 References: <47f49a55-66b0-1c02-4530-4701a3bd0c43@nethead.se> <20180718170157.GA40221@night.db.net> In-Reply-To: From: David Cornejo Date: Sun, 22 Jul 2018 22:46:53 -1000 Message-ID: Subject: Re: rpi3 and Adafruit GPS Hat To: peo@nethead.se Cc: db@db.net, freebsd-arm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 08:47:07 -0000 this might be a little blasphemous, but for grins I tried an Oncore with PPS to a GPIO and running the serial through a TTL-USB serial cable and that seems to work ok. there's probably some good reason that this is a bad idea. dave c On Sun, Jul 22, 2018 at 9:09 PM Per olof Ljungmark wrote: > On 07/18/18 19:01, Diane Bruce wrote: > > On Wed, Jul 18, 2018 at 05:10:16PM +0200, Per olof Ljungmark wrote: > >> Being a complete newbie to arm I thought a nice project would be to > >> build a NTP server with the parts in the subject line. > >> > >> Unfortunately I have almost no idea where to start, it seems FreeBSD f= or > >> arm have shifted around quite a bit, almost none of the googled pages = I > >> find has relevance, and to add insult to injury, the Pi project > >> apparently shifted the serial ports around for the Pi3. > >> > >> What I need to achieve, > >> > >> - Stop the kernel to use the uart for console output (I have ethernet > >> and HDMI connected) > > > > No need. > > > > change your config.txt > > > > #dtoverlay=3Dpi3-disable-bt > > device_tree_address=3D0x4000 > > kernel=3Du-boot.bin > > enable_uart=3D1 > > > > This moves the console port to the less capable micro uart port > > this will free up the good uart (the pl011 device) as /dev/ttyu0 > > > > Remove the pi3-disable-dt in config.txt > > enable_uart=3D1 is needed. > > > >> VERY grateful if someone that knows better can give me a push in the > >> right direction for up to date information. > > .. > > > > This is assuming you use FreeBSD-12 (Head of tree) > > > > Yes, 12.0-CURRENT #2 r336461. > > Unfortunately your advice did not solve the problem, when the hat is > attached it sends NMEA sequences to the u-boot loader making it > impossible to boot further, just like it is described in this thread: > > > http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-shield-on-a-= Raspberry-Pi-td6236680.html > > > _______________________________________________ > 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" > --=20 Kailua, Hawai=CA=BBi US +1 (808) 728-3050 UK +44 (020) 3286 2808 From owner-freebsd-arm@freebsd.org Mon Jul 23 09:40:22 2018 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 F18501045486 for ; Mon, 23 Jul 2018 09:40:21 +0000 (UTC) (envelope-from peo@nethead.se) Received: from ns1.nethead.se (ns1.nethead.se [5.150.237.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns1.nethead.se", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C44A7482E for ; Mon, 23 Jul 2018 09:40:21 +0000 (UTC) (envelope-from peo@nethead.se) X-Virus-Scanned: amavisd-new at Nethead AB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nethead.se; s=NETHEADSE; t=1532338820; bh=OteSV5Zm0iG1KQhmL6oxZvVA6cBkgsg/mozyOet+gxo=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=3u6C+Na5rQewjbx8/ESX/CiuSYKoExHu8lvd1+owv+/4G1YS3QwJvZGl9t+pGgXRv ZmcFJlaQ5c7Bna/usjnBr8IrFh0gl1H4blNaku14MO4WlOqKaXV9d73SI+6KXb+2lO RaWvEamWm3p7ODp0WdSbnu07mYckFHr5R3KzTs58= Subject: Re: rpi3 and Adafruit GPS Hat To: David Cornejo Cc: db@db.net, freebsd-arm References: <47f49a55-66b0-1c02-4530-4701a3bd0c43@nethead.se> <20180718170157.GA40221@night.db.net> From: Per olof Ljungmark Message-ID: <7a14173c-cc28-6dc7-3787-a5b77a396b30@nethead.se> Date: Mon, 23 Jul 2018 11:40:17 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 09:40:22 -0000 On 07/23/18 10:46, David Cornejo wrote: > this might be a little blasphemous, but for grins I tried an Oncore with > PPS to a GPIO and running the serial through a TTL-USB serial cable and > that seems to work ok. > > there's probably some good reason that this is a bad idea. Depends on what precision you are after, but for lowest possible jitter you need to use the uart, the difference is in magnitudes. > On Sun, Jul 22, 2018 at 9:09 PM Per olof Ljungmark > wrote: > > On 07/18/18 19:01, Diane Bruce wrote: > > On Wed, Jul 18, 2018 at 05:10:16PM +0200, Per olof Ljungmark wrote: > >> Being a complete newbie to arm I thought a nice project would be to > >> build a NTP server with the parts in the subject line. > >> > >> Unfortunately I have almost no idea where to start, it seems > FreeBSD for > >> arm have shifted around quite a bit, almost none of the googled > pages I > >> find has relevance, and to add insult to injury, the Pi project > >> apparently shifted the serial ports around for the Pi3. > >> > >> What I need to achieve, > >> > >> - Stop the kernel to use the uart for console output (I have ethernet > >> and HDMI connected) > > > > No need. > > > > change your config.txt > > > > #dtoverlay=pi3-disable-bt > > device_tree_address=0x4000 > > kernel=u-boot.bin > > enable_uart=1 > > > > This moves the console port to the less capable micro uart port > > this will free up the good uart (the pl011 device) as /dev/ttyu0 > > > > Remove the pi3-disable-dt in config.txt > > enable_uart=1 is needed. > > > >> VERY grateful if someone that knows better can give me a push in the > >> right direction for up to date information. > > .. > > > > This is assuming you use FreeBSD-12 (Head of tree) > > > > Yes, 12.0-CURRENT #2 r336461. > > Unfortunately your advice did not solve the problem, when the hat is > attached it sends NMEA sequences to the u-boot loader making it > impossible to boot further, just like it is described in this thread: > > http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-shield-on-a-Raspberry-Pi-td6236680.html > > > _______________________________________________ > 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 > " > > > > -- > Kailua, HawaiÊ»i > US +1 (808) 728-3050 > UK +44 (020) 3286 2808 > From owner-freebsd-arm@freebsd.org Mon Jul 23 14:46:24 2018 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 C4811104CBA9 for ; Mon, 23 Jul 2018 14:46:23 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 3DF6B7F373 for ; Mon, 23 Jul 2018 14:46:23 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: 27c90b48-8e87-11e8-aff6-0b9b8210da61 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 outbound1.eu.mailhop.org (Halon) with ESMTPSA id 27c90b48-8e87-11e8-aff6-0b9b8210da61; Mon, 23 Jul 2018 14:46:19 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w6NEkHab013115; Mon, 23 Jul 2018 08:46:17 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1532357176.1344.130.camel@freebsd.org> Subject: Re: rpi3 and Adafruit GPS Hat From: Ian Lepore To: Per olof Ljungmark , David Cornejo Cc: freebsd-arm Date: Mon, 23 Jul 2018 08:46:16 -0600 In-Reply-To: <7a14173c-cc28-6dc7-3787-a5b77a396b30@nethead.se> References: <47f49a55-66b0-1c02-4530-4701a3bd0c43@nethead.se> <20180718170157.GA40221@night.db.net> <7a14173c-cc28-6dc7-3787-a5b77a396b30@nethead.se> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 14:46:24 -0000 On Mon, 2018-07-23 at 11:40 +0200, Per olof Ljungmark wrote: > On 07/23/18 10:46, David Cornejo wrote: > > > > this might be a little blasphemous, but for grins I tried an Oncore with > > PPS to a GPIO and running the serial through a TTL-USB serial cable and > > that seems to work ok. > > > > there's probably some good reason that this is a bad idea. > Depends on what precision you are after, but for lowest possible jitter > you need to use the uart, the difference is in magnitudes. > Technically that may be correct, but it's meaningless. On a usb 1.x adapter there may be ~500us of jitter from one measurement to the next. On a usb 2.x adapter the jitter drops to typically ~60us. Those values are pretty much in the noise for ntpd, which uses a median filter to smooth any serious jitter out of the measurements. Here are some real-world measurements. The pps source for all 3 inputs is the same gps-disciplined rubidium oscillator, so all the jitter is within the uart, usb hardware, and freebsd drivers. The usb adapters are both FTDI chips, which have a fixed latency on reporting a change on the DCD pin (pin-change status messages are only delivered once a millisecond on ftdi chips).      remote      refid   st t when poll reach   delay   offset  jitter ====================================================================== xPPS(0)          .uart.   0 l    6   16  377    0.000    1.097   0.001 xPPS(1)          .usb1.   0 l    4   16  377    0.000   -0.051   0.773 oPPS(2)          .usb2.   0 l    4   16  377    0.000   -0.001   0.035 *dvb.hippie.lan  .GPS.    1 u   12   64  377    1.234    1.296   2.707 +utcnist2.colora .NIST.   1 u    1   64  377   13.605    3.940   2.729 You can see in this case ntpd actually chose the usb2 pps input as the system peer. It did so because at startup the clock offset was closer than the uart, and the difference in jitter between the two wasn't significant, so the ntpd code that prevents clock-hopping chose to stick with the peer with the smaller offset. -- Ian > > > > On Sun, Jul 22, 2018 at 9:09 PM Per olof Ljungmark > > wrote: > > > >     On 07/18/18 19:01, Diane Bruce wrote: > >     > On Wed, Jul 18, 2018 at 05:10:16PM +0200, Per olof Ljungmark > > wrote: > >     >> Being a complete newbie to arm I thought a nice project > > would be to > >     >> build a NTP server with the parts in the subject line. > >     >> > >     >> Unfortunately I have almost no idea where to start, it seems > >     FreeBSD for > >     >> arm have shifted around quite a bit, almost none of the > > googled > >     pages I > >     >> find has relevance, and to add insult to injury, the Pi > > project > >     >> apparently shifted the serial ports around for the Pi3. > >     >> > >     >> What I need to achieve, > >     >> > >     >> - Stop the kernel to use the uart for console output (I have > > ethernet > >     >> and HDMI connected) > >     > > >     > No need. > >     > > >     > change your config.txt > >     > > >     > #dtoverlay=pi3-disable-bt > >     > device_tree_address=0x4000 > >     > kernel=u-boot.bin > >     > enable_uart=1 > >     > > >     > This moves the console port to the less capable micro uart > > port > >     > this will free up the good uart (the pl011 device) as > > /dev/ttyu0 > >     > > >     > Remove the pi3-disable-dt in config.txt > >     > enable_uart=1 is needed. > >     > > >     >> VERY grateful if someone that knows better can give me a > > push in the > >     >> right direction for up to date information. > >     > .. > >     > > >     > This is assuming you use FreeBSD-12 (Head of tree) > >     > > > > >     Yes, 12.0-CURRENT #2 r336461. > > > >     Unfortunately your advice did not solve the problem, when the > > hat is > >     attached it sends NMEA sequences to the u-boot loader making it > >     impossible to boot further, just like it is described in this > > thread: > > > >     http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-sh > > ield-on-a-Raspberry-Pi-td6236680.html > > > > > >     _______________________________________________ > >     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 Jul 23 14:55:20 2018 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 8E56F104CFC6 for ; Mon, 23 Jul 2018 14:55:20 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0D1A37FAB4 for ; Mon, 23 Jul 2018 14:55:19 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=dNw21FXTwojaBrgILaiMlgcEvmzO+jFxEtazfRaSVlI=; b=TQldLazTtF4gN3vlXik7s1IFUgRvkJuZcf6RuqbpdbZvEKJz/zo0jeQqvNmP/ksmy5TekAWXdWqY2RXZxfLG9TAiYYyfyTO+NGN7igvccACvAQjznU81s7alVffOm/vbdu06M6g10pZ+fFEzGumKp7eCP81DK8BiiDQPpL1KX14= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 8b61aa6c TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO for ; Mon, 23 Jul 2018 14:55:11 +0000 (UTC) Date: Mon, 23 Jul 2018 17:55:01 +0300 From: Greg V Subject: Scaleway ARM64 VPS can be depenguinated! To: freebsd-arm@freebsd.org Message-Id: <1532357701.75524.1@hraggstad.unrelenting.technology> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 14:55:20 -0000 Hi everyone, I managed to run FreeBSD on Scaleway's cheap ThunderX KVM virtual servers. The full notes are on their forum: https://community.online.net/t/freebsd-on-arm64/6678 tl;dr: - run Ubuntu, copy root fs to a tmpfs, pivot_root into the tmpfs - download memstick image, dd it onto the disk - resize the GPT using gdisk from 2 to 4 entries (related bug in geom/gpart: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229977) - reboot, 'set console=comconsole,efi' and 'boot' - install, using shell for partitioning, create a ZFS partition after the installer one - in the post-install chroot, add 'opensolaris_load="YES"' and 'console="comconsole,efi"' to /boot/loader.conf and 'zfs_enable="YES"' to /etc/rc.conf - reboot and it works! From owner-freebsd-arm@freebsd.org Mon Jul 23 15:20:21 2018 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 3EAEE104DA92 for ; Mon, 23 Jul 2018 15:20:21 +0000 (UTC) (envelope-from peo@nethead.se) Received: from ns1.nethead.se (ns1.nethead.se [5.150.237.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns1.nethead.se", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C64BA80FED; Mon, 23 Jul 2018 15:20:20 +0000 (UTC) (envelope-from peo@nethead.se) X-Virus-Scanned: amavisd-new at Nethead AB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nethead.se; s=NETHEADSE; t=1532359216; bh=XqIpecbsQBSIwW5TOoFpBUChJJbz535QXHp6cAvMFNE=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=w9eNBfe9ViUGKQT1agZ3PjjAeyqrJOUa/sJl7y2KZDnZIxU0PYpBwW7vbV9PJZd/Y cMBrIrVjpZiWXKRzEqD7k56ptVBMeWHPe3K30RYsijhXIckBYfbyic5k0aDVgAJZOF bLtCFufJ8V89luKYAEAtvcfxN0tr+0sIFY2jGhZw= Subject: Re: rpi3 and Adafruit GPS Hat To: Ian Lepore , David Cornejo Cc: freebsd-arm References: <47f49a55-66b0-1c02-4530-4701a3bd0c43@nethead.se> <20180718170157.GA40221@night.db.net> <7a14173c-cc28-6dc7-3787-a5b77a396b30@nethead.se> <1532357176.1344.130.camel@freebsd.org> From: Per olof Ljungmark Message-ID: Date: Mon, 23 Jul 2018 17:20:13 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <1532357176.1344.130.camel@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 15:20:21 -0000 On 07/23/18 16:46, Ian Lepore wrote: > On Mon, 2018-07-23 at 11:40 +0200, Per olof Ljungmark wrote: >> On 07/23/18 10:46, David Cornejo wrote: >>> >>> this might be a little blasphemous, but for grins I tried an Oncore with >>> PPS to a GPIO and running the serial through a TTL-USB serial cable and >>> that seems to work ok. >>> >>> there's probably some good reason that this is a bad idea. >> Depends on what precision you are after, but for lowest possible jitter >> you need to use the uart, the difference is in magnitudes. >> > > Technically that may be correct, but it's meaningless. On a usb 1.x > adapter there may be ~500us of jitter from one measurement to the next. > On a usb 2.x adapter the jitter drops to typically ~60us. Those values > are pretty much in the noise for ntpd, which uses a median filter to > smooth any serious jitter out of the measurements. > > Here are some real-world measurements. The pps source for all 3 inputs > is the same gps-disciplined rubidium oscillator, so all the jitter is > within the uart, usb hardware, and freebsd drivers. The usb adapters > are both FTDI chips, which have a fixed latency on reporting a change > on the DCD pin (pin-change status messages are only delivered once a > millisecond on ftdi chips). > >      remote      refid   st t when poll reach   delay   offset  jitter > ====================================================================== > xPPS(0)          .uart.   0 l    6   16  377    0.000    1.097   0.001 > xPPS(1)          .usb1.   0 l    4   16  377    0.000   -0.051   0.773 > oPPS(2)          .usb2.   0 l    4   16  377    0.000   -0.001   0.035 > *dvb.hippie.lan  .GPS.    1 u   12   64  377    1.234    1.296   2.707 > +utcnist2.colora .NIST.   1 u    1   64  377   13.605    3.940   2.729 > > You can see in this case ntpd actually chose the usb2 pps input as the > system peer. It did so because at startup the clock offset was closer > than the uart, and the difference in jitter between the two wasn't > significant, so the ntpd code that prevents clock-hopping chose to > stick with the peer with the smaller offset. > Yes, I was technically correct but of course you are right too - however, the main problem is not the jitter but rather that I am unable to switch off the serial console and stop the u-boot loader from receiving NMEA data. The Adafruit GPS Hat is made to sit right on the Pi 40-pin header, as you probably know. To quote one of the posters in the thread I linked to: "... I am seriously baffled by how difficult (nearly impossible) it had been to get rid of the serial console..." Unfortunately I am not fluid enough to figure out where to make the changes, the advices I've seen so far is not applicable to 12-CURRENT in an easy way. And that is also why I wrote bugreport 229976. It may be that all the folks involved with FreeBSD/ARM are serious developers so they do not see it as a problem but for me it is, being more on the application/administration side of things. Thanks, //per >>> >>> On Sun, Jul 22, 2018 at 9:09 PM Per olof Ljungmark >> > wrote: >>> >>>     On 07/18/18 19:01, Diane Bruce wrote: >>>     > On Wed, Jul 18, 2018 at 05:10:16PM +0200, Per olof Ljungmark >>> wrote: >>>     >> Being a complete newbie to arm I thought a nice project >>> would be to >>>     >> build a NTP server with the parts in the subject line. >>>     >> >>>     >> Unfortunately I have almost no idea where to start, it seems >>>     FreeBSD for >>>     >> arm have shifted around quite a bit, almost none of the >>> googled >>>     pages I >>>     >> find has relevance, and to add insult to injury, the Pi >>> project >>>     >> apparently shifted the serial ports around for the Pi3. >>>     >> >>>     >> What I need to achieve, >>>     >> >>>     >> - Stop the kernel to use the uart for console output (I have >>> ethernet >>>     >> and HDMI connected) >>>     > >>>     > No need. >>>     > >>>     > change your config.txt >>>     > >>>     > #dtoverlay=pi3-disable-bt >>>     > device_tree_address=0x4000 >>>     > kernel=u-boot.bin >>>     > enable_uart=1 >>>     > >>>     > This moves the console port to the less capable micro uart >>> port >>>     > this will free up the good uart (the pl011 device) as >>> /dev/ttyu0 >>>     > >>>     > Remove the pi3-disable-dt in config.txt >>>     > enable_uart=1 is needed. >>>     > >>>     >> VERY grateful if someone that knows better can give me a >>> push in the >>>     >> right direction for up to date information. >>>     > .. >>>     > >>>     > This is assuming you use FreeBSD-12 (Head of tree) >>>     > >>> >>>     Yes, 12.0-CURRENT #2 r336461. >>> >>>     Unfortunately your advice did not solve the problem, when the >>> hat is >>>     attached it sends NMEA sequences to the u-boot loader making it >>>     impossible to boot further, just like it is described in this >>> thread: >>> >>>     http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-sh >>> ield-on-a-Raspberry-Pi-td6236680.html >>> >>> >>>     _______________________________________________ >>>     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 Jul 23 15:24:44 2018 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 8F8EE104DD97 for ; Mon, 23 Jul 2018 15:24:44 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 18E528140E for ; Mon, 23 Jul 2018 15:24:43 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: 83408b58-8e8c-11e8-aff6-0b9b8210da61 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 outbound1.eu.mailhop.org (Halon) with ESMTPSA id 83408b58-8e8c-11e8-aff6-0b9b8210da61; Mon, 23 Jul 2018 15:24:39 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w6NFOcGK013224; Mon, 23 Jul 2018 09:24:38 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1532359478.1344.142.camel@freebsd.org> Subject: Re: rpi3 and Adafruit GPS Hat From: Ian Lepore To: Per olof Ljungmark , David Cornejo Cc: freebsd-arm Date: Mon, 23 Jul 2018 09:24:38 -0600 In-Reply-To: References: <47f49a55-66b0-1c02-4530-4701a3bd0c43@nethead.se> <20180718170157.GA40221@night.db.net> <7a14173c-cc28-6dc7-3787-a5b77a396b30@nethead.se> <1532357176.1344.130.camel@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 15:24:44 -0000 On Mon, 2018-07-23 at 17:20 +0200, Per olof Ljungmark wrote: > On 07/23/18 16:46, Ian Lepore wrote: > > > > On Mon, 2018-07-23 at 11:40 +0200, Per olof Ljungmark wrote: > > > > > > On 07/23/18 10:46, David Cornejo wrote: > > > > > > > > > > > > this might be a little blasphemous, but for grins I tried an Oncore with > > > > PPS to a GPIO and running the serial through a TTL-USB serial cable and > > > > that seems to work ok. > > > > > > > > there's probably some good reason that this is a bad idea. > > > Depends on what precision you are after, but for lowest possible jitter > > > you need to use the uart, the difference is in magnitudes. > > > > > Technically that may be correct, but it's meaningless. On a usb 1.x > > adapter there may be ~500us of jitter from one measurement to the next. > > On a usb 2.x adapter the jitter drops to typically ~60us. Those values > > are pretty much in the noise for ntpd, which uses a median filter to > > smooth any serious jitter out of the measurements. > > > > Here are some real-world measurements. The pps source for all 3 inputs > > is the same gps-disciplined rubidium oscillator, so all the jitter is > > within the uart, usb hardware, and freebsd drivers. The usb adapters > > are both FTDI chips, which have a fixed latency on reporting a change > > on the DCD pin (pin-change status messages are only delivered once a > > millisecond on ftdi chips). > > > >      remote      refid   st t when poll reach   delay   offset  jitter > > ====================================================================== > > xPPS(0)          .uart.   0 l    6   16  377    0.000    1.097   0.001 > > xPPS(1)          .usb1.   0 l    4   16  377    0.000   -0.051   0.773 > > oPPS(2)          .usb2.   0 l    4   16  377    0.000   -0.001   0.035 > > *dvb.hippie.lan  .GPS.    1 u   12   64  377    1.234    1.296   2.707 > > +utcnist2.colora .NIST.   1 u    1   64  377   13.605    3.940   2.729 > > > > You can see in this case ntpd actually chose the usb2 pps input as the > > system peer. It did so because at startup the clock offset was closer > > than the uart, and the difference in jitter between the two wasn't > > significant, so the ntpd code that prevents clock-hopping chose to > > stick with the peer with the smaller offset. > > > Yes, I was technically correct but of course you are right too - > however, the main problem is not the jitter but rather that I am unable > to switch off the serial console and stop the u-boot loader from > receiving NMEA data. The Adafruit GPS Hat is made to sit right on the Pi > 40-pin header, as you probably know. > > To quote one of the posters in the thread I linked to: > "... I am seriously baffled by how difficult (nearly impossible) it had > been to get rid of the serial console..." > > Unfortunately I am not fluid enough to figure out where to make the > changes, the advices I've seen so far is not applicable to 12-CURRENT in > an easy way. > > And that is also why I wrote bugreport 229976. It may be that all the > folks involved with FreeBSD/ARM are serious developers so they do not > see it as a problem but for me it is, being more on the > application/administration side of things. > > Thanks, > > //per > Unfortunately, I can't help with the rpi part of this, since it's related to the firmware and uboot, and that part of the rpi world has changed drastically since I was involved with it years ago. I know you can build a custom uboot that disables serial console support completely, but I don't know if there's a way to achieve that with the stock uboot. -- Ian From owner-freebsd-arm@freebsd.org Mon Jul 23 15:32:44 2018 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 F18C9104DFA8 for ; Mon, 23 Jul 2018 15:32:43 +0000 (UTC) (envelope-from ralph@ralphsmith.org) Received: from ralphsmith.org (ralphsmith.org [98.172.20.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ralphsmith.org", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9226B81820 for ; Mon, 23 Jul 2018 15:32:43 +0000 (UTC) (envelope-from ralph@ralphsmith.org) Received: from [192.168.140.100] ([198.99.129.142]) (authenticated bits=0) by ralphsmith.org (8.15.2/8.15.2) with ESMTPSA id w6NFBJce045715 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 23 Jul 2018 11:11:22 -0400 (EDT) (envelope-from ralph@ralphsmith.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ralphsmith.org; s=201502; t=1532358683; bh=F6GoTHR8fiIzh6ls8oQi0Jzup25J7WsW44iiq2IPoWI=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=uBZhS+gftmP4G+WvgU5Jc/qjQ+emQ9F6ozci/qo7nmxVAbAE4uRLrxPbqB3C9FUt5 NkiKL28vf96ITwUAQj4B4r3uDb5muY0j5xQasDlW4sdF6HsEpX9gIdFv4zD81aD2tu oUO7OIKlHPJONwjwvbbmYY6l6SRVb9QWGpBb/M5A= Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: rpi3 and Adafruit GPS Hat From: Ralph Smith X-Mailer: iPhone Mail (15F79) In-Reply-To: <7a14173c-cc28-6dc7-3787-a5b77a396b30@nethead.se> Date: Mon, 23 Jul 2018 11:11:12 -0400 Cc: David Cornejo , freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <72A10F81-7BC3-4B4F-BDC0-26A47DB04ABD@ralphsmith.org> References: <47f49a55-66b0-1c02-4530-4701a3bd0c43@nethead.se> <20180718170157.GA40221@night.db.net> <7a14173c-cc28-6dc7-3787-a5b77a396b30@nethead.se> To: Per olof Ljungmark X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 15:32:44 -0000 Sent from my iPhone >> On Jul 23, 2018, at 5:40 AM, Per olof Ljungmark wrote: >>=20 >> On 07/23/18 10:46, David Cornejo wrote: >> this might be a little blasphemous, but for grins I tried an Oncore with >> PPS to a GPIO and running the serial through a TTL-USB serial cable and >> that seems to work ok. >>=20 >> there's probably some good reason that this is a bad idea. >=20 > Depends on what precision you are after, but for lowest possible jitter > you need to use the uart, the difference is in magnitudes. But he=E2=80=99s not running the PPS through the USB serial port, it is goin= g directly to GPIO. Correct me if I=E2=80=99m wrong here, but once ntpd lock= s to the PPS there is no real difference between the two. I=E2=80=99m runnin= g that exact scenario here with two Pis, both Model 2. One has an Adafruit G= PS HAT directly attached, and the other has the GPS connected to a USB-TTL s= erial adapter, with the PPS connected to the GPIO. Both sync to PPS with the= offset typically around 4 =CE=BCs and jitter around 2 =CE=BCs. I may try it= with an Oncore I have on hand but that will have to wait a month or so for o= ther things to settle down.=20 Ralph >> On Sun, Jul 22, 2018 at 9:09 PM Per olof Ljungmark > > wrote: >>=20 >>>> On 07/18/18 19:01, Diane Bruce wrote: >>>> On Wed, Jul 18, 2018 at 05:10:16PM +0200, Per olof Ljungmark wrote: >>>> Being a complete newbie to arm I thought a nice project would be to >>>> build a NTP server with the parts in the subject line. >>>>=20 >>>> Unfortunately I have almost no idea where to start, it seems >> FreeBSD for >>>> arm have shifted around quite a bit, almost none of the googled >> pages I >>>> find has relevance, and to add insult to injury, the Pi project >>>> apparently shifted the serial ports around for the Pi3. >>>>=20 >>>> What I need to achieve, >>>>=20 >>>> - Stop the kernel to use the uart for console output (I have ethernet >>>> and HDMI connected) >>>=20 >>> No need. >>>=20 >>> change your config.txt >>>=20 >>> #dtoverlay=3Dpi3-disable-bt >>> device_tree_address=3D0x4000 >>> kernel=3Du-boot.bin >>> enable_uart=3D1 >>>=20 >>> This moves the console port to the less capable micro uart port >>> this will free up the good uart (the pl011 device) as /dev/ttyu0 >>>=20 >>> Remove the pi3-disable-dt in config.txt >>> enable_uart=3D1 is needed. >>>=20 >>>> VERY grateful if someone that knows better can give me a push in the >>>> right direction for up to date information. >>> .. >>>=20 >>> This is assuming you use FreeBSD-12 (Head of tree) >>=20 >> Yes, 12.0-CURRENT #2 r336461. >>=20 >> Unfortunately your advice did not solve the problem, when the hat is >> attached it sends NMEA sequences to the u-boot loader making it >> impossible to boot further, just like it is described in this thread: >>=20 >> http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-shield-on= -a-Raspberry-Pi-td6236680.html >>=20 >>=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 >> " >>=20 >>=20 >>=20 >> --=20 >> Kailua, Hawai=CA=BBi >> US +1 (808) 728-3050 >> UK +44 (020) 3286 2808 > _______________________________________________ > 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 Jul 23 15:38:07 2018 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 8474C104E0E9 for ; Mon, 23 Jul 2018 15:38:07 +0000 (UTC) (envelope-from ralph@ralphsmith.org) Received: from ralphsmith.org (ralphsmith.org [98.172.20.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ralphsmith.org", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1595E81AB5; Mon, 23 Jul 2018 15:38:07 +0000 (UTC) (envelope-from ralph@ralphsmith.org) Received: from [192.168.140.100] ([198.99.129.142]) (authenticated bits=0) by ralphsmith.org (8.15.2/8.15.2) with ESMTPSA id w6NFc16n046136 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 23 Jul 2018 11:38:04 -0400 (EDT) (envelope-from ralph@ralphsmith.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ralphsmith.org; s=201502; t=1532360285; bh=5qWBxpPB6bXRo5Wguezf6PJJGAdsdcBImG319iuDKFM=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=X+X9m8zqF8pL97cTjtVqLJYz6+DnvNxkn3MbEkTpLp645bmigB9K3c0uQUVRw4cFJ uQ2xbByoZrxToebtr4BXfWwSMv9fmKdR5HS3Y4RAZlc1+zwqm/OaYwVmLL8IzufwZI HTC6e1CupqZynCrA9uIkql8Ug5aeil04HYFXGqxY= Mime-Version: 1.0 (1.0) Subject: Re: rpi3 and Adafruit GPS Hat From: Ralph Smith X-Mailer: iPhone Mail (15F79) In-Reply-To: <1532359478.1344.142.camel@freebsd.org> Date: Mon, 23 Jul 2018 11:37:56 -0400 Cc: Per olof Ljungmark , David Cornejo , freebsd-arm Message-Id: <002D469F-26E0-492A-BEB7-8A61A56ECABF@ralphsmith.org> References: <47f49a55-66b0-1c02-4530-4701a3bd0c43@nethead.se> <20180718170157.GA40221@night.db.net> <7a14173c-cc28-6dc7-3787-a5b77a396b30@nethead.se> <1532357176.1344.130.camel@freebsd.org> <1532359478.1344.142.camel@freebsd.org> To: Ian Lepore Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 15:38:07 -0000 Sent from my iPhone > On Jul 23, 2018, at 11:24 AM, Ian Lepore wrote: >=20 >> On Mon, 2018-07-23 at 17:20 +0200, Per olof Ljungmark wrote: >>> On 07/23/18 16:46, Ian Lepore wrote: >>>=20 >>>> On Mon, 2018-07-23 at 11:40 +0200, Per olof Ljungmark wrote: >>>>=20 >>>>> On 07/23/18 10:46, David Cornejo wrote: >>>>>=20 >>>>>=20 >>>>> this might be a little blasphemous, but for grins I tried an Oncore wi= th >>>>> PPS to a GPIO and running the serial through a TTL-USB serial cable an= d >>>>> that seems to work ok. >>>>>=20 >>>>> there's probably some good reason that this is a bad idea. >>>> Depends on what precision you are after, but for lowest possible jitter= >>>> you need to use the uart, the difference is in magnitudes. >>>>=20 >>> Technically that may be correct, but it's meaningless. On a usb 1.x >>> adapter there may be ~500us of jitter from one measurement to the next. >>> On a usb 2.x adapter the jitter drops to typically ~60us. Those values >>> are pretty much in the noise for ntpd, which uses a median filter to >>> smooth any serious jitter out of the measurements. >>>=20 >>> Here are some real-world measurements. The pps source for all 3 inputs >>> is the same gps-disciplined rubidium oscillator, so all the jitter is >>> within the uart, usb hardware, and freebsd drivers. The usb adapters >>> are both FTDI chips, which have a fixed latency on reporting a change >>> on the DCD pin (pin-change status messages are only delivered once a >>> millisecond on ftdi chips). >>>=20 >>> remote refid st t when poll reach delay offset jitter >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>> xPPS(0) .uart. 0 l 6 16 377 0.000 1.097 0.001 >>> xPPS(1) .usb1. 0 l 4 16 377 0.000 -0.051 0.773 >>> oPPS(2) .usb2. 0 l 4 16 377 0.000 -0.001 0.035 >>> *dvb.hippie.lan .GPS. 1 u 12 64 377 1.234 1.296 2.707 >>> +utcnist2.colora .NIST. 1 u 1 64 377 13.605 3.940 2.729 >>>=20 >>> You can see in this case ntpd actually chose the usb2 pps input as the >>> system peer. It did so because at startup the clock offset was closer >>> than the uart, and the difference in jitter between the two wasn't >>> significant, so the ntpd code that prevents clock-hopping chose to >>> stick with the peer with the smaller offset. >>>=20 >> Yes, I was technically correct but of course you are right too - >> however, the main problem is not the jitter but rather that I am unable >> to switch off the serial console and stop the u-boot loader from >> receiving NMEA data. The Adafruit GPS Hat is made to sit right on the Pi >> 40-pin header, as you probably know. >>=20 >> To quote one of the posters in the thread I linked to: >> "... I am seriously baffled by how difficult (nearly impossible) it had >> been to get rid of the serial console..." >>=20 >> Unfortunately I am not fluid enough to figure out where to make the >> changes, the advices I've seen so far is not applicable to 12-CURRENT in >> an easy way. >>=20 >> And that is also why I wrote bugreport 229976. It may be that all the >> folks involved with FreeBSD/ARM are serious developers so they do not >> see it as a problem but for me it is, being more on the >> application/administration side of things. >>=20 >> Thanks, >>=20 >> //per >>=20 >=20 > Unfortunately, I can't help with the rpi part of this, since it's > related to the firmware and uboot, and that part of the rpi world has > changed drastically since I was involved with it years ago. I know you > can build a custom uboot that disables serial console support > completely, but I don't know if there's a way to achieve that with the > stock uboot. Not using the stock uboot, you will need to modify it. I have this working o= n 12-CURRENT for the Pi 2, I haven=E2=80=99t tried it on the Pi 3. I documen= ted how I modified u-boot for 11-STABLE in https://docs.freebsd.org/cgi/getm= sg.cgi?fetch=3D188164+0+archive/2018/freebsd-arm/20180204.freebsd-arm, this s= hould apply to the current u-boot port as well. You will also meet to modify= the DTB so the system doesn=E2=80=99t send console output to the uart as we= ll.=20 Ralph= From owner-freebsd-arm@freebsd.org Mon Jul 23 15:38:19 2018 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 62D7F104E10D for ; Mon, 23 Jul 2018 15:38:19 +0000 (UTC) (envelope-from peo@nethead.se) Received: from ns1.nethead.se (ns1.nethead.se [5.150.237.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns1.nethead.se", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C2B1081AC8 for ; Mon, 23 Jul 2018 15:38:18 +0000 (UTC) (envelope-from peo@nethead.se) X-Virus-Scanned: amavisd-new at Nethead AB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nethead.se; s=NETHEADSE; t=1532360297; bh=cNy+/5WHIhkIc3buSYwVAlzgbyARV9JinzYDQSFAFUM=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=c826UJW69Y8YWmmukQaE6XRGd9Oj+/NKbJ6OHtxCCv+HSCd6f+v5G31s0lfsXmhaq fQYXkqdsv9j97+wbBq5ipDDBf13STaLLmKHphY75/dqhi+FRdTAFGabHlVYyzwze2N awCyU7i+GKC5ALGy5DKKdlOXbEtClG7HObF6531Q= Subject: Re: rpi3 and Adafruit GPS Hat To: Ralph Smith Cc: David Cornejo , freebsd-arm References: <47f49a55-66b0-1c02-4530-4701a3bd0c43@nethead.se> <20180718170157.GA40221@night.db.net> <7a14173c-cc28-6dc7-3787-a5b77a396b30@nethead.se> <72A10F81-7BC3-4B4F-BDC0-26A47DB04ABD@ralphsmith.org> From: Per olof Ljungmark Message-ID: <7b7277dc-18bf-8762-9eb8-4cf42b4744e3@nethead.se> Date: Mon, 23 Jul 2018 17:38:13 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <72A10F81-7BC3-4B4F-BDC0-26A47DB04ABD@ralphsmith.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 15:38:19 -0000 On 07/23/18 17:11, Ralph Smith wrote: > > > Sent from my iPhone > >>> On Jul 23, 2018, at 5:40 AM, Per olof Ljungmark wrote: >>> >>> On 07/23/18 10:46, David Cornejo wrote: >>> this might be a little blasphemous, but for grins I tried an Oncore with >>> PPS to a GPIO and running the serial through a TTL-USB serial cable and >>> that seems to work ok. >>> >>> there's probably some good reason that this is a bad idea. >> >> Depends on what precision you are after, but for lowest possible jitter >> you need to use the uart, the difference is in magnitudes. > > But he’s not running the PPS through the USB serial port, it is going directly to GPIO. Correct me if I’m wrong here, but once ntpd locks to the PPS there is no real difference between the two. I’m running that exact scenario here with two Pis, both Model 2. One has an Adafruit GPS HAT directly attached, and the other has the GPS connected to a USB-TTL serial adapter, with the PPS connected to the GPIO. Both sync to PPS with the offset typically around 4 μs and jitter around 2 μs. I may try it with an Oncore I have on hand but that will have to wait a month or so for other things to settle down. Yes again, but the real issue here is the fact the the serial console on FBSD ARM is very difficult to switch off. I can imagine a number of cases when you want to use the uart for something else. //per >>> On Sun, Jul 22, 2018 at 9:09 PM Per olof Ljungmark >> > wrote: >>> >>>>> On 07/18/18 19:01, Diane Bruce wrote: >>>>> On Wed, Jul 18, 2018 at 05:10:16PM +0200, Per olof Ljungmark wrote: >>>>> Being a complete newbie to arm I thought a nice project would be to >>>>> build a NTP server with the parts in the subject line. >>>>> >>>>> Unfortunately I have almost no idea where to start, it seems >>> FreeBSD for >>>>> arm have shifted around quite a bit, almost none of the googled >>> pages I >>>>> find has relevance, and to add insult to injury, the Pi project >>>>> apparently shifted the serial ports around for the Pi3. >>>>> >>>>> What I need to achieve, >>>>> >>>>> - Stop the kernel to use the uart for console output (I have ethernet >>>>> and HDMI connected) >>>> >>>> No need. >>>> >>>> change your config.txt >>>> >>>> #dtoverlay=pi3-disable-bt >>>> device_tree_address=0x4000 >>>> kernel=u-boot.bin >>>> enable_uart=1 >>>> >>>> This moves the console port to the less capable micro uart port >>>> this will free up the good uart (the pl011 device) as /dev/ttyu0 >>>> >>>> Remove the pi3-disable-dt in config.txt >>>> enable_uart=1 is needed. >>>> >>>>> VERY grateful if someone that knows better can give me a push in the >>>>> right direction for up to date information. >>>> .. >>>> >>>> This is assuming you use FreeBSD-12 (Head of tree) >>> >>> Yes, 12.0-CURRENT #2 r336461. >>> >>> Unfortunately your advice did not solve the problem, when the hat is >>> attached it sends NMEA sequences to the u-boot loader making it >>> impossible to boot further, just like it is described in this thread: >>> >>> http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-shield-on-a-Raspberry-Pi-td6236680.html >>> >>> >>> _______________________________________________ >>> 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 >>> " >>> >>> >>> >>> -- >>> Kailua, HawaiÊ»i >>> US +1 (808) 728-3050 >>> UK +44 (020) 3286 2808 >> _______________________________________________ >> 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 Jul 23 15:48:55 2018 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 80968104E736 for ; Mon, 23 Jul 2018 15:48:55 +0000 (UTC) (envelope-from peo@nethead.se) Received: from ns1.nethead.se (ns1.nethead.se [5.150.237.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns1.nethead.se", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 03A1B820A6; Mon, 23 Jul 2018 15:48:54 +0000 (UTC) (envelope-from peo@nethead.se) X-Virus-Scanned: amavisd-new at Nethead AB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nethead.se; s=NETHEADSE; t=1532360933; bh=oci33I7/XwsDwDQAWYFzQzpV2KLcRlrQ02EnF9bo02c=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=Apm6ii5bqdeVRUdzrK+PQlFT1A9QO5nJq/rSmobN35iHfZ6Pp1R9lHloFX05D4TZ5 CQNQO0UjEp09v4APV63ch6V6qst9QZfQyZjyaqIwir7obvGR97vCsa4sGvEsFKyrJq 2NETDPBDnxBkerNjx9oEu1RxZvrR4nJjqyGQTfjU= Subject: Re: rpi3 and Adafruit GPS Hat To: Ralph Smith Cc: Ian Lepore , David Cornejo , freebsd-arm References: <47f49a55-66b0-1c02-4530-4701a3bd0c43@nethead.se> <20180718170157.GA40221@night.db.net> <7a14173c-cc28-6dc7-3787-a5b77a396b30@nethead.se> <1532357176.1344.130.camel@freebsd.org> <1532359478.1344.142.camel@freebsd.org> <002D469F-26E0-492A-BEB7-8A61A56ECABF@ralphsmith.org> From: Per olof Ljungmark Message-ID: <11249434-0a4d-8f6b-2e45-bb3d97a3b1ab@nethead.se> Date: Mon, 23 Jul 2018 17:48:51 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <002D469F-26E0-492A-BEB7-8A61A56ECABF@ralphsmith.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 15:48:55 -0000 On 07/23/18 17:37, Ralph Smith wrote: > [snip...] >> stock uboot. > > Not using the stock uboot, you will need to modify it. I have this > working on 12-CURRENT for the Pi 2, I haven’t tried it on the Pi 3. I > documented how I modified u-boot for 11-STABLE > in https://docs.freebsd.org/cgi/getmsg.cgi?fetch=188164+0+archive/2018/freebsd-arm/20180204.freebsd-arm, > this should apply to the current u-boot port as well. You will also meet > to modify the DTB so the system doesn’t send console output to the uart > as well.  Yes, I know, but "but I am seriously baffled by how difficult (nearly impossible) it had been to get rid of the serial console" as it says in one message. To be able to use the instructions in the link you need (if you use 12) to figure out where those files are now (because they moved or does not exist) and try to guess which of all the new files to patch. As I said, I'm not a developer, I am a user and not very well versed in source code. That is why I filed 229976. Thanks, //per From owner-freebsd-arm@freebsd.org Mon Jul 23 15:51:45 2018 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 EFB77104E9A5 for ; Mon, 23 Jul 2018 15:51:44 +0000 (UTC) (envelope-from mmitchel@gmail.com) Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46AC8823F4; Mon, 23 Jul 2018 15:51:44 +0000 (UTC) (envelope-from mmitchel@gmail.com) Received: by mail-pg1-x534.google.com with SMTP id s7-v6so679443pgv.3; Mon, 23 Jul 2018 08:51:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=y6Ko/nVghq620l9R/lgpAYpNivMd6e4oUm02i60wsdQ=; b=osF0kncK0Fa5nLFk/8zU01nLWPDK7cPIDj0qO/8iWyUX4mIyOFlBi7qN06sGUq6KT/ WA5/Ifa55CWssA1rWcy7e1VlHLAIlysfFOsVJ787641dwvkKTfihseXZFDFReRE+ifHE OEtw+If8eyIQJNf45DWRTR61c5Cog6MSadCaEeWmssJ7GWnSwGvMJrrP7ImfJha20buk pt/e0T5LRCatGtkThfdQjAIpGTMd0Bs+3ZG0Gz+ruH1Nh/gzLzlTbJwyNhTw3dhyVin7 9kslomijalpaGevU4T5ZqBiizzcpahnuhSHans55p5xpQ55iASpEm4nQF72heGPo/UST j47A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=y6Ko/nVghq620l9R/lgpAYpNivMd6e4oUm02i60wsdQ=; b=rgvZTmF+AqnXeoFUDcJb0NT0hHERBxbHUKvx4n228aNhTl8L5Z3mr86N9hlrQYj86f x97LCKTyMCQfLkPhFz+GR55N0dFwM8V3xIboZCP72UgYOqxFVGsRGPKPlj50AI/9o3FB CG3904d/szMwXKH7WT46ua2kEcV1KDFXBDQN5fkTe2/ngtWmgIoYItg0QJmKxASyrSna xlJR8rNnUyogVlmC0P08Pdwsi9OFUl0Ig6S4x22OBAvLhN1K1y0MiPXg37MEBkHozXOH bhHqKVU8YRiURozA8G3vR+cu4OMINH+GyG8xMZictHuuD2a3ZDiRGFUhFLkPNeKy+vVh ZkiQ== X-Gm-Message-State: AOUpUlGeneDeHDxD6v+IwR+GLFI9N6BIkO5wNeR2+nYAGrK08H//Mv2O pKEd+pEejVFMXq2veSqzRLw/5gU= X-Google-Smtp-Source: AAOMgpfwKMg47uJ584eotsPWE3EtSw4ukhnC/9eJN2G67DaEBu2FWHnR9o8qMadfJLWs6YzWyHwCaQ== X-Received: by 2002:a63:4203:: with SMTP id p3-v6mr12720042pga.184.1532361103162; Mon, 23 Jul 2018 08:51:43 -0700 (PDT) Received: from [192.168.1.47] (cpe-70-95-124-159.san.res.rr.com. [70.95.124.159]) by smtp.gmail.com with ESMTPSA id n26-v6sm5468172pgv.78.2018.07.23.08.51.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Jul 2018 08:51:42 -0700 (PDT) From: Michael Mitchell Message-Id: <23DA127A-B954-44A8-8BA3-4D4F1E0D11A2@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: rpi3 and Adafruit GPS Hat Date: Mon, 23 Jul 2018 08:51:40 -0700 In-Reply-To: <002D469F-26E0-492A-BEB7-8A61A56ECABF@ralphsmith.org> Cc: Ian Lepore , freebsd-arm To: Ralph Smith References: <47f49a55-66b0-1c02-4530-4701a3bd0c43@nethead.se> <20180718170157.GA40221@night.db.net> <7a14173c-cc28-6dc7-3787-a5b77a396b30@nethead.se> <1532357176.1344.130.camel@freebsd.org> <1532359478.1344.142.camel@freebsd.org> <002D469F-26E0-492A-BEB7-8A61A56ECABF@ralphsmith.org> X-Mailer: Apple Mail (2.3445.9.1) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 15:51:45 -0000 hi all: maybe this would be the supported u-boot method to give up the serial output messages during startup: https://github.com/u-boot/u-boot/blob/master/doc/README.silent = just a thought mdm > On Jul 23, 2018, at 8:37 AM, Ralph Smith wrote: >=20 >=20 >=20 > Sent from my iPhone >=20 >> On Jul 23, 2018, at 11:24 AM, Ian Lepore wrote: >>=20 >>> On Mon, 2018-07-23 at 17:20 +0200, Per olof Ljungmark wrote: >>>> On 07/23/18 16:46, Ian Lepore wrote: >>>>=20 >>>>> On Mon, 2018-07-23 at 11:40 +0200, Per olof Ljungmark wrote: >>>>>=20 >>>>>> On 07/23/18 10:46, David Cornejo wrote: >>>>>>=20 >>>>>>=20 >>>>>> this might be a little blasphemous, but for grins I tried an = Oncore with >>>>>> PPS to a GPIO and running the serial through a TTL-USB serial = cable and >>>>>> that seems to work ok. >>>>>>=20 >>>>>> there's probably some good reason that this is a bad idea. >>>>> Depends on what precision you are after, but for lowest possible = jitter >>>>> you need to use the uart, the difference is in magnitudes. >>>>>=20 >>>> Technically that may be correct, but it's meaningless. On a usb 1.x >>>> adapter there may be ~500us of jitter from one measurement to the = next. >>>> On a usb 2.x adapter the jitter drops to typically ~60us. Those = values >>>> are pretty much in the noise for ntpd, which uses a median filter = to >>>> smooth any serious jitter out of the measurements. >>>>=20 >>>> Here are some real-world measurements. The pps source for all 3 = inputs >>>> is the same gps-disciplined rubidium oscillator, so all the jitter = is >>>> within the uart, usb hardware, and freebsd drivers. The usb = adapters >>>> are both FTDI chips, which have a fixed latency on reporting a = change >>>> on the DCD pin (pin-change status messages are only delivered once = a >>>> millisecond on ftdi chips). >>>>=20 >>>> remote refid st t when poll reach delay offset = jitter >>>> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>> xPPS(0) .uart. 0 l 6 16 377 0.000 1.097 = 0.001 >>>> xPPS(1) .usb1. 0 l 4 16 377 0.000 -0.051 = 0.773 >>>> oPPS(2) .usb2. 0 l 4 16 377 0.000 -0.001 = 0.035 >>>> *dvb.hippie.lan .GPS. 1 u 12 64 377 1.234 1.296 = 2.707 >>>> +utcnist2.colora .NIST. 1 u 1 64 377 13.605 3.940 = 2.729 >>>>=20 >>>> You can see in this case ntpd actually chose the usb2 pps input as = the >>>> system peer. It did so because at startup the clock offset was = closer >>>> than the uart, and the difference in jitter between the two wasn't >>>> significant, so the ntpd code that prevents clock-hopping chose to >>>> stick with the peer with the smaller offset. >>>>=20 >>> Yes, I was technically correct but of course you are right too - >>> however, the main problem is not the jitter but rather that I am = unable >>> to switch off the serial console and stop the u-boot loader from >>> receiving NMEA data. The Adafruit GPS Hat is made to sit right on = the Pi >>> 40-pin header, as you probably know. >>>=20 >>> To quote one of the posters in the thread I linked to: >>> "... I am seriously baffled by how difficult (nearly impossible) it = had >>> been to get rid of the serial console..." >>>=20 >>> Unfortunately I am not fluid enough to figure out where to make the >>> changes, the advices I've seen so far is not applicable to = 12-CURRENT in >>> an easy way. >>>=20 >>> And that is also why I wrote bugreport 229976. It may be that all = the >>> folks involved with FreeBSD/ARM are serious developers so they do = not >>> see it as a problem but for me it is, being more on the >>> application/administration side of things. >>>=20 >>> Thanks, >>>=20 >>> //per >>>=20 >>=20 >> Unfortunately, I can't help with the rpi part of this, since it's >> related to the firmware and uboot, and that part of the rpi world has >> changed drastically since I was involved with it years ago. I know = you >> can build a custom uboot that disables serial console support >> completely, but I don't know if there's a way to achieve that with = the >> stock uboot. >=20 > Not using the stock uboot, you will need to modify it. I have this = working on 12-CURRENT for the Pi 2, I haven=E2=80=99t tried it on the Pi = 3. I documented how I modified u-boot for 11-STABLE in = https://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D188164+0+archive/2018/free= bsd-arm/20180204.freebsd-arm, this should apply to the current u-boot = port as well. You will also meet to modify the DTB so the system = doesn=E2=80=99t send console output to the uart as well.=20 >=20 > Ralph > _______________________________________________ > 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 Jul 23 15:52:58 2018 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 44FC4104EB7A for ; Mon, 23 Jul 2018 15:52:58 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9A4E6824FB for ; Mon, 23 Jul 2018 15:52:57 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w6NFrCW4047728 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 23 Jul 2018 08:53:13 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w6NFrCt7047727; Mon, 23 Jul 2018 08:53:12 -0700 (PDT) (envelope-from fbsd) Date: Mon, 23 Jul 2018 08:53:11 -0700 From: bob prohaska To: Mark Millard Cc: Trev , freebsd-arm@freebsd.org, bob prohaska Subject: Re: RPI3 swap experiments Message-ID: <20180723155311.GB45726@www.zefox.net> References: <20180629233937.GC35717@www.zefox.net> <0f137e06-214a-3e8c-a216-f061ec04ac2c@sentry.org> <20180630005145.GA43801@www.zefox.net> <6f3406e2-71f3-d0c2-2b65-703e1a1d3c25@sentry.org> <8e92b2b7-da61-3efb-7231-9fac76b2c1d4@sentry.org> <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> <20180723063526.GA45726@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 15:52:58 -0000 On Mon, Jul 23, 2018 at 12:11:19AM -0700, Mark Millard wrote: > > > On 2018-Jul-22, at 11:35 PM, bob prohaska wrote: > > >> . . . > > There is some reason to think "newer" Sandisk Extreme devices differ, perhaps > > in a bad way, from older devices. The older device in my tests is model > > SDCZ80-064G and is simply labeled USB3.0. The newer, troublesome device > > is model SDCZ800-064G and is labeled Extreme Go USB 3.1. There are reports > > that the Extreme Go is slower, advising to buy the older devices if possible. > > > > The USB3.1 flash drive is back in test, with the results of a j4 buildworld > > under r336567 at > > http://www.zefox.net/~fbsd/rpi3/swaptests/r336567/ > > > > The worst case results are still fairly dismal, close to a minute. All the > > swap was on microSD, so OOMA didn't strike and buildworld completed successfully. > > Near as I can tell no errors were reported on the console. > > > Rebuilds that do not rebuild the llvm materials (clang, lld, lldb, etc.) are not all that > comparable to ones that do. (This is visible in the time differences in the builds that > complete.) The llvm related build activity likely involves most of the potential > swapping, for example. Also: lots of I/O. > > There can be two rebuilds of some of the llvm material. One stage with such is the > cross-compiler: > --- buildworld --- > make[1]: "/usr/src/Makefile.inc1" line 341: SYSTEM_COMPILER: Determined that CC=cc matches the source tree. Not bootstrapping a cross-compiler. > make[1]: "/usr/src/Makefile.inc1" line 346: SYSTEM_LINKER: Determined that LD=ld matches the source tree. Not bootstrapping a cross-linker. > (it was not rebuilt in the example). The other involves the build of the system llvm materials for > use in the (potentially) installed system, such as the system's clang. > > Taking an environment that worked for lack of llvm related rebuilds may not > well indicate the result for rebuilds that would try to rebuild the llvm related > materials. > > It is something to consider in what builds are compared, how they are > compared, and what one infers from comparisons. > The first step in the experiment is to run a cleanup script, consisting of make -j8 cleandir > cleandir.log && make -j8 cleandir > cleandir.log && rm -rf /usr/obj/usr/src && rm *.log Might this be insufficient to ensure a clean start? There's no obvious reason to build a cross compiler, since this is an RPI3 building world for itself. Is there an error in the cleanup script? Thanks for reading! bob prohaska From owner-freebsd-arm@freebsd.org Mon Jul 23 17:54:07 2018 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 D2DD21051413 for ; Mon, 23 Jul 2018 17:54:06 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic316-8.consmr.mail.gq1.yahoo.com (sonic316-8.consmr.mail.gq1.yahoo.com [98.137.69.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5679287696 for ; Mon, 23 Jul 2018 17:54:06 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: de52GvIVM1nVafEBd1gND9lCOGyhpA9EdEFmEYRRnjQnI6c.AVVCXnehmuEuUgi 4eY9hKPd_Ow_7HgaV4Q0yY11M0h66F6W3iltST8D33Z3GhSXhS2E8eGMmP2J7u8eih_xccuim_T8 j6pWk3T1oEbvzqldfFR1IkJRDByXNGOS1Vg40F_xIu1aOCpy_IQ0wnJzlMYohRkC7UgHjX7VOCEK dHFjfwKCa2nuK1fbSPt_Ta8AYz2YgWWyane9MXi74qgG5I9S.T7x4GgRVus9b3.hZiFfFNjCxcNa hIPrwrpB6pkl98T1TXwk5HQP1K13Xf1Wm76yf7ILzoOb2rEVZVZATA_mKniVDcJEoBvNa2JKRf.d MCleUhRWINYs_05Eubyq42jRK3PaE_7zJjrW25XQEF8PLiI_Z1Zow0douBtDMMwrOf.sxlftgGtk Odk9Z8oRkrIqTASMOA0.Jb2gaN3cFQGgS1mXjGuQ.lXJSrTPWt8xCgVg083qhqeQavWEvOboPdSg 90_skTQEHxb2HwYa9.B6tBQ1jJ1V9TbespvUiO7IE3y5YNofAwAFAhQTFbBZUt.hIMVhFgLwgi.H jUKZ6swOIaY9LKH_F3bJKJz6CtM7S1syl6.3EzSLGrkdcJsJqmPZQSdyRsm2cn9XaYKhZt3lb_vB 4kaXA12KMuVvKpyYR0lO1JqERIsHT.3tnHnFpS2tYtrck3hpvf0ztgUzPQ0tp0_vOYEc9uU9jpxi J1IXgCiMBqlTj1mtw.n.qehHho9SS7Fk8KKEykoLDpX.Lgb7GtM1ZvMCZbgN.XeZOhGtqzdgPoVp 14HkQjwyuOwze7uVOjtllKFx6KaoqeSL4LOyChLpzdrAuPstaa7nVEhHiLQF0QXLVFoo7gUZ_fmR HJq6IXM5h7eHRIz3ZLLogbaE6CFIjiastOxvlntsZqFMdXd5m9_bTx8bX9fhh4zonFkiW6x2Y46o ucDOHK_R2laitqCO8Wf3pPCtqfm8njSjE0EywW0Rnd41uuLLCqgRkwgv4u8aA0Ereqf7MJrZHjsD 2DEQ4rxaH Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.gq1.yahoo.com with HTTP; Mon, 23 Jul 2018 17:53:59 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp413.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 624a896f7e42f0b79fdd10575f371a4a; Mon, 23 Jul 2018 17:53:58 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: RPI3 swap experiments From: Mark Millard In-Reply-To: <20180723155311.GB45726@www.zefox.net> Date: Mon, 23 Jul 2018 10:53:56 -0700 Cc: Trev , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <4ED9B658-A5A8-4BA6-9412-EBB7150B4B66@yahoo.com> References: <20180629233937.GC35717@www.zefox.net> <0f137e06-214a-3e8c-a216-f061ec04ac2c@sentry.org> <20180630005145.GA43801@www.zefox.net> <6f3406e2-71f3-d0c2-2b65-703e1a1d3c25@sentry.org> <8e92b2b7-da61-3efb-7231-9fac76b2c1d4@sentry.org> <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> <20180723063526.GA45726@www.zefox.net> <20180723155311.GB45726@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 17:54:07 -0000 On 2018-Jul-23, at 8:53 AM, bob prohaska wrote: > On Mon, Jul 23, 2018 at 12:11:19AM -0700, Mark Millard wrote: >>=20 >>=20 >> On 2018-Jul-22, at 11:35 PM, bob prohaska = wrote: >>=20 >>>> . . . >>> There is some reason to think "newer" Sandisk Extreme devices = differ, perhaps >>> in a bad way, from older devices. The older device in my tests is = model >>> SDCZ80-064G and is simply labeled USB3.0. The newer, troublesome = device >>> is model SDCZ800-064G and is labeled Extreme Go USB 3.1. There are = reports >>> that the Extreme Go is slower, advising to buy the older devices if = possible. >>>=20 >>> The USB3.1 flash drive is back in test, with the results of a j4 = buildworld >>> under r336567 at >>> http://www.zefox.net/~fbsd/rpi3/swaptests/r336567/ >>>=20 >>> The worst case results are still fairly dismal, close to a minute. = All the >>> swap was on microSD, so OOMA didn't strike and buildworld completed = successfully. >>> Near as I can tell no errors were reported on the console. >>=20 >>=20 >> Rebuilds that do not rebuild the llvm materials (clang, lld, lldb, = etc.) are not all that >> comparable to ones that do. (This is visible in the time differences = in the builds that >> complete.) The llvm related build activity likely involves most of = the potential >> swapping, for example. Also: lots of I/O. >>=20 >> There can be two rebuilds of some of the llvm material. One stage = with such is the >> cross-compiler: >> --- buildworld --- >> make[1]: "/usr/src/Makefile.inc1" line 341: SYSTEM_COMPILER: = Determined that CC=3Dcc matches the source tree. Not bootstrapping a = cross-compiler. >> make[1]: "/usr/src/Makefile.inc1" line 346: SYSTEM_LINKER: Determined = that LD=3Dld matches the source tree. Not bootstrapping a cross-linker. >> (it was not rebuilt in the example). The other involves the build of = the system llvm materials for >> use in the (potentially) installed system, such as the system's = clang. >>=20 >> Taking an environment that worked for lack of llvm related rebuilds = may not >> well indicate the result for rebuilds that would try to rebuild the = llvm related >> materials. >>=20 >> It is something to consider in what builds are compared, how they are >> compared, and what one infers from comparisons. >>=20 >=20 > The first step in the experiment is to run a cleanup script, = consisting of >=20 > make -j8 cleandir > cleandir.log && make -j8 cleandir > cleandir.log = && rm -rf /usr/obj/usr/src && rm *.log >=20 > Might this be insufficient to ensure a clean start? There's no obvious = reason to build > a cross compiler, since this is an RPI3 building world for itself. Is = there an error in the=20 > cleanup script? My note was intended just as a caution, not as a claim of a specific bad comparison. I did not know how you established the initial context for the build. If you are getting the same (re)build activity each time, then things = should be similar and comparisons easier and more reliable for such contexts. On occasion builds that are updating the -r?????? might find CC=3Dcc or = LD=3Dld does not match the source tree. Such builds would have a lot more activity = and take longer. (This seems the most likely large variation in activity given an = explicit cleanout before the build.) I have not been doing a detailed comparison of the activity in your = various builds. I've not been checking/comparing the overall build times either = (for builds that completed). A rule of thumb (for rebuilds that complete) on the same storage device configuration: similar build times tend to be more directly comparable. = Large differences in build times suggest more cautious comparisons. It might = also suggest another rebuild (that would have, say, the matching source tree = and avoid the cross compiler build). Time tends to work as a rule of thumb = only for builds that complete unless similarity is confirmed for earlier = stopping points. Of course completing a build that includes rebuilding those cross tools = is more/better evidence suggesting a good build context. Multiple rounds of doing so: even more. It is when a build that also built the cross tools, but that eventually fails, that the comparisons are more complicated compared to successes that did not build the cross tools(for example). =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Mon Jul 23 19:02:44 2018 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 07755105292F for ; Mon, 23 Jul 2018 19:02:44 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 746CE8A7A8 for ; Mon, 23 Jul 2018 19:02:43 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w6NJ2wtK048264 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 23 Jul 2018 12:02:59 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w6NJ2w3q048263; Mon, 23 Jul 2018 12:02:58 -0700 (PDT) (envelope-from fbsd) Date: Mon, 23 Jul 2018 12:02:57 -0700 From: bob prohaska To: Mark Millard Cc: Trev , freebsd-arm@freebsd.org, bob prohaska Subject: Re: RPI3 swap experiments Message-ID: <20180723190257.GA47869@www.zefox.net> References: <20180630005145.GA43801@www.zefox.net> <6f3406e2-71f3-d0c2-2b65-703e1a1d3c25@sentry.org> <8e92b2b7-da61-3efb-7231-9fac76b2c1d4@sentry.org> <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> <20180723063526.GA45726@www.zefox.net> <20180723155311.GB45726@www.zefox.net> <4ED9B658-A5A8-4BA6-9412-EBB7150B4B66@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4ED9B658-A5A8-4BA6-9412-EBB7150B4B66@yahoo.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 19:02:44 -0000 On Mon, Jul 23, 2018 at 10:53:56AM -0700, Mark Millard wrote: > > My note was intended just as a caution, not as a claim of a specific bad > comparison. I did not know how you established the initial context for > the build. > Understood and appreciated! I posed the question about cleaning up because the docs I've seen imply that running make cleandir twice in /usr/src should remove things in /usr/obj on the second pass. At some point I looked and found residues below /usr/obj/usr (possibly just empty directories, I didn't check) so I added the rm -rf /usr/obj/usr.... as a precaution. I'm not entirely sure the precautions taken to insure a clean start are sufficient even now. > If you are getting the same (re)build activity each time, then things should be > similar and comparisons easier and more reliable for such contexts. > The only point of consistency is that failures now take the form of OOMA kills. When -j4 buildworld succeeds using the USB3.1 flash it's imperative (so far) that all swap be on microSD. When using the USB3.0 flash all the swap must be on that device. Mixing swap (some on USB, some on microSD) seems to fail reliably, always with OOMA kills, when either USB device is in use. Stress2 is no longer able to produce a prompt panic, even stalling the system takes most of a day. > On occasion builds that are updating the -r?????? might find CC=cc or LD=ld does > not match the source tree. Such builds would have a lot more activity and take > longer. (This seems the most likely large variation in activity given an explicit > cleanout before the build.) > > I have not been doing a detailed comparison of the activity in your various > builds. I've not been checking/comparing the overall build times either (for > builds that completed). > > A rule of thumb (for rebuilds that complete) on the same storage device > configuration: similar build times tend to be more directly comparable. Large > differences in build times suggest more cautious comparisons. It might also > suggest another rebuild (that would have, say, the matching source tree and > avoid the cross compiler build). Time tends to work as a rule of thumb only > for builds that complete unless similarity is confirmed for earlier stopping > points. > > Of course completing a build that includes rebuilding those cross tools is > more/better evidence suggesting a good build context. Multiple rounds of > doing so: even more. Here's a point I find confusing: What is the purpose of cross tools when the build is self-hosted? Is "cross-tools" a component of bootstrap tools? > > It is when a build that also built the cross tools, but that eventually > fails, that the comparisons are more complicated compared to successes > that did not build the cross tools(for example). > I've been using peak swap usage as a measure of test thoroughness: If swap usage hits 1.3-1.4 GB without errors I've thought the test successful. Thanks for reading, and all your counsel. bob prohaska From owner-freebsd-arm@freebsd.org Mon Jul 23 19:42:53 2018 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 CEC3810536B8 for ; Mon, 23 Jul 2018 19:42:52 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic309-14.consmr.mail.bf2.yahoo.com (sonic309-14.consmr.mail.bf2.yahoo.com [74.6.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4C1E28BC41 for ; Mon, 23 Jul 2018 19:42:52 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: TNVtgaAVM1mO3ge_JdzFTLU5vfyAL4BSNf9RrFghOneKzVHM7szPwL.6PVr8dTG SqgWO.wZCxbPc0UElY5KpGsAkH_8n4deiW6Xl.OvKkzjP08giYz7V1patjBDglDsIAJVVrUmpAhu gE1NyRwPpT424MqrJdXJldQ4da1Vx1br2QH3h4jfZbvzWOJokx1wHtyNKeNmcAPL7mkAjr8iS5E_ bkDaLmNrOqaj3j808UTt0vtCrRtZlz_lzCmF9Ulyhi60snCrHCl0si0dl4sIIQD154PjXFbu8A0B kRjkfGbd3T47YXO5EyPHco6ylhAqT6Nu9673QlsbqJq4vVwF8hoEo4uezm7XZ3PKuYWp9zorZGeS NicXHVHcq8JmCauU5pg3SCAyARDlixl6IWMVDuxAKQ3PXq.reoGu0ldCczxYjcgp.E8DJc9_EaGN 7elaS1aF21d..05.FzwTs.wsfu7FKLhvhOsIDruEU6f8wRei.Mqxgb7Y9nEZ8I9vKOe0r4w9nw.9 fzzGRYxO5BgFVM4h3RfZUowwGBZi1M1dmg3G6Io4jWD04IhjMnPpYRsDlqyidUE_iVTT3H3xlmDJ x6MKbap9QDCL7EVAiTdBBdG_eI6UWFgVZHgTJ1J1lCXJBHXZlZgdHYBeZYK5fdP00QGI_f_T_AN8 0qEtdMahroRdxNMKztT5XUV2M39S1kVZPD5wk_i03DQiceQCC9IwyGEzEjxZBafgrkJZA8bHYmHS Eu4cOCYbk5b95P6lkzWZyGE2Pv4hxC_10y.Up_YEBdzVOBaPuHCHunnryJO.oM5qdWhpmJnZJTEY 2RjQDBrlLY7DYDgneavx9isWpDy6TElp3_sCEuhVtt2ps6Qbs0T1m0ttCnhJL1MPSxwrkzgAZfQg I0gxyLNnqwg2IEafd9gVRIhXQ4bKfCFiNhg8YJ3.tjm6.SW7izXqW5XC9P6mrU2qfP3jMGKM9_80 AHexS.j8Lytt3e6fGYWeXQTjwuMU4QpooWID5wdHPUPBOhRLhdN25bVLWIFHN4uJRl.MRaSEUbM5 lyMtmeDXoFA-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.bf2.yahoo.com with HTTP; Mon, 23 Jul 2018 19:42:45 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp413.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 93008fd70d1c0c00c172c8400c29bef1; Mon, 23 Jul 2018 19:42:42 +0000 (UTC) From: Mark Millard Message-Id: <76BCFCB9-1071-4557-9FDE-017444ADBF42@yahoo.com> Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: RPI3 swap experiments Date: Mon, 23 Jul 2018 12:42:39 -0700 In-Reply-To: <20180723190257.GA47869@www.zefox.net> Cc: Trev , freebsd-arm@freebsd.org To: bob prohaska References: <20180630005145.GA43801@www.zefox.net> <6f3406e2-71f3-d0c2-2b65-703e1a1d3c25@sentry.org> <8e92b2b7-da61-3efb-7231-9fac76b2c1d4@sentry.org> <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> <20180723063526.GA45726@www.zefox.net> <20180723155311.GB45726@www.zefox.net> <4ED9B658-A5A8-4BA6-9412-EBB7150B4B66@yahoo.com> <20180723190257.GA47869@www.zefox.net> X-Mailer: Apple Mail (2.3445.9.1) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 19:42:53 -0000 On 2018-Jul-23, at 12:02 PM, bob prohaska wrote: > . . . > Here's a point I find confusing: What is the purpose of cross tools = when the build > is self-hosted? Is "cross-tools" a component of bootstrap tools?=20 When clang is updated, using the existing system clang need not be sufficient. Imagine an extreme case: the jump from clang 5 to clang 6 as the system compiler. clang 6 should be built and used to make the new version of FreeBSD. (Think of other llvm toolchain items than clang as well.) Lesser updates can end up with a similar status. Another context is, say, some 11.x building to update to a 12.x . The temporary bootstrap compiler/toolchain is a form of "self hosted cross-tools". (The "cross" aspect does not involve cpu architecture but other context differences.) (Of course there are FreeBSD architectures that still can not use clang or the related system-llvm tool chain.) Of: -------------------------------------------------------------- >>> stage 1.2: bootstrap tools -------------------------------------------------------------- . . . -------------------------------------------------------------- >>> stage 2.3: build tools -------------------------------------------------------------- . . . -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- it is stage 3 that has the likes of, for example, --- cross-tools --- =3D=3D=3D> lib/clang (obj,all,install) --- all_subdir_lib/clang/libllvm --- =3D=3D=3D> lib/clang/libllvm (all) --- all_subdir_lib/clang/libclang --- =3D=3D=3D> lib/clang/libclang (all) --- all_subdir_lib/clang/headers --- =3D=3D=3D> lib/clang/headers (all) --- realinstall_subdir_lib/clang/libllvm --- =3D=3D=3D> lib/clang/libllvm (install) --- realinstall_subdir_lib/clang/libclang --- =3D=3D=3D> lib/clang/libclang (install) --- realinstall_subdir_lib/clang/headers --- =3D=3D=3D> lib/clang/headers (install) clang 5 would build clang 6 in my example. Then clang 6 would be used to build FreeBSD. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Tue Jul 24 14:46:24 2018 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 5FD7E104DD5C for ; Tue, 24 Jul 2018 14:46:24 +0000 (UTC) (envelope-from grzegorz@blach.pl) Received: from 6.mo179.mail-out.ovh.net (6.mo179.mail-out.ovh.net [46.105.56.76]) (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 D719471DF3 for ; Tue, 24 Jul 2018 14:46:23 +0000 (UTC) (envelope-from grzegorz@blach.pl) Received: from player758.ha.ovh.net (unknown [10.109.159.90]) by mo179.mail-out.ovh.net (Postfix) with ESMTP id 891A3DDE28 for ; Tue, 24 Jul 2018 16:46:15 +0200 (CEST) Received: from starpad.nine (public-gprs368108.centertel.pl [37.47.69.45]) (Authenticated sender: grzegorz@blach.pl) by player758.ha.ovh.net (Postfix) with ESMTPSA id 397982C00AC for ; Tue, 24 Jul 2018 16:46:14 +0200 (CEST) To: freebsd-arm@freebsd.org From: Grzegorz Blach Subject: Boot problem on Raspberry PI 2 Message-ID: <2e95efca-080b-f439-9161-a1c6ae0abe27@blach.pl> Date: Tue, 24 Jul 2018 16:45:58 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Ovh-Tracer-Id: 4302626497949490809 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedtiedrjeeggdejlecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemuceftddtnecu X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2018 14:46:24 -0000 Hi everyone, Yesterday I reported issue related to booting FreeBSD on Raspberry PI 2. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229996 Can anyone investigate this? From owner-freebsd-arm@freebsd.org Tue Jul 24 19:44:33 2018 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 DC220105448D for ; Tue, 24 Jul 2018 19:44:33 +0000 (UTC) (envelope-from peo@nethead.se) Received: from ns1.nethead.se (ns1.nethead.se [5.150.237.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns1.nethead.se", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6EBB47CEC8 for ; Tue, 24 Jul 2018 19:44:32 +0000 (UTC) (envelope-from peo@nethead.se) X-Virus-Scanned: amavisd-new at Nethead AB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nethead.se; s=NETHEADSE; t=1532461463; bh=ahBVcGuCl3JzoyLPAka5pnPusezvgbgS5FSd4q3U2jo=; h=To:From:Subject:Date; b=frZiS9GXeLDi7PBJzqdBfKgDnh/c26Cdd4kSwF8fYh7bK+1YOGQthDMw6UDTzHkSH K7BGseQLXP0OWMWzl9B+CT9+MEQi84xq1FlwFkXQckbyRuEUjc7M5FLVe9vzP+JIt5 vl49QZ/riYDe6410sn/+8uVvoJEI+iWztjIMQZC8= To: freebsd-arm From: Per olof Ljungmark Subject: rpi3 and Adafruit GPS hat continued Message-ID: Date: Tue, 24 Jul 2018 21:44:20 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2018 19:44:34 -0000 Thanks to http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-shield-on-a-Raspberry-Pi-td6236680.html and helpful people on the list I managed to get the pi to boot by silencing the console messages in u-boot. I skipped the switch and patched rpi.h: @@ -85,10 +87,13 @@ #define CONFIG_INITRD_TAG /* Environment */ +#define CONFIG_SYS_DEVICE_NULLDEV +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_RELOC +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_SET #define ENV_DEVICE_SETTINGS \ - "stdin=serial,usbkbd\0" \ - "stdout=serial,vidconsole\0" \ - "stderr=serial,vidconsole\0" + "stdin=usbkbd\0" \ + "stdout=vidconsole\0" \ + "stderr=vidconsole\0" and now the pi is booting. Now to the next problem, I need to rewire TXD and RXD and add reception of the PPS signal on pin 4. The advice in the link above is not appclicable to current and rpi3. Right now uart1 is wired to the RXD and TXD pins, I want uart0. Is it recompile a dts or use gpioctl? uart0: mem 0x7e201000-0x7e201fff irq 24 on simplebus0 uart1: mem 0x7e215040-0x7e21507f irq 32 on simplebus0 uart1: console (115200,n,8,1) Thank you for your patience, //per From owner-freebsd-arm@freebsd.org Wed Jul 25 02:25:03 2018 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 EB7CD103B01A for ; Wed, 25 Jul 2018 02:25:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 76ACC8ABA7 for ; Wed, 25 Jul 2018 02:25:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x236.google.com with SMTP id q19-v6so5099870ioh.11 for ; Tue, 24 Jul 2018 19:25:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=QgGMvrT2hLGdtLmS/a7cVDzHcRPJwQwSjrXXFicjN8I=; b=DbEOjq0M50FIlDrJ6TfaLO5eYdBwRipXbpPTxcMoFxObzslmfmCAO2kaR2raf/w+B/ NXUik26eViLLkbpJSDoUvFtMg4GTaLp8UUEswY93BSNBPIrOQiB03uzUsux3DUse5aK5 kZ5QXEQL5rIsBUy8DuXAdGZ/0QY1z06ZjjOz2ZoJfJ7x/ePQAS+zNLfuw/xhOfN3c/LQ xDWII3ZieVksXFikVfNcMs1rUu3HiYVpdFNbXAqFpvxrP/JbQla1BpRFpqlGaVn7t4Jo ql5YOo8tD4SaOTrE+oDyBQAHzyGAH/I8bz/5rxZTKc3eK9XpR5NOq0zpb58hRUmxu1YY trnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=QgGMvrT2hLGdtLmS/a7cVDzHcRPJwQwSjrXXFicjN8I=; b=cljX2xOlUsJjoMGMeBsYZFmyv/1CH7LXQn5n/nmk7B6NXtzP6pMZey4UMwX4jdy9QK 6SV1NsCZVvigRe6gXSdXvvwyH+mOWHTDhZWBC9IbJPmpEjG0hRqD2irVp2+aWKnAgFWM +oLz7jL2Fvhm7NqHLfT/ryIudwG7IPkxVwQ/NrhmGFefaW4wBK084MuxEBUrFDBW4J0R hYfMa0A3pfc96taXtr5oUVOnSmcKTczqw7g+uoRwKQs/j4pkSqjEIUZynr8ORu/4Y9UL Pjh3IFFhTf4qe81EScGlVbh1ycfbglCtofco/7P4H7mqfjXo5Z+EK+XpvywbPwDokIhE 4+ag== X-Gm-Message-State: AOUpUlFU6vS0LZfQyScOkmWHKJli+ZMn9U3jv+AcmRxcvc91qtqepNk0 NiteCKGHj3mIP4TL2LogF3jA/3hwGpTqsF+P/JikiniIO8w= X-Google-Smtp-Source: AAOMgpcRAiamspuvAQjyy3v/nJuVyNBqsE4XWuxIR+agB5KmFF9viwkJ3CZP5841Sg+wu4FHBiVddiNOc+DFn39LKhc= X-Received: by 2002:a6b:d004:: with SMTP id x4-v6mr14866058ioa.299.1532485501729; Tue, 24 Jul 2018 19:25:01 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:4485:0:0:0:0:0 with HTTP; Tue, 24 Jul 2018 19:25:01 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: From: Warner Losh Date: Tue, 24 Jul 2018 20:25:01 -0600 X-Google-Sender-Auth: pclWH5zD1UgU-bVl61byTGoGGSA Message-ID: Subject: Re: rpi3 and Adafruit GPS hat continued To: Per olof Ljungmark Cc: freebsd-arm Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 02:25:03 -0000 On Tue, Jul 24, 2018 at 1:44 PM, Per olof Ljungmark wrote: > Thanks to > http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-shield-on-a- > Raspberry-Pi-td6236680.html > and helpful people on the list I managed to get the pi to boot by > silencing the console messages in u-boot. > > I skipped the switch and patched rpi.h: > > @@ -85,10 +87,13 @@ > #define CONFIG_INITRD_TAG > > /* Environment */ > +#define CONFIG_SYS_DEVICE_NULLDEV > +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_RELOC > +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_SET > #define ENV_DEVICE_SETTINGS \ > - "stdin=serial,usbkbd\0" \ > - "stdout=serial,vidconsole\0" \ > - "stderr=serial,vidconsole\0" > + "stdin=usbkbd\0" \ > + "stdout=vidconsole\0" \ > + "stderr=vidconsole\0" > > and now the pi is booting. > > Now to the next problem, I need to rewire TXD and RXD and add reception > of the PPS signal on pin 4. The advice in the link above is not > appclicable to current and rpi3. > > Right now uart1 is wired to the RXD and TXD pins, I want uart0. Is it > recompile a dts or use gpioctl? > > uart0: mem 0x7e201000-0x7e201fff irq 24 on > simplebus0 > uart1: mem 0x7e215040-0x7e21507f irq 32 on simplebus0 > uart1: console (115200,n,8,1) > I'm pretty sure that you'll need to hack dts. Warner From owner-freebsd-arm@freebsd.org Wed Jul 25 09:28:02 2018 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 2032C1045893 for ; Wed, 25 Jul 2018 09:28:02 +0000 (UTC) (envelope-from peo@nethead.se) Received: from ns1.nethead.se (ns1.nethead.se [5.150.237.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns1.nethead.se", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B2B967690B for ; Wed, 25 Jul 2018 09:28:01 +0000 (UTC) (envelope-from peo@nethead.se) X-Virus-Scanned: amavisd-new at Nethead AB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nethead.se; s=NETHEADSE; t=1532510879; bh=2fhKKGcXQt13cZMWW7/7aJLGOGR1GpbE6vhdQUy9lM0=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=b/3VpSKDYLJGUdN66pozIyu1X0HzgCBFxfqspQIZp3O6NIgCgtVBJ5GKWzBXxTU1q RgA8GfD7T3cY+/rvFd10F1D0fzsbt4aYtVsS9gHbWhTLdoyuq5QShvBrRXCHzVMqsV /eNW822RKMjZszj1DtojJ+FSkBoQz/k80GWS+vdA= Subject: Re: rpi3 and Adafruit GPS hat continued To: Warner Losh Cc: freebsd-arm References: From: Per olof Ljungmark Message-ID: Date: Wed, 25 Jul 2018 11:27:53 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 09:28:02 -0000 On 07/25/18 04:25, Warner Losh wrote: > > > On Tue, Jul 24, 2018 at 1:44 PM, Per olof Ljungmark > wrote: > > Thanks to > http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-shield-on-a-Raspberry-Pi-td6236680.html > > and helpful people on the list I managed to get the pi to boot by > silencing the console messages in u-boot. > > I skipped the switch and patched rpi.h: > > @@ -85,10 +87,13 @@ >  #define CONFIG_INITRD_TAG > >  /* Environment */ > +#define CONFIG_SYS_DEVICE_NULLDEV > +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_RELOC > +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_SET >  #define ENV_DEVICE_SETTINGS \ > -       "stdin=serial,usbkbd\0" \ > -       "stdout=serial,vidconsole\0" \ > -       "stderr=serial,vidconsole\0" > +       "stdin=usbkbd\0" \ > +       "stdout=vidconsole\0" \ > +       "stderr=vidconsole\0" > > and now the pi is booting. > > Now to the next problem, I need to rewire TXD and RXD and add reception > of the PPS signal on pin 4. The advice in the link above is not > appclicable to current and rpi3. > > Right now uart1 is wired to the RXD and TXD pins, I want uart0. Is it > recompile a dts or use gpioctl? > > uart0: mem 0x7e201000-0x7e201fff irq 24 on > simplebus0 > uart1: mem 0x7e215040-0x7e21507f irq 32 on > simplebus0 > uart1: console (115200,n,8,1) > > > I'm pretty sure that you'll need to hack dts. Yes. Most importantly, stop the kernel from talking to the serial console. I've been wandering around the source and right now the theory is to change /usr/src/sys/gnu/dts/arm/bcm283x.dtsi, it is the only place in all the included dts files where I find a reference to the console: chosen { stdout-path = "serial0:115200n8"; }; Says nothing about stdin though, not anywhere. From owner-freebsd-arm@freebsd.org Wed Jul 25 09:55:51 2018 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 93CDF10463B4 for ; Wed, 25 Jul 2018 09:55:51 +0000 (UTC) (envelope-from peo@nethead.se) Received: from ns1.nethead.se (ns1.nethead.se [5.150.237.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns1.nethead.se", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 250A577804 for ; Wed, 25 Jul 2018 09:55:51 +0000 (UTC) (envelope-from peo@nethead.se) X-Virus-Scanned: amavisd-new at Nethead AB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nethead.se; s=NETHEADSE; t=1532512549; bh=vBSysvR+WtyIBg2euqQ0t4ABRXBk6iJP7HzFE6hnyq0=; h=Subject:From:Cc:References:To:Date:In-Reply-To; b=On9bjwj3UKOwngZe01cN+IxdZ5NIj5+8aQcf77QhEguDH/ULGuMgWuD/JNe7x8pZ3 HKNCGKesVvxdjvAzY/W58BE1rpxyGAe3g9mw8WkGyhShfcxVdeX6b0YNx31ODbzR8w cNwGLSvI10iRlYk3ixg7PFwZp7kxM8dkV9Wqd3tw= Subject: Re: rpi3 and Adafruit GPS hat continued From: Per olof Ljungmark References: To: freebsd-arm Message-ID: <2f55aaea-6832-7441-1011-b8288628a4a9@nethead.se> Date: Wed, 25 Jul 2018 11:55:47 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 09:55:51 -0000 On 07/25/18 11:27, Per olof Ljungmark wrote: > On 07/25/18 04:25, Warner Losh wrote: >> >> >> On Tue, Jul 24, 2018 at 1:44 PM, Per olof Ljungmark > > wrote: >> >> Thanks to >> http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-shield-on-a-Raspberry-Pi-td6236680.html >> >> and helpful people on the list I managed to get the pi to boot by >> silencing the console messages in u-boot. >> >> I skipped the switch and patched rpi.h: >> >> @@ -85,10 +87,13 @@ >>  #define CONFIG_INITRD_TAG >> >>  /* Environment */ >> +#define CONFIG_SYS_DEVICE_NULLDEV >> +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_RELOC >> +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_SET >>  #define ENV_DEVICE_SETTINGS \ >> -       "stdin=serial,usbkbd\0" \ >> -       "stdout=serial,vidconsole\0" \ >> -       "stderr=serial,vidconsole\0" >> +       "stdin=usbkbd\0" \ >> +       "stdout=vidconsole\0" \ >> +       "stderr=vidconsole\0" >> >> and now the pi is booting. >> >> Now to the next problem, I need to rewire TXD and RXD and add reception >> of the PPS signal on pin 4. The advice in the link above is not >> appclicable to current and rpi3. >> >> Right now uart1 is wired to the RXD and TXD pins, I want uart0. Is it >> recompile a dts or use gpioctl? >> >> uart0: mem 0x7e201000-0x7e201fff irq 24 on >> simplebus0 >> uart1: mem 0x7e215040-0x7e21507f irq 32 on >> simplebus0 >> uart1: console (115200,n,8,1) >> >> >> I'm pretty sure that you'll need to hack dts. > > Yes. Most importantly, stop the kernel from talking to the serial console. > > I've been wandering around the source and right now the theory is to > change /usr/src/sys/gnu/dts/arm/bcm283x.dtsi, it is the only place in > all the included dts files where I find a reference to the console: > > chosen { > stdout-path = "serial0:115200n8"; > }; > > Says nothing about stdin though, not anywhere. Tried stdout-path = ""; but that did not help. I'm giving up and move to rpi2 and 11.2 instead. Phew. From owner-freebsd-arm@freebsd.org Wed Jul 25 10:36:02 2018 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 72F181046FDC for ; Wed, 25 Jul 2018 10:36:02 +0000 (UTC) (envelope-from ralph@ralphsmith.org) Received: from ralphsmith.org (ralphsmith.org [98.172.20.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ralphsmith.org", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1233B78DBC for ; Wed, 25 Jul 2018 10:36:01 +0000 (UTC) (envelope-from ralph@ralphsmith.org) Received: from [192.168.0.179] ([192.168.0.179]) (authenticated bits=0) by ralphsmith.org (8.15.2/8.15.2) with ESMTPSA id w6PAZsSX097452 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 25 Jul 2018 06:35:54 -0400 (EDT) (envelope-from ralph@ralphsmith.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ralphsmith.org; s=201502; t=1532514954; bh=CzsaTLHs8e+VySSRLCZlHFp5pHRZFGjZwvH6zgjfb3E=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=LTB9xEhbAWuynLonxu2eYOvoL5LrTuFhASbwrJrVRHzL7P2t2gbCrDAlx6o8EXNa5 eHwI/1cEy0mCKENGkO3G2RFWnBiFLKVrqnt+1ZUGO9zjLQtMcH4kaE9C0fK1FPC0r/ 6TDsG0/jV5nag1nddcyukKcVkeq8Vq3ugPtL0JLw= Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: rpi3 and Adafruit GPS hat continued From: Ralph Smith X-Mailer: iPhone Mail (15G77) In-Reply-To: <2f55aaea-6832-7441-1011-b8288628a4a9@nethead.se> Date: Wed, 25 Jul 2018 06:35:53 -0400 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: References: <2f55aaea-6832-7441-1011-b8288628a4a9@nethead.se> To: Per olof Ljungmark X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 10:36:02 -0000 Sent from my iPhone > On Jul 25, 2018, at 5:55 AM, Per olof Ljungmark wrote: >=20 >> On 07/25/18 11:27, Per olof Ljungmark wrote: >>> On 07/25/18 04:25, Warner Losh wrote: >>>=20 >>>=20 >>> On Tue, Jul 24, 2018 at 1:44 PM, Per olof Ljungmark >> > wrote: >>>=20 >>> Thanks to >>> http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-shield-o= n-a-Raspberry-Pi-td6236680.html >>> >>> and helpful people on the list I managed to get the pi to boot by >>> silencing the console messages in u-boot. >>>=20 >>> I skipped the switch and patched rpi.h: >>>=20 >>> @@ -85,10 +87,13 @@ >>> #define CONFIG_INITRD_TAG >>>=20 >>> /* Environment */ >>> +#define CONFIG_SYS_DEVICE_NULLDEV >>> +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_RELOC >>> +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_SET >>> #define ENV_DEVICE_SETTINGS \ >>> - "stdin=3Dserial,usbkbd\0" \ >>> - "stdout=3Dserial,vidconsole\0" \ >>> - "stderr=3Dserial,vidconsole\0" >>> + "stdin=3Dusbkbd\0" \ >>> + "stdout=3Dvidconsole\0" \ >>> + "stderr=3Dvidconsole\0" >>>=20 >>> and now the pi is booting. >>>=20 >>> Now to the next problem, I need to rewire TXD and RXD and add recepti= on >>> of the PPS signal on pin 4. The advice in the link above is not >>> appclicable to current and rpi3. >>>=20 >>> Right now uart1 is wired to the RXD and TXD pins, I want uart0. Is it= >>> recompile a dts or use gpioctl? >>>=20 >>> uart0: mem 0x7e201000-0x7e201fff irq 24 on >>> simplebus0 >>> uart1: mem 0x7e215040-0x7e21507f irq 32 on >>> simplebus0 >>> uart1: console (115200,n,8,1) >>>=20 >>>=20 >>> I'm pretty sure that you'll need to hack dts. >>=20 >> Yes. Most importantly, stop the kernel from talking to the serial console= . >>=20 >> I've been wandering around the source and right now the theory is to >> change /usr/src/sys/gnu/dts/arm/bcm283x.dtsi, it is the only place in >> all the included dts files where I find a reference to the console: >>=20 >> chosen { >> stdout-path =3D "serial0:115200n8"; >> }; >>=20 >> Says nothing about stdin though, not anywhere. >=20 > Tried stdout-path =3D ""; but that did not help. >=20 > I'm giving up and move to rpi2 and 11.2 instead. Phew. Just another gotcha to worry about: be aware of the difference between the r= pi2 board versions 1.1 and 1.2. They quietly changed the SOC, so FreeBSD 11.= 1 would not boot on the rev 1.2 board. It will boot FreeBSD 11.2, but I=E2=80= =99ve not tried the GPS HAT on that yet.=20 Ralph= From owner-freebsd-arm@freebsd.org Wed Jul 25 10:45:33 2018 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 96D7F10472DB for ; Wed, 25 Jul 2018 10:45:33 +0000 (UTC) (envelope-from peo@nethead.se) Received: from ns1.nethead.se (ns1.nethead.se [5.150.237.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns1.nethead.se", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0D0BA79146 for ; Wed, 25 Jul 2018 10:45:33 +0000 (UTC) (envelope-from peo@nethead.se) X-Virus-Scanned: amavisd-new at Nethead AB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nethead.se; s=NETHEADSE; t=1532515531; bh=brNJOuBWHGgY/xHaBOVRxu0WPoRDY2hAoEGVpoJSu9U=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=MurhmIflqJ1eiqgfV3j+vvCzdoF2zHKn/Pr0dsXI0uWwu8pw9yK/oMVXN4I9WvEqi U6NFGC4I0yloBjP+hr/LoakZBYiWMviCTdQvGVd7k+gkSC4W+2MAwpkUSACnuG2MJv Uj0ADWJaPV2r5g2NxagBLTi11xQzVsmnyZWemT5o= Subject: Re: rpi3 and Adafruit GPS hat continued To: Ralph Smith Cc: freebsd-arm References: <2f55aaea-6832-7441-1011-b8288628a4a9@nethead.se> From: Per olof Ljungmark Message-ID: <61aca7dc-0c71-b697-6d57-aeded7ce780f@nethead.se> Date: Wed, 25 Jul 2018 12:45:29 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 10:45:33 -0000 On 07/25/18 12:35, Ralph Smith wrote: > > > Sent from my iPhone > >> On Jul 25, 2018, at 5:55 AM, Per olof Ljungmark wrote: >> >>> On 07/25/18 11:27, Per olof Ljungmark wrote: >>>> On 07/25/18 04:25, Warner Losh wrote: >>>> >>>> >>>> On Tue, Jul 24, 2018 at 1:44 PM, Per olof Ljungmark >>> > wrote: >>>> >>>> Thanks to >>>> http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-shield-on-a-Raspberry-Pi-td6236680.html >>>> >>>> and helpful people on the list I managed to get the pi to boot by >>>> silencing the console messages in u-boot. >>>> >>>> I skipped the switch and patched rpi.h: >>>> >>>> @@ -85,10 +87,13 @@ >>>> #define CONFIG_INITRD_TAG >>>> >>>> /* Environment */ >>>> +#define CONFIG_SYS_DEVICE_NULLDEV >>>> +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_RELOC >>>> +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_SET >>>> #define ENV_DEVICE_SETTINGS \ >>>> - "stdin=serial,usbkbd\0" \ >>>> - "stdout=serial,vidconsole\0" \ >>>> - "stderr=serial,vidconsole\0" >>>> + "stdin=usbkbd\0" \ >>>> + "stdout=vidconsole\0" \ >>>> + "stderr=vidconsole\0" >>>> >>>> and now the pi is booting. >>>> >>>> Now to the next problem, I need to rewire TXD and RXD and add reception >>>> of the PPS signal on pin 4. The advice in the link above is not >>>> appclicable to current and rpi3. >>>> >>>> Right now uart1 is wired to the RXD and TXD pins, I want uart0. Is it >>>> recompile a dts or use gpioctl? >>>> >>>> uart0: mem 0x7e201000-0x7e201fff irq 24 on >>>> simplebus0 >>>> uart1: mem 0x7e215040-0x7e21507f irq 32 on >>>> simplebus0 >>>> uart1: console (115200,n,8,1) >>>> >>>> >>>> I'm pretty sure that you'll need to hack dts. >>> >>> Yes. Most importantly, stop the kernel from talking to the serial console. >>> >>> I've been wandering around the source and right now the theory is to >>> change /usr/src/sys/gnu/dts/arm/bcm283x.dtsi, it is the only place in >>> all the included dts files where I find a reference to the console: >>> >>> chosen { >>> stdout-path = "serial0:115200n8"; >>> }; >>> >>> Says nothing about stdin though, not anywhere. >> >> Tried stdout-path = ""; but that did not help. >> >> I'm giving up and move to rpi2 and 11.2 instead. Phew. > > Just another gotcha to worry about: be aware of the difference between the rpi2 board versions 1.1 and 1.2. They quietly changed the SOC, so FreeBSD 11.1 would not boot on the rev 1.2 board. It will boot FreeBSD 11.2, but I’ve not tried the GPS HAT on that yet. Thank you for the heads up - I have not checked yet what version of rpi2 I have, think I have one of each. I'll be back and report later. From owner-freebsd-arm@freebsd.org Wed Jul 25 14:26:20 2018 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 6DA32104C6DA for ; Wed, 25 Jul 2018 14:26:20 +0000 (UTC) (envelope-from peo@nethead.se) Received: from ns1.nethead.se (ns1.nethead.se [5.150.237.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns1.nethead.se", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D6F398054F for ; Wed, 25 Jul 2018 14:26:19 +0000 (UTC) (envelope-from peo@nethead.se) X-Virus-Scanned: amavisd-new at Nethead AB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nethead.se; s=NETHEADSE; t=1532528777; bh=Dxw3HawDi8sqYNQWXqVEH21xQavb9eeLOgpyc6KYI6g=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=ec6xU2tCRWfsVYx/am0FSKO2EM3DMkA4WlQRvYhqX0qJFKdpAsvwdZd4O8rwHTGsl hFcQAtfyaHALOkG+I9MmDNx6FauTURWIbfBoy0gXiEVasmWBXiwalNQVebIJPlSsp2 QxhAZFYxhYdq2Aw3onPciR9QXGlwq+qcmgcxF6xw= Subject: Re: rpi3 and Adafruit GPS hat continued To: Ralph Smith Cc: freebsd-arm References: <2f55aaea-6832-7441-1011-b8288628a4a9@nethead.se> From: Per olof Ljungmark Message-ID: <2aee4fd4-c221-23a6-00e4-1db2694bfef6@nethead.se> Date: Wed, 25 Jul 2018 16:26:15 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 14:26:20 -0000 On 07/25/18 12:35, Ralph Smith wrote: > > > Sent from my iPhone > >> On Jul 25, 2018, at 5:55 AM, Per olof Ljungmark wrote: >> >>> On 07/25/18 11:27, Per olof Ljungmark wrote: >>>> On 07/25/18 04:25, Warner Losh wrote: >>>> >>>> >>>> On Tue, Jul 24, 2018 at 1:44 PM, Per olof Ljungmark >>> > wrote: >>>> >>>> Thanks to >>>> http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-shield-on-a-Raspberry-Pi-td6236680.html >>>> >>>> and helpful people on the list I managed to get the pi to boot by >>>> silencing the console messages in u-boot. >>>> >>>> I skipped the switch and patched rpi.h: >>>> >>>> @@ -85,10 +87,13 @@ >>>> #define CONFIG_INITRD_TAG >>>> >>>> /* Environment */ >>>> +#define CONFIG_SYS_DEVICE_NULLDEV >>>> +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_RELOC >>>> +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_SET >>>> #define ENV_DEVICE_SETTINGS \ >>>> - "stdin=serial,usbkbd\0" \ >>>> - "stdout=serial,vidconsole\0" \ >>>> - "stderr=serial,vidconsole\0" >>>> + "stdin=usbkbd\0" \ >>>> + "stdout=vidconsole\0" \ >>>> + "stderr=vidconsole\0" >>>> >>>> and now the pi is booting. >>>> >>>> Now to the next problem, I need to rewire TXD and RXD and add reception >>>> of the PPS signal on pin 4. The advice in the link above is not >>>> appclicable to current and rpi3. >>>> >>>> Right now uart1 is wired to the RXD and TXD pins, I want uart0. Is it >>>> recompile a dts or use gpioctl? >>>> >>>> uart0: mem 0x7e201000-0x7e201fff irq 24 on >>>> simplebus0 >>>> uart1: mem 0x7e215040-0x7e21507f irq 32 on >>>> simplebus0 >>>> uart1: console (115200,n,8,1) >>>> >>>> >>>> I'm pretty sure that you'll need to hack dts. >>> >>> Yes. Most importantly, stop the kernel from talking to the serial console. >>> >>> I've been wandering around the source and right now the theory is to >>> change /usr/src/sys/gnu/dts/arm/bcm283x.dtsi, it is the only place in >>> all the included dts files where I find a reference to the console: >>> >>> chosen { >>> stdout-path = "serial0:115200n8"; >>> }; >>> >>> Says nothing about stdin though, not anywhere. >> >> Tried stdout-path = ""; but that did not help. >> >> I'm giving up and move to rpi2 and 11.2 instead. Phew. > > Just another gotcha to worry about: be aware of the difference between the rpi2 board versions 1.1 and 1.2. They quietly changed the SOC, so FreeBSD 11.1 would not boot on the rev 1.2 board. It will boot FreeBSD 11.2, but I’ve not tried the GPS HAT on that yet. I have dug out a rpi2 v1.1 and now wandering what image to boot, the v1.1 is armv7 but can't find any images for 11 and armv7. Does this mean I have to build it? The idea here was to aviod 12 due to the dts shuffle. From owner-freebsd-arm@freebsd.org Wed Jul 25 14:35:45 2018 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 56E20104CAC2 for ; Wed, 25 Jul 2018 14:35:45 +0000 (UTC) (envelope-from ralph@ralphsmith.org) Received: from ralphsmith.org (ralphsmith.org [98.172.20.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ralphsmith.org", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0548080C6B for ; Wed, 25 Jul 2018 14:35:44 +0000 (UTC) (envelope-from ralph@ralphsmith.org) Received: from [192.168.140.100] ([198.99.129.142]) (authenticated bits=0) by ralphsmith.org (8.15.2/8.15.2) with ESMTPSA id w6PEZeS5011981 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 25 Jul 2018 10:35:42 -0400 (EDT) (envelope-from ralph@ralphsmith.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ralphsmith.org; s=201502; t=1532529343; bh=CNihH8dacf6lbf+bSGqk9MTx94inNZSglfnF7khYMJk=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=ekBJmVltMvF/obXGBFMuLqDzQRGpSSYTgVeA7mD34InHt5GwjZJKspB6phHkM5Fvy zS3J7sOnjrp+oY3upL7or87QiFkmIjgZalwEPKk7jNsam8wQyRQKev56d6Dna+7cET CMBe9dG/KPKtspuGYHby3P+fmVH+u38j0XOCTOgY= Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: rpi3 and Adafruit GPS hat continued From: Ralph Smith X-Mailer: iPhone Mail (15G77) In-Reply-To: <2aee4fd4-c221-23a6-00e4-1db2694bfef6@nethead.se> Date: Wed, 25 Jul 2018 10:35:35 -0400 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <6DCECF08-1366-4289-9929-94A967284291@ralphsmith.org> References: <2f55aaea-6832-7441-1011-b8288628a4a9@nethead.se> <2aee4fd4-c221-23a6-00e4-1db2694bfef6@nethead.se> To: Per olof Ljungmark X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 14:35:45 -0000 Sent from my iPhone > On Jul 25, 2018, at 10:26 AM, Per olof Ljungmark wrote: >=20 >> On 07/25/18 12:35, Ralph Smith wrote: >>=20 >>=20 >> Sent from my iPhone >>=20 >>>> On Jul 25, 2018, at 5:55 AM, Per olof Ljungmark wrote:= >>>>=20 >>>>> On 07/25/18 11:27, Per olof Ljungmark wrote: >>>>> On 07/25/18 04:25, Warner Losh wrote: >>>>>=20 >>>>>=20 >>>>> On Tue, Jul 24, 2018 at 1:44 PM, Per olof Ljungmark >>>> > wrote: >>>>>=20 >>>>> Thanks to >>>>> http://freebsd.1045724.x6.nabble.com/Adding-a-GPS-Module-hat-shield-= on-a-Raspberry-Pi-td6236680.html >>>>> >>>>> and helpful people on the list I managed to get the pi to boot by >>>>> silencing the console messages in u-boot. >>>>>=20 >>>>> I skipped the switch and patched rpi.h: >>>>>=20 >>>>> @@ -85,10 +87,13 @@ >>>>> #define CONFIG_INITRD_TAG >>>>>=20 >>>>> /* Environment */ >>>>> +#define CONFIG_SYS_DEVICE_NULLDEV >>>>> +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_RELOC >>>>> +#define CONFIG_SILENT_CONSOLE_UPDATE_ON_SET >>>>> #define ENV_DEVICE_SETTINGS \ >>>>> - "stdin=3Dserial,usbkbd\0" \ >>>>> - "stdout=3Dserial,vidconsole\0" \ >>>>> - "stderr=3Dserial,vidconsole\0" >>>>> + "stdin=3Dusbkbd\0" \ >>>>> + "stdout=3Dvidconsole\0" \ >>>>> + "stderr=3Dvidconsole\0" >>>>>=20 >>>>> and now the pi is booting. >>>>>=20 >>>>> Now to the next problem, I need to rewire TXD and RXD and add recept= ion >>>>> of the PPS signal on pin 4. The advice in the link above is not >>>>> appclicable to current and rpi3. >>>>>=20 >>>>> Right now uart1 is wired to the RXD and TXD pins, I want uart0. Is i= t >>>>> recompile a dts or use gpioctl? >>>>>=20 >>>>> uart0: mem 0x7e201000-0x7e201fff irq 24 on >>>>> simplebus0 >>>>> uart1: mem 0x7e215040-0x7e21507f irq 32 on >>>>> simplebus0 >>>>> uart1: console (115200,n,8,1) >>>>>=20 >>>>>=20 >>>>> I'm pretty sure that you'll need to hack dts. >>>>=20 >>>> Yes. Most importantly, stop the kernel from talking to the serial conso= le. >>>>=20 >>>> I've been wandering around the source and right now the theory is to >>>> change /usr/src/sys/gnu/dts/arm/bcm283x.dtsi, it is the only place in >>>> all the included dts files where I find a reference to the console: >>>>=20 >>>> chosen { >>>> stdout-path =3D "serial0:115200n8"; >>>> }; >>>>=20 >>>> Says nothing about stdin though, not anywhere. >>>=20 >>> Tried stdout-path =3D ""; but that did not help. >>>=20 >>> I'm giving up and move to rpi2 and 11.2 instead. Phew. >>=20 >> Just another gotcha to worry about: be aware of the difference between th= e rpi2 board versions 1.1 and 1.2. They quietly changed the SOC, so FreeBSD 1= 1.1 would not boot on the rev 1.2 board. It will boot FreeBSD 11.2, but I=E2= =80=99ve not tried the GPS HAT on that yet.=20 >=20 > I have dug out a rpi2 v1.1 and now wandering what image to boot, the > v1.1 is armv7 but can't find any images for 11 and armv7. Does this mean > I have to build it? The idea here was to aviod 12 due to the dts shuffle. For 11 you will need to use armv6.=20= From owner-freebsd-arm@freebsd.org Wed Jul 25 19:49:41 2018 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 5079E1052F51 for ; Wed, 25 Jul 2018 19:49:41 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BEA6C8BE91 for ; Wed, 25 Jul 2018 19:49:40 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=dN9WlHYTURLVPlwz0sUhzM3+wQe/bPGOmKyo+zkMfMo=; b=oWhsjS+jarvrxymFe7NHRfpaiz19sPiCJoHSzZhrj8ZJP0EB5pNMwRfi0gk0Yjlqs9m66hb2YZoEZ6wjCxieOZeGxFr9RLdR9dy+IcHSuUqXNRV09f7FqE32bWQDpL1j/V7JFmLFZkSACd17rNT3PNUKLuV2yJ7UGQ7+QSbhkBk= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id feb04b8c TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO for ; Wed, 25 Jul 2018 19:49:29 +0000 (UTC) Date: Wed, 25 Jul 2018 22:49:23 +0300 From: Greg V Subject: Allwinner dtb overlays on CURRENT. Also, flashrom SPI! To: freebsd-arm@freebsd.org Message-Id: <1532548163.59286.0@hraggstad.unrelenting.technology> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 19:49:41 -0000 Hi, One thing I have noticed with CURRENT on an Orange Pi PC: since we're=20 using device trees imported from Linux, some drivers are not accessible=20 out of the box. So I wrote a couple overlays: Thermal sensor: https://github.com/freebsd/freebsd/pull/162 SPI: https://github.com/freebsd/freebsd/pull/166 But not everyone would figure out how to make and even just use=20 overlays=85 (if anyone is wondering: place them into /boot/dtb/overlays and add a=20 list of them (filenames including extension) to /boot/loader.conf like=20 so: fdt_overlays=3D"sun8i-h3-sid.dtbo,sun8i-h3-ts.dtbo,sun8i-h3-spi.dtbo"=20 =97 and reboot) Can someone commit these overlays / add more for other SoCs maybe? P.S. I also wrote spigen support for flashrom:=20 https://github.com/flashrom/flashrom/pull/53 With this, I can flash and verify a Winbond W25Q32.V flash chip from my=20 Orange Pi! :) = From owner-freebsd-arm@freebsd.org Wed Jul 25 20:14:52 2018 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 4C8171053AA5 for ; Wed, 25 Jul 2018 20:14:52 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F3EB58D0D6 for ; Wed, 25 Jul 2018 20:14:51 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f173.google.com (mail-lj1-f173.google.com [209.85.208.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 92A2F1F92D for ; Wed, 25 Jul 2018 20:14:51 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f173.google.com with SMTP id 203-v6so7746572ljj.13 for ; Wed, 25 Jul 2018 13:14:51 -0700 (PDT) X-Gm-Message-State: AOUpUlFrWvpBL74vGLGa8F/IYcuPWrLz5MjFUKjggrsOMBM4RtPggOBY 8t1klbL7tsK+oZKHDJIMgERJ3vTNSWIMnf/Ssbs= X-Google-Smtp-Source: AAOMgpe1y+EB0TENCZy2VTk87CzAuIhY4xJm4QIOo5qXaE5myPd10eMg77B24HA3ZaGaFrmhV1klFa1i9D07oTcUwa0= X-Received: by 2002:a2e:1004:: with SMTP id j4-v6mr17130797lje.2.1532549690181; Wed, 25 Jul 2018 13:14:50 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Wed, 25 Jul 2018 13:14:29 -0700 (PDT) In-Reply-To: <1532548163.59286.0@hraggstad.unrelenting.technology> References: <1532548163.59286.0@hraggstad.unrelenting.technology> From: Kyle Evans Date: Wed, 25 Jul 2018 15:14:29 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Allwinner dtb overlays on CURRENT. Also, flashrom SPI! To: Greg V Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 20:14:52 -0000 On Wed, Jul 25, 2018 at 2:49 PM, Greg V wrote= : > Hi, > > One thing I have noticed with CURRENT on an Orange Pi PC: since we're usi= ng > device trees imported from Linux, some drivers are not accessible out of = the > box. > > So I wrote a couple overlays: > > Thermal sensor: https://github.com/freebsd/freebsd/pull/162 > > SPI: https://github.com/freebsd/freebsd/pull/166 > > But not everyone would figure out how to make and even just use overlays= =E2=80=A6 > > (if anyone is wondering: place them into /boot/dtb/overlays and add a lis= t > of them (filenames including extension) to /boot/loader.conf like so: > fdt_overlays=3D"sun8i-h3-sid.dtbo,sun8i-h3-ts.dtbo,sun8i-h3-spi.dtbo" =E2= =80=94 and > reboot) Just FYI- omitting the extension should also work fine here. If it doesn't, that's another bug on its own. =3D) > Can someone commit these overlays / add more for other SoCs maybe? I think manu was working on some thermal sensor stuff earlier (though my memory may be wrong), so we'll see what he says. > P.S. I also wrote spigen support for flashrom: > https://github.com/flashrom/flashrom/pull/53 > With this, I can flash and verify a Winbond W25Q32.V flash chip from my > Orange Pi! :) > > _______________________________________________ > 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 Wed Jul 25 21:40:04 2018 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 239261054D04 for ; Wed, 25 Jul 2018 21:40:04 +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 781C38F568; Wed, 25 Jul 2018 21:40:02 +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 537f85e9; Wed, 25 Jul 2018 23:40:01 +0200 (CEST) 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=EoZ+C/rJmYnsY7NLtwpCurL/S5s=; b=CLONHyCcfTdEN0DIZtWeYgZzOljh G0dR+tf5xhA8jfzzUsyQt6tlPdAoHO2IoNUMyLzVKYvepkNWalArssAGoAwvNDSL vctnuB+wDt49sGobFPH6AUMPHfNE86iU8x0qFdxm/Jq3DehgfIsj8+RlDHCZ+JSA MFO7Ol1tQ7ViMuM= 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=my1d2M89segc28z1CWaFiLXSmjdAxpt3aVUIZxppWfm9mkarjEGiHYwL nfrHmwzuZTZs8cU5MOqUFOU+h5z3xoiyFMayCEYnXFvFPLqvij5SIJH0+y7Ss3JJ TtBPn0xEDfTllvKbYcVrEDGRCC6ltGR+xFzX7aSyq59HnaV6q24= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id a82aeef3 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 25 Jul 2018 23:40:01 +0200 (CEST) Date: Wed, 25 Jul 2018 23:40:00 +0200 From: Emmanuel Vadot To: Kyle Evans Cc: Greg V , "freebsd-arm@freebsd.org" Subject: Re: Allwinner dtb overlays on CURRENT. Also, flashrom SPI! Message-Id: <20180725234000.e917566724f997319f8fe2fd@bidouilliste.com> In-Reply-To: References: <1532548163.59286.0@hraggstad.unrelenting.technology> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 21:40:04 -0000 On Wed, 25 Jul 2018 15:14:29 -0500 Kyle Evans wrote: > On Wed, Jul 25, 2018 at 2:49 PM, Greg V wro= te: > > Hi, > > > > One thing I have noticed with CURRENT on an Orange Pi PC: since we're u= sing > > device trees imported from Linux, some drivers are not accessible out o= f the > > box. > > > > So I wrote a couple overlays: > > > > Thermal sensor: https://github.com/freebsd/freebsd/pull/162 > > This is wrong bindings. Yes I know that it's working with our driver for ths but this is wrong. 1) ths module isn't in ahb but apb. 2) We need nvmem framework to get the sensor calibration data, please see https://reviews.freebsd.org/D16419 > > SPI: https://github.com/freebsd/freebsd/pull/166 What is the point of the spigen interface ? If aw_spi is working on H3 (I haven't check but it should), if you have a good dtb with the spi flash described you can use it directly. > > But not everyone would figure out how to make and even just use overlay= s? > > > > (if anyone is wondering: place them into /boot/dtb/overlays and add a l= ist > > of them (filenames including extension) to /boot/loader.conf like so: > > fdt_overlays=3D"sun8i-h3-sid.dtbo,sun8i-h3-ts.dtbo,sun8i-h3-spi.dtbo" ?= and > > reboot) >=20 > Just FYI- omitting the extension should also work fine here. If it > doesn't, that's another bug on its own. =3D) >=20 > > Can someone commit these overlays / add more for other SoCs maybe? >=20 > I think manu was working on some thermal sensor stuff earlier (though > my memory may be wrong), so we'll see what he says. I am, currently upstreaming bindings/dts changes. > > P.S. I also wrote spigen support for flashrom: > > https://github.com/flashrom/flashrom/pull/53 > > With this, I can flash and verify a Winbond W25Q32.V flash chip from my > > Orange Pi! :) > > > > _______________________________________________ > > 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" > _______________________________________________ > 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" --=20 Emmanuel Vadot From owner-freebsd-arm@freebsd.org Wed Jul 25 23:24:45 2018 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 7C3FA1056857 for ; Wed, 25 Jul 2018 23:24:45 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D7661722E2 for ; Wed, 25 Jul 2018 23:24:44 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w6PNOs3u057812 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 25 Jul 2018 16:24:55 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w6PNOrrX057811; Wed, 25 Jul 2018 16:24:54 -0700 (PDT) (envelope-from fbsd) Date: Wed, 25 Jul 2018 16:24:53 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Re: RPI3 swap experiments Message-ID: <20180725232453.GA57716@www.zefox.net> References: <8e92b2b7-da61-3efb-7231-9fac76b2c1d4@sentry.org> <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> <20180723063526.GA45726@www.zefox.net> <20180723155311.GB45726@www.zefox.net> <4ED9B658-A5A8-4BA6-9412-EBB7150B4B66@yahoo.com> <20180723190257.GA47869@www.zefox.net> <76BCFCB9-1071-4557-9FDE-017444ADBF42@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <76BCFCB9-1071-4557-9FDE-017444ADBF42@yahoo.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 23:24:45 -0000 Made another pass at using mixed (microSD plus USB) swap to run a -j4 buildworld on r336704. As expected, it stopped with 13:18:50 www kernel: pid 94472 (c++), uid 0, was killed: out of swap space However, the longest write delay recorded happened much earlier and didn't seem to route OOMA's ire at all: dT: 10.039s w: 10.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w d/s kBps ms/d %busy Name 0 0 0 3 5.1 0 3 5.6 0 0 0.0 0.1 mmcsd0 49 1 0 0 0.0 1 13 35716 0 0 0.0 104.7 da0 0 0 0 3 5.2 0 3 5.6 0 0 0.0 0.1 mmcsd0s2 0 0 0 3 5.2 0 3 5.7 0 0 0.0 0.1 ufs/rootfs 40 1 0 0 0.0 1 13 34915 0 0 0.0 104.7 da0d Wed Jul 25 12:44:37 PDT 2018 Device 1K-blocks Used Avail Capacity /dev/mmcsd0s3b 1048576 7272 1041304 1% /dev/da0b 1048576 7028 1041548 1% Total 2097152 14300 2082852 1% The machine ran normally for about half an hour after the worst-case write delay, before OOMA caught on (to something) and reacted. The worst read delay happens even earlier: dT: 10.002s w: 10.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w d/s kBps ms/d %busy Name 0 30 0 0 0.0 30 571 3.1 0 0 0.0 9.0 mmcsd0 0 45 0 0 27403 45 484 8631 0 0 0.0 70.8 da0 0 30 0 0 0.0 30 571 3.1 0 0 0.0 9.2 mmcsd0s3 0 30 0 0 0.0 30 571 3.2 0 0 0.0 9.2 mmcsd0s3a 0 0 0 0 27403 0 0 0.0 0 0 0.0 274.0 da0a 0 45 0 0 0.0 45 484 8631 0 0 0.0 70.8 da0d Wed Jul 25 10:15:31 PDT 2018 Device 1K-blocks Used Avail Capacity /dev/mmcsd0s3b 1048576 4384 1044192 0% /dev/da0b 1048576 4292 1044284 0% Total 2097152 8676 2088476 0% Jul 25 08:54:18 www su[1420]: bob to root on /dev/pts/0 Jul 25 09:32:26 www sshd[28651]: error: maximum authentication attempts exceeded for invalid user admin from 1.171.181.193 port 43216 ssh2 [preauth] even earlier in buildworld, with likewise no disturbing effect. Is it even possible for slow storage speeds to account for the OOMA kills? It looks as if the swap partitions aren't particularly busy at the time. Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Thu Jul 26 09:48:40 2018 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 282EF10499F2 for ; Thu, 26 Jul 2018 09:48:40 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E856882B3; Thu, 26 Jul 2018 09:48:39 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=aWfjggBWF76OX/M8g2Wbt0H8i5ZiJoggIsnMv8Baa4M=; b=cg8ZlHNpqx6jmOBP0NKRcrKH5YcBorIp+aZk+0CdWj7wJqAPNKLUGXqdZIQOY2deDE7Tr5ns7r9WGJuh21LzkDpr3pDOy4bZMUZ4GxX/eVcgxqfOSwjKyJT/3+XqLxiqNU/War/KrqtYKzfXQYrtXwSFDdN7JBxJbz3KaaVXurU= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id e42f2aff TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 26 Jul 2018 09:48:30 +0000 (UTC) Date: Thu, 26 Jul 2018 12:48:24 +0300 From: Greg V Subject: Re: Allwinner dtb overlays on CURRENT. Also, flashrom SPI! To: Emmanuel Vadot Cc: Kyle Evans , "freebsd-arm@freebsd.org" Message-Id: <1532598504.2425.0@hraggstad.unrelenting.technology> In-Reply-To: <20180725234000.e917566724f997319f8fe2fd@bidouilliste.com> References: <1532548163.59286.0@hraggstad.unrelenting.technology> <20180725234000.e917566724f997319f8fe2fd@bidouilliste.com> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jul 2018 09:48:40 -0000 On Thu, Jul 26, 2018 at 12:40 AM, Emmanuel Vadot=20 wrote: > On Wed, 25 Jul 2018 15:14:29 -0500 > Kyle Evans wrote: >=20 >> On Wed, Jul 25, 2018 at 2:49 PM, Greg V=20 >> wrote: >> > Hi, >> > >> > One thing I have noticed with CURRENT on an Orange Pi PC: since=20 >> we're using >> > device trees imported from Linux, some drivers are not accessible=20 >> out of the >> > box. >> > >> > So I wrote a couple overlays: >> > >> > Thermal sensor: https://github.com/freebsd/freebsd/pull/162 >> > >=20 > This is wrong bindings. Yes I know that it's working with our driver > for ths but this is wrong. > 1) ths module isn't in ahb but apb. > 2) We need nvmem framework to get the sensor calibration data, please > see https://reviews.freebsd.org/D16419 I guess it's good to have a framework, but the existing driver=20 communicates with aw_sid directly (aw_sid_read_tscalib), and that seems=20 to work fine? >> > SPI: https://github.com/freebsd/freebsd/pull/166 >=20 > What is the point of the spigen interface ? > If aw_spi is working on H3 (I haven't check but it should), if you > have a good dtb with the spi flash described you can use it directly. Uhhh I'm surprised you don't know what's the point of spigen=85 The point is raw *userspace* access. Like /dev/spidevX.Y on Linux, spigen gives us /dev/spigenX.Y. As you can see below, I wrote spigen support for flashrom :) We already have a spigen dtb overlay for the Raspberry Pi. So now it's possible to use the same userspace applications that talks=20 SPI directly (like flashrom) on both RPi and H3! >> > But not everyone would figure out how to make and even just use=20 >> overlays? >> > >> > (if anyone is wondering: place them into /boot/dtb/overlays and=20 >> add a list >> > of them (filenames including extension) to /boot/loader.conf like=20 >> so: >> >=20 >> fdt_overlays=3D"sun8i-h3-sid.dtbo,sun8i-h3-ts.dtbo,sun8i-h3-spi.dtbo"=20 >> ? and >> > reboot) >>=20 >> Just FYI- omitting the extension should also work fine here. If it >> doesn't, that's another bug on its own. =3D) >>=20 >> > Can someone commit these overlays / add more for other SoCs maybe? >>=20 >> I think manu was working on some thermal sensor stuff earlier=20 >> (though >> my memory may be wrong), so we'll see what he says. >=20 > I am, currently upstreaming bindings/dts changes. >=20 >> > P.S. I also wrote spigen support for flashrom: >> > https://github.com/flashrom/flashrom/pull/53 >> > With this, I can flash and verify a Winbond W25Q32.V flash chip=20 >> from my >> > Orange Pi! :) = From owner-freebsd-arm@freebsd.org Thu Jul 26 10:09:36 2018 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 4AF68104A25C for ; Thu, 26 Jul 2018 10:09:36 +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 93D5A88AF3; Thu, 26 Jul 2018 10:09:35 +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 3dc24990; Thu, 26 Jul 2018 12:09:27 +0200 (CEST) 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=LurdouCcnK7HSSSc58KVg2vOBXg=; b=BfJbBsNNHyRaierpdXuh4fsqLcOE /yL7+mF8rkID47cIVwLL1X15JSyxXO6tTVUIa6kRWYOoZc2NI1M/ZvlSV0h5+cji 63Vhx7ibOKLdtSlDfHqS9PjpotfgETj57ZnoCPwX7WC3lDFb6CsAkR2W/xhq2+N+ PvE/uppmpoGp9bY= 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=cUlbgLPc5DZjoVLEjfilMfHLtcO/5ET01gNgXCL8MAwpc1liaC7t+jZY vucXPEr5ZrB9PD9br3k3OBCjNmXSL27VcQOMbSDRBcKTkg9EE25kKWAACOJxMmdT uwLkndlgIpnngAZ+r3oNtMThYEeJv6DcEOpsUD36w+NbSs9O8r0= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id cf1b563d TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 26 Jul 2018 12:09:27 +0200 (CEST) Date: Thu, 26 Jul 2018 12:09:26 +0200 From: Emmanuel Vadot To: Greg V Cc: Kyle Evans , "freebsd-arm@freebsd.org" Subject: Re: Allwinner dtb overlays on CURRENT. Also, flashrom SPI! Message-Id: <20180726120926.9648d6b691ab7be7cbb37653@bidouilliste.com> In-Reply-To: <1532598504.2425.0@hraggstad.unrelenting.technology> References: <1532548163.59286.0@hraggstad.unrelenting.technology> <20180725234000.e917566724f997319f8fe2fd@bidouilliste.com> <1532598504.2425.0@hraggstad.unrelenting.technology> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jul 2018 10:09:36 -0000 On Thu, 26 Jul 2018 12:48:24 +0300 Greg V wrote: >=20 >=20 > On Thu, Jul 26, 2018 at 12:40 AM, Emmanuel Vadot=20 > wrote: > > On Wed, 25 Jul 2018 15:14:29 -0500 > > Kyle Evans wrote: > >=20 > >> On Wed, Jul 25, 2018 at 2:49 PM, Greg V=20 > >> wrote: > >> > Hi, > >> > > >> > One thing I have noticed with CURRENT on an Orange Pi PC: since=20 > >> we're using > >> > device trees imported from Linux, some drivers are not accessible=20 > >> out of the > >> > box. > >> > > >> > So I wrote a couple overlays: > >> > > >> > Thermal sensor: https://github.com/freebsd/freebsd/pull/162 > >> > > >=20 > > This is wrong bindings. Yes I know that it's working with our driver > > for ths but this is wrong. > > 1) ths module isn't in ahb but apb. > > 2) We need nvmem framework to get the sensor calibration data, please > > see https://reviews.freebsd.org/D16419 >=20 > I guess it's good to have a framework, but the existing driver=20 > communicates with aw_sid directly (aw_sid_read_tscalib), and that seems=20 > to work fine? Yeah and this is really gross. Also the bindings aren't upstreamed and can't be without nvmem-cells. > >> > SPI: https://github.com/freebsd/freebsd/pull/166 > >=20 > > What is the point of the spigen interface ? > > If aw_spi is working on H3 (I haven't check but it should), if you > > have a good dtb with the spi flash described you can use it directly. >=20 > Uhhh I'm surprised you don't know what's the point of spigen? > The point is raw *userspace* access. I'm surprised that you thing I don't know what spigen is :) If your DTB expose the spi node and the spi flash node when devmatch start you will have : Starting devd. Autoloading module: aw_spi.ko aw_spi0: mem 0x1c68000-0x1c68fff irq 27 on simplebus0 spibus0: on aw_spi0 spibus0: at cs 0 mode 0 Autoloading module: mx25l.ko mx25l0: at cs 0 mode 0 on spibus0 mx25l0: device type w25q128, size 16384K in 256 sectors of 64K, erase size 4K This will create a /dev/flash/spi0 where you can dd u-boot directly on it. > Like /dev/spidevX.Y on Linux, spigen gives us /dev/spigenX.Y. > As you can see below, I wrote spigen support for flashrom :) >=20 > We already have a spigen dtb overlay for the Raspberry Pi. > So now it's possible to use the same userspace applications that talks=20 > SPI directly (like flashrom) on both RPi and H3! Having a spigen for things other than flash is good, for flash I don't see the point. =20 > >> > But not everyone would figure out how to make and even just use=20 > >> overlays? > >> > > >> > (if anyone is wondering: place them into /boot/dtb/overlays and=20 > >> add a list > >> > of them (filenames including extension) to /boot/loader.conf like=20 > >> so: > >> >=20 > >> fdt_overlays=3D"sun8i-h3-sid.dtbo,sun8i-h3-ts.dtbo,sun8i-h3-spi.dtbo"= =20 > >> ? and > >> > reboot) > >>=20 > >> Just FYI- omitting the extension should also work fine here. If it > >> doesn't, that's another bug on its own. =3D) > >>=20 > >> > Can someone commit these overlays / add more for other SoCs maybe? > >>=20 > >> I think manu was working on some thermal sensor stuff earlier=20 > >> (though > >> my memory may be wrong), so we'll see what he says. > >=20 > > I am, currently upstreaming bindings/dts changes. > >=20 > >> > P.S. I also wrote spigen support for flashrom: > >> > https://github.com/flashrom/flashrom/pull/53 > >> > With this, I can flash and verify a Winbond W25Q32.V flash chip=20 > >> from my > >> > Orange Pi! :) --=20 Emmanuel Vadot From owner-freebsd-arm@freebsd.org Thu Jul 26 14:02:16 2018 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 71D091050400 for ; Thu, 26 Jul 2018 14:02:16 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [IPv6:2605:2700:0:3:a800:ff:fee9:2feb]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D6959909FE; Thu, 26 Jul 2018 14:02:15 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=ItywaOraNwoE8ndONMRFpObmrWQFf0nY+c7/gqb+lDk=; b=mqukIS6/kxEH/Id5QSqnwktZpNMFiwrW90PiwIxMJSVgTjszMG7Z4vW3o2FI9aK3zRmgLJWtr8uavlYjk5VO5giOsnvudIzuGHoXP8m47/w8Fd4wLNunbgjpRst7jeEYeR7fpV+NwhnNQod4D5s3CprsXCO9orEh223xvlPE6UA= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 8dc89728 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 26 Jul 2018 14:02:03 +0000 (UTC) Date: Thu, 26 Jul 2018 17:01:57 +0300 From: Greg V Subject: Re: Allwinner dtb overlays on CURRENT. Also, flashrom SPI! To: Emmanuel Vadot Cc: Kyle Evans , "freebsd-arm@freebsd.org" Message-Id: <1532613717.49616.0@hraggstad.unrelenting.technology> In-Reply-To: <20180726120926.9648d6b691ab7be7cbb37653@bidouilliste.com> References: <1532548163.59286.0@hraggstad.unrelenting.technology> <20180725234000.e917566724f997319f8fe2fd@bidouilliste.com> <1532598504.2425.0@hraggstad.unrelenting.technology> <20180726120926.9648d6b691ab7be7cbb37653@bidouilliste.com> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jul 2018 14:02:16 -0000 On Thu, Jul 26, 2018 at 1:09 PM, Emmanuel Vadot =20 wrote: > On Thu, 26 Jul 2018 12:48:24 +0300 > Greg V wrote: >> On Thu, Jul 26, 2018 at 12:40 AM, Emmanuel Vadot >> wrote: >> > On Wed, 25 Jul 2018 15:14:29 -0500 >> > Kyle Evans wrote: >> > This is wrong bindings. Yes I know that it's working with our=20 >> driver >> > for ths but this is wrong. >> > 1) ths module isn't in ahb but apb. >> > 2) We need nvmem framework to get the sensor calibration data,=20 >> please >> > see https://reviews.freebsd.org/D16419 >>=20 >> I guess it's good to have a framework, but the existing driver >> communicates with aw_sid directly (aw_sid_read_tscalib), and that=20 >> seems >> to work fine? >=20 > Yeah and this is really gross. > Also the bindings aren't upstreamed and can't be without nvmem-cells. It's nice that we're going to have clean upstreamable stuff, but it's a=20 bit sad that making everything work out of the box on current *now* is=20 not a priority. Especially since overlays are perfect for enabling=20 temporary hacks. >> >> > SPI: https://github.com/freebsd/freebsd/pull/166 >> > >> > What is the point of the spigen interface ? >> > If aw_spi is working on H3 (I haven't check but it should), if=20 >> you >> > have a good dtb with the spi flash described you can use it=20 >> directly. >>=20 >> Uhhh I'm surprised you don't know what's the point of spigen? >> The point is raw *userspace* access. >=20 > I'm surprised that you thing I don't know what spigen is :) Hah, sorry, I guess you should've added "for accessing flash" right=20 there before the question mark. > Having a spigen for things other than flash is good, for flash I=20 > don't > see the point. Yeah, it should be exposed out of the box for all kinds of things,=20 exactly! Kernel drivers are good for permanently attached flash, but if you're=20 going to, say, connect various motherboards' flash chips to=20 dump/recover the firmware or flash coreboot, you don't want kernel=20 drivers, you specifically want *flashrom* with its auto detection (and=20 probably its support for more chips=85) Fun story: I recovered my PC after a bad firmware update using an RPi=20 once. I couldn't attach all the wires because the board has a header=20 with 2mm pins and I had thicker connectors, so I ended up not=20 connecting ground. It didn't work at default speed, but flashrom=20 detected the chip when using very low speed and flashing was successful=20 :D = From owner-freebsd-arm@freebsd.org Thu Jul 26 15:00:11 2018 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 E44941051D60 for ; Thu, 26 Jul 2018 15:00:10 +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 5355893626; Thu, 26 Jul 2018 15:00:09 +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 28ce43e8; Thu, 26 Jul 2018 17:00:07 +0200 (CEST) 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=n4LpKtuBiyM0VI8RCN6KwZgQzbw=; b=n/MAdU1CClL1zG2sFFddIqTEQ6+H Wsw+mArHGmTwf6zmoN7SHlcfluuyOw6JO1DIT6XdDUc1HzTm8bnVR0Fc/CRsgm/P oTeCh8RyI757Yh2RKqHbzcoOs+yRLjHSCA/WamdEQwpSagXBfwJ8oXZpMgOlhiB7 UsE8oOeo6f0MxJ8= 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=H0u4i6Kd1NYMTL8Y2siz/HWG085yFZ2N7SzGuaTMEYU1u2KJPCJBn6+m 0Tghu1TvbV95TYk2oTGWSp1/EsrcX9adfEMq4tv4OdAHRawSwdwtNysOpxqSK7yY AT8MzOgaaiX2jlFPmjh1oB0fzJa8BXIGIAmHuJF+md9gg34aM4U= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 2d6528db TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 26 Jul 2018 17:00:07 +0200 (CEST) Date: Thu, 26 Jul 2018 17:00:07 +0200 From: Emmanuel Vadot To: Greg V Cc: Kyle Evans , "freebsd-arm@freebsd.org" Subject: Re: Allwinner dtb overlays on CURRENT. Also, flashrom SPI! Message-Id: <20180726170007.a825dcaca1d96ec739719259@bidouilliste.com> In-Reply-To: <1532613717.49616.0@hraggstad.unrelenting.technology> References: <1532548163.59286.0@hraggstad.unrelenting.technology> <20180725234000.e917566724f997319f8fe2fd@bidouilliste.com> <1532598504.2425.0@hraggstad.unrelenting.technology> <20180726120926.9648d6b691ab7be7cbb37653@bidouilliste.com> <1532613717.49616.0@hraggstad.unrelenting.technology> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jul 2018 15:00:11 -0000 On Thu, 26 Jul 2018 17:01:57 +0300 Greg V wrote: >=20 >=20 > On Thu, Jul 26, 2018 at 1:09 PM, Emmanuel Vadot =20 > wrote: > > On Thu, 26 Jul 2018 12:48:24 +0300 > > Greg V wrote: > >> On Thu, Jul 26, 2018 at 12:40 AM, Emmanuel Vadot > >> wrote: > >> > On Wed, 25 Jul 2018 15:14:29 -0500 > >> > Kyle Evans wrote: > >> > This is wrong bindings. Yes I know that it's working with our=20 > >> driver > >> > for ths but this is wrong. > >> > 1) ths module isn't in ahb but apb. > >> > 2) We need nvmem framework to get the sensor calibration data,=20 > >> please > >> > see https://reviews.freebsd.org/D16419 > >>=20 > >> I guess it's good to have a framework, but the existing driver > >> communicates with aw_sid directly (aw_sid_read_tscalib), and that=20 > >> seems > >> to work fine? > >=20 > > Yeah and this is really gross. > > Also the bindings aren't upstreamed and can't be without nvmem-cells. >=20 > It's nice that we're going to have clean upstreamable stuff, but it's a=20 > bit sad that making everything work out of the box on current *now* is=20 > not a priority. Enabling it on current is my priority, which is why I'm working on the upstream process. > Especially since overlays are perfect for enabling=20 > temporary hacks. Temporary hacks don't exists. > >> >> > SPI: https://github.com/freebsd/freebsd/pull/166 > >> > > >> > What is the point of the spigen interface ? > >> > If aw_spi is working on H3 (I haven't check but it should), if=20 > >> you > >> > have a good dtb with the spi flash described you can use it=20 > >> directly. > >>=20 > >> Uhhh I'm surprised you don't know what's the point of spigen? > >> The point is raw *userspace* access. > >=20 > > I'm surprised that you thing I don't know what spigen is :) >=20 > Hah, sorry, I guess you should've added "for accessing flash" right=20 > there before the question mark. >=20 > > Having a spigen for things other than flash is good, for flash I=20 > > don't > > see the point. >=20 > Yeah, it should be exposed out of the box for all kinds of things,=20 > exactly! >=20 > Kernel drivers are good for permanently attached flash, but if you're=20 > going to, say, connect various motherboards' flash chips to=20 > dump/recover the firmware or flash coreboot, you don't want kernel=20 > drivers, you specifically want *flashrom* with its auto detection (and=20 > probably its support for more chips?) Ok I see. Your SPI overlays needs to be split (one for SPI0 and one for SPI1). Can you open a review on https://reviews.freebsd.org/ for this ? Thanks >=20 > Fun story: I recovered my PC after a bad firmware update using an RPi=20 > once. I couldn't attach all the wires because the board has a header=20 > with 2mm pins and I had thicker connectors, so I ended up not=20 > connecting ground. It didn't work at default speed, but flashrom=20 > detected the chip when using very low speed and flashing was successful=20 > :D --=20 Emmanuel Vadot From owner-freebsd-arm@freebsd.org Thu Jul 26 16:41:48 2018 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 13DB61054760 for ; Thu, 26 Jul 2018 16:41:48 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8D75697518 for ; Thu, 26 Jul 2018 16:41:47 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=hHuZrrXf3wwm97ncm5/v8FNrkNuZY8levFPLdULwnek=; b=LrqaSeUciSF2lUJadwFvhSz/jJq3oVgLPO7Pe5o2Yh3pmYZaH8yT5jc5xZ684yQ8fOVpXtAkNpaELb0GcIiODTAZC9RP+rCMATe4cSkB3GTXKmTUHULSqpxASjufvY8g+35xBcbjm+4p9uTPLJO33bkThUwQmBRAPNO33lfykkM= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 7fe60dea TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO for ; Thu, 26 Jul 2018 16:41:43 +0000 (UTC) Date: Thu, 26 Jul 2018 19:41:38 +0300 From: Greg V Subject: Re: Allwinner dtb overlays on CURRENT. Also, flashrom SPI! To: "freebsd-arm@freebsd.org" Message-Id: <1532623298.49616.1@hraggstad.unrelenting.technology> In-Reply-To: <20180726170007.a825dcaca1d96ec739719259@bidouilliste.com> References: <1532548163.59286.0@hraggstad.unrelenting.technology> <20180725234000.e917566724f997319f8fe2fd@bidouilliste.com> <1532598504.2425.0@hraggstad.unrelenting.technology> <20180726120926.9648d6b691ab7be7cbb37653@bidouilliste.com> <1532613717.49616.0@hraggstad.unrelenting.technology> <20180726170007.a825dcaca1d96ec739719259@bidouilliste.com> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jul 2018 16:41:48 -0000 On Thu, Jul 26, 2018 at 6:00 PM, Emmanuel Vadot wrote: > Your SPI overlays needs to be split (one for SPI0 and one for SPI1). > Can you open a review on https://reviews.freebsd.org/ for this ? Sure https://reviews.freebsd.org/D16461 From owner-freebsd-arm@freebsd.org Sat Jul 28 16:47:58 2018 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 DCB6E1056886 for ; Sat, 28 Jul 2018 16:47:57 +0000 (UTC) (envelope-from alc@rice.edu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 69B2C7544F for ; Sat, 28 Jul 2018 16:47:57 +0000 (UTC) (envelope-from alc@rice.edu) Received: by mailman.ysv.freebsd.org (Postfix) id 2E3401056884; Sat, 28 Jul 2018 16:47:57 +0000 (UTC) Delivered-To: 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 0C4251056883 for ; Sat, 28 Jul 2018 16:47:57 +0000 (UTC) (envelope-from alc@rice.edu) Received: from mx0a-0010f301.pphosted.com (mx0a-0010f301.pphosted.com [148.163.149.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.pphosted.com", Issuer "thawte SHA256 SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A7917544C for ; Sat, 28 Jul 2018 16:47:56 +0000 (UTC) (envelope-from alc@rice.edu) Received: from pps.filterd (m0102855.ppops.net [127.0.0.1]) by mx0b-0010f301.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w6SGkGul010980 for ; Sat, 28 Jul 2018 11:47:54 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rice.edu; h=to : cc : from : subject : message-id : date : mime-version : content-type : content-transfer-encoding; s=ricemail; bh=W0+V5QFiVvjHb+kDEjOVC5y4uAV4YcHcDSAlWjEfc5o=; b=ncE5z/Z5HqR1H3BUy3vMwqDha9D3EiVk7f4DO/cHNMoIlPgOJ1ILB5xB+/5e+V03Udlm uz2H4ORQKPL4GLKdb/qchE0nqFl3Wfpe39hffNLWVwcxy8HAf71RJvsZ6TNVZ7vFhMo6 4jeMm7WCMpufEGw/9h9OdopX3Fa4NArXCAzsbEzMj4O+7yJRh8FREPT9WtAW6MwQgtwL MA/sFEzH1L7cgRvKQaI0D+UnOEUxVRlXFlVffgBDXwvIK4wZIimVjikJ6rlQxSGQTlZn hBScDK36gsSYF1mWlUVAqMb56PTk5HNysEc1Q2Ne/gX2RucIXMcSQKBHZourtCI38YVy bw== Received: from mh11.mail.rice.edu (mh11.mail.rice.edu [128.42.199.30]) by mx0b-0010f301.pphosted.com with ESMTP id 2kgnt5g9q4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Sat, 28 Jul 2018 11:47:54 -0500 Received-X: from mh11.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh11.mail.rice.edu (Postfix) with ESMTP id 708494C0688 for ; Sat, 28 Jul 2018 11:47:53 -0500 (CDT) Received-X: from mh11.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh11.mail.rice.edu (Postfix) with ESMTP id 6EDEA4C067D; Sat, 28 Jul 2018 11:47:53 -0500 (CDT) X-Virus-Scanned: by amavis-2.7.0 at mh11.mail.rice.edu, auth channel Received-X: from mh11.mail.rice.edu ([127.0.0.1]) by mh11.mail.rice.edu (mh11.mail.rice.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id aIpibLUdQM8t; Sat, 28 Jul 2018 11:47:53 -0500 (CDT) Received: from 108-254-203-201.lightspeed.hstntx.sbcglobal.net (108-254-203-201.lightspeed.hstntx.sbcglobal.net [108.254.203.201]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: alc) by mh11.mail.rice.edu (Postfix) with ESMTPSA id 2C23A4C0678; Sat, 28 Jul 2018 11:47:53 -0500 (CDT) To: "arm@freebsd.org" Cc: Alan Cox From: Alan Cox Subject: pmap-v6.c patches Openpgp: preference=signencrypt Autocrypt: addr=alc@rice.edu; prefer-encrypt=mutual; keydata= xsBNBFG8q4IBCADBE55F7sX+cKhEadxhNkXrbtVSJhw3TQDPvc3nBWxsfdMAhPWozhpLczV/ hr8mDJV5tirit0qhw4ANPwtsn7i/xlcSdC9p8Jvkcpp/AfiA5B78Y08AsC6K6tbNHZ06qPq3 eCXDNbPzsUXyvyt25A+ZnQj4HbW4FpA6C5ITG1eeJPGO8WV9vhBQ4X/BWI61RXaJw68Jxtwo c9eovzdxbWTd5po/oGHL2ganYoBMu1OGpGFWvTDwy2ARCV7i+fSkfKXUPaQm17AuVVbZu8OU Ig6caCEA5MlZVsMpwuJQp7xdEQzPaDML3drkl32l3Rb09g5vKjjLHb+LXx/7PyeEWsG1ABEB AAHNGkFsYW4gQ294IDxhbGNARnJlZUJTRC5vcmc+wsB4BBMBAgAiBQJRvK14AhsDBgsJCAcD AgYVCAIJCgsEFgIDAQIeAQIXgAAKCRCFEwQ8M+KJO7tKB/462f5Zzygqera1acLTIrIfdDXp cfyq3+OhFzbBh91b2Jw+CVKvH+hVpCUSW86Sgfv4sSvgsqdS9nMwN82MZDchNROfkkoY1Nkl 0EgayOmOoYroRp1bM65OZAMrw7qK/iG8FeJ1s6ex4wSSfeRETmFNhK0KMfTeLiKlIjW+KhIQ h+trVIWt9ZlvHI3xw6RUuEQ1CFvzETcwj/+YxLd8aha0Mr6qW/4VDw0G9g+YnqR8jnm1dOsO x8s+vJt2QmRuWGSsj5nk9Dc+Tpzytbvrv3rOCsEwuadWZU53/wL576XnqliWwkte3njN+BwI LoDuKBoqxIvdqI7lqTzYdww5BPd3zsBNBFG8q4IBCAC0hrybH/nTPvIeQm5qa5ZzwThdjb6y otBFjl/5LnMNfa2yhhJp0tQkr/WsJ/RiaYEmp7bGKnowbKR+6X7MF6qcRHwEPpibN8fpxKFg JlvhQhQWmU7nuBWqt8I1/y8aVLci7BPLRk6IKaMQJWWk18Wetijnao5gGEFu/iF9CzbYmJ/U ijVMJj08WlhQCiPnKFkirV8XjAOER5F2ecfLtfPLL/bZ+/Wm6xM+eo1ipc30oRf1Z7Rkcg94 RjiRpVacSnBQEFMXukD33w6WaKYT18B4rwN27tJfzTmGKRKggWEc3EWeQgzi3rD7x35owBJ7 x+G6lIjdSG4o9ytB3qTVazo3ABEBAAHCwF8EGAECAAkFAlG8q4ICGwwACgkQhRMEPDPiiTuH kAgAo3MUNRzGplyvgPezfnLgnwtlDYMF1HWp+67IIvY3WwcC51FQNHWmGis+H7Bor+aeSAfo KREw9l4U0Tu2YC9uiWKZzA4zer2WMhsB4VGMQ8GPuE2R2sFob5n293FsLWDSWM4Midory9zN EAYQ+Ijpv8WaATS217YYygA+iFlfMmQSKDS1G6HBnUjzQe23sX/06JAAxAvwmOI7OjwLlOCU Q5FaHPz6s8UjdHpZ/OUTElc7URPTr/KramlLhwuTRC2p8XyBrzYqz3Kfl42jEcOuxeHy07DG dm1Euqa5/CKTNBhMWjcujz11TUeI9+f5J2xUSlbj7nGJsnL5P34+SvtsKg== Message-ID: Date: Sat, 28 Jul 2018 11:47:52 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-07-28_07:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=3 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=428 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1806210000 definitions=main-1807280183 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2018 16:47:58 -0000 Could someone please test the pmap-v6.c patch at https://reviews.freebsd.org/D16443 on HEAD? If the patched kernel boots, and can recompile a new kernel, that should suffice for testing. This patch is not intended to make any significant functional changes by itself, but to ease porting of a newish pmap feature/optimization that we have on amd64, arm64, and i386. Thanks. From owner-freebsd-arm@freebsd.org Sat Jul 28 17:18:40 2018 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 59B14105769C for ; Sat, 28 Jul 2018 17:18:40 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C0AB776215 for ; Sat, 28 Jul 2018 17:18:39 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-wm0-x242.google.com with SMTP id s14-v6so9021786wmc.1 for ; Sat, 28 Jul 2018 10:18:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :user-agent; bh=CQLao8vk2u0OMeIrhSv6bAmzsYoQyDzwO6wkjiaB034=; b=Ezc/TYjvDQJYpXGSMZFUqJgAkPPrryPBZmvwyfuztB4D+aeTIApM7RCPaqwPMADo4B WoFEZUSrBfprHe2traPsPlvgrjO/akf2rnfpA706nwjzsZ/i00q+XMO/TwCCydCGABMp ghiWvFPuzMrPOrpZ3BxULIMudCuK/ejJMrOTqKXMYI3mYB8xeVpsS0BaXgHq+IO7Es5w iU0IdDEw+Q/u5jb5q7H7UrcaI7k111hGbCJdwUzjz4b/OStQhAjuIDu+wyqpxwHJf82b gRgwc+f5EZ+tZSbUfFVR44vcK8By3t+IGIYFn9JTlLd7/DDPsKFMxq1cbsZxOPGetqZE bLaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:user-agent; bh=CQLao8vk2u0OMeIrhSv6bAmzsYoQyDzwO6wkjiaB034=; b=GNcU9FkMWfDkgeeZ+1A5wJ5U5HZ7pPrLjoTSxBfZmL1UucK4qkW7/oPp79ef4YbHNF aDXW+gNfQzFpVRciCtb2MEJlshOAsmmgMg3QoOVC5XhVSAwMaynMtwXUoPuyqA9ECgbE fc40euPlKGxSaz+WaxSYPFqcYOesicNMbexp9ZKr2WSB7c4XigbwGK+Q47DBjtCmZESQ r25tEthc3jH79p/+dwPAOqWM3gTEJE1QQJhyAq2JjZEYrGIzDjx9tA6znzD026v4Ttq7 7znA+EFWIB2IibBbOAItOvGH95mYr4DBfEdz+zEtIpcgduC/Z+L0RaVDMBWymPFwJHfc 5dJw== X-Gm-Message-State: AOUpUlHvaUhMF5tom2pJNiBHQ4LfyX4MTUExjDpG+KyZOHbPBA0jRAOZ FtWK1MnMpTf99JU6XMy/ek8yxg== X-Google-Smtp-Source: AAOMgpeL2qbWPzYtxtXu16+gFfkgo2h0dfq28tkJFmYfq8aN2cjHhPGJRBjDDHX7kyzj5ma4kGxu9w== X-Received: by 2002:a1c:6709:: with SMTP id b9-v6mr8917104wmc.68.1532798318281; Sat, 28 Jul 2018 10:18:38 -0700 (PDT) Received: from mutt-hbsd (tor-exit0-readme.dfri.se. [171.25.193.20]) by smtp.gmail.com with ESMTPSA id f9-v6sm7578297wmc.29.2018.07.28.10.18.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 28 Jul 2018 10:18:37 -0700 (PDT) Date: Sat, 28 Jul 2018 13:17:45 -0400 From: Shawn Webb To: freebsd-current@freebsd.org, imp@freebsd.org Cc: freebsd-arm@freebsd.org Subject: Booting arm64 uefi broken Message-ID: <20180728171745.e5g6dfrcjdn2mtg4@mutt-hbsd> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="lrstudwzs4myzhby" Content-Disposition: inline X-Operating-System: FreeBSD mutt-hbsd 12.0-CURRENT FreeBSD 12.0-CURRENT X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: NeoMutt/20180622 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2018 17:18:40 -0000 --lrstudwzs4myzhby Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable It appears with the latest 12-CURRENT/arm64, booting is broken. The boot process gets stuck after the "Using DTB provided by..." message. This is on my SoftIron OverDrive 1000: >> FreeBSD EFI boot block = =20 Loader path: /boot/loader.efi = =20 = =20 Initializing modules: ZFS UFS = =20 Load Path: \EFI\BOOT\BOOTAA64.EFI = =20 Load Device: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(1,G= PT,73365FD5-9260-11E8-9F00-0026B93F5298,0x3,0x640) BootCurrent: 0002 = =20 BootOrder: 0001 0005 0006 0000 0002[*] = =20 Probing 7 block devices......+..* done = =20 ZFS found the following pools: rpool = =20 UFS found 1 partition = =20 Consoles: EFI console = =20 FreeBSD/arm64 EFI loader, Revision 1.1 = =20 (Sat Jul 28 11:32:06 UTC 2018 root@nyi-01.build.hardenedbsd.org) = =20 = =20 Command line arguments: loader.efi = =20 EFI version: 2.60 = =20 EFI Firmware: SoftIron Overdrive 1000 (rev 1.00) = =20 Console: efi (0) = =20 Load Path: HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00)= =20 Load Device: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(2,G= PT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) BootCurrent: 0002 = =20 BootOrder: 0001 0005 0006 0000 0002[*] = =20 BootInfo Path: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0) = =20 Ignoring Boot0002: Only one DP found = =20 Trying ESP: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(2,GPT,7= 3365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) Setting currdev to disk1p2: = =20 Loading /boot/defaults/loader.conf = =20 /boot/kernel/kernel text=3D0x8a7169 data=3D0x1384d0+0x7d39fc syms=3D[0x8+0x= 11d108+0x8+0x10e646] /boot/entropy size=3D0x1000 = =20 efi-autoresizecons: Neither Graphics Output Protocol nor Universal Graphics= Adapter present = =20 Hit [Enter] to boot immediately, or any other key for command prompt. = =20 Booting [/boot/kernel/kernel]... = =20 Using DTB provided by EFI at 0x801fe00000. Thanks, --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: lattera@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --lrstudwzs4myzhby Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAltcpTUACgkQaoRlj1JF bu6WZBAAiMqyxjuVx0VmvVHMLJ5FI7zugUGjIEvnhaNJfnc86+9UUsc1pW9Ztn65 xP32REdbKLywBDYPrexUT2Rpq16s613SwKuPMGmndfEKmbLY9/FnAJS5QgJ1kaUQ PsdnBSw6kJzxe5LiB2lLVuapwbwOl/QK3lgrWf5Fd1rGvQoD0U6TAPYxAhKLVr9q kbDMuLp+f35PKX5TKg1xV1LMNtRfWADSmalCt0/SozzkXLh4Kl5MMJbZ5KpvppRT OiyRKQACEXHkPPB8ALr1/4zuY6T2HeswnIAKVSmY91rz7WbGNxfU3ydk245WqIno TQ6UQzc47fsKO6pzdRKSB9Nl5oKUcHyMUWlh0ORX0L0Yzrn2DIzJy78UWjdb8wGY t8t92cqfW1J3RrfDcxFGOhEZzQ+cPsPnY0HFmapg9jLTJ/qm3Tx2kbFTVdxy0NYy YAQlH+HLhYAfw1TtChYt8Z3b9Q43qbPDjR207GM+qGmE41T+Sd9GOiSczwcb7Xtr CyybpV+dqiJcauUGLe3epxrb1R5o0hgo1BVHv1BFitotTsvmvDjUpeN4ydzNLxHs cC7104YuO9QxhvpdcvSNAYUXe5IwlEAbssxwA+RvMGt+S4mBp5GmsqB0+u61ztx1 iJdiTXHIMX5pExn2HHIwrtkvMEfugVBLhB4x+HytI/vmqiko4qg= =Jkmr -----END PGP SIGNATURE----- --lrstudwzs4myzhby-- From owner-freebsd-arm@freebsd.org Sat Jul 28 18:08:39 2018 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 533671058B70; Sat, 28 Jul 2018 18:08:39 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DA99977DAB; Sat, 28 Jul 2018 18:08:38 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pg1-x532.google.com with SMTP id n7-v6so5016629pgq.4; Sat, 28 Jul 2018 11:08:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=6ZRhc3iECwNdn7XNogoWFWL/7A0Yjpiyu1QQ4yAIwy0=; b=k5fVv/wYF8Bl1nOFxxixgL4zZh44NxZ8hOeSay7o3LOfycb2NCUHib9VS/kH3lOMaS JN9AJYHv1pDGjHrYEDYvQ4IS9sypS9gnQqaFFZiVf3OStBWqh1l+mNrDaZ+6D8OAq5lB kOO8cDTn6fKLg50viYTrM7XeJyqF67UFPkKBF1DVCTCRpwKSE7Q9Ajqd4iwD3Ck8Bobt DRH6wtSbjpBQYF7Al0BJweuGm/DVmmLpKgddVi193uXcOjUBlDeLOkwnyBLEfzUl0Png 57p5xUxWoPi5qzmlhfyUo8qMvy8yeV2gxBG25HJgPPKf//pT5383sbVz69qjHQWVoGGX TeVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=6ZRhc3iECwNdn7XNogoWFWL/7A0Yjpiyu1QQ4yAIwy0=; b=Zl1aWdfAygxs1fuCJzavOaQFbhW8itsGugCttIvhVu/IK7myGstKFjZODHqZA3irtX 5ME/4vw6OX/IAmSm54n4YD8d6n1UkKwfeLK3eoDCdvqDFxdBf+bbF2RonhkV+zPQYrci XeuvTJDu7ChJxwIhOgUOTGzViFCJoRZWwPJSbEPCvg8h60AI37XvdEcYqHN33UZbvaDw 5HB55BR2EJCI2VunGUu8cuD3AMH9nMX6d/Q++SXVW5LYFkhmjykDPVwZ+WLqtprQRMOP khd0nSa6vtSZZIb+YnlX1SFiXO2vEDa/vOSNkGNGxrIyo5mTGVqXBrlaKuGpBPlQd/Br 2Rig== X-Gm-Message-State: AOUpUlFJqM2eGhT9sjWH4XzFUxB3GYgjZs7ss4CHcGmO5Qr6FxdCXGt3 KBGUwqXqbpDJYOFX+mcwto7t3DCE X-Google-Smtp-Source: AAOMgpdC60Bv+lNxPpmVmpW5s9KPf4hjWQj4L3b3rZuXzIiJRqKNEfx3GRkI8MZ6IXkhjcnU1YEvYw== X-Received: by 2002:a63:6188:: with SMTP id v130-v6mr10542494pgb.100.1532801317840; Sat, 28 Jul 2018 11:08:37 -0700 (PDT) Received: from raichu (toroon0560w-lp130-03-174-88-72-141.dsl.bell.ca. [174.88.72.141]) by smtp.gmail.com with ESMTPSA id h69-v6sm22382450pfh.13.2018.07.28.11.08.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 28 Jul 2018 11:08:36 -0700 (PDT) Sender: Mark Johnston Date: Sat, 28 Jul 2018 14:08:31 -0400 From: Mark Johnston To: Shawn Webb Cc: freebsd-current@freebsd.org, imp@freebsd.org, freebsd-arm@freebsd.org Subject: Re: Booting arm64 uefi broken Message-ID: <20180728180831.GA73141@raichu> References: <20180728171745.e5g6dfrcjdn2mtg4@mutt-hbsd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180728171745.e5g6dfrcjdn2mtg4@mutt-hbsd> User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2018 18:08:39 -0000 On Sat, Jul 28, 2018 at 01:17:45PM -0400, Shawn Webb wrote: > It appears with the latest 12-CURRENT/arm64, booting is broken. The > boot process gets stuck after the "Using DTB provided by..." message. > > This is on my SoftIron OverDrive 1000: You might try the patch here: https://reviews.freebsd.org/D16463 From owner-freebsd-arm@freebsd.org Sat Jul 28 18:10:54 2018 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 E0D551058CDE for ; Sat, 28 Jul 2018 18:10:53 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 74A3B77FD3 for ; Sat, 28 Jul 2018 18:10:53 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id g191-v6so992550ita.0 for ; Sat, 28 Jul 2018 11:10:53 -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=Bn5VMqpjRlypqt9bc1LgGKulb5rv+0XvGi17nEjBJz4=; b=g5loSrIXw2ATH/CjJsJ3/sVHe7VzN8gnzQ3K+AIwMdLQEgKFW7lhkgMI+hXJRy5+Hk 8bTgxADglgcLf+hjyCJ9FI5OMrCqMpEIg6LbND5iwNAKduW86+gxdVylfZwLVYEE6Co2 Bgjar2HagA427hGr8iC7U10aT1JWSXc9e6mLpbzhT3R9zbLqDhcZZsUbv/7rvrmp4e1z DpvMtmbSK8uSekr7EBtNK1upnjvI/IC7ROaC2Nc2RssAg5UHQgoscvNF6qm2TBZ2fXL3 kIGWlGpr5R5Hl9WR1V06Wert7un0t4UXr6T/DnsT0xnLaLm0Y9d6vMr0ggRXAmNk1sNa p5yg== 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=Bn5VMqpjRlypqt9bc1LgGKulb5rv+0XvGi17nEjBJz4=; b=ihNk0WhSC9mg2Wc+4UB2eAGuvoq4PiqUYUr9/TsM3Yl6FLjmEvNq+mXUxHEvpMSQYQ gkxU0piaW//a29q/OyLiU1OXc7gAyCLy3ph1+AZncTYF35I5PKcQJoDhrjuQyVAQ5DJX OaQmCfWe7L6Zr//Nh7afjgXWxiYNA1ZrGROJu63s0BtsP2Yxjj61rtjL8OkRkM3DqPOj +YmbT4719GwemHYaTdPAwX0bUSJAUB8+o9bmR7H1dHaiukaSknLpBqyaL9FtwR7kEPwE 0q+IyehpOfuCRsUKiF0kyIWAmpUxeJR6gtn0NqgR6LRlQkEDK9N2fM/SJc5pFSd+LCR3 1Jvg== X-Gm-Message-State: AOUpUlE/N3oBzzGZNvbyWp2bQxVGigO9BQl+7n+FrhFG3GY32GPM+EzR W3nJw9kjaO7aMMgy3ScN/ldVgmmOcFy2ZmhGEr9ejA== X-Google-Smtp-Source: AAOMgpeDvqlfgcf3jArcZyRAr+A2aNcm8Xz+mTjyvbk/xcVgmp7treJK6pzAunnXnPYDoQm3rhZxpoacETPAt+yR2/0= X-Received: by 2002:a24:3ec3:: with SMTP id s186-v6mr1996373its.73.1532801452708; Sat, 28 Jul 2018 11:10:52 -0700 (PDT) MIME-Version: 1.0 References: <20180728171745.e5g6dfrcjdn2mtg4@mutt-hbsd> <20180728180831.GA73141@raichu> In-Reply-To: <20180728180831.GA73141@raichu> From: Warner Losh Date: Sat, 28 Jul 2018 12:10:40 -0600 Message-ID: Subject: Re: Booting arm64 uefi broken To: Mark Johnston Cc: Shawn Webb , FreeBSD Current , imp@freebsd.org, freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2018 18:10:54 -0000 On Sat, Jul 28, 2018, 12:08 PM Mark Johnston wrote: > On Sat, Jul 28, 2018 at 01:17:45PM -0400, Shawn Webb wrote: > > It appears with the latest 12-CURRENT/arm64, booting is broken. The > > boot process gets stuck after the "Using DTB provided by..." message. > > > > This is on my SoftIron OverDrive 1000: > > You might try the patch here: https://reviews.freebsd.org/D16463 That's in the tree now... Warner > > From owner-freebsd-arm@freebsd.org Sat Jul 28 18:28:40 2018 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 6BB7D1059699; Sat, 28 Jul 2018 18:28:40 +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 AC7E779120; Sat, 28 Jul 2018 18:28:39 +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 4480a98d; Sat, 28 Jul 2018 20:28:31 +0200 (CEST) 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=TOKSQbC/nbtMpiXP8RDIWN8NoRE=; b=LFlvJTH/v7k2314K5nocDV/jPVlh xBDf6ZYB6u5vObrq9FSYxo1XAUPd1o4gHhhogD0G8MdSQI5UXBMaEDvUhXQtALuX gdds5u2K62ke9/SWYNV8qgttdipO6jyN8ARifDflc/i1Y/xlB1g9p346n+jsCKRo wZVigYTuTTW5UWA= 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=IexAdoD7PEnTea9ajb6/qkLcqymFdM/1uzrvAnNR3iqCcTFNCBB9zeKM xwX1HzFu5LtDQpebZGDrU8zw2mevdckMUPiFUyBno+ne+TxgloU764AkWvM/OShy 9r3O+cLOCCXreC1mwFRRjoQTJNNh34lXGUA10+M96l+3ITl8VDM= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id b6f3ea70 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sat, 28 Jul 2018 20:28:31 +0200 (CEST) Date: Sat, 28 Jul 2018 20:28:30 +0200 From: Emmanuel Vadot To: Shawn Webb Cc: freebsd-current@freebsd.org, imp@freebsd.org, freebsd-arm@freebsd.org Subject: Re: Booting arm64 uefi broken Message-Id: <20180728202830.5ff22ce7b88c6cbf2cf25e18@bidouilliste.com> In-Reply-To: <20180728171745.e5g6dfrcjdn2mtg4@mutt-hbsd> References: <20180728171745.e5g6dfrcjdn2mtg4@mutt-hbsd> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2018 18:28:40 -0000 On Sat, 28 Jul 2018 13:17:45 -0400 Shawn Webb wrote: > It appears with the latest 12-CURRENT/arm64, booting is broken. The > boot process gets stuck after the "Using DTB provided by..." message. > > This is on my SoftIron OverDrive 1000: > > >> FreeBSD EFI boot block > Loader path: /boot/loader.efi > > Initializing modules: ZFS UFS > Load Path: \EFI\BOOT\BOOTAA64.EFI > Load Device: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(1,GPT,73365FD5-9260-11E8-9F00-0026B93F5298,0x3,0x640) > BootCurrent: 0002 > BootOrder: 0001 0005 0006 0000 0002[*] > Probing 7 block devices......+..* done > ZFS found the following pools: rpool > UFS found 1 partition > Consoles: EFI console > FreeBSD/arm64 EFI loader, Revision 1.1 > (Sat Jul 28 11:32:06 UTC 2018 root@nyi-01.build.hardenedbsd.org) > > Command line arguments: loader.efi > EFI version: 2.60 > EFI Firmware: SoftIron Overdrive 1000 (rev 1.00) > Console: efi (0) > Load Path: HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > Load Device: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > BootCurrent: 0002 > BootOrder: 0001 0005 0006 0000 0002[*] > BootInfo Path: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0) > Ignoring Boot0002: Only one DP found > Trying ESP: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > Setting currdev to disk1p2: > Loading /boot/defaults/loader.conf > /boot/kernel/kernel text=0x8a7169 data=0x1384d0+0x7d39fc syms=[0x8+0x11d108+0x8+0x10e646] > /boot/entropy size=0x1000 > efi-autoresizecons: Neither Graphics Output Protocol nor Universal Graphics Adapter present > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > Using DTB provided by EFI at 0x801fe00000. > > Thanks, > > -- > Shawn Webb > Cofounder and Security Engineer > HardenedBSD > > Tor-ified Signal: +1 443-546-8752 > Tor+XMPP+OTR: lattera@is.a.hacker.sx > GPG Key ID: 0x6A84658F52456EEE > GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE Latest kernel works for me : FreeBSD od1000.home.blih.net 12.0-CURRENT FreeBSD 12.0-CURRENT #3 r336834: Sat Jul 28 20:23:33 CEST 2018 root@od1000.home.blih.net:/usr/o bj/usr/src/arm64.aarch64/sys/GENERIC arm64 I'll try with latest loader.efi -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Sat Jul 28 18:34:34 2018 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 5CC1A1059B4B; Sat, 28 Jul 2018 18:34:34 +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 9D154798F6; Sat, 28 Jul 2018 18:34:33 +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 81595a3b; Sat, 28 Jul 2018 20:34:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=mail; bh=lFL2I0tdaV+a EV1B15/2RsjBMQc=; b=Y/29eBCRxumpRvHgt/EmkPuqthlbmim+v39v+OzdJl9O LOimAkC/fK+ly1EwGFswTMR3NCM4Uni9/ivEZpnjf5Omh/SQevzinJ0ofsPuRzCE ujnDyMoM6yrT2WXCiy6KBMeud/U4QdX+cZ9qOwo2Z9sZ5zQlFl3I7GTZE4B/gpQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=mail; b=JI4L06 Pa0u37szhQM9b8Yaw2jXXp8oucVIDDyDffoLNfNaMvRcW+BkpC0Sx1QG2KHxPpbQ FZnAxS59lBJlLKEFd/IyJ4sWDxlebe5+syz4I/PszDK/z1HDwnHtX26COcKQqCgg jhpBbEIpmMFvzPFJIrM79qOsIYH/eh1iCpg8Y= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id c27a64d7 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sat, 28 Jul 2018 20:34:32 +0200 (CEST) Date: Sat, 28 Jul 2018 20:34:31 +0200 From: Emmanuel Vadot To: Shawn Webb , freebsd-current@freebsd.org, imp@freebsd.org, freebsd-arm@freebsd.org Subject: Re: Booting arm64 uefi broken Message-Id: <20180728203431.4cb39877c0e1a9c55daf9641@bidouilliste.com> In-Reply-To: <20180728202830.5ff22ce7b88c6cbf2cf25e18@bidouilliste.com> References: <20180728171745.e5g6dfrcjdn2mtg4@mutt-hbsd> <20180728202830.5ff22ce7b88c6cbf2cf25e18@bidouilliste.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2018 18:34:34 -0000 On Sat, 28 Jul 2018 20:28:30 +0200 Emmanuel Vadot wrote: > On Sat, 28 Jul 2018 13:17:45 -0400 > Shawn Webb wrote: > > > It appears with the latest 12-CURRENT/arm64, booting is broken. The > > boot process gets stuck after the "Using DTB provided by..." message. > > > > This is on my SoftIron OverDrive 1000: > > > > >> FreeBSD EFI boot block > > Loader path: /boot/loader.efi > > > > Initializing modules: ZFS UFS > > Load Path: \EFI\BOOT\BOOTAA64.EFI > > Load Device: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(1,GPT,73365FD5-9260-11E8-9F00-0026B93F5298,0x3,0x640) > > BootCurrent: 0002 > > BootOrder: 0001 0005 0006 0000 0002[*] > > Probing 7 block devices......+..* done > > ZFS found the following pools: rpool > > UFS found 1 partition > > Consoles: EFI console > > FreeBSD/arm64 EFI loader, Revision 1.1 > > (Sat Jul 28 11:32:06 UTC 2018 root@nyi-01.build.hardenedbsd.org) > > > > Command line arguments: loader.efi > > EFI version: 2.60 > > EFI Firmware: SoftIron Overdrive 1000 (rev 1.00) > > Console: efi (0) > > Load Path: HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > Load Device: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > BootCurrent: 0002 > > BootOrder: 0001 0005 0006 0000 0002[*] > > BootInfo Path: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0) > > Ignoring Boot0002: Only one DP found > > Trying ESP: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > Setting currdev to disk1p2: > > Loading /boot/defaults/loader.conf > > /boot/kernel/kernel text=0x8a7169 data=0x1384d0+0x7d39fc syms=[0x8+0x11d108+0x8+0x10e646] > > /boot/entropy size=0x1000 > > efi-autoresizecons: Neither Graphics Output Protocol nor Universal Graphics Adapter present > > > > Hit [Enter] to boot immediately, or any other key for command prompt. > > Booting [/boot/kernel/kernel]... > > Using DTB provided by EFI at 0x801fe00000. > > > > Thanks, > > > > -- > > Shawn Webb > > Cofounder and Security Engineer > > HardenedBSD > > > > Tor-ified Signal: +1 443-546-8752 > > Tor+XMPP+OTR: lattera@is.a.hacker.sx > > GPG Key ID: 0x6A84658F52456EEE > > GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE > > Latest kernel works for me : > > FreeBSD od1000.home.blih.net 12.0-CURRENT FreeBSD 12.0-CURRENT #3 > r336834: Sat Jul 28 20:23:33 CEST 2018 > root@od1000.home.blih.net:/usr/o bj/usr/src/arm64.aarch64/sys/GENERIC > arm64 > > I'll try with latest loader.efi > > -- > Emmanuel Vadot > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Latest loader.efi fails for me the same way, Shawn did you start bisecting ? -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Sat Jul 28 18:37:11 2018 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 5B24F1059CD7 for ; Sat, 28 Jul 2018 18:37:11 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7028379B76 for ; Sat, 28 Jul 2018 18:37:10 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-wm0-x243.google.com with SMTP id l2-v6so4757260wme.1 for ; Sat, 28 Jul 2018 11:37:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=c7p80zJtut5YpD+vey4bzPLDdMlbtfNfHnuuKjrTBKA=; b=D//UON6jyWbUwFsgM30etJ2VGp6D7eReaoFml+/iLMygNt+2nZGzN9vK2MoSzwXp1P CApEddvKz+FowuSerOIsb4znJ5kzo3gzLMOlTpi/Ed9Eab2LUEoMlHCG35z/f7WIGkGH 600f2MjQCwpzQprGqjGeFdK+xirYodVrW8X6R4ck1eCLBmt44dKOZz5b554mp26r8mGO XPhwkDes3lHm8RQRy+A11poKxVxmNeo2bFv9CoOgea2+bAqApxUJG1oj88+c9LasuJsD zYhYQCOdxvh1T+cec9X8K6OVuhh3eQ7QR1xl+HGegLkZyxX7gjIt50DaVl/wTsP5xNf7 5jfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=c7p80zJtut5YpD+vey4bzPLDdMlbtfNfHnuuKjrTBKA=; b=R7/7nuohbTCSvBxsayzdL4oeAObbqokgxNRVYfPVWKlolSHmgUYMljjx9dHLUsA+vC 3TFkh0Y28krIywSBwaI4sqvGSvpLIO9hzp5h+S/GkbjSxMd8RRPVLbJ2UZHKAC5oJuZd vosd2ziE6t8Ql63grmf08N7QMvF1pDmXfL76L/IvfjojZuKEt69jJhl2oatRaOxEFxK+ vCFcblxLvOr0lP667warsIhBQdxF5HEBhKo0McoaNCU3kpp/rnXsRak3xVq4aR4QksVs JI9tUQ5m/3VzznuO7Tq/wQaC8bzYuM8QAhzrID+d0rKytxOqEOv3ULmUcUQct3StnX/T wqgA== X-Gm-Message-State: AOUpUlGWey91mOHh1Mgd8VH/vJ266bFS8QyNWV5UvwmOQRknY9U20BfM yquik7+YNCoQdbEP8claAQ01MQ== X-Google-Smtp-Source: AAOMgpfTtYKtVExshjmnR1EwxlwGrpLny24nJrPaWergIqoCay9tXq02aQpO0WyzKF0w31/1sI03og== X-Received: by 2002:a1c:6c14:: with SMTP id h20-v6mr9257625wmc.138.1532803029276; Sat, 28 Jul 2018 11:37:09 -0700 (PDT) Received: from mutt-hbsd ([185.248.160.21]) by smtp.gmail.com with ESMTPSA id w4-v6sm1047208wrl.46.2018.07.28.11.37.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 28 Jul 2018 11:37:08 -0700 (PDT) Date: Sat, 28 Jul 2018 14:36:29 -0400 From: Shawn Webb To: Emmanuel Vadot Cc: freebsd-current@freebsd.org, imp@freebsd.org, freebsd-arm@freebsd.org Subject: Re: Booting arm64 uefi broken Message-ID: <20180728183629.wxxabsnyrnqlmwog@mutt-hbsd> References: <20180728171745.e5g6dfrcjdn2mtg4@mutt-hbsd> <20180728202830.5ff22ce7b88c6cbf2cf25e18@bidouilliste.com> <20180728203431.4cb39877c0e1a9c55daf9641@bidouilliste.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xfblujcxadv7knd2" Content-Disposition: inline In-Reply-To: <20180728203431.4cb39877c0e1a9c55daf9641@bidouilliste.com> X-Operating-System: FreeBSD mutt-hbsd 12.0-CURRENT FreeBSD 12.0-CURRENT X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: NeoMutt/20180622 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2018 18:37:11 -0000 --xfblujcxadv7knd2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 28, 2018 at 08:34:31PM +0200, Emmanuel Vadot wrote: > On Sat, 28 Jul 2018 20:28:30 +0200 > Emmanuel Vadot wrote: >=20 > > On Sat, 28 Jul 2018 13:17:45 -0400 > > Shawn Webb wrote: > >=20 > > > It appears with the latest 12-CURRENT/arm64, booting is broken. The > > > boot process gets stuck after the "Using DTB provided by..." message. > > >=20 > > > This is on my SoftIron OverDrive 1000: > > >=20 > > > >> FreeBSD EFI boot block = =20 > > > Loader path: /boot/loader.efi = =20 > > > = =20 > > > Initializing modules: ZFS UFS = =20 > > > Load Path: \EFI\BOOT\BOOTAA64.EFI = =20 > > > Load Device: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/= HD(1,GPT,73365FD5-9260-11E8-9F00-0026B93F5298,0x3,0x640) > > > BootCurrent: 0002 = =20 > > > BootOrder: 0001 0005 0006 0000 0002[*] = =20 > > > Probing 7 block devices......+..* done = =20 > > > ZFS found the following pools: rpool = =20 > > > UFS found 1 partition = =20 > > > Consoles: EFI console = =20 > > > FreeBSD/arm64 EFI loader, Revision 1.1 = =20 > > > (Sat Jul 28 11:32:06 UTC 2018 root@nyi-01.build.hardenedbsd.org) = =20 > > > = =20 > > > Command line arguments: loader.efi = =20 > > > EFI version: 2.60 = =20 > > > EFI Firmware: SoftIron Overdrive 1000 (rev 1.00) = =20 > > > Console: efi (0) = =20 > > > Load Path: HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x1= 07D00) =20 > > > Load Device: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/= HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > > BootCurrent: 0002 = =20 > > > BootOrder: 0001 0005 0006 0000 0002[*] = =20 > > > BootInfo Path: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0= ) =20 > > > Ignoring Boot0002: Only one DP found = =20 > > > Trying ESP: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(2= ,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > > Setting currdev to disk1p2: = =20 > > > Loading /boot/defaults/loader.conf = =20 > > > /boot/kernel/kernel text=3D0x8a7169 data=3D0x1384d0+0x7d39fc syms=3D[= 0x8+0x11d108+0x8+0x10e646] > > > /boot/entropy size=3D0x1000 = =20 > > > efi-autoresizecons: Neither Graphics Output Protocol nor Universal Gr= aphics Adapter present > > > = =20 > > > Hit [Enter] to boot immediately, or any other key for command prompt.= =20 > > > Booting [/boot/kernel/kernel]... = =20 > > > Using DTB provided by EFI at 0x801fe00000. > > >=20 > > > Thanks, > > >=20 > > > --=20 > > > Shawn Webb > > > Cofounder and Security Engineer > > > HardenedBSD > > >=20 > > > Tor-ified Signal: +1 443-546-8752 > > > Tor+XMPP+OTR: lattera@is.a.hacker.sx > > > GPG Key ID: 0x6A84658F52456EEE > > > GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6E= EE > >=20 > > Latest kernel works for me : > >=20 > > FreeBSD od1000.home.blih.net 12.0-CURRENT FreeBSD 12.0-CURRENT #3 > > r336834: Sat Jul 28 20:23:33 CEST 2018 > > root@od1000.home.blih.net:/usr/o bj/usr/src/arm64.aarch64/sys/GENERIC > > arm64 > >=20 > > I'll try with latest loader.efi > >=20 > > --=20 > > Emmanuel Vadot > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 > Latest loader.efi fails for me the same way, Shawn did you start > bisecting ? Not yet. I don't have the time to right now. Probably won't for a while. Thanks, --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: lattera@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --xfblujcxadv7knd2 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAltct6wACgkQaoRlj1JF bu7E7RAAingoE1tCaX3WddW9eljNvWJHYoI4ufChuRqAfFziVMiauW4GxzXbxt7A gogcl2NcvJKzkVBYdhf8Kvv2S3O5867Cf98uR3GwgG217i4El+NFApNpnAjJaqWb QDLT/ChTayZy7IrhFJfpYFwOk/Vxo0wqPP2r9QpvAUASDZwI6hMbunBSMFdawsp6 PeuYmPCkhCG0HeI+Vhkm5mXxaDDOvSvMb4L+YFh9c6JjW5ohrA8hUBVDlYuAZp1H jPcnT9pcuQhKIqxHzlaSkjrEQfurFxKiRSRJdljYYn77Jv5ueHNbtNmNbcCPVzCq apnWQRElao5gK5fbSmudqRsTm6sxYCgNZAJ3DnEFAad/n9DfYpXVuY7P6d+9rxKA kc7Ukcf3smFwSWKfydjU9PCqj9/mMZFIW9afMpDLrER+vY1irE+Hf5dABCcAvWBd BMLzqq/hn9ZXInokoOB1McnZDA4dr9KPTFaMtl/X97M0lUibtW52n1Yqqg4tMoUc yM3gVaYtgNbtEB+K/V4OnDPo4j7v0fP/VOD3ZF/3V3gZDq3lqNggG3lMkQMZLSCt OPHli1rV8Jgqf1+vasjeGsTOp+RxeMdRmFo3dUqfQ6FI97E/jcOEIYoFkXQJh8Ng VEui5swrBPPsxj6Eo3XzSV5mDbrJ67zZG92++nKlAlDizcl+z6c= =YNPl -----END PGP SIGNATURE----- --xfblujcxadv7knd2-- From owner-freebsd-arm@freebsd.org Sat Jul 28 18:52:21 2018 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 0ADFE105A45C; Sat, 28 Jul 2018 18:52:21 +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 3E2297A94F; Sat, 28 Jul 2018 18:52:20 +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 273df023; Sat, 28 Jul 2018 20:52:18 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=mail; bh=bnWQwJ59H2NC 0kVAjhydsZenQmw=; b=CivJYgJDacDoE9/0FLzXYFu3354gZ2Dh9CB54c5chTDC GZPPm2zvA0OJk7VfHbbfVwdBYHeuVJycTk8ErcK0v8lhJ8xl6QUnmHGkodC4hqm0 7cQKLw20FCrwGoTcpkFaqP9gf2WKx/dkRojGJq3RO5rd2XWyDySV25EHQLJ92Ls= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=mail; b=DefcAN K6DiY5fhdwMo1KRisxMA0WU79ftMePadnzdyRBeyCReDYP5uC6QESLg0DnLPMP+a jpGj88IMH+zErHTrbrmOx99ZBS3gnTIi4z0ieBpWwYjzxNiSEPTp++80AaIWsDVa JuWp6NCnjV7iqD4KPzdaJYfzzJtBZ7pZin68Y= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 6e800f86 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sat, 28 Jul 2018 20:52:18 +0200 (CEST) Date: Sat, 28 Jul 2018 20:52:18 +0200 From: Emmanuel Vadot To: Shawn Webb , freebsd-current@freebsd.org, imp@freebsd.org, freebsd-arm@freebsd.org Subject: Re: Booting arm64 uefi broken Message-Id: <20180728205218.ef2661f72f27709c5d829708@bidouilliste.com> In-Reply-To: <20180728203431.4cb39877c0e1a9c55daf9641@bidouilliste.com> References: <20180728171745.e5g6dfrcjdn2mtg4@mutt-hbsd> <20180728202830.5ff22ce7b88c6cbf2cf25e18@bidouilliste.com> <20180728203431.4cb39877c0e1a9c55daf9641@bidouilliste.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2018 18:52:21 -0000 On Sat, 28 Jul 2018 20:34:31 +0200 Emmanuel Vadot wrote: > On Sat, 28 Jul 2018 20:28:30 +0200 > Emmanuel Vadot wrote: > > > On Sat, 28 Jul 2018 13:17:45 -0400 > > Shawn Webb wrote: > > > > > It appears with the latest 12-CURRENT/arm64, booting is broken. The > > > boot process gets stuck after the "Using DTB provided by..." message. > > > > > > This is on my SoftIron OverDrive 1000: > > > > > > >> FreeBSD EFI boot block > > > Loader path: /boot/loader.efi > > > > > > Initializing modules: ZFS UFS > > > Load Path: \EFI\BOOT\BOOTAA64.EFI > > > Load Device: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(1,GPT,73365FD5-9260-11E8-9F00-0026B93F5298,0x3,0x640) > > > BootCurrent: 0002 > > > BootOrder: 0001 0005 0006 0000 0002[*] > > > Probing 7 block devices......+..* done > > > ZFS found the following pools: rpool > > > UFS found 1 partition > > > Consoles: EFI console > > > FreeBSD/arm64 EFI loader, Revision 1.1 > > > (Sat Jul 28 11:32:06 UTC 2018 root@nyi-01.build.hardenedbsd.org) > > > > > > Command line arguments: loader.efi > > > EFI version: 2.60 > > > EFI Firmware: SoftIron Overdrive 1000 (rev 1.00) > > > Console: efi (0) > > > Load Path: HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > > Load Device: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > > BootCurrent: 0002 > > > BootOrder: 0001 0005 0006 0000 0002[*] > > > BootInfo Path: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0) > > > Ignoring Boot0002: Only one DP found > > > Trying ESP: PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > > Setting currdev to disk1p2: > > > Loading /boot/defaults/loader.conf > > > /boot/kernel/kernel text=0x8a7169 data=0x1384d0+0x7d39fc syms=[0x8+0x11d108+0x8+0x10e646] > > > /boot/entropy size=0x1000 > > > efi-autoresizecons: Neither Graphics Output Protocol nor Universal Graphics Adapter present > > > > > > Hit [Enter] to boot immediately, or any other key for command prompt. > > > Booting [/boot/kernel/kernel]... > > > Using DTB provided by EFI at 0x801fe00000. > > > > > > Thanks, > > > > > > -- > > > Shawn Webb > > > Cofounder and Security Engineer > > > HardenedBSD > > > > > > Tor-ified Signal: +1 443-546-8752 > > > Tor+XMPP+OTR: lattera@is.a.hacker.sx > > > GPG Key ID: 0x6A84658F52456EEE > > > GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE > > > > Latest kernel works for me : > > > > FreeBSD od1000.home.blih.net 12.0-CURRENT FreeBSD 12.0-CURRENT #3 > > r336834: Sat Jul 28 20:23:33 CEST 2018 > > root@od1000.home.blih.net:/usr/o bj/usr/src/arm64.aarch64/sys/GENERIC > > arm64 > > > > I'll try with latest loader.efi > > > > -- > > Emmanuel Vadot > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > Latest loader.efi fails for me the same way, Shawn did you start > bisecting ? > Problem is between 20180709 and 20180719 -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Sat Jul 28 19:27:21 2018 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 1CC7A105B4B3 for ; Sat, 28 Jul 2018 19:27:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A7D057BF6B for ; Sat, 28 Jul 2018 19:27:20 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22c.google.com with SMTP id 72-v6so12186415itw.3 for ; Sat, 28 Jul 2018 12:27:20 -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=u8lEF3azVlg8efjkeqkMcIZL/47YrOXSgRF3rGv+QP8=; b=tI5bD/VLYsNBAnghR7AoNCy2enfhQwQcIHPJerm79l0bGheLItyi409s3ZvCPd1nOB fv+BYGTXw4D9ylK0yduC1TLUSbV6KCJ63IrszZIryI6lwAdFT0QzySd3qUXTy4vL3p8N TqcgPDYoRksD889NHe7S5YN8XOXmDVUeIjEZOCdByZne98zJCVjFHGWND6u3LZHEya/k vyIsUjGZFwFaBWSQG4ny1ST+u2RiUjTHeJNqIhqlgYTeW6MzJJs6+yh5HQpO5OpL4lxd 72bOZrL4bBJc7NhsaUMD3VSMibvn+f+b5MDg7O8rY04TKHa2Auh5MUwfv+kJoBkj5nRt erNg== 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=u8lEF3azVlg8efjkeqkMcIZL/47YrOXSgRF3rGv+QP8=; b=QdrIIllnZtCREuKhkii/QtzGXA3XvuYSZS1aQ7QjuVWJLDhDlh/F2ghKB8hCIgrVEk JYm96bnmHs5As9g+bZZ4VsIzD1CBi52yBiMqOeoED0JqiHmN5l0cNrIio45y3K0Uvxxd 6cCAqmK3SL/HHaN5jOGr1KhA8mIoiQT9FipRN/Aqi8XZPGGzjxQ3hQDeqsoBvq99HSur TWFoE9xrhWK4BezhB5MGHMvHu3w4yPZHKq3/AenO6S3GJ/OOhne2utObVcyZ8KxAQ/XA SGFEsedoCDe2c1kyH+TOWOZdrYl68/MSvvKY8NzGFvpyhsWgiyi8jFQtBNJJfBJHz4en DVaQ== X-Gm-Message-State: AOUpUlF32IpROL+dR4fxKiN1ZzhI6e+hLdzQSH1a/PfxbuyGHtCbtNNu QbtWjQzBhqcvL284seF7KdYdWtQwcNJB0Iv+c6negg== X-Google-Smtp-Source: AAOMgpfOBVwOxl1SJokX/+Vw1ejjmKF3v2B3pMWaP2+QePcQnVtb/MmHNHbiQDVDKTh96frA7iZm6Qjafs9TuRDeKvA= X-Received: by 2002:a24:4f52:: with SMTP id c79-v6mr9529838itb.36.1532806039962; Sat, 28 Jul 2018 12:27:19 -0700 (PDT) MIME-Version: 1.0 References: <20180728171745.e5g6dfrcjdn2mtg4@mutt-hbsd> <20180728202830.5ff22ce7b88c6cbf2cf25e18@bidouilliste.com> <20180728203431.4cb39877c0e1a9c55daf9641@bidouilliste.com> <20180728205218.ef2661f72f27709c5d829708@bidouilliste.com> In-Reply-To: <20180728205218.ef2661f72f27709c5d829708@bidouilliste.com> From: Warner Losh Date: Sat, 28 Jul 2018 13:27:08 -0600 Message-ID: Subject: Re: Booting arm64 uefi broken To: Emmanuel Vadot Cc: Shawn Webb , FreeBSD Current , imp@freebsd.org, freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2018 19:27:21 -0000 Let me know the rev... all my fixes are in the tree... Warner On Sat, Jul 28, 2018, 12:52 PM Emmanuel Vadot wrote: > On Sat, 28 Jul 2018 20:34:31 +0200 > Emmanuel Vadot wrote: > > > On Sat, 28 Jul 2018 20:28:30 +0200 > > Emmanuel Vadot wrote: > > > > > On Sat, 28 Jul 2018 13:17:45 -0400 > > > Shawn Webb wrote: > > > > > > > It appears with the latest 12-CURRENT/arm64, booting is broken. The > > > > boot process gets stuck after the "Using DTB provided by..." message. > > > > > > > > This is on my SoftIron OverDrive 1000: > > > > > > > > >> FreeBSD EFI boot block > > > > > Loader path: /boot/loader.efi > > > > > > > > > > Initializing modules: ZFS UFS > > > > > Load Path: \EFI\BOOT\BOOTAA64.EFI > > > > > Load Device: > PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(1,GPT,73365FD5-9260-11E8-9F00-0026B93F5298,0x3,0x640) > > > > BootCurrent: 0002 > > > > > BootOrder: 0001 0005 0006 0000 0002[*] > > > > > Probing 7 block devices......+..* done > > > > > ZFS found the following pools: rpool > > > > > UFS found 1 partition > > > > > Consoles: EFI console > > > > > FreeBSD/arm64 EFI loader, Revision 1.1 > > > > > (Sat Jul 28 11:32:06 UTC 2018 root@nyi-01.build.hardenedbsd.org) > > > > > > > > > > Command line arguments: loader.efi > > > > > EFI version: 2.60 > > > > > EFI Firmware: SoftIron Overdrive 1000 (rev 1.00) > > > > > Console: efi (0) > > > > > Load Path: > HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > > > Load Device: > PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > > > BootCurrent: 0002 > > > > > BootOrder: 0001 0005 0006 0000 0002[*] > > > > > BootInfo Path: > PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0) > > > > Ignoring Boot0002: Only one DP found > > > > > Trying ESP: > PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > > > Setting currdev to disk1p2: > > > > > Loading /boot/defaults/loader.conf > > > > > /boot/kernel/kernel text=0x8a7169 data=0x1384d0+0x7d39fc > syms=[0x8+0x11d108+0x8+0x10e646] > > > > /boot/entropy size=0x1000 > > > > > efi-autoresizecons: Neither Graphics Output Protocol nor Universal > Graphics Adapter present > > > > > > > > > Hit [Enter] to boot immediately, or any other key for command > prompt. > > > > Booting [/boot/kernel/kernel]... > > > > > Using DTB provided by EFI at 0x801fe00000. > > > > > > > > Thanks, > > > > > > > > -- > > > > Shawn Webb > > > > Cofounder and Security Engineer > > > > HardenedBSD > > > > > > > > Tor-ified Signal: +1 443-546-8752 > > > > Tor+XMPP+OTR: lattera@is.a.hacker.sx > > > > GPG Key ID: 0x6A84658F52456EEE > > > > GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 > 6EEE > > > > > > Latest kernel works for me : > > > > > > FreeBSD od1000.home.blih.net 12.0-CURRENT FreeBSD 12.0-CURRENT #3 > > > r336834: Sat Jul 28 20:23:33 CEST 2018 > > > root@od1000.home.blih.net:/usr/o bj/usr/src/arm64.aarch64/sys/GENERIC > > > arm64 > > > > > > I'll try with latest loader.efi > > > > > > -- > > > Emmanuel Vadot > > > _______________________________________________ > > > freebsd-current@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > > > Latest loader.efi fails for me the same way, Shawn did you start > > bisecting ? > > > > Problem is between 20180709 and 20180719 > > -- > Emmanuel Vadot > From owner-freebsd-arm@freebsd.org Sat Jul 28 19:50:28 2018 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 7C8EA105BF29; Sat, 28 Jul 2018 19:50:28 +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 B88267CE61; Sat, 28 Jul 2018 19:50:27 +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 760810c6; Sat, 28 Jul 2018 21:50:25 +0200 (CEST) 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=+VMEA4ZsaA23W7gU/m2rwuSGuGE=; b=sIQ6ozSy7cOlmpBi+kS9bu+gPhG+ ZtWpVL98wkUBT2ZkjOBXqXopxDGMQRLzTOl99pHgnN/Iswub+k47x8JUTdoA9zUY 0rppnftJTzmISBt8FqsxZU1QblgFWCo2IWPUAQCT+31xSNjiyaAgapdAn2Lk/jZB bGYLW1y0gA48FMQ= 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=aBIt9tPMqSSCqqFpq3Du5uZIo6owne22NZaNeu4WXTK9jFIRt9Sq4aGp fWkgbqbbIPBrDJk80kxS34ci9Jfl1YmWyBmjpHmyzgRi4I/NtrJvln+qReEIAGPq DC5ipT2AntYrthqCnMiirLbbhCHzpL0e8la+Qpqy+w/Q1waFFuw= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 37850b65 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sat, 28 Jul 2018 21:50:25 +0200 (CEST) Date: Sat, 28 Jul 2018 21:50:25 +0200 From: Emmanuel Vadot To: Warner Losh Cc: Shawn Webb , FreeBSD Current , imp@freebsd.org, freebsd-arm@freebsd.org Subject: Re: Booting arm64 uefi broken Message-Id: <20180728215025.f5acbac48ab0969eff2e7545@bidouilliste.com> In-Reply-To: References: <20180728171745.e5g6dfrcjdn2mtg4@mutt-hbsd> <20180728202830.5ff22ce7b88c6cbf2cf25e18@bidouilliste.com> <20180728203431.4cb39877c0e1a9c55daf9641@bidouilliste.com> <20180728205218.ef2661f72f27709c5d829708@bidouilliste.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2018 19:50:28 -0000 On Sat, 28 Jul 2018 13:27:08 -0600 Warner Losh wrote: > Let me know the rev... all my fixes are in the tree... > > Warner Fixed by r336837 Thanks, > On Sat, Jul 28, 2018, 12:52 PM Emmanuel Vadot wrote: > > > On Sat, 28 Jul 2018 20:34:31 +0200 > > Emmanuel Vadot wrote: > > > > > On Sat, 28 Jul 2018 20:28:30 +0200 > > > Emmanuel Vadot wrote: > > > > > > > On Sat, 28 Jul 2018 13:17:45 -0400 > > > > Shawn Webb wrote: > > > > > > > > > It appears with the latest 12-CURRENT/arm64, booting is broken. The > > > > > boot process gets stuck after the "Using DTB provided by..." message. > > > > > > > > > > This is on my SoftIron OverDrive 1000: > > > > > > > > > > >> FreeBSD EFI boot block > > > > > > > Loader path: /boot/loader.efi > > > > > > > > > > > > > > Initializing modules: ZFS UFS > > > > > > > Load Path: \EFI\BOOT\BOOTAA64.EFI > > > > > > > Load Device: > > PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(1,GPT,73365FD5-9260-11E8-9F00-0026B93F5298,0x3,0x640) > > > > > BootCurrent: 0002 > > > > > > > BootOrder: 0001 0005 0006 0000 0002[*] > > > > > > > Probing 7 block devices......+..* done > > > > > > > ZFS found the following pools: rpool > > > > > > > UFS found 1 partition > > > > > > > Consoles: EFI console > > > > > > > FreeBSD/arm64 EFI loader, Revision 1.1 > > > > > > > (Sat Jul 28 11:32:06 UTC 2018 root@nyi-01.build.hardenedbsd.org) > > > > > > > > > > > > > > Command line arguments: loader.efi > > > > > > > EFI version: 2.60 > > > > > > > EFI Firmware: SoftIron Overdrive 1000 (rev 1.00) > > > > > > > Console: efi (0) > > > > > > > Load Path: > > HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > > > > Load Device: > > PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > > > > BootCurrent: 0002 > > > > > > > BootOrder: 0001 0005 0006 0000 0002[*] > > > > > > > BootInfo Path: > > PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0) > > > > > Ignoring Boot0002: Only one DP found > > > > > > > Trying ESP: > > PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > > > > Setting currdev to disk1p2: > > > > > > > Loading /boot/defaults/loader.conf > > > > > > > /boot/kernel/kernel text=0x8a7169 data=0x1384d0+0x7d39fc > > syms=[0x8+0x11d108+0x8+0x10e646] > > > > > /boot/entropy size=0x1000 > > > > > > > efi-autoresizecons: Neither Graphics Output Protocol nor Universal > > Graphics Adapter present > > > > > > > > > > > > Hit [Enter] to boot immediately, or any other key for command > > prompt. > > > > > Booting [/boot/kernel/kernel]... > > > > > > > Using DTB provided by EFI at 0x801fe00000. > > > > > > > > > > Thanks, > > > > > > > > > > -- > > > > > Shawn Webb > > > > > Cofounder and Security Engineer > > > > > HardenedBSD > > > > > > > > > > Tor-ified Signal: +1 443-546-8752 > > > > > Tor+XMPP+OTR: lattera@is.a.hacker.sx > > > > > GPG Key ID: 0x6A84658F52456EEE > > > > > GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 > > 6EEE > > > > > > > > Latest kernel works for me : > > > > > > > > FreeBSD od1000.home.blih.net 12.0-CURRENT FreeBSD 12.0-CURRENT #3 > > > > r336834: Sat Jul 28 20:23:33 CEST 2018 > > > > root@od1000.home.blih.net:/usr/o bj/usr/src/arm64.aarch64/sys/GENERIC > > > > arm64 > > > > > > > > I'll try with latest loader.efi > > > > > > > > -- > > > > Emmanuel Vadot > > > > _______________________________________________ > > > > freebsd-current@freebsd.org mailing list > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > To unsubscribe, send any mail to " > > freebsd-current-unsubscribe@freebsd.org" > > > > > > Latest loader.efi fails for me the same way, Shawn did you start > > > bisecting ? > > > > > > > Problem is between 20180709 and 20180719 > > > > -- > > Emmanuel Vadot > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Sat Jul 28 19:55:09 2018 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 70E1B105C224 for ; Sat, 28 Jul 2018 19:55:09 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F0C867D2F1 for ; Sat, 28 Jul 2018 19:55:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x234.google.com with SMTP id r15-v6so6827153ioa.3 for ; Sat, 28 Jul 2018 12:55:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=OC7+XE3C/YzAKfodjQc3kR5PTd2eDk9QM+VQptf/oDU=; b=cDH1IWk6UdSxCoA7zAxrRrVtYCPy/Oh1RKwj+HSh8+oqFMBIuxoOZ8rRvZwjumBzMw ix8VZJd5LVEV3hG5YLQoB/UY81+4aHEDl+r6Y19R19Rhr9jtj0BKdKgd7NnOWC3E1qnh D17z191QbjCS7dLduc2ptLhGLdXJp2uKyKgI1YHavAmE16TFjxQuQEkiac8xBZWxFdvq BRpV9b4yeiHJOTufwxZSHwNONwvfnTRpd5c5xUuf6zsIWQ9UKZiVUpGIYFrmsJvR2oxL Er9Zxgw3meMTLDIvvORhcTFqW6JsHekdHo2NR4zwO5t10VHD5gYQkYOVly7PqRfv4BaW bHdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=OC7+XE3C/YzAKfodjQc3kR5PTd2eDk9QM+VQptf/oDU=; b=p8Wy7ebce0FjcC0g2egJ5/JrRpriCZ9HXlwAqAacVNyAALBQma/+VYY9sO1xeSDTIj vRfBRM57wlD8h6bE0dNVZwSCy9FKQ+wAY3VitQYVVmYTuYTbHaID8/xy5W5tUjctkahm nXE89sWVvzQ4peCyNXhzcz1zFmMKEAfABQBZY6Qurqu62M+YzyTknyozi5/0M8cFSNng zwAWgLmzIm7yON167nkg6bpNTt9I5BlPqNXZRFuTHUIRMRJyCtM4pMPoNRNPhs5uHU/B 7Jlfn9EgNt5VYiwd/HR1XFdGzMg3GxGpz0VwXq8HI1CjZ1E8A83DCVGEQZTadnHbjLdB /8xQ== X-Gm-Message-State: AOUpUlG/FC52DzlO1sLQNABSi9H434IQEA5Xp7xhVf3tCXzU/kYLVKc1 CpZKBMdKSgeM62bBGrogx92vCl6JhJlLD15dlGBeLTVUUjE= X-Google-Smtp-Source: AAOMgpdWkuVG8dSkOyM1j8FcITdwrJgBDuxz3a2g7KxDxqyyOpOta6SxemK5RZW37imFRXZW6nTeKd6SL8GdN2Q2qD4= X-Received: by 2002:a6b:f719:: with SMTP id k25-v6mr9338531iog.37.1532807708261; Sat, 28 Jul 2018 12:55:08 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:4485:0:0:0:0:0 with HTTP; Sat, 28 Jul 2018 12:55:07 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180728215025.f5acbac48ab0969eff2e7545@bidouilliste.com> References: <20180728171745.e5g6dfrcjdn2mtg4@mutt-hbsd> <20180728202830.5ff22ce7b88c6cbf2cf25e18@bidouilliste.com> <20180728203431.4cb39877c0e1a9c55daf9641@bidouilliste.com> <20180728205218.ef2661f72f27709c5d829708@bidouilliste.com> <20180728215025.f5acbac48ab0969eff2e7545@bidouilliste.com> From: Warner Losh Date: Sat, 28 Jul 2018 13:55:07 -0600 X-Google-Sender-Auth: Gj_O2jLT7kWXIaI028P5AO-Avik Message-ID: Subject: Re: Booting arm64 uefi broken To: Emmanuel Vadot Cc: Shawn Webb , FreeBSD Current , Warner Losh , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2018 19:55:09 -0000 On Sat, Jul 28, 2018 at 1:50 PM, Emmanuel Vadot wrote: > On Sat, 28 Jul 2018 13:27:08 -0600 > Warner Losh wrote: > > > Let me know the rev... all my fixes are in the tree... > > > > Warner > > Fixed by r336837 > Yea, I thought I'd pushed all my in-flight src/stand branches yesterday, but I had one on a different machine that wasn't, and it was this one. Sorry for the hassle, it had been ready to go for a couple days... Warner > Thanks, > > > On Sat, Jul 28, 2018, 12:52 PM Emmanuel Vadot > wrote: > > > > > On Sat, 28 Jul 2018 20:34:31 +0200 > > > Emmanuel Vadot wrote: > > > > > > > On Sat, 28 Jul 2018 20:28:30 +0200 > > > > Emmanuel Vadot wrote: > > > > > > > > > On Sat, 28 Jul 2018 13:17:45 -0400 > > > > > Shawn Webb wrote: > > > > > > > > > > > It appears with the latest 12-CURRENT/arm64, booting is broken. > The > > > > > > boot process gets stuck after the "Using DTB provided by..." > message. > > > > > > > > > > > > This is on my SoftIron OverDrive 1000: > > > > > > > > > > > > >> FreeBSD EFI boot block > > > > > > > > > Loader path: /boot/loader.efi > > > > > > > > > > > > > > > > > > Initializing modules: ZFS UFS > > > > > > > > > Load Path: \EFI\BOOT\BOOTAA64.EFI > > > > > > > > > Load Device: > > > PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD( > 1,GPT,73365FD5-9260-11E8-9F00-0026B93F5298,0x3,0x640) > > > > > > BootCurrent: 0002 > > > > > > > > > BootOrder: 0001 0005 0006 0000 0002[*] > > > > > > > > > Probing 7 block devices......+..* done > > > > > > > > > ZFS found the following pools: rpool > > > > > > > > > UFS found 1 partition > > > > > > > > > Consoles: EFI console > > > > > > > > > FreeBSD/arm64 EFI loader, Revision 1.1 > > > > > > > > > (Sat Jul 28 11:32:06 UTC 2018 root@nyi-01.build.hardenedbsd.org) > > > > > > > > > > > > > > > > > > Command line arguments: loader.efi > > > > > > > > > EFI version: 2.60 > > > > > > > > > EFI Firmware: SoftIron Overdrive 1000 (rev 1.00) > > > > > > > > > Console: efi (0) > > > > > > > > > Load Path: > > > HD(2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > > > > > Load Device: > > > PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD( > 2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > > > > > BootCurrent: 0002 > > > > > > > > > BootOrder: 0001 0005 0006 0000 0002[*] > > > > > > > > > BootInfo Path: > > > PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0) > > > > > > Ignoring Boot0002: Only one DP found > > > > > > > > > Trying ESP: > > > PcieRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/USB(0x2,0x0)/HD( > 2,GPT,73365FE7-9260-11E8-9F00-0026B93F5298,0x643,0x107D00) > > > > > > Setting currdev to disk1p2: > > > > > > > > > Loading /boot/defaults/loader.conf > > > > > > > > > /boot/kernel/kernel text=0x8a7169 data=0x1384d0+0x7d39fc > > > syms=[0x8+0x11d108+0x8+0x10e646] > > > > > > /boot/entropy size=0x1000 > > > > > > > > > efi-autoresizecons: Neither Graphics Output Protocol nor > Universal > > > Graphics Adapter present > > > > > > > > > > > > > > > Hit [Enter] to boot immediately, or any other key for command > > > prompt. > > > > > > Booting [/boot/kernel/kernel]... > > > > > > > > > Using DTB provided by EFI at 0x801fe00000. > > > > > > > > > > > > Thanks, > > > > > > > > > > > > -- > > > > > > Shawn Webb > > > > > > Cofounder and Security Engineer > > > > > > HardenedBSD > > > > > > > > > > > > Tor-ified Signal: +1 443-546-8752 > > > > > > Tor+XMPP+OTR: lattera@is.a.hacker.sx > > > > > > GPG Key ID: 0x6A84658F52456EEE > > > > > > GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F > 5245 > > > 6EEE > > > > > > > > > > Latest kernel works for me : > > > > > > > > > > FreeBSD od1000.home.blih.net 12.0-CURRENT FreeBSD 12.0-CURRENT #3 > > > > > r336834: Sat Jul 28 20:23:33 CEST 2018 > > > > > root@od1000.home.blih.net:/usr/o bj/usr/src/arm64.aarch64/sys/ > GENERIC > > > > > arm64 > > > > > > > > > > I'll try with latest loader.efi > > > > > > > > > > -- > > > > > Emmanuel Vadot > > > > > _______________________________________________ > > > > > freebsd-current@freebsd.org mailing list > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > > To unsubscribe, send any mail to " > > > freebsd-current-unsubscribe@freebsd.org" > > > > > > > > Latest loader.efi fails for me the same way, Shawn did you start > > > > bisecting ? > > > > > > > > > > Problem is between 20180709 and 20180719 > > > > > > -- > > > Emmanuel Vadot > > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@ > freebsd.org" > > > -- > Emmanuel Vadot > From owner-freebsd-arm@freebsd.org Sat Jul 28 20:28:35 2018 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 719DE105D4E2 for ; Sat, 28 Jul 2018 20:28:35 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DA2BA7F70A for ; Sat, 28 Jul 2018 20:28:34 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-wm0-x242.google.com with SMTP id s9-v6so8866129wmh.3 for ; Sat, 28 Jul 2018 13:28:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Nv7fhfwYdmhNOvta9xg5noV3G4SV4WFuEsIcU9zxhME=; b=aJACxx9emOzUgS5egeUBQfnEP2VZQbZblekRrvhuffgUvbb608M0pT9DJWbLKE7jPc zwBIdyw0b5YSjnjvm3o+5Wcircw1Mi+Vo1c5mf7CQqvVfL3phjlsi7gBGcy6l8BftDcS dI0AveR3voPLKmtyPLx2ha0joWBMXBXKmT6DUduAoPj3dya03pIRz4yvuPIi9LbCVnd3 nCijdoFkJ35ASAq8vVAbkNrfzz6BVeTl9xd5PwWVwt+jQWmNtGaLcCXzJ4y/DhLLvJ+1 jIIOVHhIcje/BOjgtNvKX1mJX9FEIUqSYDGicWlkF9Y4peoCimtelJOiTYu4NC/XILxD d2nA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Nv7fhfwYdmhNOvta9xg5noV3G4SV4WFuEsIcU9zxhME=; b=EN/UgRw+JlyoxDCymDEjTo6F9hgEXFdtWsy2rXAOyCCKLm6Zlumw0ra5p1T/1jqGWy bOrGHkfIhwweEh4MP5E+AXyHeWwpJ0xadWq9dUvkRr4jimzhjoQQiMlzKF/Z5S0JBhf4 PXBv/I0TA8vjRj1IAEtCz8roRxFQGzmldDACMu+Fcwqqv9+jHMYMY12EfZErNFCesT12 czMQnO8JTUx++2jbGiTouSzzdXwQXYRA2i6Lr1TxLobxDLVQrT5g1uqX7sHFGBspWPSB fo81k+djEDoh1RFB6JkBIXm3i/uSKLUzu7o1v1yvO/x8gg20A1jY0Xw5w3OovB1JWVOy GQFA== X-Gm-Message-State: AOUpUlFxRHB1RkyDh/BVralrGgf0e2Dx3qLhPl1VXj3xkKIk1ZpiXf+v s8b8tggexUZTYLLMIS1LTf+KJQ== X-Google-Smtp-Source: AAOMgpesLz4jsEYZPfASjnYaPc1YSm8U0rmNp47I01V8lmd+LyjQM66L0n96N+rfjyzDL8gYs9MRDQ== X-Received: by 2002:a1c:180e:: with SMTP id 14-v6mr9426615wmy.120.1532809713662; Sat, 28 Jul 2018 13:28:33 -0700 (PDT) Received: from mutt-hbsd ([185.220.102.4]) by smtp.gmail.com with ESMTPSA id q1-v6sm11169154wrw.42.2018.07.28.13.28.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 28 Jul 2018 13:28:32 -0700 (PDT) Date: Sat, 28 Jul 2018 16:27:53 -0400 From: Shawn Webb To: Warner Losh Cc: Emmanuel Vadot , FreeBSD Current , Warner Losh , "freebsd-arm@freebsd.org" Subject: Re: Booting arm64 uefi broken Message-ID: <20180728202753.p7mou4gmot54mzy6@mutt-hbsd> References: <20180728171745.e5g6dfrcjdn2mtg4@mutt-hbsd> <20180728202830.5ff22ce7b88c6cbf2cf25e18@bidouilliste.com> <20180728203431.4cb39877c0e1a9c55daf9641@bidouilliste.com> <20180728205218.ef2661f72f27709c5d829708@bidouilliste.com> <20180728215025.f5acbac48ab0969eff2e7545@bidouilliste.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="55hrtwwwlxxehgq4" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD mutt-hbsd 12.0-CURRENT FreeBSD 12.0-CURRENT X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: NeoMutt/20180622 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2018 20:28:35 -0000 --55hrtwwwlxxehgq4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 28, 2018 at 01:55:07PM -0600, Warner Losh wrote: > On Sat, Jul 28, 2018 at 1:50 PM, Emmanuel Vadot > wrote: >=20 > > On Sat, 28 Jul 2018 13:27:08 -0600 > > Warner Losh wrote: > > > > > Let me know the rev... all my fixes are in the tree... > > > > > > Warner > > > > Fixed by r336837 > > >=20 > Yea, I thought I'd pushed all my in-flight src/stand branches yesterday, > but I had one on a different machine that wasn't, and it was this one. > Sorry for the hassle, it had been ready to go for a couple days... Thanks for commiting the fix! I really appreciate it. :) --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: lattera@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --55hrtwwwlxxehgq4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAltc0cUACgkQaoRlj1JF bu4O1xAAkrLqjYZq4l2M3YKdtIvfuvlWhfhzp2YMOQ5cbQY6pPb5WCEOCzhyr0OD z04n5mlYzanT8zPBPnRF0tu+RGnDsJQXalvGq/iSszecdoy8KT2OZwPA4Ozm/hMK mCUj7RDUguYHGdQxjEIEHidSXkLs0RWeE7h5tCSUoS8wG4UkO3ulTSSPyf7g7C7t GAusBE4ZVYhpaJg23nAeSO03oIiL8Q4q3ykoY0dMMvoT7JB3ZL1x/x29rAnTR4zZ 0IQVm6UM94uia7Z5xazmU8u/mH3PEc0G7LZ4hgeAe3gfhCO2u/R3qtwdJahuMg8S +72k6om/oef3xAPYE4fWdxRCmkif/22wZcMBDHEJZMMtn+e6uw+vG9mk4Jxq0kk7 jLI4x6mCb8Ry7yLEarvNDEQJEkr7PZABlmAiHWaYNPXM74ZOzyHl5he5ydakuVGm nC9ezhoV4l10FLWv8MXSZ8jy9ECo2dz2NhuGTdCOtwLm6aCDIsV0xIZhLzAOQ/UT vEC23VsthwQK2f2/cQ4IU0fAvSs3HGY+TMWiCYtUVUEoN8EOJR6Lf5Qrf/CaanHw LBzmCZmYeT/GDUsMvC9AR/76S/3gHQ/xqTp7HS/n4jW+oZKNh8Sa+Nq4rKYq3Bto PcxZGInbIl+zmIAM/yk39+fRdZYknI0+R2x18nIb+SRfRoppsn8= =tbMu -----END PGP SIGNATURE----- --55hrtwwwlxxehgq4--