From owner-freebsd-arm@freebsd.org Sun May 31 00:33:01 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D43E52FCEFD for ; Sun, 31 May 2020 00:33:01 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from midget.dons.net.au (midget.dons.net.au [IPv6:2403:5800:5101:0:ea:1cff:fefa:f00]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "dons.net.au", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49ZK5k0133z42Gp for ; Sun, 31 May 2020 00:32:56 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from midget.dons.net.au (localhost [127.0.0.1]) by midget.dons.net.au (8.15.2/8.15.2) with ESMTPS id 04V0WT1F013935 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Sun, 31 May 2020 10:02:41 +0930 (ACST) (envelope-from darius@dons.net.au) Received: (from mailnull@localhost) by midget.dons.net.au (8.15.2/8.15.2/Submit) id 04V0WDQ5013927 for ; Sun, 31 May 2020 10:02:13 +0930 (ACST) (envelope-from darius@dons.net.au) X-MIMEDefang-Relay-be813b1f1da6d6b27d681222cb70cc4f5b642383: 2403:5800:5101:0:6590:84a8:b7e6:6508 Received: from [IPv6:2403:5800:5101:0:6590:84a8:b7e6:6508] ([IPv6:2403:5800:5101:0:6590:84a8:b7e6:6508] [2403:5800:5101:0:6590:84a8:b7e6:6508]) by midget.dons.net.au (envelope-sender ) (MIMEDefang) with ESMTP id 04V0W8MX013920; Sun, 31 May 2020 10:02:13 +0930 Subject: Re: code generation Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Content-Type: text/plain; charset=us-ascii From: "O'Connor, Daniel" X-Priority: 3 (Normal) In-Reply-To: <7aed18ab40ff22810b64bbb77b481c78.squirrel@www.nlned.nl> Date: Sun, 31 May 2020 10:02:07 +0930 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <7aed18ab40ff22810b64bbb77b481c78.squirrel@www.nlned.nl> To: mlist@nlned.nl X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Spam-Score: 0 () No, score=0.0 required=5.0 tests=HELO_NO_DOMAIN, T_SPF_PERMERROR autolearn=unavailable autolearn_force=no version=3.4.2 X-Scanned-By: MIMEDefang 2.83 on 10.0.2.1 X-Rspamd-Queue-Id: 49ZK5k0133z42Gp X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.28 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.02)[-1.017]; R_DKIM_ALLOW(-0.20)[dons.net.au:s=default]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[dons.net.au:+]; RCPT_COUNT_TWO(0.00)[2]; HAS_X_PRIO_THREE(0.00)[3]; NEURAL_HAM_SHORT(-0.76)[-0.759]; DMARC_POLICY_ALLOW(-0.50)[dons.net.au,quarantine]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:4764, ipnet:2403:5800:5000::/36, country:AU]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 00:33:01 -0000 > On 31 May 2020, at 07:22, Jack Raats wrote: > Can anyone explain why a simple hello_world.c compiles on a AMD64 = machine > to +/- 21000 bytes while on a raspberry pi 3 +/- 206000 bytes (10 = times > more) >=20 > I use FreeBSD 12.1 stable on RPi3 and cc -o hello hello.c to compile. That would seem like a regression - I have a Beagle Bone Black with a = stale install and the binaries it produces are ~10% smaller than my = amd64 system.. Beaglebone: [gps 0:30] ~ >cc --version FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on = LLVM 8.0.1) Target: armv7-unknown-freebsd13.0-gnueabihf Thread model: posix InstalledDir: /usr/bin [gps 0:31] ~ >cc test.c -o test [gps 0:31] ~ >ll test -rwxr-xr-x 1 darius darius 20068 31 May 00:31 test amd64: [midget 9:59] ~ >cc --version FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on = LLVM 8.0.1) Target: x86_64-unknown-freebsd12.1 Thread model: posix InstalledDir: /usr/bin [midget 10:01] ~ >cc test.c -o test [midget 10:01] ~ >ll test -rwxr-xr-x 1 darius users 22936 31 May 10:01 test -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum From owner-freebsd-arm@freebsd.org Sun May 31 00:45:25 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 81A302FCE47 for ; Sun, 31 May 2020 00:45:25 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gold.funkthat.com [IPv6:2001:470:800b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49ZKN34GQqz42xX for ; Sun, 31 May 2020 00:45:23 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id 04V0jFgj032474 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 30 May 2020 17:45:15 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id 04V0jFXN032472; Sat, 30 May 2020 17:45:15 -0700 (PDT) (envelope-from jmg) Date: Sat, 30 May 2020 17:45:15 -0700 From: John-Mark Gurney To: Jack Raats Cc: freebsd-arm@freebsd.org Subject: Re: code generation Message-ID: <20200531004515.GU4213@funkthat.com> Mail-Followup-To: Jack Raats , freebsd-arm@freebsd.org References: <7aed18ab40ff22810b64bbb77b481c78.squirrel@www.nlned.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7aed18ab40ff22810b64bbb77b481c78.squirrel@www.nlned.nl> X-Operating-System: FreeBSD 11.3-STABLE amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Sat, 30 May 2020 17:45:15 -0700 (PDT) X-Rspamd-Queue-Id: 49ZKN34GQqz42xX X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of jmg@gold.funkthat.com has no SPF policy when checking 2001:470:800b::2) smtp.mailfrom=jmg@gold.funkthat.com X-Spamd-Result: default: False [2.50 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.25)[0.247]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[funkthat.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.33)[0.331]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.72)[0.722]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[jmg@funkthat.com,jmg@gold.funkthat.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[jmg@funkthat.com,jmg@gold.funkthat.com]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 00:45:25 -0000 Jack Raats wrote this message on Sat, May 30, 2020 at 23:52 +0200: > Hi, > > Can anyone explain why a simple hello_world.c compiles on a AMD64 machine > to +/- 21000 bytes while on a raspberry pi 3 +/- 206000 bytes (10 times > more) > > I use FreeBSD 12.1 stable on RPi3 and cc -o hello hello.c to compile. What file, and what's your compiler options. This is on 13-current, but shouldn't be dramatically different. it's on a Pine64 A64-LTS, but that shouldn't mater either. freebsd@generic:~ $ cat hello.c #include int main(void) { printf("hello world\n"); return 0; } freebsd@generic:~ $ cc -o hello hello.c freebsd@generic:~ $ ls -l hello -rwxr-xr-x 1 freebsd freebsd 14232 Jan 1 16:14 hello freebsd@generic:~ $ ./hello hello world This is even smaller when you strip it: freebsd@generic:~ $ strip hello freebsd@generic:~ $ file hello hello: ELF 64-bit LSB executable, ARM aarch64, version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 13.0 (1300094), FreeBSD-style, stripped freebsd@generic:~ $ ls -l hello -rwxr-xr-x 1 freebsd freebsd 5456 Jan 1 16:19 hello Though on the other hand, compile it static and: freebsd@generic:~ $ cc -o hello hello.c -static -O2 freebsd@generic:~ $ ls -l hello -rwxr-xr-x 1 freebsd freebsd 4229680 Jan 1 16:14 hello 4MB seems a bit huge for a statically compiled program... But that's because of debug symbols: freebsd@generic:~ $ cc -o hello hello.c -static -O2 freebsd@generic:~ $ file hello hello: ELF 64-bit LSB executable, ARM aarch64, version 1 (FreeBSD), statically linked, for FreeBSD 13.0 (1300094), FreeBSD-style, with debug_info, not stripped freebsd@generic:~ $ strip hello freebsd@generic:~ $ ls -l hello -rwxr-xr-x 1 freebsd freebsd 701808 Jan 1 16:17 hello But even stripped, it's still VERY large... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arm@freebsd.org Sun May 31 00:49:44 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9D5432FCFD3 for ; Sun, 31 May 2020 00:49:44 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out0.migadu.com (out0.migadu.com [94.23.1.103]) (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 49ZKT31c6pz43Hj for ; Sun, 31 May 2020 00:49:42 +0000 (UTC) (envelope-from greg@unrelenting.technology) Date: Sun, 31 May 2020 00:49:35 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1590886175; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=/mPFX4t84khHjcifNclq6PxF6Yh1kZFr6Uo5xYSKRhA=; b=kpjOTNzG5LVUHBTKfj2uglfvgYGlsr4TsbLbJjfKiwstgDRNu5HAeTMHrVJVaPtjJEBlxf VNKCTg8vFHNDXMAdwl7i+JYS8JNLt5QWZHhL9wcywomsp2y/EcGU9iItOYfe2LJBFAz6ag Abfq176w2IkGPPPd877Wh+JX9vPFpNE= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: myfreeweb To: =?ISO-8859-1?Q?Klaus_K=FCchemann?= , freebsd-arm@freebsd.org Subject: Re: rpi4-uefi.dev Re: RaspberryPi 4B 8G model not boot In-Reply-To: <83980CE0-276E-4DD9-B035-5ED2B561324B@googlemail.com> References: <20200530.130909.120260481726933388.shigeru@os-hackers.jp> <50DC156A-CA39-4809-85B7-02A5180DAB63@yahoo.com> <2DE76C92-8F4B-4658-94E4-FB7C7B7C6135@googlemail.com> <0AD80BEF-AA71-41F0-AD71-DF8516B790D9@yahoo.com> <67808784-29A6-4BC2-9B25-E31DE6DA862A@googlemail.com> <20C49D55-9940-422F-9699-4C56CFCF281B@unrelenting.technology> <83980CE0-276E-4DD9-B035-5ED2B561324B@googlemail.com> Message-ID: <53680CD3-4FE9-42C9-A534-416A71263A08@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49ZKT31c6pz43Hj X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=kpjOTNzG; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 94.23.1.103 as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.88 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.993]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:94.23.1.103]; NEURAL_HAM_LONG(-1.01)[-1.013]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; NEURAL_HAM_SHORT(-0.87)[-0.874]; FREEMAIL_TO(0.00)[googlemail.com,freebsd.org]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[94.23.1.103:from]; ASN(0.00)[asn:16276, ipnet:94.23.0.0/16, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 00:49:44 -0000 On May 30, 2020 9:37:22 PM UTC, "Klaus K=C3=BCchemann" wrote: >=2E=2E O=2EK=2E, why do we do an acpi-split if there=E2=80=99s nothing el= se than PNP0D10 in it ?=20 >NetBSD & OpenBSD don=E2=80=99t do that file-split , afaik They don't have driver inheritance=2E We do, so the usual pattern for devi= ces available with both acpi and fdt is to have them inherit from a common = driver that doesn't attach=2E >> Looks like the problem is that the PCIe controller isn't getting initia= lized, >pcie isn`t exposed ( to the OS) in RPI4UEFI-dev , that=E2=80=99s what @An= drejWarkentin told us =E2=80=A6 >And he told us what to do (in general, while not the easiest to understan= d ;-) Yep=2E Something has to initialize the actual controller though, that's wh= at _INI does=2E So the OS runs the AML bytecode and initializes PCIe withou= t even knowing PCIe exists=2E I'll maybe look into this again soon=2E >( attention : QWord ) >cutoff of an OpenBSD-file : >xhci_acpi_parse_resources That looks like just OpenBSD weirdness, the resources should be handled by= generic acpi code=2E >to anticipate it: if we have solved this problem, we will probably end up= on vfs_mountroot because the uSD driver is not recognized under acpi, afai= k Screw uSD, I just put the OS on a USB stick and only the firmware on uSD= =2E From owner-freebsd-arm@freebsd.org Sun May 31 05:59:52 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CA2A532C075 for ; Sun, 31 May 2020 05:59:52 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic313-21.consmr.mail.gq1.yahoo.com (sonic313-21.consmr.mail.gq1.yahoo.com [98.137.65.84]) (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 49ZSLv53H6z4SFj for ; Sun, 31 May 2020 05:59:51 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: LX1z14IVM1lDn4.BXNF1PBJHECHebQZpu1iVnUFBEZhZWfLLS7iDDG6Ie_.RgMX SCoyp4wx8uBlhXU6EN7o1tzepK4HRTchPIJg3hC7vBaVp84tyD48tjcKwRFWQG.1cdvt2bURsDdX Pp7NhWVKlh0BBOUvOMp8ycp8WdRhT7BcBCv0nAXZ3xa.hx9skAmEbtZ5sJOX0ngBIY9doX4J7LjA IKd8DB2QVHkqh8PgIttY8OtpaTgNZo6IHyu2WwfHl4JOKrUNGnvWtb.46dLNVxrE.MWvtVOOA0Ra 6dBqFRqhk9dBihEnvMROl48ECc_aXOJzbbwCRStEDZv2w6L.qrz_hS2lP2VGFX5RsKitH7Xv4LTe ebhb5odUTHx0zrIzcLaS2tBSpzr2yZgdf8oTmY8R6Rxk4_zdxHtGm9b12q5RyHneHbcFJetrpBmi eFgXrCDGP1GiY0R7l_yyKky5T3HlrqAd4YX9YcTjlC60oukh2M6TVZ3hPah5If2H.3sNTiXSa8Wl piLho.FAEOpEXCo7pD8gHCXPMzeiU8ffHV5URYiGDG23Ybs2V2sIrfJAiVQX7y7ddA6R_85LTkm. 916pqa_jaatCaCbYc9MLFwcJu06n2gEqxvM1WUhgpdY3I2IItaxy58DyS5joTcyCRI.q7.oz23qh CxdyaoAOV0Tv0AqgaAzmx91n1Lj0_oczN_B2V_AE3ncMu.3NfDPCq3N2E8kyZi7CRXCqOAZ7R4Zc PEe5WGdvTo_17Fo24B6rvlBaDxk37Y6cFNiOZnD0z.tAWI_T4MpgcyS_t4FESHPj.Xs67LSlz8Gk hWpiJUd5kK_.yFdIsuShEh.kYC2XxOAGh7rZbQfbJR2cgjarEd.f3c_LryvpIsAxm44vRrl4YaP_ QbY7zigoaIVoqFOfQNfGg.lJvbrPiLuhj7OfMZ0lATPycD8Pi56xkqSb_jdDGNA9C5YojN8ff5Im ._3R_.4QR3ytK9SZDqzCsWSQGUVKxLy4hzz7dO6JIFIfQ5XUlZTiZwoY70WNVKQ8vWnt527fFew_ HX5YMTIa6tQr1aaYoad372WP4Bc._pxCGyuVQhU119dMrYibUrT318z.l4FL69CLpq38uSyIN2Mp m6xTb8RjJ1c0J.6FeqHKc7MJRcAScV6rhScLAWfiHKhoaQ_jYNzc4a6IN2UadAd2scAmkQlZBySf 6yVOUO3dqR2A0q52jki6u3NN_UIsiFr5JhvGaV5KwrGTdwS0.IJtMCpgdT4S9hmP0I.acL9EUsk_ S836prY25neDC0.HP7hHgKVNOodGXm6S2KeOKCQpGl9_BaVIf5RRDI3YmXriRYgvrLIyMZqAVQG4 Og6iZO_LUP8GOIZS.M9RcZZTXMyVoWd6jYuFYiS8eytK_ZHsO9TOFd4KiFYEUVTAqtyVfDKw8ia8 LisRYotowExM0zJ0xsrml Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.gq1.yahoo.com with HTTP; Sun, 31 May 2020 05:59:49 +0000 Received: by smtp406.mail.gq1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 8753dda583088dccce7a138d8a15b8e0; Sun, 31 May 2020 05:59:46 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: bootverbose Test-session Re: Driver for Raspberry Pi 4 PCI-express controller From: Mark Millard In-Reply-To: <3040F106-13F6-462C-B655-DE7F79FFE52A@googlemail.com> Date: Sat, 30 May 2020 22:59:45 -0700 Cc: Robert Crowston , freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: References: <7F058E92-DDD3-4728-9A51-09BF1D47855C@googlemail.com> <1RBZ-1AclgkiNDwWUqrWhun8T8YSAX6g64NeSc2DKy9EF1wGsJobselP4UYGflpcmbfUx3sEEM2YplIJOXPmZ6EG_GwiMC1_3GLrqpZxisQ=@protonmail.com> <46519DEB-E96D-43DD-B739-401F9F51371E@googlemail.com> <87EE030D-5323-477B-9FF3-CB8970138729@googlemail.com> <3040F106-13F6-462C-B655-DE7F79FFE52A@googlemail.com> To: =?utf-8?Q?Klaus_K=C3=BCchemann?= X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49ZSLv53H6z4SFj X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.98 / 15.00]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-1.46)[-1.457]; FREEMAIL_TO(0.00)[googlemail.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.01)[-1.011]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.01)[-1.014]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.65.84:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.65.84:from]; FREEMAIL_CC(0.00)[protonmail.com,freebsd.org]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 05:59:52 -0000 On 2020-May-28, at 20:07, Klaus K=C3=BCchemann via freebsd-arm = wrote: >=20 >> Am 28.05.2020 um 20:45 schrieb Robert Crowston = : >>=20 >> I did test on a pi4 with the latest USB firmware. A keyboard = functioned okay without me doing anything special. >>=20 >> =E2=80=A6. >>>=20 >=20 >=20 > O.K., here is a funny bootverbose test-session (using Original = rpi-power adaptor 3A & UPS(Uninterruptible power supply ) : >=20 >=20 > =E2=80=94Test No. 1 ( with connected HDMI-Display[and = UART&USB-stick&keyboard/mouse]) -: =E2=80=94=E2=80=94=E2=80=94 >=20 > ugen0.2: at usbus0 (disconnected) > ugen0.2: at usbus0 > ---- > xhci0: Resetting controller > ugen0.2: at usbus0 (disconnected) > ugen0.2: at usbus0 (disconnected) > uhub0: at usbus0, port 1, addr 1 (disconnected) > uhub0: detached > uhub0 on usbus0 > uhub0: <0x1106 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on = usbus0 > uhub0: 5 ports with 4 removable, self powered > xhci0: Resetting controller > ugen0.2: at usbus0 (disconnected) > ugen0.2: at usbus0 (disconnected) > uhub0: at usbus0, port 1, addr 1 (disconnected) > uhub0: detached > uhub0 on usbus0 > uhub0: <0x1106 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on = usbus0 > uhub0: 5 ports with 4 removable, self powered > xhci0: Resetting controller > ugen0.2: at usbus0 (disconnected) > ugen0.2: at usbus0 (disconnected) > uhub0: at usbus0, port 1, addr 1 (disconnected) > uhub0: detached > uhub0 on usbus0 > uhub0: <0x1106 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on = usbus0 > uhub0: 5 ports with 4 removable, self powered > ugen0.2: at usbus0 (disconnected) > =E2=80=94 end Test No. 1 =E2=80=94 >=20 > =E2=80=94Test No. 2 ( WITHOUT connected HDMI-Display [but with = UART&USB-stick&keyboard/mouse] ) : =E2=80=94=E2=80=94=E2=80=94 >=20 > . . . > =E2=80=94=E2=80=94end Test No.2 =E2=80=94 >=20 > Hot-Plugging the HDMI-Display freezed the system =E2=80=A6. >=20 > . . . I do not know if the following has any significance or not. I got as far as seeing if my lumina build was working on the NetBSD RPi4 configuration I've been testing doing builds on. This means that I plugged in a keyboard and mouse (and I had earlier booted with the HDMI connected). This was to a USB2 port, not USB3. The RPi mouse was plugged into an RPi keyboard and the RPi keyboard was in turn plugged into the RPi4. A while after having quit lumina (so proving the mouse was working while using lumina). . . [ 1036.8743574] wsmouse0: detached [ 1036.8743574] ums0: detached [ 1036.8843604] uhidev2: detached [ 1036.8843604] uhidev2: at uhub3 port 2 (addr 5) disconnected [ 1038.8143543] uhidev2 at uhub3 port 2 configuration 1 interface 0 [ 1038.8143543] uhidev2: PixArt (0x093a) USB Optical Mouse (0x2510), rev = 1.10/1.00, addr 5, iclass 3/1 [ 1038.8343570] ums0 at uhidev2: 3 buttons and Z dir [ 1038.8343570] wsmouse0 at ums0 mux 0 So I tried plugging in to a RPI4 USB3 port instead and started up and used lumina for a bit and then quit lumina. After a while: [ 2030.8193248] wsmouse0: detached [ 2030.8193248] ums0: detached [ 2030.8193248] uhidev2: detached [ 2030.8193248] uhidev2: at uhub3 port 2 (addr 5) disconnected [ 2032.7593189] uhidev2 at uhub3 port 2 configuration 1 interface 0 [ 2032.7593189] uhidev2: PixArt (0x093a) USB Optical Mouse (0x2510), rev = 1.10/1.00, addr 5, iclass 3/1 [ 2032.7793222] ums0 at uhidev2: 3 buttons and Z dir [ 2032.7793222] wsmouse0 at ums0 mux 0 (Other than the timestamps, it is the same text for both port types.) With the keyboard/mouse combination left connected, these messages repeated periodically: [ 2030.8193248] wsmouse0: detached . . . [ 2093.0289255] wsmouse0: detached . . . [ 2154.9885123] wsmouse0: detached The file system was on a USB3 SSD plugged into one of the USB3 ports. That was it for USB connections. The USB SSD continued to operate well. (There is a fan, EtherNet, and the serial console as well. The power supply is rated for 5.1V 3.5A.) =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Sun May 31 06:31:35 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A445D32CB5D for ; Sun, 31 May 2020 06:31:35 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gold.funkthat.com [IPv6:2001:470:800b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49ZT3W0hVDz4VR2 for ; Sun, 31 May 2020 06:31:34 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id 04V6VPeF077450 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 30 May 2020 23:31:25 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id 04V6VOqp077449; Sat, 30 May 2020 23:31:24 -0700 (PDT) (envelope-from jmg) Date: Sat, 30 May 2020 23:31:24 -0700 From: John-Mark Gurney To: "Dr. Rolf Jansen" Cc: freebsd-arm@freebsd.org Subject: Re: BeagleBone AI Message-ID: <20200531063124.GY4213@funkthat.com> Mail-Followup-To: "Dr. Rolf Jansen" , freebsd-arm@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 11.3-STABLE amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Sat, 30 May 2020 23:31:25 -0700 (PDT) X-Rspamd-Queue-Id: 49ZT3W0hVDz4VR2 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of jmg@gold.funkthat.com has no SPF policy when checking 2001:470:800b::2) smtp.mailfrom=jmg@gold.funkthat.com X-Spamd-Result: default: False [2.63 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.37)[0.368]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[funkthat.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.33)[0.331]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.73)[0.726]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[jmg@funkthat.com,jmg@gold.funkthat.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[jmg@funkthat.com,jmg@gold.funkthat.com]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 06:31:35 -0000 Dr. Rolf Jansen wrote this message on Fri, May 29, 2020 at 23:21 -0300: > What modern SBC with more than 1 I²C bus and which can run FreeBSD 13++ would you suggest? I'd look at ARM64 boards. The life will be longer, and the support from the FreeBSD community will likely receive more attention. Many boards have multiple I2C buses... the Pine A64-LTS has a couple I2C buses, but they are both on ribbon conenctors (TP and CSI)... There is also the Zynq-7000 option, though it's an armv7 cpu.. I recently brought up the Cora Z7 board... With the PL (FPGA), you can add many more I2C interfaces... We don't have a driver for Xilinx's AXI I2C yet, but with that, (and a bit of block building w/ Vivado), you could have 10 or 20 I2C buses... Let me know if you'd like more info. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arm@freebsd.org Sun May 31 14:14:39 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A61C5335B76 for ; Sun, 31 May 2020 14:14:39 +0000 (UTC) (envelope-from crowston@protonmail.com) Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49ZgKp4kGtz49cv for ; Sun, 31 May 2020 14:14:38 +0000 (UTC) (envelope-from crowston@protonmail.com) Date: Sun, 31 May 2020 14:14:28 +0000 To: myfreeweb From: Robert Crowston Cc: =?UTF-8?Q?Klaus_K=C3=BCchemann?= , "freebsd-arm@freebsd.org" Reply-To: Robert Crowston Subject: Re: rpi4-uefi.dev Re: RaspberryPi 4B 8G model not boot Message-ID: In-Reply-To: <53680CD3-4FE9-42C9-A534-416A71263A08@unrelenting.technology> References: <20200530.130909.120260481726933388.shigeru@os-hackers.jp> <50DC156A-CA39-4809-85B7-02A5180DAB63@yahoo.com> <2DE76C92-8F4B-4658-94E4-FB7C7B7C6135@googlemail.com> <0AD80BEF-AA71-41F0-AD71-DF8516B790D9@yahoo.com> <67808784-29A6-4BC2-9B25-E31DE6DA862A@googlemail.com> <20C49D55-9940-422F-9699-4C56CFCF281B@unrelenting.technology> <83980CE0-276E-4DD9-B035-5ED2B561324B@googlemail.com> <53680CD3-4FE9-42C9-A534-416A71263A08@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49ZgKp4kGtz49cv X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.72 / 15.00]; HAS_REPLYTO(0.00)[crowston@protonmail.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[protonmail.com]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; DKIM_TRACE(0.00)[protonmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.22:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.04)[-1.041]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.37)[0.369]; NEURAL_HAM_LONG(-0.95)[-0.950]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[protonmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.22:from]; FREEMAIL_CC(0.00)[googlemail.com,freebsd.org] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 14:14:39 -0000 > pcie isn`t exposed ( to the OS) in RPI4UEFI-dev , that=E2=80=99s what @An= drejWarkentin told us =E2=80=A6 Something about this doesn't make sense, because there is a PCI-E driver fo= r OpenBSD that was written specifically for the Rpi4 UEFI. =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Sunday, 31 May 2020 01:49, myfreeweb wrote= : > > > On May 30, 2020 9:37:22 PM UTC, "Klaus K=C3=BCchemann"maciphone2@googlema= il.com wrote: > > > .. O.K., why do we do an acpi-split if there=E2=80=99s nothing else tha= n PNP0D10 in it ? > > NetBSD & OpenBSD don=E2=80=99t do that file-split , afaik > > They don't have driver inheritance. We do, so the usual pattern for devic= es available with both acpi and fdt is to have them inherit from a common d= river that doesn't attach. > > > > Looks like the problem is that the PCIe controller isn't getting init= ialized, > > > pcie isn`t exposed ( to the OS) in RPI4UEFI-dev , that=E2=80=99s what= @AndrejWarkentin told us =E2=80=A6 > > > And he told us what to do (in general, while not the easiest to under= stand ;-) > > Yep. Something has to initialize the actual controller though, that's wha= t _INI does. So the OS runs the AML bytecode and initializes PCIe without e= ven knowing PCIe exists. > > I'll maybe look into this again soon. > > > ( attention : QWord ) > > cutoff of an OpenBSD-file : > > xhci_acpi_parse_resources > > That looks like just OpenBSD weirdness, the resources should be handled b= y generic acpi code. > > > to anticipate it: if we have solved this problem, we will probably end = up on vfs_mountroot because the uSD driver is not recognized under acpi, af= aik > > Screw uSD, I just put the OS on a USB stick and only the firmware on uSD. > > 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 Sun May 31 14:31:09 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C43EE336156 for ; Sun, 31 May 2020 14:31:09 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail-40134.protonmail.ch (mail-40134.protonmail.ch [185.70.40.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49Zghr6J99z4Bfx for ; Sun, 31 May 2020 14:31:08 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Sun, 31 May 2020 14:31:03 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1590935466; bh=Urp2WnzcJ2TiDvnP20ye7Ibd4TEhZjJiiAFm7Nlss0Q=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=o5aWuYFYcCC/jODnhPKj+jh+YFNk6ASSqKDapczoOKVB1IBHcqKhfUEIIwosDosri 7xoAbPkXoqOe5doqYkD5y3VRSckxKUXTTWf26RJYqxtlMdZVxbyciAb5ifvlMm8AzV FKb5ss3l9o3d1Fj40aUQJD4uiFxfFhzOBAOr0xSA= To: "greg@unrelenting.technology" From: Dan Kotowski Cc: freebsd-arm Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> References: <37858865a8ebddd3fe1e3a228a19ef62@unrelenting.technology> <7066da0bc417ed047dc27b4741c90e81@unrelenting.technology> <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49Zghr6J99z4Bfx X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=o5aWuYFY; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.134 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-2.84 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; NEURAL_HAM_LONG(-0.94)[-0.940]; MIME_GOOD(-0.10)[text/plain]; NEURAL_SPAM_SHORT(0.25)[0.253]; ARC_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.134:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_MEDIUM(-1.05)[-1.053]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.134:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 14:31:09 -0000 > I've sent a link to a known firmware build before: > https://drive.google.com/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvErK/view > Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe? I decided to go back to the UEFI sources and have found some differences th= at I think need to be reconciled before moving forward. That said, I'm not = an ACPI wizard by any means - for me it's low-level mage spells at best... In https://github.com/SolidRun/edk2-platforms we have 2 different branches = that SolidRun seems to use: 1. LSDK-19.09-sr 2. master-lx2160a I've been building from the latter branch, but found some significant diffe= rences in the former that I think may be important to merge in. =3D=3D=3D=3D=3D 1. Platform/SolidRun/LX2160aCex7/DeviceTree/fsl-lx2160a-cex= 7.dts and Silicon/NXP/LX2160A/Include/DeviceTreeInclude/fsl-lx2160a.dtsi The former branch includes a number of devices and aliases that are not pre= sent in the latter (e.g. pcs_mdio5) =3D=3D=3D=3D=3D 2. Silicon/NXP/Include/Pcie.h Again, the former branch contains a handful of extra lines, but also forces= unsigned long on PCI_SEG_MMIO64_MAX_DIFF while the latter does not. =3D=3D=3D=3D=3D 3. Silicon/NXP/Library/MmcLib/MmcInterface.c The former branch has a preprocessor conditional IsCardReadOnly. =3D=3D=3D=3D=3D 4. AcpiTables This is where I'm actually out of my depth. The former branch has them unde= r Platform/NXP/LX2160aCex7Pkg/AcpiTables/ while the latter under Silicon/NX= P/LX2160A/AcpiTables/ Start diving in and you start to notice some ugly differences. Just in Plat= form.h, we can see right at the top that the former branch is defined for t= he CEX7 platform while the latter is for the Reference Dev Board (RDB) plat= form. You can also see some pretty significant differences in the watchdogs= and then PCI and Stream IDs at the bottom. AcpiTables.inf and LX2170aCex7.inf share a BASE_NAME and FILE_GUID, but dif= ferent sources. =3D=3D=3D=3D=3D I can easily bodge in the first few itmes above, but I'd really appreciate = a second set of eyes from somebody with more ACPI experience as to whether = or not we need to merge anything from the LSDK-19.09-sr into master-lx2160a= . https://github.com/agrajag9/edk2-platforms/tree/a9-lx2160acex7 From owner-freebsd-arm@freebsd.org Sun May 31 14:54:22 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6D713336CC5 for ; Sun, 31 May 2020 14:54:22 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out1.migadu.com (out1.migadu.com [IPv6:2001:41d0:2:863f::]) (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 49ZhCd1RM2z4DPT for ; Sun, 31 May 2020 14:54:20 +0000 (UTC) (envelope-from greg@unrelenting.technology) Date: Sun, 31 May 2020 14:54:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1590936851; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=gIq5wliJw3FacgYmyX33C+0I4AGDXOAEUOly+0V5cmY=; b=lAQ/WF1Ndejv40pF054uwUvMxELq2X3otEaYC42s5TVZnggEI/O0jMfsvqY0aFP6VWcmOi VtTOc1QBI87r4TEXL6FgpIXKsy44RRIRYCeMlGCMhhOXl2nrTKJfPxqRCjbF7XMVRcFHEW LZ8xMBWvZ5NY9AOPOzI72z6ZA2tgYtQ= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: myfreeweb To: Dan Kotowski CC: freebsd-arm Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X In-Reply-To: References: <37858865a8ebddd3fe1e3a228a19ef62@unrelenting.technology> <7066da0bc417ed047dc27b4741c90e81@unrelenting.technology> <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> Message-ID: <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49ZhCd1RM2z4DPT X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=lAQ/WF1N; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:863f:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.21 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.07)[-1.066]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:863f::]; NEURAL_HAM_LONG(-1.00)[-1.001]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; NEURAL_HAM_SHORT(-0.15)[-0.145]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 14:54:22 -0000 On May 31, 2020 2:31:03 PM UTC, Dan Kotowski wrote: >> I've sent a link to a known firmware build before: >> https://drive=2Egoogle=2Ecom/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvErK/v= iew >> Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe? > >I decided to go back to the UEFI sources and have found some differences = that I think need to be reconciled before moving forward=2E That said, I'm = not an ACPI wizard by any means - for me it's low-level mage spells at best= =2E=2E=2E > >In https://github=2Ecom/SolidRun/edk2-platforms we have 2 different branc= hes that SolidRun seems to use: > >1=2E LSDK-19=2E09-sr >2=2E master-lx2160a > >I've been building from the latter branch, but found some significant dif= ferences in the former that I think may be important to merge in=2E To me it seems like 19=2E09 is just outdated and doesn't have any benefits= =2E Ask the solidrun people to be sure=2E Either way, nothing here would fix the interrupt bug=2E It's *our* bug sin= ce NetBSD works fine :( From owner-freebsd-arm@freebsd.org Sun May 31 15:16:56 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2F741337221 for ; Sun, 31 May 2020 15:16:56 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.70]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49Zhjg37t6z4FVB for ; Sun, 31 May 2020 15:16:55 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from mather.gromit23.net (c-98-244-101-97.hsd1.va.comcast.net [98.244.101.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 07C0D3C1; Sun, 31 May 2020 11:16:48 -0400 (EDT) From: Paul Mather Message-Id: Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\)) Subject: Re: BeagleBone AI Date: Sun, 31 May 2020 11:16:48 -0400 In-Reply-To: Cc: freebsd-arm@freebsd.org To: Sulev-Madis Silber References: <54BFDAE5-67CF-4033-BD38-3F38F7FE70F8@cyclaero.com> X-Mailer: Apple Mail (2.3445.104.14) X-Rspamd-Queue-Id: 49Zhjg37t6z4FVB X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=vt.edu (policy=none); spf=none (mx1.freebsd.org: domain of paul@gromit.dlib.vt.edu has no SPF policy when checking 128.173.49.70) smtp.mailfrom=paul@gromit.dlib.vt.edu X-Spamd-Result: default: False [2.45 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; NEURAL_SPAM_SHORT(0.71)[0.711]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; NEURAL_SPAM_MEDIUM(0.40)[0.402]; RECEIVED_SPAMHAUS_PBL(0.00)[98.244.101.97:received]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.83)[0.833]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[hot.ee]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:1312, ipnet:128.173.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[vt.edu : No valid SPF, No valid DKIM,none] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 15:16:56 -0000 On May 30, 2020, at 12:16 PM, Sulev-Madis Silber = wrote: > worth mentioning anyway, as ideas kept to oneself are useless ideas >=20 >=20 > somehow noone else has replied so far, including ones i consider more > competent on subject >=20 > to me, ti am* soc seems like solid option. unsure if one wants to use > c.o.t.s. board for industrial use, though? i mean as opposed to = designing > own pcb >=20 > when others finally arrive, they might want to correct me, but next > platform to consider (fbsd-support-wise) could be imx6 >=20 > then there are allwinner socs which seem to be like more oriented = towards > consumer mobile devices and rpi-class (media players?) >=20 > but nothing stops one from "abusing" readily available hw, if you = ruggedize > it and take appropriate precautions :) Note that there is an industrial version of the BeagleBone Black: = https://beagleboard.org/arrowbbbi Cheers, Paul. From owner-freebsd-arm@freebsd.org Sun May 31 15:30:39 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 617A033744A for ; Sun, 31 May 2020 15:30:39 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49Zj1V23f3z4GgM for ; Sun, 31 May 2020 15:30:38 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: by mail-wr1-x42e.google.com with SMTP id l11so9049128wru.0 for ; Sun, 31 May 2020 08:30:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=nkVLmJCAKQZsfds1NyXGm7uGP1kB+xDPSpneZz4bK+M=; b=bz9sm3ontWfoy0E9PVaClKbMY35Yj0jUu+M4T8UoNV8xhWpHFjd8ulME+NWXSl+e1u uQdCu1M+C6QLD1qzSwX8xikbI8SO0xT4EE8fMRsf/cI0nrdppWWuoSMEknDn1TW1h/F5 F43SG8oeSyqLLQroTF5v5xDvjrWc3V1MEb1UI2vIWUd/h2P3YFJCksKd4SM/VgszieLk NWWO7kmdbOV3oxsrWb88r7zNX9OCn2j8Yth4LNO/qVf/WqJfNEeZDciezmRW8rgxS6+j VY1bZcYYJC5XV8hz3urzi+sd/A+T5E5cpSiM428cYtaLSYbzfmC4qAP/kKNy04fGC1HC S28g== X-Gm-Message-State: AOAM531ChwE3k/bPViiq9XomIOV6FaJWgdHF7X5z8l4pZUExmtOlmoun zjMZVmS8YGQBaU5DXspfWm4= X-Google-Smtp-Source: ABdhPJwQL76ynIvxaT68AeXs8D+cUBo+adjbLD+HhZ2l6Kguo9hFmPbNlv67TXxQzZhPjNY9OXeUMA== X-Received: by 2002:adf:f68d:: with SMTP id v13mr16684477wrp.291.1590939036727; Sun, 31 May 2020 08:30:36 -0700 (PDT) Received: from [192.168.1.167] ([46.114.105.196]) by smtp.googlemail.com with ESMTPSA id 40sm18285296wrc.15.2020.05.31.08.30.35 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 31 May 2020 08:30:36 -0700 (PDT) From: =?utf-8?Q?Klaus_K=C3=BCchemann?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: rpi4-uefi.dev Re: RaspberryPi 4B 8G model not boot Date: Sun, 31 May 2020 17:30:34 +0200 References: <20200530.130909.120260481726933388.shigeru@os-hackers.jp> <50DC156A-CA39-4809-85B7-02A5180DAB63@yahoo.com> <2DE76C92-8F4B-4658-94E4-FB7C7B7C6135@googlemail.com> <0AD80BEF-AA71-41F0-AD71-DF8516B790D9@yahoo.com> <67808784-29A6-4BC2-9B25-E31DE6DA862A@googlemail.com> <20C49D55-9940-422F-9699-4C56CFCF281B@unrelenting.technology> <83980CE0-276E-4DD9-B035-5ED2B561324B@googlemail.com> <53680CD3-4FE9-42C9-A534-416A71263A08@unrelenting.technology> To: Robert Crowston , freebsd-arm@freebsd.org In-Reply-To: Message-Id: <5539A25D-AE42-498A-8349-9E7E32051BC8@googlemail.com> X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49Zj1V23f3z4GgM X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.54 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[googlemail.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; FREEMAIL_TO(0.00)[protonmail.com,freebsd.org]; RECEIVED_SPAMHAUS_PBL(0.00)[46.114.105.196:received]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[googlemail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.07)[-1.067]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.02)[0.019]; NEURAL_HAM_LONG(-0.99)[-0.994]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::42e:from]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 15:30:39 -0000 > Am 31.05.2020 um 16:14 schrieb Robert Crowston = : >=20 >> pcie isn`t exposed ( to the OS) in RPI4UEFI-dev , that=E2=80=99s what = @AndrejWarkentin told us =E2=80=A6 >=20 > Something about this doesn't make sense, because there is a PCI-E = driver for OpenBSD that was written specifically for the Rpi4 UEFI. >=20 >=20 OpenBSD`s pcie-driver for RPI4UEFI-dev targets DeviceTree (not ACPI),=20 Meanwhile there are 3 boot - options in their v 1.3 : DeviceTree (only), ACPI (only) & ACPi & DeviceTree (both) From owner-freebsd-arm@freebsd.org Sun May 31 16:00:30 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C7B86338047 for ; Sun, 31 May 2020 16:00:30 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49Zjgx5TsGz4K02 for ; Sun, 31 May 2020 16:00:29 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Sun, 31 May 2020 16:00:22 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1590940826; bh=b3KD+2nZnf3fOCRTArzn1SlOrsiKTlEJ8CkvQ384CKY=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=EiZhYwuTYWAAt3bw/pUfAQLH18Iadp4RjAd3l9bV7SoFI5sxALfhBtfbCjCTDrk5+ rEa8CL9HtjAlkjGZ8hGPzFIagOEg6zYZhDYRO5Si960Uc+LNSMWqrDQoPjkiBLkFD8 wAfjPrywI1EenbYHWUpAwTuLFOOFVbGBLyYWVH3E= To: myfreeweb From: Dan Kotowski Cc: freebsd-arm Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> References: <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49Zjgx5TsGz4K02 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=EiZhYwuT; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.22 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-3.81 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; SH_EMAIL_DBL_DONT_QUERY_IPS(0.00)[0.0.0.1:email]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; NEURAL_HAM_LONG(-0.96)[-0.962]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_MEDIUM(-1.06)[-1.061]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.22:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; RCPT_COUNT_TWO(0.00)[2]; DBL_PROHIBIT(0.00)[0.0.0.1:email]; NEURAL_HAM_SHORT(-0.69)[-0.690]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.22:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 16:00:30 -0000 > > > I've sent a link to a known firmware build before: > > > https://drive.google.com/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvErK/vie= w > > > Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe? > > > > I decided to go back to the UEFI sources and have found some difference= s that I think need to be reconciled before moving forward. That said, I'm = not an ACPI wizard by any means - for me it's low-level mage spells at best= ... > > In https://github.com/SolidRun/edk2-platforms we have 2 different branc= hes that SolidRun seems to use: > > > > 1. LSDK-19.09-sr > > 2. master-lx2160a > > > > I've been building from the latter branch, but found some significant d= ifferences in the former that I think may be important to merge in. > > To me it seems like 19.09 is just outdated and doesn't have any benefits.= Ask the solidrun people to be sure. > > Either way, nothing here would fix the interrupt bug. It's our bug since = NetBSD works fine :( Any thoughts on the "Poll mode" comment below from the dts? We're still not= seeing any of the PHYs in either BSD. ``` &emdio1 { rgmii_phy1: ethernet-phy@1 { /* AR8035 PHY - "compatible" property not strictly needed */ compatible =3D "ethernet-phy-id004d.d072"; reg =3D <0x1>; /* Poll mode - no "interrupts" property defined */ }; }; ``` From owner-freebsd-arm@freebsd.org Sun May 31 16:09:10 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 14F213382D7 for ; Sun, 31 May 2020 16:09:10 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out0.migadu.com (out0.migadu.com [IPv6:2001:41d0:2:267::]) (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 49Zjsw4NQtz4KcW for ; Sun, 31 May 2020 16:09:08 +0000 (UTC) (envelope-from greg@unrelenting.technology) Date: Sun, 31 May 2020 16:08:59 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1590941340; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=JsqJumabboaaU5r/zBnnExRxT/o4leWHYUiNwAuD0X8=; b=K9/iXzIQrejEM+kqQofi8dwu8u6KWO7fTfz9XZ0bvDpOrl5wH0x933un2rWMC+s/CfB2Gj RxIZamfsb5rrV/OSFae7v4W4TVoUNpzfQxzw4KioSIsQ+aXH2VzRqFMzc+0AQrg79LxMeo O0QHrUkVDtd2ws03wk9ES7tYsOPUxGU= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: myfreeweb To: Dan Kotowski CC: freebsd-arm Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X In-Reply-To: References: <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> Message-ID: <4E21DEB1-0C86-41CD-BE89-FBF2EF45443C@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49Zjsw4NQtz4KcW X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=K9/iXzIQ; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:267:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.46 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.07)[-1.074]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; FROM_HAS_DN(0.00)[]; SH_EMAIL_DBL_DONT_QUERY_IPS(0.00)[0.0.0.1:email]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:267::]; NEURAL_HAM_LONG(-1.00)[-0.998]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; DBL_PROHIBIT(0.00)[0.0.0.1:email]; NEURAL_HAM_SHORT(-0.39)[-0.389]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 16:09:10 -0000 On May 31, 2020 4:00:22 PM UTC, Dan Kotowski wrote: >> > > I've sent a link to a known firmware build before: >> > > https://drive=2Egoogle=2Ecom/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvE= rK/view >> > > Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe? >> > >> > I decided to go back to the UEFI sources and have found some differen= ces that I think need to be reconciled before moving forward=2E That said, = I'm not an ACPI wizard by any means - for me it's low-level mage spells at = best=2E=2E=2E >> > In https://github=2Ecom/SolidRun/edk2-platforms we have 2 different b= ranches that SolidRun seems to use: >> > >> > 1=2E LSDK-19=2E09-sr >> > 2=2E master-lx2160a >> > >> > I've been building from the latter branch, but found some significant= differences in the former that I think may be important to merge in=2E >> >> To me it seems like 19=2E09 is just outdated and doesn't have any benef= its=2E Ask the solidrun people to be sure=2E >> >> Either way, nothing here would fix the interrupt bug=2E It's our bug si= nce NetBSD works fine :( > >Any thoughts on the "Poll mode" comment below from the dts? We're still n= ot seeing any of the PHYs in either BSD=2E > >``` >&emdio1 { > rgmii_phy1: ethernet-phy@1 { > /* AR8035 PHY - "compatible" property not strictly needed */ > compatible =3D "ethernet-phy-id004d=2Ed072"; > reg =3D <0x1>; > /* Poll mode - no "interrupts" property defined */ > }; >}; >``` Why are you looking at Ethernet stuff? We do not have a driver for NXP's NIC in any BSD=2E (I do wonder if the Semihalf work on the Layerscape family would eventuall= y include Ethernet=2E=2E) From owner-freebsd-arm@freebsd.org Sun May 31 16:15:49 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C6520338912 for ; Sun, 31 May 2020 16:15:49 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from 44-233-67-66-mail.ore.mailhop.org (44-233-67-66-mail.ore.mailhop.org [44.233.67.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49Zk1d2QZRz4LMB for ; Sun, 31 May 2020 16:15:49 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1590941741; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=L6R022icPxyub6x3fzzs6VPc7SBPrBDQWuqJt6rN2UwnGYlL1/2JN872mj6NZXhebTT/sUEkAJDlq oqopjNpy0o+p4biMkN/VHk/4B03LuIvKDN0xE6AJww8fMD419HxhpvQQze90O1kjL90nFy8K9GrAG1 XKRBBp9k52yYWS5o78YUTf3wDNjYtpWjIW/Pk6CVEB548ySH6XIbTlFUm/5Qe7H7ss/QaMX03i4dqH bcB0MFPZfygMjSApK6JRo3GZfY+6SM8WFZGNKzrLwaH17ksVpwxcirsUo8jSrllyl4RPJKjTVn8GqE FzG4S0XpkRMvrxlidEob6o2+rEuPU5w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=vCQykd97ZHfLPGjVLxegk/JegcbXEj4zfedDni/FCbo=; b=hUJxLPNsy6rdAsXGmCvdK6ZS7l1FwJzk3c6r5m7gwR1orSHLLzg3K0rNb9OI9iGvkpWzG2f6DzP+C f59EXx9HdkVf0kyeTZMKkO3Ib+GjgqwIQxzcuA2jHvPIGbfBlAVRDUSFLKgMUiglBjJ964Vu4N/Q5C MvM/DtLWgda+P1vSvbx/qaPmGjy3kFkq22OZM1xV1C7fYUsPeVC7ghd5OIfUQ17sW/TUAEwc9hyh1V hEs9wgHRSu2u6lqEj6ujIZHC7IRr0OqsO6o31OQXHExABRmslbH/sfGZjclypHW3PR0nbIHFwl+ozy AQbRV6EsI5pikmeLQ2s5skzKmYsOPVQ== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=vCQykd97ZHfLPGjVLxegk/JegcbXEj4zfedDni/FCbo=; b=KgifdfZ2FiVBZGIvN4CrWhu6IoVfLsioCbFra073x4q7IegFScm8KaH0ZDbQ7m9lyVK5FAMoSRWsP qQIco97mDEL+2nj56SP1EsBwn1yIMbpUeT7zumI5T0qTmTL5ntbJnsUYkoD0wz1Wv+l+/t/g3n82gc hNhQfpDWKOyJzW9Cc6VL9vfmBcQ02Zre0HZV2++zZ9jmGJXTAxA96tkfyT/R3ixcLqJQOLpOnizlaS pXpb3mTjadnPW4kAfMQDTDvY8MaGN+tGjyuCyR0ltaxqrf8l39AMZzOJQdlrTmI87OMcS8b6rCzjKi W6QHbbZwqKSbGacPUTkL3/aW7cP5ZnQ== X-MHO-RoutePath: aGlwcGll X-MHO-User: f6e8c87b-a359-11ea-b10c-b5956a7dd1a1 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (c-67-177-211-60.hsd1.co.comcast.net [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id f6e8c87b-a359-11ea-b10c-b5956a7dd1a1; Sun, 31 May 2020 16:15:40 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id 04VGFb3V056953; Sun, 31 May 2020 10:15:37 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <7e3d0d24188a05415252429bf9d7a9bb93040ea0.camel@freebsd.org> Subject: Re: code generation From: Ian Lepore To: mlist@nlned.nl, freebsd-arm@freebsd.org Date: Sun, 31 May 2020 10:15:37 -0600 In-Reply-To: <7aed18ab40ff22810b64bbb77b481c78.squirrel@www.nlned.nl> References: <7aed18ab40ff22810b64bbb77b481c78.squirrel@www.nlned.nl> Content-Type: text/plain; charset="ASCII" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49Zk1d2QZRz4LMB X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:16509, ipnet:44.224.0.0/11, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 16:15:49 -0000 On Sat, 2020-05-30 at 23:52 +0200, Jack Raats wrote: > Hi, > > Can anyone explain why a simple hello_world.c compiles on a AMD64 > machine > to +/- 21000 bytes while on a raspberry pi 3 +/- 206000 bytes (10 > times > more) > > I use FreeBSD 12.1 stable on RPi3 and cc -o hello hello.c to compile. > > Gr., > Jack > > I recall some discussion recently about sections of executable files in arm binaries now being aligned to a much larger page size than the old 4K alignment. When you have a mix of readonly and readwrite data, they have to go into separate sections/pages so that proper read/write permission bits can be set on the pages containing the data. So all in all, this is probably lots and lots of zero-padding in the files that didn't used to be there. It's onerous only in that it makes a large collection of small programs (e.g., /usr/bin) take a lot more disk space. -- Ian From owner-freebsd-arm@freebsd.org Sun May 31 17:04:28 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 66A443392BC for ; Sun, 31 May 2020 17:04:28 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch [185.70.40.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49Zl5l2sfBz4PMl for ; Sun, 31 May 2020 17:04:27 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Sun, 31 May 2020 17:04:16 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1590944664; bh=fS8DwIWGDgD+xuoICbaYXWSRemXLcI+1qpM6Px9uegE=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=RRLNz9xtiKzvqNHxrJYazSJr2BvrttePlCTOL4W/2UXA9LISyuFu0P2D0IcbDqdpC LXMrZGIm1M4oEZjpCIhbl1AneWsHVKBAkfLX3I7cgaRMH+4W2tFSjrtttJOaYvqFo0 3316zRv7UprsRpXE0nzZLz2HlMznxsDtK2cKk5hg= To: myfreeweb From: Dan Kotowski Cc: freebsd-arm Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: <4E21DEB1-0C86-41CD-BE89-FBF2EF45443C@unrelenting.technology> References: <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <4E21DEB1-0C86-41CD-BE89-FBF2EF45443C@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49Zl5l2sfBz4PMl X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=RRLNz9xt; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.131 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-3.93 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; NEURAL_HAM_LONG(-0.97)[-0.968]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_MEDIUM(-1.05)[-1.054]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_SHORT(-0.81)[-0.808]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[185.70.40.131:from]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.131:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 17:04:28 -0000 > Why are you looking at Ethernet stuff? > We do not have a driver for NXP's NIC in any BSD. Just comparing all the different versions of this dts I'm finding in SR's v= arious repos, curious as to why we're not even seeing the eth or sfp device= s show up in dmesg at all, even if there's no driver support. From owner-freebsd-arm@freebsd.org Sun May 31 17:04:43 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1102B339151 for ; Sun, 31 May 2020 17:04:43 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from 44-233-67-66-mail.ore.mailhop.org (44-233-67-66-mail.ore.mailhop.org [44.233.67.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49Zl625kLYz4P8f for ; Sun, 31 May 2020 17:04:42 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1590944681; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=YqqoSx7y0pR6uc9+iFohtW0w7Ei9tzPWfU0BsMcipuITWn4MhZzJeo9MCbbv2PLIyE6fYYZpwLQpw Gw87vsFtFLtohJjDm6c557ZK5+u+52WQBt1pZF6TLscSmcyeO0ig0s8hCxZq+APAGFPWqm56yzKB7j lT1xiUFgCtfsx3jT/VekP/mFPVrzDFUn4tDh4wzzq4TveGt3cSvqv80Dv1XGK9YPs+OiTh26p2oLlf a/24wsVuLs4EAnb4N0GANc08bK43VEkWy/4BaOQNuHigQLsSOryUwnIftFHTuy+mvL7y+egh9Wz1Dw cFeq385pwph/HzaG50j+GU7ssrOOfNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=w0Fd006MIs6YJOqg96XBH/xLue59xktFyB+mtcLpF+g=; b=gdR5k3IzI8/nFQWhCbrSqx3zBi4qooS8g/yWugNFyJTb8RjX8sRx62d40v+j21za1sM7hHq647qAT vrnmNUGJPwbY8ko2asIckgBFPfYjAC1TUVbb2V8Xq8Zq/IFsuSSAwC/y6JU3itc4aIrVOsWG91aIEa YovxypTrG84PNlsLxMeGrdCKfqtkMvbouzYtaCZMM9RVGEXmSesCBaOMZAzvD5ILA69JFdEztPsMr0 Z6+DNkxggOaLYNHDNZd/dO6YWD4I9gJpAWtciYqRPooLugwIIzij8TWkXtQTwSFkTZ/U5hOUVR9ns+ ajmT3bj+MCode9vmP7oHDvDJHIIO8cA== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=w0Fd006MIs6YJOqg96XBH/xLue59xktFyB+mtcLpF+g=; b=Jyk6Lo2rzFJeSYGof+4EvDHzj0tw49BKp46bqc2fVKuMNf3aQfrVGdU3Xk99rloC8UUdgwragY1by CGYQ7zkCd1H53W5kicqpPPzGLObiTquXg1LPkqY6tk6H92UjXpYe1Xj9Dc4dWwp7ElkIH8lDQLXHR5 rulXGSqDwDgixGIa6RaxKYfeCEkqkcMPWeFuIZUxynrt3juIQ37NKvP5u7woMB0VBQWqxj985slsiA Wv68aeNuZdM/Tjlpb89Iudup41DZzGZLWkYE/5j7iJ4kFYA3VYP/EY2WB8Z1B2zvyQuNBqDFlmQla7 vH0aCEQhtP2Vu2WL+SYdBVCrl9Gkm2A== X-MHO-RoutePath: aGlwcGll X-MHO-User: cfae2756-a360-11ea-b10c-b5956a7dd1a1 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (c-67-177-211-60.hsd1.co.comcast.net [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id cfae2756-a360-11ea-b10c-b5956a7dd1a1; Sun, 31 May 2020 17:04:39 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id 04VH4cwO057101; Sun, 31 May 2020 11:04:38 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <845302190a78fdc46fac0f34326daad4496c7227.camel@freebsd.org> Subject: Re: BeagleBone AI From: Ian Lepore To: "Dr. Rolf Jansen" , freebsd-arm@freebsd.org Date: Sun, 31 May 2020 11:04:37 -0600 In-Reply-To: References: Content-Type: text/plain; charset="iso-8859-7" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 49Zl625kLYz4P8f X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:16509, ipnet:44.224.0.0/11, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 17:04:43 -0000 On Fri, 2020-05-29 at 23:21 -0300, Dr. Rolf Jansen wrote: > We are starting a new project of industrial device controllers. We > want to utilize ARM-SBCs as unit controllers (and here a unit is one > industrial device), and we need to attach at least 24 ADCs, 8 DACs > and 16 DIOs to each unit controller (UC). Many unit controllers > (eventually tenths to hundreds) would then communicate by a custom > protocol over ethernet with a command and control server. The UCs and > the C&C server would be operated by FreeBSD. Direct interoperability > of the UCs with 3rd party IT systems is not a concern, integration > needs to be done via the C&C server. > > Since the sample/update rate requirements are quite low, we are going > the I²C path, and initial testing has been done using the BeagleBone > Black. It got 2 separate I²C 400 kbit/s busses which helps already, > avoiding I²C address conflicts. Yet, the 8 port I²C switch TCA9548A > is working very well, and we are now sure to be able to attach enough > ADCs, DACs and DIOs to each unit controller. > > Although the initial viability tests were done with a BeagleBone > Black running FreeBSD 13-CURRENT, we could start with another more > modern SBC. > > First Question: > > What modern SBC with more than 1 I²C bus and which can run FreeBSD > 13++ would you suggest? > > > Now recently, I found the BeagleBone AI site > https://beagleboard.org/ai/ . This one > got also 2 I²C busses, and physically, with respect to a housing, it > could be a 1:1 replacement for a BBB. It seems, this one is still too > new for FreeBSD. I am very fond of the BB concept - for me it is much > more appealing for industrial embedded applications than for example > any RPI. However, the BBB came to age, and I would start a new > project with it only, if there would be a reasonable chance for an > upgrade path. > > Two more Questions: > > Is it reasonable to assume that FreeBSD would run on a BBAI in the > future, let¢s say in 2 to 3 years? > > Perhaps I could help porting FreeBSD to a BBAI. What would be the > general steps? > > > Many thanks in advance for any suggestions, advices and > clarifications. > > Best regards > > Rolf > The only problem with the Beaglebone is that the TI linux developers are continually tinkering with their drivers and DTS source, and they seemingly don't care about the devicetree rules for maintaining compatibility, so freebsd tends to break on BB boards every time we import new DTS sources. If you want to stick with armv7/32-bit stuff, I would say your best bet for long term freebsd support would be Allwinner or imx6. I keep hearing mumbling about freebsd throwing all 32-bit support overboard in a future release. I have no idea how serious any of that mumbling is, but if there's any truth to it at all, then switching to one of the low-cost well-supported arm64 boards, such as pine64, might be a better option. -- Ian From owner-freebsd-arm@freebsd.org Sun May 31 17:08:46 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 95E0A3396C1 for ; Sun, 31 May 2020 17:08:46 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2k.ore.mailhop.org (outbound2k.ore.mailhop.org [54.148.219.64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49ZlBk0vQdz4PST for ; Sun, 31 May 2020 17:08:45 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1590944924; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=tOK1ydOl43i5L5Eb2evxWM4W52ItAlibJyz8mix+JGX1bAgAiMIyssiubBsJmM1KchwuzwI0fO8zC rksY9RKYbYBZGHuKRfIQUSxMkFwtK4ir6JtdsY2x2h3o4F1WVHt61OUx4seOSEd5TPNK1b9O496S54 mmFPseesCdtnlB8hsJ4U6EQZEqTlzhSyE25yEM1BPuh+2/FHklm7v6vnHEvgezabiasP98aZv0W7kJ 2muVXjzYKCDCWgUnIcYYj0nQw9A/ZyTTCJ1s746TRuzp6ADXXtexS4pXCAWfRh8awftYwTQuTBilJZ IMBNxzLxE4rz74WvQn7UY7V6YX31rrw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=1ZiSFFZVNcFJkIFy005nupRXxd93irQYCVCmbdHrkYY=; b=WRXl01Ay9/grA1whaP3NdRPRQXPMbGsACT89ElzFEtf0aYQcbZvgO2IW3tvzP2oTyJXzEgCKHeNwK C6z0Qzno+fU2YCFlGnbEJxKrregrnrzSSj8jA0qM8wErCPRQCPjPTJAOskvGRm0BH3vkLLOxc8eTVr aTfd/TuM8hnI7yVmpfDsPjuKomIdVYXdLGA+kUofMVH7nIH8vCtxbCtK12Fp4iA1Jpn/ImGQ2gGOiS /Ef4PHDP4rd76Zryuk8oCes5/8aeMUYGr7W0maHK4ts8WzZ5Y5s+nQfXspxZew7pyAi4nlqXPdpq2I D7Zb3syfgi5gnGK2X95ep7nBJ6j00Cw== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=1ZiSFFZVNcFJkIFy005nupRXxd93irQYCVCmbdHrkYY=; b=LABFqw8ST5XmKmJzz87PDojhUg6jf6oJw58nkD9uFscx7bmTAcv0rPFkyYlbv2BqqwIBkdYtDqQf+ dyhvEcu6oCif2Q8a+OLJbN+M4HOcw4itp6xfLcgzxcvb4h4FW0oMO++gLC5l81DCp72JfWdX0btY36 lx5Va6pXeKk0FjcnX5njgKthTomB9RGy884b9W2N/H3xtkQ2ZN/FXWzSC/qtJW3MZ2XWh2cy4meFlv PZ+4USSFx7aeG9XVDBpLTq1pppl96RfKe5Q05c0XfM7+iFsCP7vL4yOTAG5E5v9CtvwU5VaTnZi3O5 U3Lvv8QO6MP1g9hZlNnVqEM53WfXwGA== X-MHO-RoutePath: aGlwcGll X-MHO-User: 6072ebba-a361-11ea-a067-6d02e42e573a X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (c-67-177-211-60.hsd1.co.comcast.net [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id 6072ebba-a361-11ea-a067-6d02e42e573a; Sun, 31 May 2020 17:08:43 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id 04VH8fe3057109; Sun, 31 May 2020 11:08:41 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <34ea730c1628556ccb0f234c24d8c3379d7a6402.camel@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X From: Ian Lepore To: Dan Kotowski , myfreeweb Cc: freebsd-arm Date: Sun, 31 May 2020 11:08:41 -0600 In-Reply-To: References: <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <4E21DEB1-0C86-41CD-BE89-FBF2EF45443C@unrelenting.technology> Content-Type: text/plain; charset="ASCII" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49ZlBk0vQdz4PST X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 17:08:46 -0000 On Sun, 2020-05-31 at 17:04 +0000, Dan Kotowski wrote: > > Why are you looking at Ethernet stuff? > > We do not have a driver for NXP's NIC in any BSD. > > Just comparing all the different versions of this dts I'm finding in > SR's various repos, curious as to why we're not even seeing the eth > or sfp devices show up in dmesg at all, even if there's no driver > support. > dmesg lists drivers that attach. If there are no drivers, there will be no messages for that hardware (same as there are no messages for CAN bus and other things likely to be on that board which have no driver). -- Ian From owner-freebsd-arm@freebsd.org Sun May 31 17:11:45 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 641AE339A08 for ; Sun, 31 May 2020 17:11:45 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2k.ore.mailhop.org (outbound2k.ore.mailhop.org [54.148.219.64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49ZlG9167Zz4Pj2 for ; Sun, 31 May 2020 17:11:45 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1590945104; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=oKes97IjduQmAE2rWkNCE7jGuIFVuHFf3NQp2uwETvZKrA/k9MbCwXSqNXAZ/+7zihhump9Y9yAZa VQmcaOgc8BA3vUn7OrMG70SaYr9k17RNb99OyNilruqXzhfWT58ejCAdkLQ9kj8b/LLoquBVfOwXd5 M4EDtJWUOfr3gpr5zfiFRDQaSgM+7EgiHjUjl4MmapHUuymSdxcEONzgNjJP6SG7w+yYNA9IIWAcJY qkNFHZWH5uiZaRzwOB3cY+W70VLLR1fPu2fATfzOvmq3pV/XfapEYZdzxdbEdwY8JzRtiia32hc5+w Un6WuHtFqmQE795MuCcZlvUhw/7Jewg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=3a3HWJ2uh9MCjbdLHsHTpwOwqwpztufijsVFiOQLlOA=; b=S3sL7drk/8oIBChmPKbHlTInq2zKpkHAPtghpPjDaAYk+WBPqzkB4AmO9tBQSEjUbii0BoUQKgxEy r9N8mkr2gn1aY5FrhHYbk+85QTmchFLR4xggwpufBzw2OUqfq8uEC4LDybcPQ3QlmttuZnYIjWvGlh g2YAnUtEb1raeJ5QmYkSm4iaQBmElaWBhgpFfPrQdZSZsrNVunJJRM1i/JkvJA00V5rjFO8jEExQCS TK1Ae5ibo3GNXtb5ghWRcIzNcYazpoDpr/QxfRHYXtln5GNGxtV8BFnCsb2Fm5rcxvOjXAOMkklvAy zynvsHzsFh3mKqZX6dWiXUbL4fncxjQ== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=3a3HWJ2uh9MCjbdLHsHTpwOwqwpztufijsVFiOQLlOA=; b=DRq4kR6sSpW6EjxrQ5S9yE8Pz6RwuOaUhN2pUA10xPDoRyZ1Lho3P+yoZjfLHQ9OARa77BdiXusIx QSCk5stT1rAcq/Rz8XjXRSRZuivtotkllZtynhqQAqDZL8QsqWYrZ4j4sgLeeikr7I3eniVjS01F5j zeWw+q9aWgtAEuCQLUwfpx+mJyipBMBL+aIsVjEbeWk0tRogKlBQ7enYboWxTaiBHVMQudJOXe5Un0 L61CcXzimde0B2WaROR5JCIeM8Pi5zKB55oeQZxqAagRM7iac6F8lPll/3O3yKbkKQWXVdx/LdhRg5 iULkCqZpoIBKIcJDE/EdWu8xvFgnT3A== X-MHO-RoutePath: aGlwcGll X-MHO-User: cbae6e3d-a361-11ea-a067-6d02e42e573a X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (c-67-177-211-60.hsd1.co.comcast.net [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id cbae6e3d-a361-11ea-a067-6d02e42e573a; Sun, 31 May 2020 17:11:42 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id 04VHBesn057135; Sun, 31 May 2020 11:11:41 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <966c33ea1924c2cfab5d9e295a9239d134e03f8a.camel@freebsd.org> Subject: Re: BeagleBone AI From: Ian Lepore To: "Dr. Rolf Jansen" , freebsd-arm@freebsd.org Date: Sun, 31 May 2020 11:11:40 -0600 In-Reply-To: References: Content-Type: text/plain; charset="iso-8859-7" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 49ZlG9167Zz4Pj2 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 17:11:45 -0000 On Fri, 2020-05-29 at 23:21 -0300, Dr. Rolf Jansen wrote: > We are starting a new project of industrial device controllers. We > want to utilize ARM-SBCs as unit controllers (and here a unit is one > industrial device), and we need to attach at least 24 ADCs, 8 DACs > and 16 DIOs to each unit controller (UC). Many unit controllers > (eventually tenths to hundreds) would then communicate by a custom > protocol over ethernet with a command and control server. The UCs and > the C&C server would be operated by FreeBSD. Direct interoperability > of the UCs with 3rd party IT systems is not a concern, integration > needs to be done via the C&C server. > > Since the sample/update rate requirements are quite low, we are going > the I²C path, and initial testing has been done using the BeagleBone > Black. It got 2 separate I²C 400 kbit/s busses which helps already, > avoiding I²C address conflicts. Yet, the 8 port I²C switch TCA9548A > is working very well, and we are now sure to be able to attach enough > ADCs, DACs and DIOs to each unit controller. > > Although the initial viability tests were done with a BeagleBone > Black running FreeBSD 13-CURRENT, we could start with another more > modern SBC. > > First Question: > > What modern SBC with more than 1 I²C bus and which can run FreeBSD > 13++ would you suggest? > > > Now recently, I found the BeagleBone AI site > https://beagleboard.org/ai/ . This one > got also 2 I²C busses, and physically, with respect to a housing, it > could be a 1:1 replacement for a BBB. It seems, this one is still too > new for FreeBSD. I am very fond of the BB concept - for me it is much > more appealing for industrial embedded applications than for example > any RPI. However, the BBB came to age, and I would start a new > project with it only, if there would be a reasonable chance for an > upgrade path. > > Two more Questions: > > Is it reasonable to assume that FreeBSD would run on a BBAI in the > future, let¢s say in 2 to 3 years? > > Perhaps I could help porting FreeBSD to a BBAI. What would be the > general steps? > > > Many thanks in advance for any suggestions, advices and > clarifications. > > Best regards > > Rolf > BTW, if you need drivers for any new i2c devices just let me know and I'll see what I can do. Also, in my experience you can often get away with running an i2c bus faster than 400khz if you need more bandwidth. I've never seen any modern chip fail to work at 800khz, and most seem to work fine up to about 1mhz; above that they become pretty unreliable. -- Ian From owner-freebsd-arm@freebsd.org Sun May 31 18:51:02 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 91C4533E005 for ; Sun, 31 May 2020 18:51:02 +0000 (UTC) (envelope-from freebsd@cyclaero.com) Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [81.169.146.216]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49ZnSh62M0z3SVV for ; Sun, 31 May 2020 18:51:00 +0000 (UTC) (envelope-from freebsd@cyclaero.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1590951058; s=strato-dkim-0002; d=cyclaero.com; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=Bcb8IacUIgri8mUp4sOdAFxnxRnZd/4fpx0tusEDyUA=; b=AEe2/8duhcBbhVEjCvPq+DmC/FcXDslWgeWNovjH9YqWkgfuDrlWGioC4NprmmQrM5 g8h0g9Fa3A88apyntKRPiF2NLlsuS7VINgFXvofbFyfzU7/dVDtH+V8BSIJL+3dpdrH+ AOgVSoqQuickkoXkfFItN3OFSKqAiV06QEdRC/YouUwO+qiiElekAoqULnhQGXMHCQyI nliNxvGIni2bL/HvxVhFVP/eh8leRsgVl0LFusQQnn0Sf9Lx+Fy3eeh/6s7JIR+6nOZX +EgbgLrgz9voHnN4l/qkxaINNkIAvcIzOb+7R4M7u3Fm/YBsFqqmfi3M7wbZDykfFs5D p6jA== X-RZG-AUTH: ":O2kGeEG7b/pS1F2rRHW2isrKl4DV03XBEi+I6ZuztdvN9wS3wFGySS4Lw+ldTBio0dVbInGjc9PbZFAm0A==" X-RZG-CLASS-ID: mo00 Received: from mail.obsigna.com by smtp.strato.de (RZmta 46.9.0 DYNA|AUTH) with ESMTPSA id I06cf5w4VIopAmc (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Sun, 31 May 2020 20:50:51 +0200 (CEST) Received: from rolf-mini.obsigna.com (rolf-mini.obsigna.com [192.168.222.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.obsigna.com (Postfix) with ESMTPSA id 2F5871350F91D; Sun, 31 May 2020 15:50:47 -0300 (-03) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: BeagleBone AI From: "Dr. Rolf Jansen" In-Reply-To: <1475482977.403029.1590862144455@mail.yahoo.com> Date: Sun, 31 May 2020 15:50:45 -0300 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <1475482977.403029.1590862144455@mail.yahoo.com> To: Oskar Holmlund X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 49ZnSh62M0z3SVV X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cyclaero.com header.s=strato-dkim-0002 header.b=AEe2/8du; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@cyclaero.com designates 81.169.146.216 as permitted sender) smtp.mailfrom=freebsd@cyclaero.com X-Spamd-Result: default: False [-1.41 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[cyclaero.com:s=strato-dkim-0002]; NEURAL_HAM_MEDIUM(-1.06)[-1.061]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:81.169.146.128/25]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cyclaero.com]; NEURAL_HAM_LONG(-0.96)[-0.957]; RWL_MAILSPIKE_GOOD(0.00)[81.169.146.216:from]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[cyclaero.com:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_NAME_HAS_TITLE(1.00)[dr]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; NEURAL_HAM_SHORT(-0.29)[-0.288]; ASN(0.00)[asn:6724, ipnet:81.169.144.0/22, country:DE]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[81.169.146.216:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 18:51:02 -0000 > Am 30.05.2020 um 15:09 schrieb Oskar Holmlund = : >=20 > Hello Rolf, >=20 >> Den l=C3=B6rdag 30 maj 2020 04:22:12 CEST, Dr. Rolf Jansen = skrev:=20 >>=20 >> ... >>=20 >> First Question: >>=20 >> What modern SBC with more than 1 I=C2=B2C bus and which can run = FreeBSD 13++ would you suggest? >>=20 >> ... >>=20 >> Two more Questions: >>=20 >> Is it reasonable to assume that FreeBSD would run on a BBAI in the = future, let=E2=80=99s say in 2 to 3 years? >>=20 >> Perhaps I could help porting FreeBSD to a BBAI. What would be the = general steps? >>=20 >>=20 >> Many thanks in advance for any suggestions, advices and = clarifications. >>=20 >> Best regards >>=20 >> Rolf >=20 > I'm also into industrial embedded systems, we currently use am3358 and = in our roadmap we have a plan to use am57xx in the future. We build our = own custom hardware and dont use Beaglebone* in the products. >=20 > First question; have a quick look at the hardware documentation from = the SoCs vendor listed insys/arm and sys/arm64. If you like the = structure of the documentation talk to the vendor and see if you can get = the product life time your project needs, do the support organisation = give some kind of design review of schematics...do the support = organisation "know" something about the BSDs? :) > I think its good if you can fix problems in the future on your own due = to the lack of manpower in freebsd@arm as both Ian Lepore and Emmanuel = Vadot has pointed out several times.=20 >=20 > Steps to get AM57xx SoCs to work: > 1 Print the schematics and parts of the documentation ( = https://www.ti.com/lit/ug/spruhz6l/spruhz6l.pdf ) on paper. > 2 Find marking pens. > 3 Build & boot u-boot - probably easy check out = ports/sysutils/u-boot-* change model/board_config maybe some patches are = needed. > 4 Dive into the devicetree (moving target and not always correct) and = understand the concept. The relationship between different parts of the = system and the documentation, find the registers & bits you need and = issue read/write (maybe some glue are needed aswell).=20 > 5 Write new/rewrite drivers. > 6 goto (4) >=20 > It will probably take a year or two to have stable support for am57xx. = If you have time to work on making freebsd boot on BBAI it will be great = - maybe we can get it done in 6 months ? :) >=20 > I will put up an initial proposal for am335x clock on = reviews.freebsd.org as soon as my account has been approved. Head boots = and i have tested most of the function except PRUs.=20 > I assume am57xx/dra7xx have some new type of clock/dpll but it should = not be too hard to add. Oskar, Thank you very much for your reply. I looked into sys/arm and = sys/arm64, however, I cannot easily figure out the responses of my two = main concerns, namely number of supported I=C2=B2C busses (and its = speed) and what=E2=80=99s the future of the board (next 5 years or so).=20= The ARM board will be build into a rugged housing, together with the = other components. In this respect the beauty of the BeagleBone series = would be, that we may start with the BeagleBone Black and in the future = replace this with the BeagleBone AI without needing to change anything = in the housing, even the I=C2=B2C pins are at the same place, and the = BBAI could even serve as a replacement part for BBB systems which are = already shipped to customers. The mechanical compatibility alone is = quite appealing, isn=E2=80=99t it? I will have a closer look at the Pine boards, though. In the specs I see = only 1 I=C2=B2C bus. John-Mark Gurney told in another message, that = there are lots more. If this turns out to be true, then these would be = worth a serious consideration. Anyway, I take form our discussion, that the BeagleBone AI would be an = option in future, albeit a lot of work needs to be done. Best regards From owner-freebsd-arm@freebsd.org Sun May 31 19:04:52 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 32ACF33E3DC for ; Sun, 31 May 2020 19:04:52 +0000 (UTC) (envelope-from freebsd@cyclaero.com) Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [81.169.146.221]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49Znmf48cYz3TwH; Sun, 31 May 2020 19:04:50 +0000 (UTC) (envelope-from freebsd@cyclaero.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1590951888; s=strato-dkim-0002; d=cyclaero.com; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=ZekruijvXJNOSo0UyOj+wftLovlFnZVInAlqwK8tAz0=; b=M9kiNAlXK8B7SAoQyJGepiFxpnVKJ+7mZa/bj9E4qkSSpx5SjGqYx86B8W36UFQyfg 2PbE2VV80naKfskPTx8cChulDjMcGPzWTA4uzszOGeTWnaqbRazOGma7AdD65uHZL/Vs WBzAsocrMVL7fGXI9a33QbIjIQyoii1WT8K63IVqLnjayURakiZLccx0fksOC37wTvON gJLSu42BAQOr6eg+uo5UrFkU2QlV7hMk0QSB5ggGgf4wVebuqxzrBSAjT9eMYKdRo3Sl Jefl8cCyVter7jdNZErXx26fOubxYW0XGQP3OsqKgx67jQiN/q/YAkas4FDelYFWogY3 jr4Q== X-RZG-AUTH: ":O2kGeEG7b/pS1F2rRHW2isrKl4DV03XBEi+I6ZuztdvN9wS3wFGySS4Lw+ldTBio0dVbInGjc9PbZFAm0A==" X-RZG-CLASS-ID: mo00 Received: from mail.obsigna.com by smtp.strato.de (RZmta 46.9.0 DYNA|AUTH) with ESMTPSA id I06cf5w4VJ4mAnD (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Sun, 31 May 2020 21:04:48 +0200 (CEST) Received: from rolf-mini.obsigna.com (rolf-mini.obsigna.com [192.168.222.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.obsigna.com (Postfix) with ESMTPSA id 101AD1350F91D; Sun, 31 May 2020 16:04:46 -0300 (-03) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: BeagleBone AI From: "Dr. Rolf Jansen" In-Reply-To: <845302190a78fdc46fac0f34326daad4496c7227.camel@freebsd.org> Date: Sun, 31 May 2020 16:04:44 -0300 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <1D278E6E-B9BC-42A7-BC71-9279BE19EFBF@cyclaero.com> References: <845302190a78fdc46fac0f34326daad4496c7227.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 49Znmf48cYz3TwH X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cyclaero.com header.s=strato-dkim-0002 header.b=M9kiNAlX; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@cyclaero.com designates 81.169.146.221 as permitted sender) smtp.mailfrom=freebsd@cyclaero.com X-Spamd-Result: default: False [-1.34 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[cyclaero.com:s=strato-dkim-0002]; NEURAL_HAM_MEDIUM(-1.06)[-1.063]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+ip4:81.169.146.128/25]; DMARC_NA(0.00)[cyclaero.com]; NEURAL_HAM_LONG(-1.01)[-1.006]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[cyclaero.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[81.169.146.221:from]; FROM_NAME_HAS_TITLE(1.00)[dr]; NEURAL_HAM_SHORT(-0.27)[-0.275]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[81.169.146.221:from]; ASN(0.00)[asn:6724, ipnet:81.169.144.0/22, country:DE]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 19:04:52 -0000 > Am 31.05.2020 um 14:04 schrieb Ian Lepore : >=20 > On Fri, 2020-05-29 at 23:21 -0300, Dr. Rolf Jansen wrote: >> ... >>=20 >> First Question: >>=20 >> What modern SBC with more than 1 I=C2=B2C bus and which can run = FreeBSD 13++ would you suggest? >>=20 >> ... >>=20 >> Two more Questions: >>=20 >> Is it reasonable to assume that FreeBSD would run on a BBAI in the = future, let=E2=80=99s say in 2 to 3 years? >>=20 >> Perhaps I could help porting FreeBSD to a BBAI. What would be the = general steps? >>=20 >>=20 >> Many thanks in advance for any suggestions, advices and = clarifications. >>=20 >> Best regards >>=20 >> Rolf >=20 > The only problem with the Beaglebone is that the TI linux developers > are continually tinkering with their drivers and DTS source, and they > seemingly don't care about the devicetree rules for maintaining > compatibility, so freebsd tends to break on BB boards every time we > import new DTS sources. Yes, this is really annoying. For getting the BeagleBone Black working = with 13-CURRENT, I need to replace the DTS at sys/gnu/dts/arm, which is = currently v5.6, with v4.2 (r347365), and then rebuild the kernel. > If you want to stick with armv7/32-bit stuff, I would say your best = bet > for long term freebsd support would be Allwinner or imx6. My concern is not 32 or 64bit. These unit controllers will never ever = run a desktop environment, so it won=E2=80=99t even come close to touch = any 32bit memory limit. That said, 64bit is not exactly needed but would = not harm either. > I keep hearing mumbling about freebsd throwing all 32-bit support > overboard in a future release. I have no idea how serious any of that > mumbling is, but if there's any truth to it at all, then switching to > one of the low-cost well-supported arm64 boards, such as pine64, might > be a better option. Well, if longterm support for 32bit of FreeBSD is questionable, this = would be a huge road block for the BeagleBone AI. I will also respond to = your other message. Best regards Rolf From owner-freebsd-arm@freebsd.org Sun May 31 19:27:23 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9AA8533EDE6 for ; Sun, 31 May 2020 19:27:23 +0000 (UTC) (envelope-from freebsd@cyclaero.com) Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [81.169.146.218]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49ZpGd3YqSz3Vwb for ; Sun, 31 May 2020 19:27:20 +0000 (UTC) (envelope-from freebsd@cyclaero.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1590953239; s=strato-dkim-0002; d=cyclaero.com; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=JYzTuvU86jlOjYT0qlterb3pGXjjiSHhxIJB9YjrYyI=; b=TZXuz92aO+igQlHy9oBryjlQ4obLLh+UNKrKnU/4COpXXUrv6ABitC89uVZSyS8ABJ zwvQ3dTZ4fInqJg22OspyUImHjnpIO74b9dxlVPN6bd03m9rHY+2wXRACH5RPAoLk9ar 2+avdooJexDwM8IZHQEAQiq0VULV3r9NkGB3buhtDyrLEoXg+J9KXRuQT4/MASHNfXcJ e3FGZTjDkkI5/DJeUeYiKaP82z0LKPfVeN/1i6upKvCJNVzgNJ8np15M7WOAI7x6kW2T zPWTveLM3tWzQhoAHPd7k1tg/O47woKL9IikbXs4jHNI2nM6+isqRvp3rioMWcK2tj7F Xd8A== X-RZG-AUTH: ":O2kGeEG7b/pS1F2rRHW2isrKl4DV03XBEi+I6ZuztdvN9wS3wFGySS4Lw+ldTBio0dVbInGjc9PbZFAm0A==" X-RZG-CLASS-ID: mo00 Received: from mail.obsigna.com by smtp.strato.de (RZmta 46.9.0 DYNA|AUTH) with ESMTPSA id I06cf5w4VJRCAoH (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Sun, 31 May 2020 21:27:12 +0200 (CEST) Received: from rolf-mini.obsigna.com (rolf-mini.obsigna.com [192.168.222.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.obsigna.com (Postfix) with ESMTPSA id 291881350F91D; Sun, 31 May 2020 16:27:10 -0300 (-03) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: BeagleBone AI From: "Dr. Rolf Jansen" In-Reply-To: <20200531063124.GY4213@funkthat.com> Date: Sun, 31 May 2020 16:27:08 -0300 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <372086B8-3BD9-48A5-828A-CBA2C11601D9@cyclaero.com> References: <20200531063124.GY4213@funkthat.com> To: John-Mark Gurney X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 49ZpGd3YqSz3Vwb X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cyclaero.com header.s=strato-dkim-0002 header.b=TZXuz92a; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@cyclaero.com designates 81.169.146.218 as permitted sender) smtp.mailfrom=freebsd@cyclaero.com X-Spamd-Result: default: False [-1.08 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[cyclaero.com:s=strato-dkim-0002]; RWL_MAILSPIKE_POSSIBLE(0.00)[81.169.146.218:from]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:81.169.146.128/25]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cyclaero.com]; NEURAL_HAM_LONG(-0.97)[-0.966]; NEURAL_SPAM_SHORT(0.06)[0.061]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[cyclaero.com:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_NAME_HAS_TITLE(1.00)[dr]; NEURAL_HAM_MEDIUM(-1.07)[-1.072]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6724, ipnet:81.169.144.0/22, country:DE]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[81.169.146.218:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 19:27:23 -0000 > Am 31.05.2020 um 03:31 schrieb John-Mark Gurney : >=20 > Dr. Rolf Jansen wrote this message on Fri, May 29, 2020 at 23:21 = -0300: >> What modern SBC with more than 1 I=C2=B2C bus and which can run = FreeBSD 13++ would you suggest? >=20 > I'd look at ARM64 boards. The life will be longer, and the support > from the FreeBSD community will likely receive more attention. >=20 > Many boards have multiple I2C buses... the Pine A64-LTS has a couple > I2C buses, but they are both on ribbon conenctors (TP and CSI)... >=20 > There is also the Zynq-7000 option, though it's an armv7 cpu.. > I recently brought up the Cora Z7 board... With the PL (FPGA), you > can add many more I2C interfaces... We don't have a driver for > Xilinx's AXI I2C yet, but with that, (and a bit of block building w/ > Vivado), you could have 10 or 20 I2C buses... >=20 > Let me know if you'd like more info. I looked into the specs of all Pine boards, but I could not find any = hint about a number of additional I=C2=B2C busses beyond the single one = on the Pi-2 connector. Like I wrote in a message to Ian, if FreeBSD does keep up the 32bit = support, 32bit or 64bit is not a matter of concern for me. If Pine = really got a number of I=C2=B2C busses, then I would like to learn about = this. However, the LTS part of the Pine A64-LTS is no more that much = appealing, since it ends in less than 2 years from now. What about the = Pine Rock64Pro or the Pine H64, do these also offer additional I=C2=B2C = busses? Ideal would be a SBC for which the FreeBSD support would be (almost) = ready to get started now, and this board is either new enough so chances = are that it is available in the next several years (perhaps the Pine = RockPro64) or there is a successor for on outdated but perfectly working = board lurking, for example like BBB -> BBAI. In the latter case the = expectation would be that I could port FreeBSD to it, perhaps with the = help, hints, recommendations, etc. of knowledgable people on the = FreeBSD-ARM list.=20 Thank you very much. Rolf= From owner-freebsd-arm@freebsd.org Sun May 31 19:57:08 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A38CE33F90D for ; Sun, 31 May 2020 19:57:08 +0000 (UTC) (envelope-from freebsd@cyclaero.com) Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [81.169.146.219]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49Zpwz0xsgz3Y2v; Sun, 31 May 2020 19:57:06 +0000 (UTC) (envelope-from freebsd@cyclaero.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1590955024; s=strato-dkim-0002; d=cyclaero.com; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=qXgXJarJqIQXnvZZ/RAJobKbag7mlgZ1IqTNxVootXk=; b=Q4lAufp0Wf0F09QrV24N4/iwpTjkm0++KN5VXQdror6rLI9soJg+IngpnklmCwcbpm fVIs8KMTytxctpfo2D1VNfQtvlli0eS5ggJFXAQ7aNsm9bqheeIt5vKgNj0RV5RqkPkq DccwkXGmPhD3WeYIeka0tdGEtzohPehNecBOqemPE6u0Xv153ACkPGvFz5opkuTctUPt Gw3vJvFzuVcqvgnNqCew2SSt7CDVou2yQGDhXdBIL3dgwHxlEhchG94Y0wU3WlkLGmpD v8a2mKowdsq9S0hfy+F2VL7P7sZZxNPSo39jwOUIB+zBJ0EDF4cG/9bDEvHpqhg1QSwe pdGw== X-RZG-AUTH: ":O2kGeEG7b/pS1F2rRHW2isrKl4DV03XBEi+I6ZuztdvN9wS3wFGySS4Lw+ldTBio0dVbInGjc9PbZFAm0A==" X-RZG-CLASS-ID: mo00 Received: from mail.obsigna.com by smtp.strato.de (RZmta 46.9.0 DYNA|AUTH) with ESMTPSA id I06cf5w4VJv3Apl (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Sun, 31 May 2020 21:57:03 +0200 (CEST) Received: from rolf-mini.obsigna.com (rolf-mini.obsigna.com [192.168.222.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.obsigna.com (Postfix) with ESMTPSA id 6D3811350F91D; Sun, 31 May 2020 16:57:00 -0300 (-03) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: BeagleBone AI From: "Dr. Rolf Jansen" In-Reply-To: <966c33ea1924c2cfab5d9e295a9239d134e03f8a.camel@freebsd.org> Date: Sun, 31 May 2020 16:56:58 -0300 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <3CA84BA5-FEA8-4BD8-A713-C794139170EE@cyclaero.com> References: <966c33ea1924c2cfab5d9e295a9239d134e03f8a.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 49Zpwz0xsgz3Y2v X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cyclaero.com header.s=strato-dkim-0002 header.b=Q4lAufp0; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@cyclaero.com designates 81.169.146.219 as permitted sender) smtp.mailfrom=freebsd@cyclaero.com X-Spamd-Result: default: False [-0.77 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[cyclaero.com:s=strato-dkim-0002]; NEURAL_HAM_MEDIUM(-1.05)[-1.055]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+ip4:81.169.146.128/25]; DMARC_NA(0.00)[cyclaero.com]; RWL_MAILSPIKE_GOOD(0.00)[81.169.146.219:from]; NEURAL_SPAM_SHORT(0.36)[0.364]; NEURAL_HAM_LONG(-0.98)[-0.984]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[cyclaero.com:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_NAME_HAS_TITLE(1.00)[dr]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6724, ipnet:81.169.144.0/22, country:DE]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[81.169.146.219:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 19:57:08 -0000 > Am 31.05.2020 um 14:11 schrieb Ian Lepore : >=20 > On Fri, 2020-05-29 at 23:21 -0300, Dr. Rolf Jansen wrote: >> ... >>=20 >> First Question: >>=20 >> What modern SBC with more than 1 I=C2=B2C bus and which can run = FreeBSD 13++ would you suggest? >>=20 >> ... >>=20 >> Two more Questions: >>=20 >> Is it reasonable to assume that FreeBSD would run on a BBAI in the = future, let=E2=80=99s say in 2 to 3 years? >>=20 >> Perhaps I could help porting FreeBSD to a BBAI. What would be the = general steps? >>=20 >>=20 >> Many thanks in advance for any suggestions, advices and = clarifications. >>=20 >> Best regards >>=20 >> Rolf >=20 > BTW, if you need drivers for any new i2c devices just let me know and > I'll see what I can do. I am pretty comfortable with register level programming, and so far I = came away with ioctl() calls for what I needed. So perhaps I won=E2=80=99t= need exactly a driver for new I=C2=B2C devices. However, I am far away = from being a perfect I=C2=B2C expert, specially when it comes to timing = and the best sequence of addressing different devices on the bus. = Perhaps, I may ask some questions when I run into problems. > Also, in my experience you can often get away with running an i2c bus > faster than 400khz if you need more bandwidth. I've never seen any > modern chip fail to work at 800khz, and most seem to work fine up to > about 1mhz; above that they become pretty unreliable. Does this =E2=80=9Eover clocking=E2=80=9C work for the ARM boards as = well? I just set the clock-frequency in the dts-overlay which activates = I2C1 of the BBB from 400000 to 800000. The bus seems to work as usual, = however, I did not yet come to check its speed. How again would I do = that? Probably there are many more questions to come :-) Best regards Rolf= From owner-freebsd-arm@freebsd.org Sun May 31 22:35:41 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 99B2A2F4105 for ; Sun, 31 May 2020 22:35:41 +0000 (UTC) (envelope-from adridg@freebsd.org) Received: from lb1-smtp-cloud7.xs4all.net (lb1-smtp-cloud7.xs4all.net [194.109.24.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.xs4all.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49ZtRx1RMhz45KD for ; Sun, 31 May 2020 22:35:40 +0000 (UTC) (envelope-from adridg@freebsd.org) Received: from beastie.bionicmutton.org ([62.251.92.29]) by smtp-cloud7.xs4all.net with ESMTP id fWYMjYCn8Np2zfWYNjSdV2; Mon, 01 Jun 2020 00:35:39 +0200 From: Adriaan de Groot To: freebsd-arm@freebsd.org, "Dr. Rolf Jansen" Subject: Re: BeagleBone AI Date: Mon, 01 Jun 2020 00:35:38 +0200 Message-ID: <3008277.bT80LyP3VS@beastie.bionicmutton.org> Organization: FreeBSD In-Reply-To: <372086B8-3BD9-48A5-828A-CBA2C11601D9@cyclaero.com> References: <20200531063124.GY4213@funkthat.com> <372086B8-3BD9-48A5-828A-CBA2C11601D9@cyclaero.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart15775477.vxEf1mJfsr"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-CMAE-Envelope: MS4wfHuCL1c2QQtFgAv82Ekx+JWZhgclsAkwJur4t0n1cbJsEcUjefm13IpcgIr1QURVqjBdtmgSnHxOvISBiC3/n+dHfgVt0lRRvJhxhsctAY3gWJiGKi6n +XnKRMLhZ/yuoCVF1YOTaNeEqbcP2Lpuw7WN4lKPQOgajKAey7uV/tSysKhk/gIbcdl24JSES/VN9CVcHL9TUq/5RRqFQABsqpLmnlnAuLFUN3uljQX5LZEC X-Rspamd-Queue-Id: 49ZtRx1RMhz45KD X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 22:35:41 -0000 --nextPart15775477.vxEf1mJfsr Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" On Sunday, 31 May 2020 21:27:08 CEST Dr. Rolf Jansen wrote: > What about the Pine Rock64Pro or the Pine H64, do these also offer > additional I=C2=B2C busses? Best place to ask that kind of hardware question is on IRC: channel #Pine64= or=20 #Rock64 on irc.pine64.xyz. Those are community channels, where you do also= =20 happen to find the people most deeply involved in the hardware. Note too that Pine64 are very supportive of community efforts and OpenBSD d= oes=20 quite well on their hardware. [ade] --nextPart15775477.vxEf1mJfsr Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEUq+pvuD+N8/vVW++WoDe9T7W/7IFAl7UMToACgkQWoDe9T7W /7Jr/RAAigA8Wut/FQBqqv1kwMMeIAdEgQ7YBD9Mi/c1pM7lFRmQj6wD23pD7LzU +bswPXAENWk5uXV68I2I5yJPLFNOLYi1NKIh4Kglf03o6Ate3ysv9UaMkp0kfsL+ bnfR+km5sLOa6FhjMiAh4GRI/Yh4n/5UYhTlZW4y36pjXJW4uL3Dqw7q1H7nbj7k 0C8CYe02jxgm1qTBQBO/S2l6c7gP8UuAM4KSUj4VGGf5Z7JdyEy+KVJ9SURu0cMy I4RiiCec5MxFwg/oyn6hk04nvvqpYAEYpCGmNyY/yYNhzmqeHIOlZ69aesZZ1KBX Lv4zR9aZwt+NzMYLlru74uhoFLk2JqG+Ax1yALkBat8avkJyFTl1kqg6xTdWly5F gzyzpwiy+gydn7BHCr5V8ShelRBgfFKUpCDfGInTQFp/OwuLzzfpYwiI0jMBiXhH 49lmi/iOFg2fuHD/T/fZ+88uAaBeZAw5LjvdWXLg6JUgH8nD6ZbUFw3Rf2LbC8RD 7mDUGAyEy17NfM5eigOg1H92j9yLBbOO9PvtYaEqbOpkrWSidbboiEa3riDPD+mC UaVYxQ7SxE6MUgRyXNFssPG/dR2ZGO3pE+RxazZQfwq+BZ8Js8Slp/b2/W/dsGve I2Muh+jXusaD6AYyV5BeZuF23d8s5pbP4Ym/EqGVSJ8Mc/k8aQs= =IwzZ -----END PGP SIGNATURE----- --nextPart15775477.vxEf1mJfsr-- From owner-freebsd-arm@freebsd.org Mon Jun 1 00:26:19 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 200132F6509 for ; Mon, 1 Jun 2020 00:26:19 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49ZwvZ0Px3z4FFq for ; Mon, 1 Jun 2020 00:26:17 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-qt1-x82f.google.com with SMTP id x29so6504545qtv.4 for ; Sun, 31 May 2020 17:26:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=5s1CUI+oSNur99fxERX+MlEne1gZGCt0DQcgpXyy9R8=; b=kS8EYqzFtq6G2T6XHCvuNP67sKBy2zO35FjVcrGzHwM4jyD6++3NL3AT2D3HM+fgQJ WNlbxAj98KGpJrq7RnlyJyc+Wh7KjW91m1Db24Q5tXMSJJUqsMB5PKqsC55iaW/0f1VU oDPj6DrQbkGS2ModqOb8OyMugcbjgM4FwlyvaGug5xDL/YF1LbCULyWG6ipXROWuKARp IimX2mpY8bvRcSrWH+rwXzdgS/QDzXk1ezivESDyWI2FeT67dknFYxibAYFTzMSVm//x JoMu8CjTIXy0yrbqjvFUlIzIfORd3fyHZxRsnrsOFkCjErcNM/vZ7hPsCtRcf1hRcg2O 6rPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=5s1CUI+oSNur99fxERX+MlEne1gZGCt0DQcgpXyy9R8=; b=puPPyF4GRwz2SDQp/eNHWwnsAYagaWmvHethnoEcld9ugTRzYPli+8MDJWoJhgC16I ivWTFiRigktN1O6BoTVbHsKbq4xDsNx13KcHCETWJ0nFg2xvzP/Gc2O7SnGh9Xb3Zkxf XLIBydz7ZUgiaLB7iOrEEPXadqQytVM56qRNE186zwx/VdeZllSuQmIr/wypqkTWSLnp 3khxAMnWKQs94xryj9flIFvgxUewYgFSBxuwIiSrcvSI6DDOdK4VBns6SD28PsyN41xi K9fk0ACePhsOPa9nKFN3/xrrOjxF5c0SvhXsdKhO3c+wvSMlIim19EOnIu9/DR1aijaY 34Ow== X-Gm-Message-State: AOAM532augo34tJm4QUCXDSXVwjsdGS6YYJG36fzguU/+rfB5mabA2cc uUdQi1/4A+da5WCKkDcX0c1KahcDfUv9MnWtrYZzwZZt X-Google-Smtp-Source: ABdhPJza+l48frwEMI0o7CcAr6i+zhj2a8Gq5K8A4wZ1dLQtMbbGZqDRA8Iy4yVxlsSNUDaviPUmdXx9mBpSUqVV78k= X-Received: by 2002:ac8:6118:: with SMTP id a24mr19512666qtm.30.1590971176612; Sun, 31 May 2020 17:26:16 -0700 (PDT) MIME-Version: 1.0 References: <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <4E21DEB1-0C86-41CD-BE89-FBF2EF45443C@unrelenting.technology> In-Reply-To: <4E21DEB1-0C86-41CD-BE89-FBF2EF45443C@unrelenting.technology> From: Marcin Wojtas Date: Mon, 1 Jun 2020 02:26:04 +0200 Message-ID: Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: myfreeweb Cc: Dan Kotowski , freebsd-arm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 49ZwvZ0Px3z4FFq X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=semihalf-com.20150623.gappssmtp.com header.s=20150623 header.b=kS8EYqzF; dmarc=none; spf=none (mx1.freebsd.org: domain of mw@semihalf.com has no SPF policy when checking 2607:f8b0:4864:20::82f) smtp.mailfrom=mw@semihalf.com X-Spamd-Result: default: False [-2.36 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.06)[-1.061]; R_DKIM_ALLOW(-0.20)[semihalf-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; SH_EMAIL_DBL_DONT_QUERY_IPS(0.00)[0.0.0.1:email]; NEURAL_HAM_LONG(-0.98)[-0.980]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[semihalf.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[semihalf-com.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-0.02)[-0.021]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::82f:from]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DBL_PROHIBIT(0.00)[0.0.0.1:email] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2020 00:26:19 -0000 Hi, niedz., 31 maj 2020 o 18:09 myfreeweb napisa= =C5=82(a): > > > > On May 31, 2020 4:00:22 PM UTC, Dan Kotowski wrote: > >> > > I've sent a link to a known firmware build before: > >> > > https://drive.google.com/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvErK/= view > >> > > Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe? > >> > > >> > I decided to go back to the UEFI sources and have found some differe= nces that I think need to be reconciled before moving forward. That said, I= 'm not an ACPI wizard by any means - for me it's low-level mage spells at b= est... > >> > In https://github.com/SolidRun/edk2-platforms we have 2 different br= anches that SolidRun seems to use: > >> > > >> > 1. LSDK-19.09-sr > >> > 2. master-lx2160a > >> > > >> > I've been building from the latter branch, but found some significan= t differences in the former that I think may be important to merge in. > >> > >> To me it seems like 19.09 is just outdated and doesn't have any benefi= ts. Ask the solidrun people to be sure. > >> > >> Either way, nothing here would fix the interrupt bug. It's our bug sin= ce NetBSD works fine :( > > > >Any thoughts on the "Poll mode" comment below from the dts? We're still = not seeing any of the PHYs in either BSD. > > > >``` > >&emdio1 { > > rgmii_phy1: ethernet-phy@1 { > > /* AR8035 PHY - "compatible" property not strictly needed */ > > compatible =3D "ethernet-phy-id004d.d072"; > > reg =3D <0x1>; > > /* Poll mode - no "interrupts" property defined */ > > }; > >}; > >``` > > Why are you looking at Ethernet stuff? > We do not have a driver for NXP's NIC in any BSD. > > (I do wonder if the Semihalf work on the Layerscape family would eventual= ly include Ethernet..) > Yes, our work included ethernet support for the LS1046 by heavily modifying the sys/dev/dpaa driver, used by PowerPC QorIQ line. As the work was done on 11.x, nice forward port here is a challenge, we currently have no free cycles for. Anyway, LS2K uses a different IP (DPAA2) - even though it has some common components with the DPAA, there's a certain amount of work to be done. In case someone has spare funds for this, please contact me directly :) Best regards, Marcin From owner-freebsd-arm@freebsd.org Mon Jun 1 02:22:15 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4AE202F8E92; Mon, 1 Jun 2020 02:22:15 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49ZzTK5GL0z4NsR; Mon, 1 Jun 2020 02:22:13 +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 0512M95N015828 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 31 May 2020 19:22:09 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id 0512M991015827; Sun, 31 May 2020 19:22:09 -0700 (PDT) (envelope-from fbsd) Date: Sun, 31 May 2020 19:22:08 -0700 From: bob prohaska To: freebsd-ports@freebsd.org, freebsd-arm@freebsd.org Subject: 'asm/hwcap.h' file not found building chromium on Pi3 Message-ID: <20200601022208.GA15761@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 49ZzTK5GL0z4NsR X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [3.17 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.58)[0.581]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.29)[0.292]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.40)[0.397]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2020 02:22:15 -0000 Made another attempt to compile www/chromium on a Pi3B, this time using a mechanical hard disk for all storage (and boot). It stopped with ../../third_party/zlib/cpu_features.c:32:10: fatal error: 'asm/hwcap.h' file not found #include ^~~~~~~~~~~~~ 1 error generated. Ports are at Revision: 537041, uname -a reports 12.1-STABLE r361429 GENERIC arm64. All make commands used -DBATCH. Thanks for reading, any hints appreciated... bob prohaska From owner-freebsd-arm@freebsd.org Mon Jun 1 04:05:41 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 76EDB2FB4EA for ; Mon, 1 Jun 2020 04:05:41 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic312-25.consmr.mail.gq1.yahoo.com (sonic312-25.consmr.mail.gq1.yahoo.com [98.137.69.206]) (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 49b1mg6Klxz4Wwy for ; Mon, 1 Jun 2020 04:05:39 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: f3rzAUgVM1lXjKWMY_kCrSBXpYqJ.zpiZx5I9o5U9nH4hHyOXOf4G1vdHxW82tg JEU89dFiU_wyFIBrIBqkTb3ebu29Jx5l_2n938RW8bw3RO_pQrk_cwa9f7JkBQvdm.JfiDZwCi1N cYXjWN8m7fqjwyzjkK7uyXFLZlYd0kzm6uKXcKMzVc_rRrs_BZmn5Bu7cD7wNEzC4TdS6GblJs5u Rv3knbmAG4T.DuuNI0AJAyfjiGTtUmfnHcppxqPdG3Fb19i9Ucwk5V9GXQCmWWxmxQYEsZpKJyUR 7zt_gvHefVq4i2h75p8psiBAutatOpv6zLR5sAL1v37BOuDsjeZd84eTfjQcuZ35vHLV_P7XNDIn Cszl71a.yUNgpJUEiZjbuJ9N_uDoRsLCA31JTsgXKmrDQOYs1FZj9QaqYgR8PwBwsM4s7Yf8DJCD gRFnfl3j1KrG1HNlSUL0uV2WKu_mMSFr5SWO1EEfpHivAugqU_xTUJzwg8rnMyUw3oUvd.1IdNhF mxSutnu.FijWPu5ezjJUx6iZeltUhBsqrykk90tU.R8drZU42zEUhy9TcOgjjw.1pxd9LnPTOdYp 8Sbqor5mPebD7IZFihGDLP7rfqaw4HHR1SRhuNcOs6UF22eAvVKyJBdbWTKH8gRAKIOcLbhKMtHp r76frzayzJzd9koOLM3hgy3gfl6DLz2uQb75fZlJQNMHfvfVlSFYs0vJdrU7MBzE9XfUVVzTMc.u wBenOFPNjeHX3RQBBKAaInLuWlgkKp9ChJmOcmrYCz_uqgDFM1afERHFYfq2MP0H3ZAf1OhCSkMa mDlsWatD7CxQrjF515x6Ed14UKh53unMElsNBeODkXGN0dxlGeiRRxqMsprl4R.krzYnMdzb_FIl pKBCRssqG5jHE1EVW2SNVHGD_ibWTXqt0heOKDp1E6jxaJ35HNDrp82HO1wfGkXsL3WjTcaUKrDI L2i.V5mCFW9Wm6FWaSdpuVlV3AQWwG378pnb_dL_DLj2y.YtqRXesRCp3brS4HaDPM4WtJWXjVAy suIl.w9iY2NSCOyrNy_oYfiQ_RAwozyjC85ele1VN0JP8gTx_L2OzBfHpETkaF6QP3xxnayn9yhf VZMoOaj3zQzcbEAATpxoP2kW3qpu.xSnPePmwO6qLxlYu3nWtCvPNh415RcA5wbXz5SzgiuGEtzS uN96OiM3z5TTWiC.kwJ0oC3m8ecWhgxv04mWY3c1.jqAb7taMAu1pLkKxjE_fz2vRFA0gZks1WyL G37DrzYQNPviRFUDwlOaU7oeBvfW35Kz2nmPRIvflYz2KtOK6SlOnvE0CFuyGdfg7bOsgyY.uWVy BfhJFRhLkix4pcT5AFLsnFz8AQrGjIdUKXr9yW_BLl6KULfSUv7jW2NZK5vpIe9PO8fAUk3R8alm t4TJhSEj5ZHiUAiRWJEjrnrxTmtNa.O0iyi5WktdAyVx_oY7Cx77vLHASjrU- Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.gq1.yahoo.com with HTTP; Mon, 1 Jun 2020 04:05:38 +0000 Received: by smtp420.mail.gq1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 672ed58712971f0ff7234d1d7958cd8d; Mon, 01 Jun 2020 04:05:37 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: 'asm/hwcap.h' file not found building chromium on Pi3 From: Mark Millard In-Reply-To: <20200601022208.GA15761@www.zefox.net> Date: Sun, 31 May 2020 21:05:36 -0700 Cc: freebsd-ports@freebsd.org, freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20200601022208.GA15761@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49b1mg6Klxz4Wwy X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.87 / 15.00]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.69.206:from]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; NEURAL_HAM_LONG(-0.99)[-0.990]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; RCVD_IN_DNSWL_NONE(0.00)[98.137.69.206:from]; NEURAL_HAM_SHORT(-0.32)[-0.318]; NEURAL_HAM_MEDIUM(-1.06)[-1.063]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2020 04:05:41 -0000 On 2020-May-31, at 19:22, bob prohaska wrote: > Made another attempt to compile www/chromium on a Pi3B, this time = using > a mechanical hard disk for all storage (and boot). It stopped with >=20 > ../../third_party/zlib/cpu_features.c:32:10: fatal error: = 'asm/hwcap.h' file not found > #include > ^~~~~~~~~~~~~ > 1 error generated. >=20 > Ports are at Revision: 537041, uname -a reports 12.1-STABLE r361429=20 > GENERIC arm64. All make commands used -DBATCH. Warning: I did not version match to -r537041 so this is only suggestive unless confirmed. But I do not keep referencing that status below. Not that it solves the problem, but some context indicates that it is likely a problem with the port (since chromium of itself does not support FreeBSD) . . . =46rom the cpu_features.c source: #if defined(ARMV8_OS_ANDROID) #include #elif defined(ARMV8_OS_LINUX) #include #include #elif defined(ARMV8_OS_FUCHSIA) #include #include #include #elif defined(ARMV8_OS_WINDOWS) || defined(X86_WINDOWS) #include #elif !defined(_MSC_VER) #include #else #error cpu_features.c CPU feature detection in not defined for your = platform #endif So your build has ARMV8_OS_LINUX defined and also tried to build based in part on: third_party/zlib/cpu_features.c A grep -r shows all the references to ARMV8_OS_LINUX are under third_party/zlib/ . ARMV8_OS_LINUX is from the third_party/zlib/BUILD.gn code: . . . if (use_arm_neon_optimizations) { config("zlib_arm_crc32_config") { # Disabled for iPhone, as described in DDI0487C_a_armv8_arm: # "All implementations of the ARMv8.1 architecture are required to # implement the CRC32* instructions. These are optional in = ARMv8.0." if (!is_ios) { defines =3D [ "CRC32_ARMV8_CRC32" ] if (is_android) { defines +=3D [ "ARMV8_OS_ANDROID" ] } else if (is_linux || is_chromeos) { defines +=3D [ "ARMV8_OS_LINUX" ] } else if (is_fuchsia) { . . . is_linux seems to in turn be from: chromium-*/build/config/BUILDCONFIG.gn and its: is_linux =3D current_os =3D=3D "chromeos" || current_os =3D=3D "linux" = || current_os =3D=3D "freebsd" The freebsd reference here (and elsewhere in that file) are from the port's patching activity. chromium does not seem to support FreeBSD of itself so it seems the problem would be considered to be in the port instead. I've no clue what a proper alternative would be for third_party/zlib/cpu_features.c to use in a FreeBSD context. =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 Jun 1 04:52:41 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 346932FBB7C for ; Mon, 1 Jun 2020 04:52:41 +0000 (UTC) (envelope-from freebsd-arm@darkain.com) Received: from MTA-09-3.privateemail.com (mta-09-3.privateemail.com [68.65.122.19]) (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 49b2pw1csrz4ZPR for ; Mon, 1 Jun 2020 04:52:39 +0000 (UTC) (envelope-from freebsd-arm@darkain.com) Received: from MTA-09.privateemail.com (localhost [127.0.0.1]) by MTA-09.privateemail.com (Postfix) with ESMTP id B3E526003F for ; Mon, 1 Jun 2020 00:52:37 -0400 (EDT) Received: from mail-il1-f170.google.com (unknown [10.20.151.247]) by MTA-09.privateemail.com (Postfix) with ESMTPA id 6B72A60034 for ; Mon, 1 Jun 2020 04:52:37 +0000 (UTC) Received: by mail-il1-f170.google.com with SMTP id p5so7081565ile.6 for ; Sun, 31 May 2020 21:52:37 -0700 (PDT) X-Gm-Message-State: AOAM530ryDgBwkT7VxUA7FxqCchoxYOT9KB9JLNa5Q5HXpGoyCCTtVSn aL7HKUNip9McupUAWc1QrJz7A1vLlbdQteInw1I= X-Google-Smtp-Source: ABdhPJxYAZvjUQ5MlBY/W1SdYkkByWhMhCgFv9MrGG4qAVGsBL4h6VbIU8W+T+veLeMAebIEDoCauY8zYVTiQt+V4LQ= X-Received: by 2002:a92:af11:: with SMTP id n17mr6469804ili.156.1590987156740; Sun, 31 May 2020 21:52:36 -0700 (PDT) MIME-Version: 1.0 References: <7F058E92-DDD3-4728-9A51-09BF1D47855C@googlemail.com> <1RBZ-1AclgkiNDwWUqrWhun8T8YSAX6g64NeSc2DKy9EF1wGsJobselP4UYGflpcmbfUx3sEEM2YplIJOXPmZ6EG_GwiMC1_3GLrqpZxisQ=@protonmail.com> <46519DEB-E96D-43DD-B739-401F9F51371E@googlemail.com> <87EE030D-5323-477B-9FF3-CB8970138729@googlemail.com> <37A9A3AA-F2AF-4F08-84BE-8A19E75DB5E0@googlemail.com> In-Reply-To: From: Vincent Milum Jr Date: Sun, 31 May 2020 21:52:25 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Driver for Raspberry Pi 4 PCI-express controller To: =?UTF-8?Q?Klaus_K=C3=BCchemann?= Cc: freebsd-arm@freebsd.org X-Virus-Scanned: ClamAV using ClamSMTP X-Rspamd-Queue-Id: 49b2pw1csrz4ZPR X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd-arm@darkain.com designates 68.65.122.19 as permitted sender) smtp.mailfrom=freebsd-arm@darkain.com X-Spamd-Result: default: False [-2.65 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.07)[-1.066]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:68.65.122.0/27]; NEURAL_HAM_LONG(-0.97)[-0.968]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[darkain.com]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.31)[-0.313]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[68.65.122.19:from]; FREEMAIL_TO(0.00)[googlemail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:22612, ipnet:68.65.122.0/24, country:US]; RCVD_TLS_LAST(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[68.65.122.19:from] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2020 04:52:41 -0000 My apologies, I forgot that my inbound and outbound email aliases were not the same, so the FreeBSD-ARM mailing list rightfully rejected my email before. > hope it=E2=80=99s okay for you to keep this discussion public Yes, it was intended to be a public discussion :) > Did you test hot-unplugging/replugging the peripherals ? Yes, for the most part it all went exactly as expected. Sometimes one of the controllers would reset, other times it would work perfectly. A couple times it would cause that endless error loop I reported before (in which case, it seems only a power cycle solves it). Console log from an unplug/replug event is listed below. This particular time is one of the times the controller reset itself, and worked properly after. > do you mean that not every boot-attempt does the same (for unknown reason= ) Correct. Once or twice, I had the infinite controller resets on boot. > or whether it`s caused by the pie-driver-electricity This was my initial thought, too. I have been powering this Pi from the USB-C port on my desktop workstation. Once or twice I saw the "low power" warning on screen, so that is certainly a possibility. I've since had the Pi running idle for over 24 hours without issue. Additional testing... USB to Serial adapter: Plugged in and /dev/cuaU0 properly showed up, but I didn't hook it up to anything to test sending/receiving yet. ugen0.8: at usbus0 uplcom0 on uhub1 uplcom0: on usbus0 Microsoft XBOX 360 Wired controller: Same as above. Plugged in, /dev/uhid0 showed up properly, but have not tested usage yet. ugen0.8: at usbus0 uhid0 on uhub1 uhid0: on usbus0 unplug/replug USB hub with multiple devices attached, with "xhci_interrupt: host system error" and controller reset: ugen0.3: at usbus0 (disconnected) uhub2: at uhub1, port 1, addr 2 (disconnected) ugen0.4: at usbus0 (disconnected) ums0: at uhub2, port 1, addr 3 (disconnected) ums0: detached ugen0.5: at usbus0 (disconnected) ure0: at uhub2, port 3, addr 4 (disconnected) rgephy0: detached miibus1: detached ure0: detached Jun 1 04:21:05 generic dhclient[7364]: receive_uhub2: detached packet failed on ue0: Device not configured Jun 1 04:21:05 generic dhclient[7364]: ioctl(SIOCGIFFLAGS) on ue0: Operation not permitted Jun 1 04:21:05 generic dhclient[7364]: Interface ue0 no longer appears valid. Jun 1 04:21:05 generic dhclient[7364]: No live interfaces to poll on - exiting. Jun 1 04:21:05 generic dhclient[7364]: exiting. Jun 1 04:21:05 generic dhclient[7364]: connection closed Jun 1 04:21:05 generic dhclient[7364]: exiting. ugen0.3: at usbus0 uhub2 on uhub1 uhub2: on usbus0 uhub2: MTT enabled uhub2: 4 ports with 4 removable, self powered ugen0.4: at usbus0 ums0 on uhub2 ums0: on usbus0 ums0: 5 buttons and [XYZ] coordinates ID=3D0 ugen0.5: at usbus0 ure0 on uhub2 ure0: on usbus0 miibus1: on ure0 rgephy0: PHY 0 on miibus1 rgephy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1000baseT-FDX-master, auto xhci_interrupt: host system error xhci0: Resetting controller uhub0: at usbus0, port 1, addr 1 (disconnected) ugen0.2: at usbus0 (disconnected) uhub1: at uhub0, port 1, addr 1 (disconnected) ugen0.3: at usbus0 (disconnected) uhub2: at uhub1, port 1, addr 2 (disconnected) ugen0.4: at usbus0 (disconnected) ums0: at uhub2, port 1, addr 3 (disconnected) ums0: detached ugen0.5: at usbus0 (disconnected) ure0: at uhub2, port 3, addr 4 (disconnected) rgephy0: detached miibus1: detached Jun 1 04:21ure0: detached :37 generic dhclient[8021]: receive_packet failed on ue0: Device not configured Jun 1 04:21:37 generic dhclient[8021]: ioctl(SIOCGIFFLAGS) on ue0: Operation not permitted Jun 1 04:21:37 generic dhclient[8021]: Interface ue0 no longer appears valid. Jun 1 04:21:37 generic dhclient[8021]: No live interfaces to poll on - exiting. Jun 1 04:21:37 generic dhclient[8021]: exiting. Jun 1 04:21:37 generic dhclient[8021]: connection closed Jun 1 04:21:37 generic dhclient[8021]: exiting. uhub2: detached uhub1: detached ugen0.7: at usbus0 (disconnected) umass0: at uhub0, port 3, addr 6 (disconnected) da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: s/n E0D55EA573F5F3B1A9B21117 detached (da0:umass-sim0:0:0:0): Periph destroyed umass0: detached uhub0: detached xhci0: Controller halt timeout. uhub0 on usbus0 uhub0: <0x1106 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 uhub0: 5 ports with 4 removable, self powered ugen0.2: at usbus0 uhub1 on uhub0 uhub1: on usbus0 uhub1: 4 ports with 4 removable, self powered ugen0.3: at usbus0 uhub2 on uhub1 uhub2: on usbus0 uhub2: MTT enabled uhub2: 4 ports with 4 removable, self powered ugen0.4: at usbus0 ums0 on uhub2 ums0: on usbus0 ums0: 5 buttons and [XYZ] coordinates ID=3D0 ugen0.5: at usbus0 ure0 on uhub2 ure0: on usbus0 miibus1: on ure0 rgephy0: PHY 0 on miibus1 rgephy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1000baseT-FDX-master, auto ugen0.6: at usbus0 umass0 on uhub0 umass0: on usbus0 umass0: SCSI over Bulk-Only; quirks =3D 0xc100 umass0:0:0: Attached to scbus0 da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Removable Direct Access SPC-4 SCSI device da0: Serial Number E0D55EA573F5F3B1A9B21117 da0: 400.000MB/s transfers da0: 14755MB (30218842 512 byte sectors) da0: quirks=3D0x2 On Sat, May 30, 2020 at 1:28 PM Klaus K=C3=BCchemann wrote: > Hi, > thanks, Vincent, for your extensive testing, very helpful ! > `hope it=E2=80=99s okay for you to keep this discussion public(forward to > freebsd-arm@freebsd.org) . > > > Am 30.05.2020 um 20:11 schrieb Vincent M. Jr <>: > > > > dmesg: https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5523 > > > > =E2=80=A6=E2=80=A6. > > It isn't perfectly stable, but at least initially working=E2=80=A6.. > > Yeah, initially (sometimes) works for me too... > > > > Testing it with a USB-C (with adapter) ethernet + 3-port hub. I'm using > this for wired ethernet rather than the built in ethernet just for testin= g. > > > > On the three hub ports, I have a microsoft keyboard, microsoft mouse, > and a kingston datatraveler thumbdriv > > There is also a Logitech keyboard on one of the Pi's USB 2.0 ports > > Did you test hot-unplugging/replugging the peripherals ? > > > > > For testing, I've created a single-drive ZFS pool with the kingston > drive. > > > > I went to delete a test file, and got the following: > > > > xhci_interrupt: host system error > > xhci0: Resetting controller > > uhub0: at usbus0, port 1, addr 1 (disconnected) > > ugen0.2: at usbus0 (disconnected) > > uhub1: at uhub0, port 1, addr 1 (disconnected) > > ugen0.3: at usbus0 (disconnected) > > uhub2: at uhub1, port 1, addr 2 (disconnected) > > ugen0.4: at usbus0 (disconnected) > > umass0: at uhub2, port 1, addr 3 (disconnected) > > (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 a0 21 a5 00 00 80 00 > > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > > (da0:umass-sim0:0:0:0): Retrying command, 3 more tries remain > > > > But every single device had to be re-detected which took ~5-10 seconds > to complete. > > Yeah, experienced that too ... > > > > > > > On another boot attempt, I'm getting this repeatedly while at the login > prompt:...usb_alloc_device: device init 2 failed (USB_ERR_TIMEOUT, > ignored)...ugen0.2: at usbus0 (disconnected)=E2=80=A6. > > This is a very interesting information : > =E2=80=A6 do you mean that not every boot-attempt = does the > same (for unknown reason) > (That=E2=80=99s what I have experienced but I wasn=E2=80=99t sure whether= my uSD is > damaged or whether it`s caused by the pie-driver-electricity ?? > Specially the at -thing only appears in some boot attempts(not > all) > In my tests the strange thing is that one boot-attempt succeeds and > another not , while left the machine completely untouched between those > attempts.. > > > > > update: i've gotten this also while doing a lengthy transfer to USB ZFS > pool, and the error cycling never stops. > > I will try to make a ZFS-pool-test... > > > > > xhci0: Controller reset timeout. > > uhub0 on usbus0 > > uhub0: <0x1106 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbu= s0 > > uhub0: 5 ports with 4 removable, self powered > > xhci0: Resetting controller > > usb_alloc_device: device init 2 failed (USB_ERR_TIMEOUT, ignored) > > ugen0.2: at usbus0 (disconnected) > > uhub_reattach_port: could not allocate new device > > uhub0: at usbus0, port 1, addr 1 (disconnected) > > uhub0: detached > > xhci0: Controller halt timeout. > > xhci0: Controller reset timeout. > > xhci0: Controller reset timeout. > > uhub0 on usbus0 > > uhub0: <0x1106 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbu= s0 > > uhub0: 5 ports with 4 removable, self powered > > xhci0: Resetting controller > > usb_alloc_device: device init 2 failed (USB_ERR_TIMEOUT, ignored) > > ugen0.2: at usbus0 (disconnected) > > uhub_reattach_port: could not allocate new device > > uhub0: at usbus0, port 1, addr 1 (disconnected) > > uhub0: detached > > xhci0: Controller halt timeout. > > xhci0: Controller reset timeout. > > xhci0: Controller reset timeout. > > > > > > =E2=80=A6=E2=80=A6.. > > xhci0 is this : > > https://svnweb.freebsd.org/base/head/sys/dev/usb/controller/generic_xhci.= c?view=3Dmarkup > (and the corresponding fdt/acpi-files) > > uhub0 is this : > https://svnweb.freebsd.org/base/head/sys/dev/usb/usb_hub.c?view=3Dmarkup > > Thanks again for testing, > Regards > > > > > > > From owner-freebsd-arm@freebsd.org Mon Jun 1 12:06:01 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 64D0D333E56 for ; Mon, 1 Jun 2020 12:06:01 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch [185.70.40.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49bDQw43ftz3Vgc for ; Mon, 1 Jun 2020 12:06:00 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Mon, 01 Jun 2020 12:05:56 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1591013157; bh=GYEQsHOfDcyiBz6AIGR9oDocUR2RbW0D4dlQapNpeDI=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=hCguklTjp8ybL22qqMKorQIgy6nS02msl5d+vXcog8S/i0QYIR/DiTIPAfrmUHTZQ 8qLzgOPNF3GCEt+JcHSBmbRFWIYFL2QpC/AgMIcvQh83HYktyg2D2uEeK3b4Cj5p9b Yy8Cug/FafEKo65XfDAmne6gx9ogGlPOQJubGiU0= To: Marcin Wojtas From: Dan Kotowski Cc: myfreeweb , freebsd-arm Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: References: <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <4E21DEB1-0C86-41CD-BE89-FBF2EF45443C@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49bDQw43ftz3Vgc X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=hCguklTj; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.131 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-3.32 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; NEURAL_HAM_LONG(-0.96)[-0.960]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_MEDIUM(-0.98)[-0.979]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_SHORT(-0.28)[-0.279]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[185.70.40.131:from]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.131:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2020 12:06:01 -0000 > > We do not have a driver for NXP's NIC in any BSD. Ah! I'll ignore the ethernet things for now and focus on interrupt problems= . Other than D20835, D20974, D21017, and D24423, is there anything else I s= hould watch for forward progress being made? Are there any more tests you'd= like me to run in the meantime? > Yes, our work included ethernet support for the LS1046 by heavily > modifying the sys/dev/dpaa driver, used by PowerPC QorIQ line. As the > work was done on 11.x, nice forward port here is a challenge, we > currently have no free cycles for. > > Anyway, LS2K uses a different IP (DPAA2) - even though it has some > common components with the DPAA, there's a certain amount of work to > be done. In case someone has spare funds for this, please contact me > directly :) > > Best regards, > Marcin I'm guessing that by "spare funds" you mean more than what a random hobbyis= t has laying around, but in case that's not true I'm happy to contribute wh= at I can! From owner-freebsd-arm@freebsd.org Tue Jun 2 06:32:09 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3E10232BAD8 for ; Tue, 2 Jun 2020 06:32:09 +0000 (UTC) (envelope-from s199p.wa1k9r@gmail.com) Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49bhzD36dcz416v for ; Tue, 2 Jun 2020 06:32:08 +0000 (UTC) (envelope-from s199p.wa1k9r@gmail.com) Received: by mail-lj1-x233.google.com with SMTP id 9so9679106ljc.8 for ; Mon, 01 Jun 2020 23:32:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:date:subject:message-id :to; bh=3jtG12NybJGRgRAlrZ/2VSosz4BSLnVNi1l+c4tKsaM=; b=r265AjeMXxlYIuM+WTG6WMcVY60FaJhx9LqjaXILlMITkdyfEBBQ0NOyrJNTixhXXx FmQX4NP7G5eS+E+YXUEuHcXHSR+MDL2ozXaXV7lVprasJTyiP+PJ8/BAb98V7JD22YbB c1397dsToVvUDs23trWpgKAOIvcJ2mUGNpbg1v6cBIdF3FtMtyucI+WSUG3HcfI1UfVb c1Es4i5oZ2oFX3qElaYPvEkTzYPRbr7mfGapg47Ee+oiOz6Cctb8V3IXuOgocOYv5Gid XjCmx+8SJQHuvNtpu8Djp8sPDXKgUkfIL5OPZw/gJg6kc3Ae3Qii3o0j7Tix+ZV2mgSL ybKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version:date :subject:message-id:to; bh=3jtG12NybJGRgRAlrZ/2VSosz4BSLnVNi1l+c4tKsaM=; b=CzsvGPZ2l9Tt3clTU1uUB9TwNVvy87B/oJHym9Eafh2dEZval7UWNpE4EB75vn36rG Kds0ySg4B2mRp1MkDKPmL3wcNHUQIkO1sVKG2KD/B7jNzFBsz9FdvTGXmkK92Ugw3KRQ 9KoQya6+8bypIplM88dda2APsTMd89lBNRCOfM/TQcDDVFGyvtFXbw5IjQOC0nsa2pnL YCQaf516xvn89/DzIsNfZUX5Lse1WtGRqjDHEadSw3S4wqSTwou7M46SEgQPwgJ09EPK JU3Tg7JZewmpUbJIctR3gB4w+YR0jpYyrIehZlKXEvfrF4U1467N90tOQqUq2vBS82Oj /lzQ== X-Gm-Message-State: AOAM532yuzmWuXayW07sTk5DlHGb0KexWhc2A30+DkLRF8i7nHj1IvX9 CUG1sBIDJvfxECRnkIWXawqOOhC/Asg= X-Google-Smtp-Source: ABdhPJzNL7/+ERnJyUCX4zTOMWuXBPzEfLxuYUU4b+ObWTYIZ2RWRIKZo+Qa6FMIEdkUT/Q59KxbrA== X-Received: by 2002:a2e:9005:: with SMTP id h5mr11669604ljg.246.1591079526133; Mon, 01 Jun 2020 23:32:06 -0700 (PDT) Received: from [192.168.1.109] (95-30-57-239.broadband.corbina.ru. [95.30.57.239]) by smtp.gmail.com with ESMTPSA id t30sm455976lfd.29.2020.06.01.23.32.05 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Jun 2020 23:32:05 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable From: Sleep Walker Mime-Version: 1.0 (1.0) Date: Tue, 2 Jun 2020 09:32:04 +0300 Subject: Video on Pinebook-pro Message-Id: <7376AECD-7836-4D8F-AEBE-FE236A3EA4F8@gmail.com> To: Free BSD X-Mailer: iPad Mail (17F75) X-Rspamd-Queue-Id: 49bhzD36dcz416v X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=r265AjeM; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of s199pwa1k9r@gmail.com designates 2a00:1450:4864:20::233 as permitted sender) smtp.mailfrom=s199pwa1k9r@gmail.com X-Spamd-Result: default: False [-2.48 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MV_CASE(0.50)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.01)[-0.007]; RECEIVED_SPAMHAUS_PBL(0.00)[95.30.57.239:received]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.97)[-0.966]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.01)[-1.009]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::233:from]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2020 06:32:09 -0000 Hello everybody. After u-boot.2020.04 was released,=20 I managed to launch Xorg via efifb on Khadas-EDGE-V and Radxa Rock-Pi4 (both= on RK3399).=20 But so far I have not been able to repeat this on Pinebook-pro. Maybe someone has patches to run video on Pinebook-pro? Sergey Tyuryukanov= From owner-freebsd-arm@freebsd.org Tue Jun 2 08:49:19 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E677D32E1CA for ; Tue, 2 Jun 2020 08:49:19 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49bm1V26JVz4FZ2 for ; Tue, 2 Jun 2020 08:49:18 +0000 (UTC) (envelope-from manu@bidouilliste.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1591087756; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=BJjVBR5u6HIGuz1xtkAik27LjRnhQkxz4kQxXEEjE/k=; b=pA6SKU5hyocj47huhrvyUicim2BdnmR2eQBooVmrdOWDb6xSwjxr5AQfgUnMcIuFhYle7f clGHpc6qYPLVcfSNSJOliLwvPFPE+IfKtmS8/xGqaPWYGe0XznKLwGOd2rX6ZkZgVWg9q+ V+902BNJ74r0PQHS1Ye0yt+ZYVe/Zzc= Received: from amy.home (lfbn-idf2-1-900-181.w86-238.abo.wanadoo.fr [86.238.131.181]) by mx.blih.net (OpenSMTPD) with ESMTPSA id c69837b7 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 2 Jun 2020 08:49:16 +0000 (UTC) Date: Tue, 2 Jun 2020 10:49:15 +0200 From: Emmanuel Vadot To: Sleep Walker Cc: Free BSD Subject: Re: Video on Pinebook-pro Message-Id: <20200602104915.7fe4fa44ce19c5d0e6e69ac7@bidouilliste.com> In-Reply-To: <7376AECD-7836-4D8F-AEBE-FE236A3EA4F8@gmail.com> References: <7376AECD-7836-4D8F-AEBE-FE236A3EA4F8@gmail.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49bm1V26JVz4FZ2 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mx header.b=pA6SKU5h; dmarc=pass (policy=none) header.from=bidouilliste.com; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.155.74 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [-2.80 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mx]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.02)[-1.024]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[bidouilliste.com,none]; NEURAL_HAM_SHORT(-0.26)[-0.257]; NEURAL_HAM_MEDIUM(-1.02)[-1.021]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2020 08:49:20 -0000 On Tue, 2 Jun 2020 09:32:04 +0300 Sleep Walker wrote: > Hello everybody. > > After u-boot.2020.04 was released, > I managed to launch Xorg via efifb on Khadas-EDGE-V and Radxa Rock-Pi4 (both on RK3399). > But so far I have not been able to repeat this on Pinebook-pro. > Maybe someone has patches to run video on Pinebook-pro? > > Sergey Tyuryukanov > _______________________________________________ > 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" Hi, PinebookPro still need patches on top of what we have, I think I've seen some on the u-boot ML but can't find them ATM. Pinebook Pro support was merged yesterday in mainline iirc, maybe the patches needed for eDP were too. -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Tue Jun 2 13:49:45 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 29D9F337AAA for ; Tue, 2 Jun 2020 13:49:45 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from 44-233-67-66-mail.ore.mailhop.org (44-233-67-66-mail.ore.mailhop.org [44.233.67.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49bth84hpkz3dQJ for ; Tue, 2 Jun 2020 13:49:44 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1591105783; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=nTdPJDQ1qsYpz7+PeY1oMbOS7R4WTxc1xIvo3qBgHwhi8K5PV60NJjNFMNWMwZkuupwmREwIuuJrR G52jGMV/gdW5hD0xD2i7weRievIJGM+rI4+idGNg5Jbh6h/3Jmqkd09HuL142LtdmWZveG/wJG+wbD Zq5Nz6gvCffAXJBHeHILdTPSXxNm/bO7GiG/8bgnP460ZEeSa5pD6Bk/JCza71jph/HmDqpJjB8akd xESLMTxu4L67d5T47E6ozoYn2iVnyn/f4mYFNyyee68Fwu+XiLRFxq+PM1iakdY7m7bjpW7PnaVwzb K0j1F/zhPqxPF4yQWBisgQpH3wRiLUg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=r8WWMZVUJqefUVMLOlmTl4qym0NhG9AgBps2Bq1Ene8=; b=B99V3IJCFIuzNTR/T5ilx+MkSYOhwBN8Jp0xaBKNCqw4mi9wMnj0RP8G/n0l9NxNj6iP/NhwHeRbO iMiitk8oFrEeHI+MMLu8GCVgH15ohABbC0e56kgvdsam+wGKTAxhpHlr4yDEk1OcQwildRwbhJ5BPs IKYZVW18mKXSpCS0xaRLO4rM6zPyHCtL7QcRHwGvIDozrHZ+TaSZHqkVQQ98vTV3MvPhtkk496YNRe DlUhOJhucUkeDCvCfLsxsvKHKGGye8g4VCQmXx0Hv3YdqRr6SiXvFH4xP33cXTvs0fLKdWVqhwElLB KqjXTuynk8ctTkpjxZ92C35PKyGnHHw== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=r8WWMZVUJqefUVMLOlmTl4qym0NhG9AgBps2Bq1Ene8=; b=c+Cv41ADfIGimMOlVvb8KZagEKvyF5KQ56uz8TAfOuKqCCKTRL3dnn/UbujtGXvxFxnMe7naM5Mfs q6DO787lnQlEPdTBhERWufph0i8Rh/T+fiZ1MXNim5eRLnfeDMKxI61Exjsy8sJppLfkLLZEjBo7/I u1bCyad695vc0FRDzlJXTyiX2r8Vku5gMYxjrFRFPsT6ruzxbQJ0ZYgPn0OC5l3SwJExGHO2Mlcc/U DlHhPcMuMX3WqUY+pQUlkUaNZdn5OV5zzilBBBKR/noTa7UfuoldRlg0Tj7gJrkr3BfjMEIWupWnAW jYu2qKpAx0J8D1f+rZpDkGNbPd4qNIQ== X-MHO-RoutePath: aGlwcGll X-MHO-User: e786a8c4-a4d7-11ea-b10c-b5956a7dd1a1 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (c-67-177-211-60.hsd1.co.comcast.net [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id e786a8c4-a4d7-11ea-b10c-b5956a7dd1a1; Tue, 02 Jun 2020 13:49:41 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id 052DndM9064848; Tue, 2 Jun 2020 07:49:39 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <840faedfcf7c3c09a372cf566acddd8ad876ff2b.camel@freebsd.org> Subject: Re: BeagleBone AI From: Ian Lepore To: "Dr. Rolf Jansen" Cc: freebsd-arm@freebsd.org Date: Tue, 02 Jun 2020 07:49:39 -0600 In-Reply-To: <3CA84BA5-FEA8-4BD8-A713-C794139170EE@cyclaero.com> References: <966c33ea1924c2cfab5d9e295a9239d134e03f8a.camel@freebsd.org> <3CA84BA5-FEA8-4BD8-A713-C794139170EE@cyclaero.com> Content-Type: text/plain; charset="iso-8859-13" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 49bth84hpkz3dQJ X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:16509, ipnet:44.224.0.0/11, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2020 13:49:45 -0000 On Sun, 2020-05-31 at 16:56 -0300, Dr. Rolf Jansen wrote: > > Am 31.05.2020 um 14:11 schrieb Ian Lepore : > > > > On Fri, 2020-05-29 at 23:21 -0300, Dr. Rolf Jansen wrote: > > > ... > > > > > > First Question: > > > > > > What modern SBC with more than 1 I²C bus and which can run > > > FreeBSD 13++ would you suggest? > > > > > > ... > > > > > > Two more Questions: > > > > > > Is it reasonable to assume that FreeBSD would run on a BBAI in > > > the future, letÿs say in 2 to 3 years? > > > > > > Perhaps I could help porting FreeBSD to a BBAI. What would be the > > > general steps? > > > > > > > > > Many thanks in advance for any suggestions, advices and > > > clarifications. > > > > > > Best regards > > > > > > Rolf > > > > BTW, if you need drivers for any new i2c devices just let me know > > and > > I'll see what I can do. > > I am pretty comfortable with register level programming, and so far I > came away with ioctl() calls for what I needed. So perhaps I wonÿt > need exactly a driver for new I²C devices. However, I am far away > from being a perfect I²C expert, specially when it comes to timing > and the best sequence of addressing different devices on the bus. > Perhaps, I may ask some questions when I run into problems. > > > Also, in my experience you can often get away with running an i2c > > bus > > faster than 400khz if you need more bandwidth. I've never seen any > > modern chip fail to work at 800khz, and most seem to work fine up > > to > > about 1mhz; above that they become pretty unreliable. > > Does this ¥over clocking´ work for the ARM boards as well? I just set > the clock-frequency in the dts-overlay which activates I2C1 of the > BBB from 400000 to 800000. The bus seems to work as usual, however, I > did not yet come to check its speed. How again would I do that? > Probably there are many more questions to come :-) > > Best regards > > Rolf I suspect it works on some boards and maybe won't work on others. Some SOCs have very flexible clock settings in their i2c controllers, a few just allow choosing between fixed low and high speeds. For experimenting, there is a sysctl dev.iicbus.#.frequency that you can change on the fly (it will override any value from the dts). The value is the frequency in hz. -- Ian From owner-freebsd-arm@freebsd.org Tue Jun 2 14:55:50 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9BA592F10FB for ; Tue, 2 Jun 2020 14:55:50 +0000 (UTC) (envelope-from freebsd@cyclaero.com) Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [85.215.255.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49bw8N5b1Bz43SZ; Tue, 2 Jun 2020 14:55:48 +0000 (UTC) (envelope-from freebsd@cyclaero.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1591109746; s=strato-dkim-0002; d=cyclaero.com; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=18GqW0XeTbAFPT4bjoWCmb5w7KiefveRXNY/GOzNe+E=; b=HT5zsW8ATf5ZFMCRCdPJQwB+CfvAW8bd9xy1fZvQWxaLTfTbW9gUbUgnaK4Ggvog/B 6bK/tY4Me2h++DhpGlaNnU8fwu/awtDZcMRaTvlDuze/1txsSpqpgWdjg8PLgXOarIX4 3HqMwhB/dJLof0aQwxdAMiY/RcvBUir2pkOgHLIs149CoETZ49vre6g/1zTGhDFuanhz nXY8POg0Ccv0vBRfuOc+BN8n8E48MSR5T0JPd6RF4RVT0jsXTUtNtqQdbsmbQqRztwkB acaXCIgim3LjtPxbkXeUocVNR25QBdAVt6zpKGABp9BWw4ojd0iQFYBHd1G9AaDgPujq wEXQ== X-RZG-AUTH: ":O2kGeEG7b/pS1F2rRHW2isrKl4DV03XBEi+I6ZuztdvN9wS3wFGySS4Lw+ldTBio0dVbInGjc9PbZFAm0A==" X-RZG-CLASS-ID: mo00 Received: from mail.obsigna.com by smtp.strato.de (RZmta 46.9.0 DYNA|AUTH) with ESMTPSA id I06cf5w52EtkOba (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Tue, 2 Jun 2020 16:55:46 +0200 (CEST) Received: from rolf-mini.obsigna.com (rolf-mini.obsigna.com [192.168.222.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.obsigna.com (Postfix) with ESMTPSA id 53CBD1350F91D; Tue, 2 Jun 2020 11:55:41 -0300 (-03) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: BeagleBone AI From: "Dr. Rolf Jansen" In-Reply-To: <840faedfcf7c3c09a372cf566acddd8ad876ff2b.camel@freebsd.org> Date: Tue, 2 Jun 2020 11:55:40 -0300 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <5299B3F7-1C95-4769-9701-F13699FE355C@cyclaero.com> References: <966c33ea1924c2cfab5d9e295a9239d134e03f8a.camel@freebsd.org> <3CA84BA5-FEA8-4BD8-A713-C794139170EE@cyclaero.com> <840faedfcf7c3c09a372cf566acddd8ad876ff2b.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 49bw8N5b1Bz43SZ X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cyclaero.com header.s=strato-dkim-0002 header.b=HT5zsW8A; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@cyclaero.com designates 85.215.255.20 as permitted sender) smtp.mailfrom=freebsd@cyclaero.com X-Spamd-Result: default: False [-1.48 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[cyclaero.com:s=strato-dkim-0002]; NEURAL_HAM_MEDIUM(-0.98)[-0.979]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+ip4:85.215.255.0/24]; DMARC_NA(0.00)[cyclaero.com]; NEURAL_HAM_LONG(-1.06)[-1.062]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[cyclaero.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[85.215.255.20:from]; FROM_NAME_HAS_TITLE(1.00)[dr]; NEURAL_HAM_SHORT(-0.44)[-0.442]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[85.215.255.20:from]; ASN(0.00)[asn:6724, ipnet:85.215.255.0/24, country:DE]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2020 14:55:50 -0000 > Am 02.06.2020 um 10:49 schrieb Ian Lepore : >=20 > On Sun, 2020-05-31 at 16:56 -0300, Dr. Rolf Jansen wrote: >>> Am 31.05.2020 um 14:11 schrieb Ian Lepore : >>>=20 >>> On Fri, 2020-05-29 at 23:21 -0300, Dr. Rolf Jansen wrote: >>>> ... >>>>=20 >>>> First Question: >>>>=20 >>>> What modern SBC with more than 1 I=C2=B2C bus and which can run >>>> FreeBSD 13++ would you suggest? >>>>=20 >>>> ... >>>>=20 >>>> Two more Questions: >>>>=20 >>>> Is it reasonable to assume that FreeBSD would run on a BBAI in >>>> the future, let=C2=B4s say in 2 to 3 years? >>>>=20 >>>> Perhaps I could help porting FreeBSD to a BBAI. What would be the >>>> general steps? >>>>=20 >>>>=20 >>>> Many thanks in advance for any suggestions, advices and >>>> clarifications. >>>>=20 >>>> Best regards >>>>=20 >>>> Rolf >>>=20 >>> BTW, if you need drivers for any new i2c devices just let me know >>> and >>> I'll see what I can do. >>=20 >> I am pretty comfortable with register level programming, and so far I >> came away with ioctl() calls for what I needed. So perhaps I won=C2=B4t= >> need exactly a driver for new I=C2=B2C devices. However, I am far = away >> from being a perfect I=C2=B2C expert, specially when it comes to = timing >> and the best sequence of addressing different devices on the bus. >> Perhaps, I may ask some questions when I run into problems. >>=20 >>> Also, in my experience you can often get away with running an i2c >>> bus >>> faster than 400khz if you need more bandwidth. I've never seen any >>> modern chip fail to work at 800khz, and most seem to work fine up >>> to >>> about 1mhz; above that they become pretty unreliable. >>=20 >> Does this =E2=80=9Eover clocking=E2=80=9C work for the ARM boards as = well? I just set >> the clock-frequency in the dts-overlay which activates I2C1 of the >> BBB from 400000 to 800000. The bus seems to work as usual, however, I >> did not yet come to check its speed. How again would I do that? >> Probably there are many more questions to come :-) >>=20 >> Best regards >>=20 >> Rolf >=20 > I suspect it works on some boards and maybe won't work on others. = Some > SOCs have very flexible clock settings in their i2c controllers, a few > just allow choosing between fixed low and high speeds. >=20 > For experimenting, there is a sysctl dev.iicbus.#.frequency that you > can change on the fly (it will override any value from the dts). The > value is the frequency in hz. >=20 > -- Ian Thank you very much for your response. I checked the sysctl setting, and = the system accepts the values. The bus works at 800000, however, I can = set it as high as 10000000 (10 MHz) and it is still working. Perhaps, = there is some sort of internal validation before the frequency value is = actually applied to the HW. In the moment this is more a matter of = curiosity than an actual need. Once we equipped the bus with all I=C2=B2C = devices, we will perhaps run into some timing issues, and then I = probably want to revisit changing the clock frequency again. Best reagrds Rolf= From owner-freebsd-arm@freebsd.org Tue Jun 2 15:08:46 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 92E8C2F1A35 for ; Tue, 2 Jun 2020 15:08:46 +0000 (UTC) (envelope-from oskar.holmlund@yahoo.com) Received: from sonic307-54.consmr.mail.ir2.yahoo.com (sonic307-54.consmr.mail.ir2.yahoo.com [87.248.110.31]) (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 49bwRJ0T31z44ww for ; Tue, 2 Jun 2020 15:08:43 +0000 (UTC) (envelope-from oskar.holmlund@yahoo.com) X-YMail-OSG: Z8.jKQ0VM1lkq_hsbFOtjJhO_Zlcm7cBwE2ke48Aw1b3cORBS.gEsegNJ4DfiAP uoLP8Mb8Ke3EsYB.meohjd5dQ1MWJNv7zqQddDGVFWQDDtxu3v731zLe4Czw.0OtP4Vx0eLrw.QN YHhkalAy5MyZ.wGS_.IcNIbaiFYoXxsBasTPeFqE0vVIsw_P8EQtGYMKski9CwSfzt3SxLJQ2ixO rVJwt4tf1vpDZ55.4_Z1GrgbtZOBo0uFXkC3xt4ydI_gyYxmYZ32aZIEl7UuO2Osk1tss6G6R4ui mvGRIgab9b.rVzS7jgYRNhSBstlxjtMwWcTkWKU8Lhinog_woBLpenx_0ITtpBsxlwCVDlZSv6fj UUI7mmUJ1Ld7QYpPmul4r4oxd6u1Bv.DfnhQpRb4kI1EwGORjTwxFnLSw5ZUiTcF4eBoOX5id4hd yWT8JGuhLVaayxqg0OuUIXp_Vfyg7jnge7nKLx99_PU0N9f3r8eUMf9MqHMqfPRtvdfB7DzRZBqS howfRndwN9QX77nbcYMFgkJpXtq48kRX1gcL78s8R54NimaKS1DCg1Imewimz2eymzDDVkt2Deon AX.MFHYjip1VZ8520uwghwEGvlvnPW5p3FKEAY7cx3SOBS..Yk_vwTXw1Pt26_ciB4D2SMsKlVU1 Q3OJbBQnx0TqomLvq_X5i5fUT7tDvjpnsJ2WM6rg4DPaDvDYY_H2YoLJJhXOlUKjbG7Q_gBh8Cmw 6SEWNe2DqFSXVkxuyAS7WihOy5kUY6Am7bToVXmJQ_LedsLyKwPabPlOcGKb1zF0WOnsP4r.byTt KcyVd_aARAKOunE4vi_YPrHW4EbNTe5jRWEqgI2lfI5rEIBSGwuT_nj6uOBVZpUR_OTUx7n8Eevr 3WOQl3yqT86yCsPBTMtVTWBXDIcn0aRE5k95kDlob7gvZE89oTCTrbC2kHG39wljrRP_pOpWqAuN 0YkXMesmlIFhRrPwejFcAwXUV1s3z49FoI2Zw08DEvcqwge.5EmExLv3bBwwkSX559IJWnWeK3gS q.2kmX38BUOeqK3ykvozKM.KQmm7V7vJUsVXGTXNJF6IiTpy2NFlmFhJfxhPvPvfKtbTbbtEEMLj MhEQOYZ47NplHD1YinazcRBlA1jfxPNlmqcOg5N8V3b4Cq2lvC3dda1Qfmk_lxNrC1vlhBIFgQ9D bJIAIvODmbM0CAwwIr8nltEliDDiolvL0ukiZRwG8TpUjJyhoCittC.wE5hIK0ZawKt9jFywo4Ny PJuWkc.uMq64P0tgqQJS6dBICj5nnYuop8LCYHksmSkMjTP2QIU0NfFTOpQ-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.ir2.yahoo.com with HTTP; Tue, 2 Jun 2020 15:08:41 +0000 Date: Tue, 2 Jun 2020 15:08:38 +0000 (UTC) From: Oskar Holmlund To: Ian Lepore , "Dr. Rolf Jansen" Cc: freebsd-arm@freebsd.org Message-ID: <479317334.2616392.1591110518765@mail.yahoo.com> In-Reply-To: <5299B3F7-1C95-4769-9701-F13699FE355C@cyclaero.com> References: <966c33ea1924c2cfab5d9e295a9239d134e03f8a.camel@freebsd.org> <3CA84BA5-FEA8-4BD8-A713-C794139170EE@cyclaero.com> <840faedfcf7c3c09a372cf566acddd8ad876ff2b.camel@freebsd.org> <5299B3F7-1C95-4769-9701-F13699FE355C@cyclaero.com> Subject: Re: BeagleBone AI MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailer: WebService/1.1.16037 YMailNorrin Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0 X-Rspamd-Queue-Id: 49bwRJ0T31z44ww X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.62 / 15.00]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; RWL_MAILSPIKE_POSSIBLE(0.00)[87.248.110.31:from]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[yahoo.com]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.01)[-1.008]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; RCVD_IN_DNSWL_NONE(0.00)[87.248.110.31:from]; NEURAL_HAM_SHORT(-0.61)[-0.610]; NEURAL_HAM_MEDIUM(-1.01)[-1.006]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:34010, ipnet:87.248.110.0/24, country:GB]; RCVD_COUNT_TWO(0.00)[2]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2020 15:08:46 -0000 Den tisdag 2 juni 2020 16:56:02 CEST, Dr. Rolf Jansen skrev:=20 > Am 02.06.2020 um 10:49 schrieb Ian Lepore : >=20 > On Sun, 2020-05-31 at 16:56 -0300, Dr. Rolf Jansen wrote: >>> Am 31.05.2020 um 14:11 schrieb Ian Lepore : >>>=20 >>> On Fri, 2020-05-29 at 23:21 -0300, Dr. Rolf Jansen wrote: >>>> ... >>>>=20 >>>> First Question: >>>>=20 >>>> What modern SBC with more than 1 I=C2=B2C bus and which can run >>>> FreeBSD 13++ would you suggest? >>>>=20 >>>> ... >>>>=20 >>>> Two more Questions: >>>>=20 >>>> Is it reasonable to assume that FreeBSD would run on a BBAI in >>>> the future, let=C2=B4s say in 2 to 3 years? >>>>=20 >>>> Perhaps I could help porting FreeBSD to a BBAI. What would be the >>>> general steps? >>>>=20 >>>>=20 >>>> Many thanks in advance for any suggestions, advices and >>>> clarifications. >>>>=20 >>>> Best regards >>>>=20 >>>> Rolf >>>=20 >>> BTW, if you need drivers for any new i2c devices just let me know >>> and >>> I'll see what I can do. >>=20 >> I am pretty comfortable with register level programming, and so far I >> came away with ioctl() calls for what I needed. So perhaps I won=C2=B4t >> need exactly a driver for new I=C2=B2C devices. However, I am far away >> from being a perfect I=C2=B2C expert, specially when it comes to timing >> and the best sequence of addressing different devices on the bus. >> Perhaps, I may ask some questions when I run into problems. >>=20 >>> Also, in my experience you can often get away with running an i2c >>> bus >>> faster than 400khz if you need more bandwidth.=C2=A0 I've never seen an= y >>> modern chip fail to work at 800khz, and most seem to work fine up >>> to >>> about 1mhz; above that they become pretty unreliable. >>=20 >> Does this =E2=80=9Eover clocking=E2=80=9C work for the ARM boards as wel= l? I just set >> the clock-frequency in the dts-overlay which activates I2C1 of the >> BBB from 400000 to 800000. The bus seems to work as usual, however, I >> did not yet come to check its speed. How again would I do that? >> Probably there are many more questions to come :-) >>=20 >> Best regards >>=20 >> Rolf >=20 > I suspect it works on some boards and maybe won't work on others.=C2=A0 S= ome > SOCs have very flexible clock settings in their i2c controllers, a few > just allow choosing between fixed low and high speeds. >=20 > For experimenting, there is a sysctl dev.iicbus.#.frequency that you > can change on the fly (it will override any value from the dts).=C2=A0 Th= e > value is the frequency in hz. >=20 > -- Ian Thank you very much for your response. I checked the sysctl setting, and th= e system accepts the values. The bus works at 800000, however, I can set it= as high as 10000000 (10 MHz) and it is still working. Perhaps, there is so= me sort of internal validation before the frequency value is actually appli= ed to the HW. In the moment this is more a matter of curiosity than an actu= al need. Once we equipped the bus with all I=C2=B2C devices, we will perhap= s run into some timing issues, and then I probably want to revisit changing= the clock frequency again. Best reagrds Rolf _______________________________________________ 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" Expect no more than 1MHz https://svnweb.freebsd.org/base/head/sys/arm/ti/ti_i2c.c?revision=3D355727&= view=3Dmarkup Line 127+ //Oskar From owner-freebsd-arm@freebsd.org Tue Jun 2 15:23:05 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1977D2F2651 for ; Tue, 2 Jun 2020 15:23:05 +0000 (UTC) (envelope-from freebsd@cyclaero.com) Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [81.169.146.219]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49bwlq2K8Lz46XJ; Tue, 2 Jun 2020 15:23:02 +0000 (UTC) (envelope-from freebsd@cyclaero.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1591111381; s=strato-dkim-0002; d=cyclaero.com; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=etEEbtGdrpJRvO/Mjr6eDCGCi0pcpCJtSlznjHAynVc=; b=kn3z5qoMgxp9brfrq2UQFIgXSGIc0g8FKqUGlni11ik7ksNBH8WIepsF5ks9fdqZtg Sg+3BQGhlZ6CzASPjwOybHx0k8E0ihEWkkxIptVizc7hjScb9gd2f/Nz5AvvWiEFRUnv E6cgNdua5Y0k7RDMFiH8Ajz5ItImJ/lH97ZxGWi0SmHlkEa2pvpCW/XbipUJuaZuamcp GhfXpQOi7UAnRHEdB1UzbVD1ebB8+Eru9WvJWOpPHYpy95SelkGy+2iQGNSY/aBuKC+W h2/YMIOcn2QyH8aXbz+pJ6tvBTBWgmoio7qxk5V0vZEXcbjzodqqYvM8rYkeyLgxAlQD 39ig== X-RZG-AUTH: ":O2kGeEG7b/pS1F2rRHW2isrKl4DV03XBEi+I6ZuztdvN9wS3wFGySS4Lw+ldTBio0dVbInGjc9PbZFAm0A==" X-RZG-CLASS-ID: mo00 Received: from mail.obsigna.com by smtp.strato.de (RZmta 46.9.0 DYNA|AUTH) with ESMTPSA id I06cf5w52FMsOgx (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Tue, 2 Jun 2020 17:22:54 +0200 (CEST) Received: from rolf-mini.obsigna.com (rolf-mini.obsigna.com [192.168.222.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.obsigna.com (Postfix) with ESMTPSA id 3505F1350F91D; Tue, 2 Jun 2020 12:22:52 -0300 (-03) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: BeagleBone AI From: "Dr. Rolf Jansen" In-Reply-To: <479317334.2616392.1591110518765@mail.yahoo.com> Date: Tue, 2 Jun 2020 12:22:51 -0300 Cc: Ian Lepore , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <72C6B827-3F3E-4CB2-8987-C926602F755D@cyclaero.com> References: <966c33ea1924c2cfab5d9e295a9239d134e03f8a.camel@freebsd.org> <3CA84BA5-FEA8-4BD8-A713-C794139170EE@cyclaero.com> <840faedfcf7c3c09a372cf566acddd8ad876ff2b.camel@freebsd.org> <5299B3F7-1C95-4769-9701-F13699FE355C@cyclaero.com> <479317334.2616392.1591110518765@mail.yahoo.com> To: Oskar Holmlund X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 49bwlq2K8Lz46XJ X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cyclaero.com header.s=strato-dkim-0002 header.b=kn3z5qoM; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@cyclaero.com designates 81.169.146.219 as permitted sender) smtp.mailfrom=freebsd@cyclaero.com X-Spamd-Result: default: False [-1.58 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[81.169.146.219:from]; R_DKIM_ALLOW(-0.20)[cyclaero.com:s=strato-dkim-0002]; ARC_NA(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:81.169.146.128/25]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cyclaero.com]; NEURAL_HAM_LONG(-1.05)[-1.053]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[cyclaero.com:+]; NEURAL_HAM_SHORT(-0.41)[-0.411]; FROM_NAME_HAS_TITLE(1.00)[dr]; NEURAL_HAM_MEDIUM(-1.02)[-1.018]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6724, ipnet:81.169.144.0/22, country:DE]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[81.169.146.219:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2020 15:23:05 -0000 > Am 02.06.2020 um 12:08 schrieb Oskar Holmlund = : >> Den tisdag 2 juni 2020 16:56:02 CEST, Dr. Rolf Jansen = skrev:=20 >>> Am 02.06.2020 um 10:49 schrieb Ian Lepore : >>> On Sun, 2020-05-31 at 16:56 -0300, Dr. Rolf Jansen wrote: >>>>> Am 31.05.2020 um 14:11 schrieb Ian Lepore : >>>>>=20 >>>>> On Fri, 2020-05-29 at 23:21 -0300, Dr. Rolf Jansen wrote: >>>>>> ... >>>>>>=20 >>>>>> First Question: >>>>>>=20 >>>>>> What modern SBC with more than 1 I=C2=B2C bus and which can run >>>>>> FreeBSD 13++ would you suggest? >>>>>>=20 >>>>>> ... >>>>>>=20 >>>>>> Two more Questions: >>>>>>=20 >>>>>> Is it reasonable to assume that FreeBSD would run on a BBAI in >>>>>> the future, let=C2=B4s say in 2 to 3 years? >>>>>>=20 >>>>>> Perhaps I could help porting FreeBSD to a BBAI. What would be the >>>>>> general steps? >>>>>>=20 >>>>>>=20 >>>>>> Many thanks in advance for any suggestions, advices and >>>>>> clarifications. >>>>>>=20 >>>>>> Best regards >>>>>>=20 >>>>>> Rolf >>>>>=20 >>>>> BTW, if you need drivers for any new i2c devices just let me know >>>>> and >>>>> I'll see what I can do. >>>>=20 >>>> I am pretty comfortable with register level programming, and so far = I >>>> came away with ioctl() calls for what I needed. So perhaps I won=C2=B4= t >>>> need exactly a driver for new I=C2=B2C devices. However, I am far = away >>>> from being a perfect I=C2=B2C expert, specially when it comes to = timing >>>> and the best sequence of addressing different devices on the bus. >>>> Perhaps, I may ask some questions when I run into problems. >>>>=20 >>>>> Also, in my experience you can often get away with running an i2c >>>>> bus >>>>> faster than 400khz if you need more bandwidth. I've never seen = any >>>>> modern chip fail to work at 800khz, and most seem to work fine up >>>>> to >>>>> about 1mhz; above that they become pretty unreliable. >>>>=20 >>>> Does this =E2=80=9Eover clocking=E2=80=9C work for the ARM boards = as well? I just set >>>> the clock-frequency in the dts-overlay which activates I2C1 of the >>>> BBB from 400000 to 800000. The bus seems to work as usual, however, = I >>>> did not yet come to check its speed. How again would I do that? >>>> Probably there are many more questions to come :-) >>>>=20 >>>> Best regards >>>>=20 >>>> Rolf >>>=20 >>> I suspect it works on some boards and maybe won't work on others. = Some >>> SOCs have very flexible clock settings in their i2c controllers, a = few >>> just allow choosing between fixed low and high speeds. >>>=20 >>> For experimenting, there is a sysctl dev.iicbus.#.frequency that you >>> can change on the fly (it will override any value from the dts). = The >>> value is the frequency in hz. >>>=20 >>> -- Ian >>=20 >> Thank you very much for your response. I checked the sysctl setting, = and the system accepts the values. The bus works at 800000, however, I = can set it as high as 10000000 (10 MHz) and it is still working. = Perhaps, there is some sort of internal validation before the frequency = value is actually applied to the HW. In the moment this is more a matter = of curiosity than an actual need. Once we equipped the bus with all I=C2=B2= C devices, we will perhaps run into some timing issues, and then I = probably want to revisit changing the clock frequency again. >>=20 >> Expect no more than 1MHz >> = https://svnweb.freebsd.org/base/head/sys/arm/ti/ti_i2c.c?revision=3D355727= &view=3Dmarkup >> Line 127+ >>=20 >> //Oskar Ah, OK, that explains the finding. So perhaps the bus is really working = at 1 MHz. Thank you very much for the hint. Best regards Rolf= From owner-freebsd-arm@freebsd.org Tue Jun 2 16:46:32 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 450172F42B1 for ; Tue, 2 Jun 2020 16:46:32 +0000 (UTC) (envelope-from s199p.wa1k9r@gmail.com) Received: from mail-lj1-x242.google.com (mail-lj1-x242.google.com [IPv6:2a00:1450:4864:20::242]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49byc73LFpz4GC9 for ; Tue, 2 Jun 2020 16:46:31 +0000 (UTC) (envelope-from s199p.wa1k9r@gmail.com) Received: by mail-lj1-x242.google.com with SMTP id 9so11945312ljc.8 for ; Tue, 02 Jun 2020 09:46:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:in-reply-to:to; bh=bGv+8DQGG+qBH2CEBg1O1OmkVS2E3gZ6uxwMlAIhAns=; b=uT9zcjLJnIOnAi2pADZqqCOBl3mfEGsIZbX6i96aajb3KSeeLAB1p3RiE+wh+LODeg S+gY+OSld+NKbwB+sI1eJhNQWOWroogJ7pxxz5iPs4epzHev/ah0e9dfU/0vafkn+C7c x3mRaiJ0PnhBkmNw38gq8CzeTpchY8FFxUP93rE+w3Kb/6/1+L8pHTUNOxcSYJzH8C8W rQFlZQ0HjrdH8d5bffFP6h9bSwpE/+G+/BnReOlGFy2raXJqm0+Ed/Xs7SKAYwZFwk0M Hd1TuSZfip1UUFV6AvhbDAPgmpq7qIUrqHJBmFY3QDpH9hUaq4pUL3I4lp+niw558Cwe bLfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:in-reply-to:to; bh=bGv+8DQGG+qBH2CEBg1O1OmkVS2E3gZ6uxwMlAIhAns=; b=nWIXv7BkQjeOyhxgv3Jww6rJVjMGGp9r/vabxc0fyNfVBvPxZLve0AmTwUIgZ5jOiO 9slb2jgvAj/7Qk6MJB6Sr8pqLdUcF1cWjoApobtyc29v9ycdL+drM+PQAZyQehTcDBlL V6ekpMYKHmH04OgLEy9A0PqULwoDm2WHVsrE2iDYHLkWL/cHoCmKt5D643l7q90ia4E2 GIiZpkgrWVlRuTmq95tEy7sWmJpuAH+T2ULIgpAee4csG9+8W+rvVxgwfEjQhxz/QME3 +zPhFNw5a8RDcAsWfJKz6AKfUE5repmAcphb1xbDdZeiPRFMv50Y9QIDIOsuCFnTCNiu oDYg== X-Gm-Message-State: AOAM533LVXQp55wJlhaNcaiax3KcbGxKusVopeOundEH32sgGdz7lIdY 1Kv5xDa+Och7FS1e9yB63zryZ4zSljU= X-Google-Smtp-Source: ABdhPJx0dWkrrO7ZiVFJaB10uAmddZsb4IM8pQuG1DUD+ynhAuCrvK9T5l2QRurpdUlkPhZAi8F37Q== X-Received: by 2002:a2e:a54f:: with SMTP id e15mr15524ljn.263.1591116389336; Tue, 02 Jun 2020 09:46:29 -0700 (PDT) Received: from [212.192.133.131] ([212.192.133.131]) by smtp.gmail.com with ESMTPSA id o23sm955228lfg.0.2020.06.02.09.46.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 Jun 2020 09:46:28 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Sleep Walker Mime-Version: 1.0 (1.0) Subject: Re: Video on Pinebook-pro Date: Tue, 2 Jun 2020 19:46:26 +0300 Message-Id: <0676289C-128D-4302-BD02-E8F17B5BE102@gmail.com> References: <20200602104915.7fe4fa44ce19c5d0e6e69ac7@bidouilliste.com> In-Reply-To: <20200602104915.7fe4fa44ce19c5d0e6e69ac7@bidouilliste.com> To: Emmanuel Vadot , Free BSD X-Mailer: iPad Mail (17F75) X-Rspamd-Queue-Id: 49byc73LFpz4GC9 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=uT9zcjLJ; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of s199pwa1k9r@gmail.com designates 2a00:1450:4864:20::242 as permitted sender) smtp.mailfrom=s199pwa1k9r@gmail.com X-Spamd-Result: default: False [-2.85 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MV_CASE(0.50)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.32)[-0.324]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.002]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.02)[-1.021]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::242:from]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2020 16:46:32 -0000 Thanks for the tip. I tried building mainline u-boot. Everything is going, the system is loading, but the video does not work. Can anyone else have any ideas? Has anyone else tried? I really want Pinebook-pro to work under FreeBSD! Sergey Tyuryukanov. > 2 =D0=B8=D1=8E=D0=BD=D1=8F 2020 =D0=B3., =D0=B2 11:49, Emmanuel Vadot =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0): >=20 > =EF=BB=BFOn Tue, 2 Jun 2020 09:32:04 +0300 > Sleep Walker wrote: >=20 >> Hello everybody. >>=20 >> After u-boot.2020.04 was released,=20 >> I managed to launch Xorg via efifb on Khadas-EDGE-V and Radxa Rock-Pi4 (b= oth on RK3399).=20 >> But so far I have not been able to repeat this on Pinebook-pro. >> Maybe someone has patches to run video on Pinebook-pro? >>=20 >> Sergey Tyuryukanov >> _______________________________________________ >> 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 > Hi, >=20 > PinebookPro still need patches on top of what we have, I think I've > seen some on the u-boot ML but can't find them ATM. Pinebook Pro > support was merged yesterday in mainline iirc, maybe the patches needed > for eDP were too. >=20 > --=20 > Emmanuel Vadot From owner-freebsd-arm@freebsd.org Wed Jun 3 13:37:46 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 21463337829 for ; Wed, 3 Jun 2020 13:37:46 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail-40134.protonmail.ch (mail-40134.protonmail.ch [185.70.40.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49cVMs0Sc7z4P3D for ; Wed, 3 Jun 2020 13:37:44 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Wed, 03 Jun 2020 13:37:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1591191462; bh=APU+28SU/am/6senfVMF3dVk+zfkneT/5q4QqA+k5tY=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=ERP0ExN5muSdqqjiQj70w/SF3ZgVc9XnGqiaXvBz94eGTkYaM8FQyzcT6qm2/IGr6 lGKxwQCuq9eK3ibeJwA0u1ucPrxbAf1qKVLcoRaAQ0guUy+H8YOJgknOVZ/6TelN+B cvZKDCjeQPETrBUZDdoUm3uzIcPIfVWpkKzmShq8= To: myfreeweb From: Dan Kotowski Cc: freebsd-arm Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> References: <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49cVMs0Sc7z4P3D X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=ERP0ExN5; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.134 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-4.25 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; NEURAL_HAM_LONG(-1.04)[-1.037]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_MEDIUM(-1.01)[-1.015]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.134:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_SHORT(-1.10)[-1.096]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.134:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2020 13:37:46 -0000 > > > I've sent a link to a known firmware build before: > > > https://drive.google.com/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvErK/vie= w > > > Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe? > > > > I decided to go back to the UEFI sources and have found some difference= s that I think need to be reconciled before moving forward. That said, I'm = not an ACPI wizard by any means - for me it's low-level mage spells at best= ... > > In https://github.com/SolidRun/edk2-platforms we have 2 different branc= hes that SolidRun seems to use: > > > > 1. LSDK-19.09-sr > > 2. master-lx2160a > > > > I've been building from the latter branch, but found some significant d= ifferences in the former that I think may be important to merge in. > > To me it seems like 19.09 is just outdated and doesn't have any benefits.= Ask the solidrun people to be sure. > > Either way, nothing here would fix the interrupt bug. It's our bug since = NetBSD works fine :( Any chance I can get a new test kernel without PCIe quirks? I just got a mu= ch more recent image from jnettlet with the following comments: BEGIN QUOTE If you are using that recent uefi firmware I posted then you shouldn't be u= sing the quirks for pcie. That has an ecam shift setup where it should beh= ave....relatively to SBSA standards. it definitely won't work with the quirk enabled though. I have to add an i= nterface to edk2 to turn the mode on or off depending if you want access to= the root bus and have a kernel with the quirk applied, or you want it to w= ork with just the devices exposed but in a more compliant manner without qu= irks END QUOTE From owner-freebsd-arm@freebsd.org Wed Jun 3 16:09:49 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5760E33AD0F for ; Wed, 3 Jun 2020 16:09:49 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out1.migadu.com (out1.migadu.com [IPv6:2001:41d0:2:863f::]) (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 49cYlH5v8wz3Tgr for ; Wed, 3 Jun 2020 16:09:47 +0000 (UTC) (envelope-from greg@unrelenting.technology) Date: Wed, 03 Jun 2020 16:09:17 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1591200579; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=33hdMC7S1H8rjEK5ZtRigB/o9lEnPK7jqVoK0LDUcnE=; b=brEgt7WlSy51WMBsf73fwRul4CsO+K3ArRcm1HpKthb72x2aMxfXmDtxrnKSlZ5VK6C30+ MGrfqAC29LR0urxzUqyLgvTUj47YT55P1ze+7jJgP//jZZXQCCduK+AFnhxQgDA7vyMkRM UcqNdJ3iGOLk8ftfh13raVx7rjgxJOU= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: myfreeweb To: Dan Kotowski CC: freebsd-arm Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X In-Reply-To: References: <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> Message-ID: <49F29C72-F76C-46DA-920A-3148B4B0415A@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49cYlH5v8wz3Tgr X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=brEgt7Wl; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:863f:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.70 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.01)[-1.015]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:863f::]; NEURAL_HAM_LONG(-1.04)[-1.041]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; NEURAL_HAM_SHORT(-0.64)[-0.640]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2020 16:09:49 -0000 On June 3, 2020 1:37:34 PM UTC, Dan Kotowski wrote: >> > > I've sent a link to a known firmware build before: >> > > https://drive=2Egoogle=2Ecom/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvE= rK/view >> > > Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe? >> > >> > I decided to go back to the UEFI sources and have found some differen= ces that I think need to be reconciled before moving forward=2E That said, = I'm not an ACPI wizard by any means - for me it's low-level mage spells at = best=2E=2E=2E >> > In https://github=2Ecom/SolidRun/edk2-platforms we have 2 different b= ranches that SolidRun seems to use: >> > >> > 1=2E LSDK-19=2E09-sr >> > 2=2E master-lx2160a >> > >> > I've been building from the latter branch, but found some significant= differences in the former that I think may be important to merge in=2E >> >> To me it seems like 19=2E09 is just outdated and doesn't have any benef= its=2E Ask the solidrun people to be sure=2E >> >> Either way, nothing here would fix the interrupt bug=2E It's our bug si= nce NetBSD works fine :( > >Any chance I can get a new test kernel without PCIe quirks? I just got a = much more recent image from jnettlet with the following comments: > >BEGIN QUOTE >If you are using that recent uefi firmware I posted then you shouldn't be= using the quirks for pcie=2E That has an ecam shift setup where it should= behave=2E=2E=2E=2Erelatively to SBSA standards=2E >it definitely won't work with the quirk enabled though=2E I have to add = an interface to edk2 to turn the mode on or off depending if you want acces= s to the root bus and have a kernel with the quirk applied, or you want it = to work with just the devices exposed but in a more compliant manner withou= t quirks >END QUOTE In the last couple kernels I posted, you should be able to set debug=2Eacp= i=2Edisabled=3Dpci_layerscape to skip the quirk=2E I'll build the next one soon though, I guess with more interrupt debug pri= nts lol From owner-freebsd-arm@freebsd.org Wed Jun 3 17:51:54 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DC12133CCCD for ; Wed, 3 Jun 2020 17:51:54 +0000 (UTC) (envelope-from luke@lukeross.name) Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49cc154zszz4079 for ; Wed, 3 Jun 2020 17:51:53 +0000 (UTC) (envelope-from luke@lukeross.name) X-Originating-IP: 84.45.129.34 Received: from clara.lan (unknown [84.45.129.34]) (Authenticated sender: luke@lukeross.name) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 515CB6000C for ; Wed, 3 Jun 2020 17:51:51 +0000 (UTC) Message-ID: <75a918d07625de979e9995b3f01662c9deb0a9c1.camel@lukeross.name> Subject: Problems with cdce/cdceem as a USB-device on R-Pi From: Luke Ross To: freebsd-arm@freebsd.org Date: Wed, 03 Jun 2020 18:51:49 +0100 Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.2-0ubuntu1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49cc154zszz4079 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of luke@lukeross.name designates 217.70.183.195 as permitted sender) smtp.mailfrom=luke@lukeross.name X-Spamd-Result: default: False [-1.40 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; NEURAL_SPAM_SHORT(0.23)[0.229]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[217.70.183.195:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.71)[-0.707]; DMARC_NA(0.00)[lukeross.name]; R_SPF_ALLOW(-0.20)[+ip4:217.70.183.192/28]; NEURAL_HAM_MEDIUM(-0.53)[-0.526]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:29169, ipnet:217.70.176.0/20, country:FR]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[217.70.183.195:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2020 17:51:54 -0000 Hi, I have a plan to run FreeBSD on a Raspberry Pi Zero configured as a USB network device, attached to a USB host. I've booted the 12.1 image, and in theory it looks like it ought to be as simple as: /boot/loader.conf: hw.usb.template=8 If I do this, the Pi does indeed have an interface ue0, and the host recognises a new CDC-ether device. Configuring both ends with IPs is successful, but no packets can be passed between the two ends. The USB serial console works fine, so there is some USB connectivity, just not the cdce network. The same applies with hw.usb.template=1 (cdce with no serial). I then reconfigured with hw.usb.template=11 for cdceem connectivity. This is more successful - using the same IP configuration, packets pass between host and pi-device in the main without problem. Every 15 seconds or so, the link freezes for a few seconds and the pi logs: cdceem0: WARNING: cdceem_bulk_read_callback: USB_ST_ERROR: USB_ERR_STALLED Unfortunately this stall is frequent enough to make cdceem mode not useful for my use-case. Has anyone else got cdce device-mode working on a Pi, or knows hows to prevent the cdceem stall? I did experiment with using a 13-CURRENT image (same behaviour) and with FreeBSD or Linux hosts (same behaviour). I double-checked for any inadvertent firewalling on the host. The same sort of set-up works fine under Raspbian, so I don't believe it's a hardware fault. Any suggestions/pointers very much appreciated! Many thanks, Luke From owner-freebsd-arm@freebsd.org Wed Jun 3 18:14:25 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 19BBE33E105 for ; Wed, 3 Jun 2020 18:14:25 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49ccW16WTCz47RZ for ; Wed, 3 Jun 2020 18:14:21 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2020.home.selasky.org (unknown [62.141.129.235]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 2761B260B9E; Wed, 3 Jun 2020 20:14:09 +0200 (CEST) Subject: Re: Problems with cdce/cdceem as a USB-device on R-Pi To: Luke Ross , freebsd-arm@freebsd.org References: <75a918d07625de979e9995b3f01662c9deb0a9c1.camel@lukeross.name> From: Hans Petter Selasky Message-ID: Date: Wed, 3 Jun 2020 20:13:51 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <75a918d07625de979e9995b3f01662c9deb0a9c1.camel@lukeross.name> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49ccW16WTCz47RZ X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of hps@selasky.org designates 2a01:4f8:c17:6c4b::2 as permitted sender) smtp.mailfrom=hps@selasky.org X-Spamd-Result: default: False [-2.34 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net]; NEURAL_HAM_LONG(-1.01)[-1.014]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[selasky.org]; NEURAL_HAM_MEDIUM(-0.99)[-0.992]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.04)[-0.036]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2020 18:14:25 -0000 On 2020-06-03 19:51, Luke Ross wrote: > cdceem0: WARNING: cdceem_bulk_read_callback: USB_ST_ERROR: > USB_ERR_STALLED Try to have a look at the USB traffic using: usbdump -i usbusX -f Y -s 65536 At both client and server side. Might be a controller driver bug, or the chip is out of available endpoints, I.E. that you can only have either ethernet or serial, but not both. --HPS From owner-freebsd-arm@freebsd.org Wed Jun 3 23:40:56 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B18292F7797 for ; Wed, 3 Jun 2020 23:40:56 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out1.migadu.com (out1.migadu.com [IPv6:2001:41d0:2:863f::]) (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 49cllq5X4Lz441G for ; Wed, 3 Jun 2020 23:40:55 +0000 (UTC) (envelope-from greg@unrelenting.technology) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1591227653; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=T9nOyiaNkn1sYmDNl3dyXpm9UQp29YWUIgmA2zEtgEU=; b=XjHEBV+JCVkQFM1HfRcwRX7veTDZpVfNzeI9xk9/GbOGupR9PEmvfii84+KJH3NqRPSTg9 8oyq64iBkXSB+7MUwyCYqCB8xWw7/6eJ8316VYK+9WR8wpulqqWB4QUGRcBtmq6jNvqiv4 Tbt22+9K0c1aEP4opOYW1ZzzQjOHpFQ= Date: Wed, 03 Jun 2020 23:40:52 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: greg@unrelenting.technology Message-ID: <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: "Dan Kotowski" Cc: "freebsd-arm" In-Reply-To: <49F29C72-F76C-46DA-920A-3148B4B0415A@unrelenting.technology> References: <49F29C72-F76C-46DA-920A-3148B4B0415A@unrelenting.technology> <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49cllq5X4Lz441G X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=XjHEBV+J; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:863f:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.55 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.004]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:863f::]; NEURAL_HAM_LONG(-1.03)[-1.035]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-0.52)[-0.516]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2020 23:40:56 -0000 June 3, 2020 7:09 PM, "myfreeweb" wrote:=0A= =0A> On June 3, 2020 1:37:34 PM UTC, Dan Kotowski wrote:=0A> =0A>>>>> I've sent a link to a known firmware build = before:=0A>>>>> https://drive.google.com/file/d/1yXSS1O1U8CmtwaIPfxNDkzhA= ClJGvErK/view=0A>>>>> Have you tried it? Any difference in FreeBSD/NetBSD= , with NVMe?=0A>>>> =0A>>>> I decided to go back to the UEFI sources and = have found some differences that I think need to be=0A>>> reconciled befo= re moving forward. That said, I'm not an ACPI wizard by any means - for m= e it's=0A>>> low-level mage spells at best...=0A>>>> In https://github.co= m/SolidRun/edk2-platforms we have 2 different branches that SolidRun seem= s to=0A>>> use:=0A>>>> =0A>>>> 1. LSDK-19.09-sr=0A>>>> 2. master-lx2160a= =0A>>>> =0A>>>> I've been building from the latter branch, but found some= significant differences in the former=0A>>> that I think may be importan= t to merge in.=0A>>> =0A>>> To me it seems like 19.09 is just outdated an= d doesn't have any benefits. Ask the solidrun people=0A>>> to be sure.=0A= >>> =0A>>> Either way, nothing here would fix the interrupt bug. It's our= bug since NetBSD works fine :(=0A>> =0A>> Any chance I can get a new tes= t kernel without PCIe quirks? I just got a much more recent image=0A>> fr= om jnettlet with the following comments:=0A>> =0A>> BEGIN QUOTE=0A>> If y= ou are using that recent uefi firmware I posted then you shouldn't be usi= ng the quirks for=0A>> pcie. That has an ecam shift setup where it should= behave....relatively to SBSA standards.=0A>> it definitely won't work wi= th the quirk enabled though. I have to add an interface to edk2 to turn= =0A>> the mode on or off depending if you want access to the root bus and= have a kernel with the quirk=0A>> applied, or you want it to work with j= ust the devices exposed but in a more compliant manner=0A>> without quirk= s=0A>> END QUOTE=0A> =0A> In the last couple kernels I posted, you should= be able to set debug.acpi.disabled=3Dpci_layerscape=0A> to skip the quir= k.=0A> =0A> I'll build the next one soon though, I guess with more interr= upt debug prints lol=0A=0Ahttps://send.firefox.com/download/ae38fa3524649= 7c1/#AVSGMsnrM0YB2MSL7rRJRQ=0A=0A- customized pcie driver=0A+ https://rev= iews.freebsd.org/D25121=0A+ more interrupt debugging (stray interrupts, a= ll GIC config writes) From owner-freebsd-arm@freebsd.org Thu Jun 4 02:02:56 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3513A2FCCDD for ; Thu, 4 Jun 2020 02:02:56 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49cpvf5n0Nz4LrB for ; Thu, 4 Jun 2020 02:02:54 +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 05422o2D026597 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 3 Jun 2020 19:02:50 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id 05422owG026596; Wed, 3 Jun 2020 19:02:50 -0700 (PDT) (envelope-from fbsd) Date: Wed, 3 Jun 2020 19:02:50 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Ssh sessions running top keep disconnecting Message-ID: <20200604020250.GA26450@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 49cpvf5n0Nz4LrB X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [1.69 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.47)[-0.466]; NEURAL_HAM_LONG(-0.05)[-0.054]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(0.31)[0.311]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 02:02:56 -0000 For some reason, ssh sessions running top seem to be quitting with packet_write_wait: Connection to 50.1.20.25 port 22: Broken pipe I'm in the habit of leaving an ssh session running top going on machines running long jobs like world or port builds. On my Pi3 running 12.1-stable those sessions keep disconnecting. No other ssh sessions, among the four open, seem to be affected. The client is a Pi3b+ running raspberry pi os. It has a dozen or so ssh sessions open, no others are affected. Any ideas what might be going on? Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Thu Jun 4 02:39:49 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CBA362FDD8F for ; Thu, 4 Jun 2020 02:39:49 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic304-25.consmr.mail.gq1.yahoo.com (sonic304-25.consmr.mail.gq1.yahoo.com [98.137.68.206]) (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 49cqkD5FzVz4Q4y for ; Thu, 4 Jun 2020 02:39:48 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: 37fN2ggVM1lAfLZXu9MAow4uixP.0l9ssPYEZoaInJ7avnEGBFHo5itQyjQ0dxh 2lgftGtyJ7Lbzfy5DJW.v8UBSYrzt1LqBz5mEcCZjN3u0SRKFkODvBDUFOEg9PvqffFZjua7PEfc mfAG2gGHXixhGW71cNRXGuBmIm01iFXONMsosbm2gWXhX1kZX7wB8H_LrFijBEnEBYevrt7m3vQZ oXbwRj0sm.3grYbFw9jr7y1WCOvi5_2rXoSyuP9Sc6kH5wT1W_rc7D5XTKEeKMEhRzGJyoBGMCcj kys9jBCqZzD3hVEiDFzLpiarWVj3Db5hPZuEEoQABNibE9SmyNJpX9jN5.cMvfhE1KYyFKym2ZjE F5ZoY0iO2VRBfTY5ygIzwNP7ESrL5l3Q4U3Bvfl68fQDV1mBWPT6Dh4xqVXfWw3Gb1u6lSI5vr1X 7JajxZaF.0IMY04.Y8wUjCxBp906ooulH1eL02j.iMyN.wWfaYI.ZEUp4_GzMTsFie.5b5EW3Nxc a.WFDLrEa7qFJ3iMeEaeVLW6jGizito7m0zqhrQ14BjphpMZgpqYdq540umLJNE5qa54G6njGuMJ vcd5Lk.EdsewQbEfG1GLkespz9CYUpGVUzv5_Kf1BPv77DeV2HisElUcLKlFD4.AAx3ddwdgBKf8 KO.1Rq4_Bm.y.58VY4PVKo6i8WJ7ItDgm2TWdyFMJknOBN4e1Y7Yb5PU70UJJK41YOfTKU27kdQp mUq.RcNjIjxnhyXzPIZHb2sm1FjwTO.Oxcat4cyYxX2ddV_508b5zr3SrUB1rRQGnRrSrQB7o0qN ayhXZ2aa_5AKAWU9cNxhLU2X5MHPAaL_fO_1uHGoksxcRwhofzaO2ZDwjl1wXoyXDdUI9L5chaXc etMqU_JLPr5am6osYrIAdKr3oYm6qK9H3tNZkFXBsp6XHfSheKdb._Mtb5.agew1GD03Ue9LF58A mtP7Sj7Zl6ZxKXLKeprjfe4ZTpZVaH.UDtTeeOrHFV5KBWF0Sjbm0i0KrCtyy4MBkuc8Ab6JyfV3 tEwZV7lZNFcxYPdKWMyBo0bForUOnU1SJedNQFgCyjYlQ3FePCwMNn8lXt7w0UymNRCmvp19VVM2 mwTFzOFuUEbslTqM.kMVEL4CzgGaiDMOT.nsmtTazFLiOM2ydn7Q8YV8f6Akl5FHCyc7aKy._5cH 5HENYC2unPKet5qs9LcaVpn0900B9bJNadkZh8K5YU1US538_VdZXIitlYMS2Bi4H5tlA1pNkHyO JR1jVKNhGkW60RTXTRlu.XDq3l6QUj9_du31v9hFFupio5YWfX257mXdiA9Rnk_h2O0_fziTlRR_ Ela8Pn.KZhXzwa2KkVZ3iCYSLamjWNZ1gqPLCIKKEfmPWpuHEaAQSSCXgKB4CGZvmyii_sP.Ocfd c92TfF7UffUFZRVoXmOeiU1th1_w9pSLZin0nNpr3LQI0DArndA-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.gq1.yahoo.com with HTTP; Thu, 4 Jun 2020 02:39:47 +0000 Received: by smtp417.mail.gq1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 31dda218e6dacd03915b9d0de04e34fe; Thu, 04 Jun 2020 02:39:45 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Ssh sessions running top keep disconnecting From: Mark Millard In-Reply-To: <20200604020250.GA26450@www.zefox.net> Date: Wed, 3 Jun 2020 19:39:44 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <7A0C9F2C-734E-49F8-B533-B3B487588D71@yahoo.com> References: <20200604020250.GA26450@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49cqkD5FzVz4Q4y X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.22 / 15.00]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.68.206:from]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; NEURAL_HAM_LONG(-1.02)[-1.023]; NEURAL_HAM_MEDIUM(-1.01)[-1.006]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[98.137.68.206:from]; NEURAL_HAM_SHORT(-0.69)[-0.695]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 02:39:49 -0000 On 2020-Jun-3, at 19:02, bob prohaska wrote: > For some reason, ssh sessions running top seem to be quitting > with > packet_write_wait: Connection to 50.1.20.25 port 22: Broken pipe > > I'm in the habit of leaving an ssh session running top going on > machines running long jobs like world or port builds. On my Pi3 > running 12.1-stable those sessions keep disconnecting. No other > ssh sessions, among the four open, seem to be affected. > > The client is a Pi3b+ running raspberry pi os. It has a dozen > or so ssh sessions open, no others are affected. > > Any ideas what might be going on? > No clue. But a possible kind of experiment . . . top keeps its ssh connection in use on a rather frequent basis, even if the mount of traffic is not large. Try having some other ssh session into the 12.1 Stable FreeBSD system that also keeps its ssh connection in use on a rather frequent basis. Does it get the same issue as the top sessions do? (Need not be at the same times but if the times were near each other for failures that might indicate something.) Of course, it may be that some of your other ssh connections to the same system already do this test --or it may be they all rarely put their connection to use (compared to top). === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Thu Jun 4 11:40:20 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 90FDC336065 for ; Thu, 4 Jun 2020 11:40:20 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49d3jv3PPpz4W5G for ; Thu, 4 Jun 2020 11:40:19 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Thu, 04 Jun 2020 11:40:14 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1591270815; bh=ZQ1Cd4oJzXa6iA8BzdZRuT2umyBpu1y0I91fkE/vt2E=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=D+4yMvdaDi9Hdb2PNECNFlLP4jfxGPpmpHbMTE3ZGmfKwFVgOwMPd6AExjJhQAG9d RMdGibOAkmRbT7VPjmx66LZpJJ3EtPUAlyXENRKpsSWpFrcBp9hn2KxWH5hBf2y9bb odi8Ib+4CRZDUMWXYMWjFZqOZcPmR/9PLjIYyJAE= To: "greg@unrelenting.technology" From: Dan Kotowski Cc: freebsd-arm Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> References: <49F29C72-F76C-46DA-920A-3148B4B0415A@unrelenting.technology> <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49d3jv3PPpz4W5G X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=D+4yMvda; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.18 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-3.79 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; NEURAL_HAM_LONG(-1.02)[-1.018]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_SHORT(-0.72)[-0.716]; NEURAL_HAM_MEDIUM(-0.95)[-0.951]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[185.70.40.18:from]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.18:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 11:40:20 -0000 > https://send.firefox.com/download/ae38fa35246497c1/#AVSGMsnrM0YB2MSL7rRJR= Q > > - customized pcie driver > > - https://reviews.freebsd.org/D25121 > - more interrupt debugging (stray interrupts, all GIC config writes) https://gist.github.com/agrajag9/484cdd9c340a15f88be0fabbe2cf9b09 With NVMe attached it no longer panics, now it just hangs Loading mps still just loops And anything attached via AHCI is still MIA From owner-freebsd-arm@freebsd.org Thu Jun 4 12:56:56 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3295B2F225C for ; Thu, 4 Jun 2020 12:56:56 +0000 (UTC) (envelope-from hardik.sanepara@gmail.com) Received: from mail-qt1-x842.google.com (mail-qt1-x842.google.com [IPv6:2607:f8b0:4864:20::842]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49d5QH3mPdz3T0X for ; Thu, 4 Jun 2020 12:56:55 +0000 (UTC) (envelope-from hardik.sanepara@gmail.com) Received: by mail-qt1-x842.google.com with SMTP id z1so5089925qtn.2 for ; Thu, 04 Jun 2020 05:56:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=utBzZ262iyudqf6n8VjWQNtiFOEjU9SXtwjEPRUVUCc=; b=qpcadISbuPMHdqLHwylSx56Dq04q6pTf7VLGFVexht/M7taHyljWdsaUV7Kg0VsAC6 XOHzOXWXzuVkgiYNOrERukNQPW2Fm63LHyIwkD3ijq6xBUvbnq7vhHYIlINGQdXW5eCM UvZdkEnVUHcnIeZKHYpB51SmKO5y6SQiM2gHiwk/EDDZ+Wf8a5//LeA8QsLF1Vs1cNJj 4hLM0rOd3jnr3BiY+sld9z7ounvYVLhwbFgQndhVSl1Tz6RfFgXIx6gJk9m0Kfi89Qpl sseeDP+sqgjVJXagARmL0Ojnw9BKe+vtAadqPVg95acL7EDbu1YaKLBgCvjTros6eOKM z+Rg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=utBzZ262iyudqf6n8VjWQNtiFOEjU9SXtwjEPRUVUCc=; b=aAS5Ak8padwWZ8cXlvYCXni49EhzSm6FUClYQLobIZgBm4b7UYuXlbrp9VSRBPPK69 7ef6HG9AYEJnB6RxV4dKzFiH4X9JokzuZ7vnBoSYckTyUr4JZ+owfZlpE4GmIZeBYMIR nJgeGPHOTKzxGTMZNG2WwQfBQvr7iEWP7rMXvEMttbq8JMLsVAaPGcuQax7GZNtkZa0g zCVm+iNaVBVqzpxfPNxNKeUbxPwG59JfvdsrbXI9X1TgvQbaG8OtXifiz8SSsKF/UlaQ zA48OMZPGF7gH4oqyXxROqFlOIb/IzDpUIRPfm0yiRfRYGHCZYqRXMF7ddz+odyk/8lw wMIA== X-Gm-Message-State: AOAM530/kTOAgRZW0uHTvPmjaMpLvrlmBqxxUpRWLq7e0sRPNYP1ZOyC 963Zwahs4ecjzi4XEQmfeFwD2BBhzrBYK8o8lwKJ73N4 X-Google-Smtp-Source: ABdhPJx9crGKg06ih25vONH2l3WQ6jnxfF35f4A9tNs19U3XXt6Y0mEadhajfcI/wNkWhrl/RQdmJg7eokIxAMKNqXs= X-Received: by 2002:ac8:312e:: with SMTP id g43mr4333926qtb.308.1591275414228; Thu, 04 Jun 2020 05:56:54 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:aed:2ac7:0:0:0:0:0 with HTTP; Thu, 4 Jun 2020 05:56:53 -0700 (PDT) In-Reply-To: References: From: Sanepara Hardik Date: Thu, 4 Jun 2020 18:26:53 +0530 Message-ID: Subject: Re: freebsd-arm Digest, Vol 736, Issue 5 To: freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 49d5QH3mPdz3T0X X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=qpcadISb; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of hardiksanepara@gmail.com designates 2607:f8b0:4864:20::842 as permitted sender) smtp.mailfrom=hardiksanepara@gmail.com X-Spamd-Result: default: False [-3.73 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-0.99)[-0.987]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.98)[-0.982]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::842:from]; NEURAL_HAM_SHORT(-0.76)[-0.758]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 12:56:56 -0000 Hi Team, I would like to unsubscribe mail. Please remove my mail id from your mail list. Thanks, Regards, Hardik On 6/4/20, freebsd-arm-request@freebsd.org wrote: > Send freebsd-arm mailing list submissions to > freebsd-arm@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > or, via email, send a message with subject or body 'help' to > freebsd-arm-request@freebsd.org > > You can reach the person managing the list at > freebsd-arm-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-arm digest..." > > > Today's Topics: > > 1. Re: FreeBSD on Layerscape/QorIQ LX2160X (Dan Kotowski) > 2. Re: FreeBSD on Layerscape/QorIQ LX2160X (myfreeweb) > 3. Problems with cdce/cdceem as a USB-device on R-Pi (Luke Ross) > 4. Re: Problems with cdce/cdceem as a USB-device on R-Pi > (Hans Petter Selasky) > 5. Re: FreeBSD on Layerscape/QorIQ LX2160X > (greg@unrelenting.technology) > 6. Ssh sessions running top keep disconnecting (bob prohaska) > 7. Re: Ssh sessions running top keep disconnecting (Mark Millard) > 8. Re: FreeBSD on Layerscape/QorIQ LX2160X (Dan Kotowski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 03 Jun 2020 13:37:34 +0000 > From: Dan Kotowski > To: myfreeweb > Cc: freebsd-arm > Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X > Message-ID: > > > Content-Type: text/plain; charset=UTF-8 > >> > > I've sent a link to a known firmware build before: >> > > https://drive.google.com/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvErK/view >> > > Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe? >> > >> > I decided to go back to the UEFI sources and have found some differences >> > that I think need to be reconciled before moving forward. That said, I'm >> > not an ACPI wizard by any means - for me it's low-level mage spells at >> > best... >> > In https://github.com/SolidRun/edk2-platforms we have 2 different >> > branches that SolidRun seems to use: >> > >> > 1. LSDK-19.09-sr >> > 2. master-lx2160a >> > >> > I've been building from the latter branch, but found some significant >> > differences in the former that I think may be important to merge in. >> >> To me it seems like 19.09 is just outdated and doesn't have any benefits. >> Ask the solidrun people to be sure. >> >> Either way, nothing here would fix the interrupt bug. It's our bug since >> NetBSD works fine :( > > Any chance I can get a new test kernel without PCIe quirks? I just got a > much more recent image from jnettlet with the following comments: > > BEGIN QUOTE > If you are using that recent uefi firmware I posted then you shouldn't be > using the quirks for pcie. That has an ecam shift setup where it should > behave....relatively to SBSA standards. > it definitely won't work with the quirk enabled though. I have to add an > interface to edk2 to turn the mode on or off depending if you want access to > the root bus and have a kernel with the quirk applied, or you want it to > work with just the devices exposed but in a more compliant manner without > quirks > END QUOTE > > > ------------------------------ > > Message: 2 > Date: Wed, 03 Jun 2020 16:09:17 +0000 > From: myfreeweb > To: Dan Kotowski > Cc: freebsd-arm > Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X > Message-ID: > <49F29C72-F76C-46DA-920A-3148B4B0415A@unrelenting.technology> > Content-Type: text/plain; charset=utf-8 > > > > On June 3, 2020 1:37:34 PM UTC, Dan Kotowski > wrote: >>> > > I've sent a link to a known firmware build before: >>> > > https://drive.google.com/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvErK/view >>> > > Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe? >>> > >>> > I decided to go back to the UEFI sources and have found some >>> > differences that I think need to be reconciled before moving forward. >>> > That said, I'm not an ACPI wizard by any means - for me it's low-level >>> > mage spells at best... >>> > In https://github.com/SolidRun/edk2-platforms we have 2 different >>> > branches that SolidRun seems to use: >>> > >>> > 1. LSDK-19.09-sr >>> > 2. master-lx2160a >>> > >>> > I've been building from the latter branch, but found some significant >>> > differences in the former that I think may be important to merge in. >>> >>> To me it seems like 19.09 is just outdated and doesn't have any benefits. >>> Ask the solidrun people to be sure. >>> >>> Either way, nothing here would fix the interrupt bug. It's our bug since >>> NetBSD works fine :( >> >>Any chance I can get a new test kernel without PCIe quirks? I just got a >> much more recent image from jnettlet with the following comments: >> >>BEGIN QUOTE >>If you are using that recent uefi firmware I posted then you shouldn't be >> using the quirks for pcie. That has an ecam shift setup where it should >> behave....relatively to SBSA standards. >>it definitely won't work with the quirk enabled though. I have to add an >> interface to edk2 to turn the mode on or off depending if you want access >> to the root bus and have a kernel with the quirk applied, or you want it >> to work with just the devices exposed but in a more compliant manner >> without quirks >>END QUOTE > > > In the last couple kernels I posted, you should be able to set > debug.acpi.disabled=pci_layerscape to skip the quirk. > > I'll build the next one soon though, I guess with more interrupt debug > prints lol > > > ------------------------------ > > Message: 3 > Date: Wed, 03 Jun 2020 18:51:49 +0100 > From: Luke Ross > To: freebsd-arm@freebsd.org > Subject: Problems with cdce/cdceem as a USB-device on R-Pi > Message-ID: > <75a918d07625de979e9995b3f01662c9deb0a9c1.camel@lukeross.name> > Content-Type: text/plain; charset="UTF-8" > > Hi, > > I have a plan to run FreeBSD on a Raspberry Pi Zero configured as a USB > network device, attached to a USB host. > > I've booted the 12.1 image, and in theory it looks like it ought to be > as simple as: > > /boot/loader.conf: hw.usb.template=8 > > If I do this, the Pi does indeed have an interface ue0, and the host > recognises a new CDC-ether device. Configuring both ends with IPs is > successful, but no packets can be passed between the two ends. The USB > serial console works fine, so there is some USB connectivity, just not > the cdce network. The same applies with hw.usb.template=1 (cdce with no > serial). > > I then reconfigured with hw.usb.template=11 for cdceem connectivity. > This is more successful - using the same IP configuration, packets pass > between host and pi-device in the main without problem. Every 15 > seconds or so, the link freezes for a few seconds and the pi logs: > > cdceem0: WARNING: cdceem_bulk_read_callback: USB_ST_ERROR: > USB_ERR_STALLED > > Unfortunately this stall is frequent enough to make cdceem mode not > useful for my use-case. > > Has anyone else got cdce device-mode working on a Pi, or knows hows to > prevent the cdceem stall? I did experiment with using a 13-CURRENT > image (same behaviour) and with FreeBSD or Linux hosts (same > behaviour). I double-checked for any inadvertent firewalling on the > host. The same sort of set-up works fine under Raspbian, so I don't > believe it's a hardware fault. > > Any suggestions/pointers very much appreciated! > > Many thanks, > > Luke > > > > > > ------------------------------ > > Message: 4 > Date: Wed, 3 Jun 2020 20:13:51 +0200 > From: Hans Petter Selasky > To: Luke Ross , freebsd-arm@freebsd.org > Subject: Re: Problems with cdce/cdceem as a USB-device on R-Pi > Message-ID: > Content-Type: text/plain; charset=utf-8; format=flowed > > On 2020-06-03 19:51, Luke Ross wrote: >> cdceem0: WARNING: cdceem_bulk_read_callback: USB_ST_ERROR: >> USB_ERR_STALLED > > Try to have a look at the USB traffic using: > > usbdump -i usbusX -f Y -s 65536 > > At both client and server side. Might be a controller driver bug, or the > chip is out of available endpoints, I.E. that you can only have either > ethernet or serial, but not both. > > --HPS > > > ------------------------------ > > Message: 5 > Date: Wed, 03 Jun 2020 23:40:52 +0000 > From: greg@unrelenting.technology > To: "Dan Kotowski" > Cc: "freebsd-arm" > Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X > Message-ID: <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> > Content-Type: text/plain; charset="utf-8" > > June 3, 2020 7:09 PM, "myfreeweb" wrote: > >> On June 3, 2020 1:37:34 PM UTC, Dan Kotowski >> wrote: >> >>>>>> I've sent a link to a known firmware build before: >>>>>> https://drive.google.com/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvErK/view >>>>>> Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe? >>>>> >>>>> I decided to go back to the UEFI sources and have found some >>>>> differences that I think need to be >>>> reconciled before moving forward. That said, I'm not an ACPI wizard by >>>> any means - for me it's >>>> low-level mage spells at best... >>>>> In https://github.com/SolidRun/edk2-platforms we have 2 different >>>>> branches that SolidRun seems to >>>> use: >>>>> >>>>> 1. LSDK-19.09-sr >>>>> 2. master-lx2160a >>>>> >>>>> I've been building from the latter branch, but found some significant >>>>> differences in the former >>>> that I think may be important to merge in. >>>> >>>> To me it seems like 19.09 is just outdated and doesn't have any >>>> benefits. Ask the solidrun people >>>> to be sure. >>>> >>>> Either way, nothing here would fix the interrupt bug. It's our bug since >>>> NetBSD works fine :( >>> >>> Any chance I can get a new test kernel without PCIe quirks? I just got a >>> much more recent image >>> from jnettlet with the following comments: >>> >>> BEGIN QUOTE >>> If you are using that recent uefi firmware I posted then you shouldn't be >>> using the quirks for >>> pcie. That has an ecam shift setup where it should behave....relatively >>> to SBSA standards. >>> it definitely won't work with the quirk enabled though. I have to add an >>> interface to edk2 to turn >>> the mode on or off depending if you want access to the root bus and have >>> a kernel with the quirk >>> applied, or you want it to work with just the devices exposed but in a >>> more compliant manner >>> without quirks >>> END QUOTE >> >> In the last couple kernels I posted, you should be able to set >> debug.acpi.disabled=pci_layerscape >> to skip the quirk. >> >> I'll build the next one soon though, I guess with more interrupt debug >> prints lol > > https://send.firefox.com/download/ae38fa35246497c1/#AVSGMsnrM0YB2MSL7rRJRQ > > - customized pcie driver > + https://reviews.freebsd.org/D25121 > + more interrupt debugging (stray interrupts, all GIC config writes) > > > ------------------------------ > > Message: 6 > Date: Wed, 3 Jun 2020 19:02:50 -0700 > From: bob prohaska > To: freebsd-arm@freebsd.org > Subject: Ssh sessions running top keep disconnecting > Message-ID: <20200604020250.GA26450@www.zefox.net> > Content-Type: text/plain; charset=us-ascii > > For some reason, ssh sessions running top seem to be quitting > with > packet_write_wait: Connection to 50.1.20.25 port 22: Broken pipe > > I'm in the habit of leaving an ssh session running top going on > machines running long jobs like world or port builds. On my Pi3 > running 12.1-stable those sessions keep disconnecting. No other > ssh sessions, among the four open, seem to be affected. > > The client is a Pi3b+ running raspberry pi os. It has a dozen > or so ssh sessions open, no others are affected. > > Any ideas what might be going on? > > Thanks for reading, > > bob prohaska > > > > > > ------------------------------ > > Message: 7 > Date: Wed, 3 Jun 2020 19:39:44 -0700 > From: Mark Millard > To: bob prohaska > Cc: freebsd-arm@freebsd.org > Subject: Re: Ssh sessions running top keep disconnecting > Message-ID: <7A0C9F2C-734E-49F8-B533-B3B487588D71@yahoo.com> > Content-Type: text/plain; charset=us-ascii > > > > On 2020-Jun-3, at 19:02, bob prohaska wrote: > >> For some reason, ssh sessions running top seem to be quitting >> with >> packet_write_wait: Connection to 50.1.20.25 port 22: Broken pipe >> >> I'm in the habit of leaving an ssh session running top going on >> machines running long jobs like world or port builds. On my Pi3 >> running 12.1-stable those sessions keep disconnecting. No other >> ssh sessions, among the four open, seem to be affected. >> >> The client is a Pi3b+ running raspberry pi os. It has a dozen >> or so ssh sessions open, no others are affected. >> >> Any ideas what might be going on? >> > > No clue. But a possible kind of experiment . . . > > top keeps its ssh connection in use on a rather > frequent basis, even if the mount of traffic is > not large. > > Try having some other ssh session into the 12.1 > Stable FreeBSD system that also keeps its ssh > connection in use on a rather frequent basis. > Does it get the same issue as the top sessions > do? (Need not be at the same times but if the > times were near each other for failures that > might indicate something.) > > Of course, it may be that some of your other ssh > connections to the same system already do this > test --or it may be they all rarely put their > connection to use (compared to top). > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > > > > ------------------------------ > > Message: 8 > Date: Thu, 04 Jun 2020 11:40:14 +0000 > From: Dan Kotowski > To: "greg@unrelenting.technology" > Cc: freebsd-arm > Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X > Message-ID: > > > Content-Type: text/plain; charset=UTF-8 > >> https://send.firefox.com/download/ae38fa35246497c1/#AVSGMsnrM0YB2MSL7rRJRQ >> >> - customized pcie driver >> >> - https://reviews.freebsd.org/D25121 >> - more interrupt debugging (stray interrupts, all GIC config writes) > > https://gist.github.com/agrajag9/484cdd9c340a15f88be0fabbe2cf9b09 > > With NVMe attached it no longer panics, now it just hangs > > Loading mps still just loops > > And anything attached via AHCI is still MIA > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > 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" > > > ------------------------------ > > End of freebsd-arm Digest, Vol 736, Issue 5 > ******************************************* > From owner-freebsd-arm@freebsd.org Thu Jun 4 13:12:12 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B4B222F2243 for ; Thu, 4 Jun 2020 13:12:12 +0000 (UTC) (envelope-from jral@posteo.no) Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.posteo.de", Issuer "StartCom Class 3 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49d5lv5fygz3VtG for ; Thu, 4 Jun 2020 13:12:11 +0000 (UTC) (envelope-from jral@posteo.no) Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id C85AD16005F for ; Thu, 4 Jun 2020 15:12:08 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.no; s=2017; t=1591276328; bh=t+TrgJNGkvESfTB11dIFjGgBfruFy76eRHalo8D3E1w=; h=Date:From:To:Cc:Subject:OpenPGP:Autocrypt:From; b=VAxD9CR2ZSM0+kapWhwoeO/wfw1bPRPeFEVyMKWuq/yFExJfPbjqpxQFVtBTP7Vu9 2I/9lTbQcc8e68a2RY/fbF65yxQl1gSNKUCXIFGgG7/D6vhtaW4dPI9Cxwtf/oK4FN fHLMyeoa3S4J1AQZvZLqo0flp/idGkUTiHDojo7j6ffj5CFcpAwk7RVuLqvAHsN37f hk40/Yk3Ax0z57U6kIrgS8v9n0myRFR1g/jcIEK5b9qKP3NSIJphiGqFWvoHAk5zwk FDusKIMCAPeMIdZ4iVwdLDK0dcauFNxrDlivcvth9blhWuuC3A6GwVIJvIf+pDwxQD CqXQL70yJvQRA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 49d5lr1SGWz9rxH; Thu, 4 Jun 2020 15:12:08 +0200 (CEST) Date: Thu, 4 Jun 2020 15:12:05 +0200 From: Rasmus Liland To: Sanepara Hardik Cc: freebsd-arm@freebsd.org Subject: Re: freebsd-arm Digest, Vol 736, Issue 5 Message-ID: <20200604131205.GA1509@posteo.no> Reply-To: Rasmus Liland Mail-Followup-To: Sanepara Hardik , freebsd-arm@freebsd.org References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cNdxnHkX5QqsyA0e" Content-Disposition: inline In-Reply-To: OpenPGP: id=60D8AF998267F318; url=https://posteo.de/keys/jral@posteo.no.asc; preference=signencrypt Autocrypt: addr=jral@posteo.no; keydata=xsFNBF6y+HEBEAC63X654anyYS3fBvUK27vsfx02kEAgVsjs+DpUc5cdGqaM5pxgao6kb95KBwjeloSow1REHtrWCmB2oj+e2wCmX+K7eRLegX+Qf/IhAEqVC4iGzxocIa+VhT9lyb1XcpyoXYVvyrX9ZMVIWQD6ryu4doOZ/V7RvET8vnvhDeIdbiHTwZHhzUXDJwIA4oqOk0OkgYwkdL8CFxk6tH9f7T0A9/Nxh+av3aYLxg0HMLD/EB+eEwwdsLib1IesxYajHU1BhB/iq/6onFzVNj9n9eK6ib5gl7tPCuJG/HxMGOmpPySOkxFv3KbRU8zdfGVMpa39WeIN/HA6x4ZB1LT7AaSdkGrPNh0OcyOfuCQOyoVqGJSCG36e0Or+SHvn5LFC+F1JzTHO4ll/Q5GzwGEcHz2ZcHUPdakTmhFgWB6G7XHogedfiCxlD45h0z2aV38fWYfN/Mv0dp7Ko9it4iE6MAVmJqwN24gGCuJgT6axkiuZubXz8gKInuUXMFjHDbfzTS4DVpTCwVOWMduy3wKExm4QwVdkc6j1y4cMqEGIeU1oUqLXkttI09yF9Ku6qQ342ChUG7rl7UjcgHAyAS9DSWECo5htjDag8ZAGJLDXLj1Awco3Zc5VQyXtybrnvw7U9IyggqFiif95TqFMzaiqroDYLvwBHfQFDNhq8EhbyOu6kwARAQABzQ5qcmFsQHBvc3Rlby5ub8LBjgQTAQgAOBYhBH7463CrvBvvT5+ZAGDYr5mCZ/MYBQJesvhxAhsDBQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAAAoJEGDYr5mCZ/MYYDIQAIDndDGIKaXzpM/JgOqKeKSXS7qB3eo4cFCl5xPPlnEmTAbLd3Gin9k4blQBmSMomTS1Jk6iS0QXhi3LdQ7DhfsqsO8z4XDjNgeOmPN94QdJloFgbPgWs2onGjMTEW A0Fbc0zRhj99e65FPmB6OV9htKeoPQvKxIVxcPd+WkAI277zJRe+A+U/+2LN2/ucJHC2Mpmi53CSI7nCoQeolgm577sDaECsnpuWB6IPbn4IkRFQsk0Uir7i3sRdITDypgO8sP/6HcNll4bUvEL8iI7cOU0De2kqXnYCMsozAr9uBLEmYE8QqR+UeZr3aDCXXvGi84GpbCSZ5x4xxXXfR3MHB5ofhw3QtghEFd37pr948WfjCzQDQF6uvo7sh2dwp6nNpGrrhk2jy29dgClw0m8uFlh/1vZ/tcRorOm31taNlEHj8YmTnX9g2u0JP4nalEUNiUU4mLFOc3eFQiVO6QfKPLDNezv6ctIwECRQ1gwaqrEc8Ue8kh40h+6DSXZOX6hHXAwKIZ5BHwtjHP/iGtjPk17jXzKxXTEAQ+f5/5DCUyIxFn8mSmQ4UJHhSYAg0zk+VzUsJCMFdGV8qlKwAGAK0gN7YzO+cLeeIBX7FZXEM4k0i8knTQKmH3gHJ7pAg6purB37A1zB74SQMZH5JhTnGEcU9ORym+zlpCMiG5P5ixzsFNBF6y+HEBEACsi1YPqFYARjKUPrHpS3MpmHSPEmoD9lZmwFjyV6Z1PSPBDZe1cGnimcoUQjN8lcRQDvFQyKW+oa1HVDsfQAxyyY4OPfABUZ9OsAuI9FznwCKAmAMoVVOmkEj0786MqqGPG7/4ZuivQ/Norn2T0RmVUHwI9gurDl9mK3jOiSLHQM2LcGqSD28I6y41TqmzophkIhfqjGgCD5vnFwTZ2+CW53xPxyY2qQoPeJiMY4jJl8mk9Y+cD1EHdQYtKrlLr5GJNFqs8jn9eQJbiqVDYiffwWGZJUZOeexxKuuZbHkRAtuz0+01g1OK6zaD+E4anjuOlq/m+3RrewhBfrvvxDr4xqRQaeE6mMHsP1C4RBtaJfu4ct+lXN/rsKpp+USea+2dUmz3qPCaFEzPP+SWVs9dybJNeHzHbyiAfDoe0SN zx0dkyhWYaHfjYb8YGqy09Ffqq722qZgAtZsHVaSG1HI4/ZwLr5E0dhtANwNz/k2JHqtaUl9eEnvzQXKoxlLkMkrjcNeepasQl2cXzb/09pXSb95sPay5/4FTGGtJ5NTjStF1FqeJHVOrfoMlHL5bVtXDUPVHdVsZpitKNYn3JWOpB0J5iljp/nAW30dolO5nFtA2kZ4/7bv+xaOsUObsqI6DIL89XDMLWDjKlegD/7VR8TJIJeKEOefQxVU+cDZcIQARAQABwsF2BBgBCAAgFiEEfvjrcKu8G+9Pn5kAYNivmYJn8xgFAl6y+HECGwwACgkQYNivmYJn8xh0dxAAmEIYtVjZg2NyOhYLJEszT0j6qvP2rz/0cwphgbIAxShioRnQnWBQM1TuyG3BtyHEQ4OAWwh+pvmObd2yREYRIKIpjirKmevX2AIEPClhDyNyXdND0LOvjrLLxzgGhoxv794N9jjbd2DwxiYHnuFFfJ9ZWz51zxb89DjArLu/6JA2SmRegK8puYkWFk0nzAxEwFDoFRBMB9GRptPQf05+LSbIqWcXDR+8Ytzt8hS7gwQRm3dra9auZT6iOjNNJpwHc9VMmMfXUZjXGdzyCADJFK5WfwCnwyfen1QLJ6OeEUZor3RrmpjzHZATttr7I0FCmBY49bdE5d8zWVd65hSn4M9Q63RPi0QPUR3BjnztDGbEzsxnT+ulvky/3xbfRfIV3sQmKm9LmwMsjRWu71mBf6xv6EQnwrdRrQ4bF2f1YAzYh9ooRjnPHer3u7PDI6hOniKV8SyRQVrP7VtIpOwu9Oyvfe+uAlTZzXgLATyLbTu0GYawZJvsIwC+RckU1Kxw/86dbE30WKwitWihZnIKn/wXUN0wTlnXToC05CDZCwL5AkoSYPyHTmxcHU7okISCyQOdaFCsT8Dt3Ukw4YwJySHUu6HGtZBiIcsdWU5wgqhDiOzCAU5MDvn9xXRn0lu/wYPuoiLXqkNFcpyd 6WlcRAKATYrjSPc2CGYODmDZK+w= X-Rspamd-Queue-Id: 49d5lv5fygz3VtG X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=posteo.no header.s=2017 header.b=VAxD9CR2; dmarc=pass (policy=none) header.from=posteo.no; spf=pass (mx1.freebsd.org: domain of jral@posteo.no designates 185.67.36.65 as permitted sender) smtp.mailfrom=jral@posteo.no X-Spamd-Result: default: False [-6.44 / 15.00]; HAS_REPLYTO(0.00)[jral@posteo.no]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.67.36.0/23]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCVD_COUNT_THREE(0.00)[3]; RCVD_IN_DNSWL_MED(-0.20)[185.67.36.65:from]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[posteo.no,none]; DKIM_TRACE(0.00)[posteo.no:+]; SIGNED_PGP(-2.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; NEURAL_HAM_SHORT(-0.71)[-0.712]; ASN(0.00)[asn:8495, ipnet:185.67.36.0/23, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.978]; R_DKIM_ALLOW(-0.20)[posteo.no:s=2017]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-0.95)[-0.947]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 13:12:12 -0000 --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2020-06-04 18:26 +0530, Sanepara Hardik wrote: > Hi Team, >=20 > I would like to unsubscribe mail. Please=20 > remove my mail id from your mail list. Dear Hardik, just send a mail to=20 freebsd-arm-request@freebsd.org with Subject line "unsubscribe" Best, Rasmus --cNdxnHkX5QqsyA0e Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEfvjrcKu8G+9Pn5kAYNivmYJn8xgFAl7Y8yIACgkQYNivmYJn 8xiN9Q//Thv1xPQr9GOKYNrfDYyJTc5zuXBeiqCMlatfG8j8dzDE1cPwTGiLywn+ 1GUSmUivU3qtIcGkX3ELhnJGi6nwo9dwXO4TKOpkfnJ4Fak0iGdJLPUZ11sCTajT MUufvzREY84I91WYG/DXcrSoDcX8fCjUxcV1eLxO4fQzlj049dP5xmthv14h90/o 6o5K29lxDdISHDVfNCm2/MaJMEi03zcYaqFwRmim0g2pWqPX3K+BnKt8c7Qkm/zj ixO0bS7aTVFnN6uPQiH0T8GJQfzm55ZS+M2dZ/jAKW7d82aNxBe3LkrOSqCXgWWh eSn8dP82d5IjBNHypaZEjTg+pCCkeTEvzW2UE8pAueGN2BPtZ61GfTXWWQ2gyd/m bStBMrCDEQdOdHRLwCaoHHnH0Hw7JB3llQaXeovCnfhjfGG7kZRn1zUl7Wzz3KOu hxQKzwvlIXqDiha1/zKiEEfaNs6fBzT9vU0BpYZbZwVx2XUaiSR0+fBLibFw5+My tnVTpStCmd4fSxKpjSaRSxF4fd/jAp2uK3XV4i11h3lLJPReK36hCij8dOtgR6rc VN4S+/b+Op1vSdvjocW2RD1+wKO83wc9TXrvWEOVSOiZCjuFCXAC+iRypig7MAwV R69W38Rkz2CcCsRI+1KUQNMQaY9bF8chlkiQbOeVe+dsYVHimaA= =ZO1R -----END PGP SIGNATURE----- --cNdxnHkX5QqsyA0e-- From owner-freebsd-arm@freebsd.org Thu Jun 4 13:15:26 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 32F3E2F29D5 for ; Thu, 4 Jun 2020 13:15:26 +0000 (UTC) (envelope-from dsl@mcusim.org) Received: from trac.mcusim.org (trac.mcusim.org [IPv6:2a00:dd80:3c::e63]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49d5qd2Vqdz3W7L for ; Thu, 4 Jun 2020 13:15:25 +0000 (UTC) (envelope-from dsl@mcusim.org) Received: from ds-laptop (unknown [IPv6:2a01:115f:77c:6700:b15d:520:8553:d458]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by trac.mcusim.org (Postfix) with ESMTPSA id 313EC25227; Thu, 4 Jun 2020 15:15:18 +0200 (CEST) Date: Thu, 4 Jun 2020 15:15:16 +0200 From: Dmitry Salychev To: Sanepara Hardik Cc: freebsd-arm@freebsd.org Subject: Re: freebsd-arm Digest, Vol 736, Issue 5 Message-ID: <20200604131516.GB6250@ds-laptop> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Unknown/0.75.1 X-Rspamd-Queue-Id: 49d5qd2Vqdz3W7L X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.05 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.03)[-1.026]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; NEURAL_HAM_LONG(-0.94)[-0.940]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.79)[-0.787]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[mcusim.org,reject]; MID_RHS_NOT_FQDN(0.50)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:36236, ipnet:2a00:dd80:3c::/48, country:US]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 13:15:26 -0000 Hi, feel free to send anything to "freebsd-arm-unsubscribe@freebsd.org" to unsubscribe from this mailing list. Regards, Dmitry From owner-freebsd-arm@freebsd.org Thu Jun 4 13:29:22 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F09B22F2FFB for ; Thu, 4 Jun 2020 13:29:22 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 49d67k4zQRz3Xy1 for ; Thu, 4 Jun 2020 13:29:22 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id A8F5C2F32EA; Thu, 4 Jun 2020 13:29:22 +0000 (UTC) Delivered-To: arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A8B812F314E for ; Thu, 4 Jun 2020 13:29:22 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lj1-f170.google.com (mail-lj1-f170.google.com [209.85.208.170]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49d67j4Klvz3Y4s for ; Thu, 4 Jun 2020 13:29:21 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lj1-f170.google.com with SMTP id m18so7278729ljo.5 for ; Thu, 04 Jun 2020 06:29:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:resent-from:resent-to:resent-date :resent-message-id:to:from:subject:openpgp:autocrypt:message-id:date :user-agent:mime-version:content-language:content-transfer-encoding; bh=Y/BUyFpuVrNXDcACiNRwfdAjfyXT6rderOVb2UNDUH4=; b=SwweERR+QDi+TGxuKGCDVypNF3fsT95ghSDOJTif7O+61keO1FeSiMI/rY7ZBnvRTi Psatr6BLtLsGhFQJmsgOgtiQ687kj1zkiDC99uQGQ02ij3dj3rnPQwxb5A3Zqamrdvrq kIMroGtvRCVZ2qntfazVFkCYOrTd779KIROWE8ldppcXuUSdj355d7cPbfXj5d1uVkqX B8iC5zyC9XX3+4Q4S4g5VBUJaKpqtqG0/zeR14ZGOKxmToTtdSwqFVx7xKb3MXinTdXQ 0+2ndTuA8s0T6nQi3t1/oJIJz8C10dJlRyXHrAmRhA2b39iSmEwvGNfP9uwV8j/LDf/K Pj8Q== X-Gm-Message-State: AOAM533H8tcF7o57vXLk6JVNgQ+ORwtZWgr6V1b+1a8qoY/qi4f533Br xpEEVmW/f1KOn71tLO4TupNc6EixSpc= X-Google-Smtp-Source: ABdhPJypxf/1DUG0wT5o10PTHvKjIyrQHHigCqRTPJLoEh89Svp9QkwMajrKh05CTqLLz5AMjz8WoA== X-Received: by 2002:a2e:9987:: with SMTP id w7mr2324933lji.242.1591277359052; Thu, 04 Jun 2020 06:29:19 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id w17sm1441839ljj.108.2020.06.04.06.29.18 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 04 Jun 2020 06:29:18 -0700 (PDT) Resent-From: Andriy Gapon Resent-To: arm@FreeBSD.org Resent-Date: Thu, 4 Jun 2020 16:29:18 +0300 Resent-Message-ID: To: arm@FreeBSD.org, mips@FreeBSD.org From: Andriy Gapon Subject: upcoming change to iicbb Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= mQINBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABtB5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz6JAlQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryLkCDQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAYkCPAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <0f177c25-7c18-86ab-51e4-718e8626734b@FreeBSD.org> Date: Thu, 4 Jun 2020 15:50:46 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Firefox/60.0 Thunderbird/60.9.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 49d67j4Klvz3Y4s X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of agapon@gmail.com designates 209.85.208.170 as permitted sender) smtp.mailfrom=agapon@gmail.com X-Spamd-Result: default: False [-2.69 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[arm@freebsd.org]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[FreeBSD.org]; NEURAL_HAM_LONG(-0.97)[-0.970]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.74)[-0.740]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.170:from]; NEURAL_HAM_MEDIUM(-0.98)[-0.983]; FORGED_SENDER(0.30)[avg@FreeBSD.org,agapon@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.170:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[avg@FreeBSD.org,agapon@gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[93.72.151.96:received] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 13:29:23 -0000 If you are using the I²C bit-banging driver (iicbb) in any form (e.g., via gpioiic) you could be interested in a change that I am planning to commit very soon: https://reviews.freebsd.org/D22206 This is quite a big change to the bit-banging is done. Its goals are to improve speeds and robustness. I will appreciate any reviews, testing or other feedback. Thank you. -- Andriy Gapon From owner-freebsd-arm@freebsd.org Thu Jun 4 14:31:47 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 44EC62F5F86 for ; Thu, 4 Jun 2020 14:31:47 +0000 (UTC) (envelope-from nikolay.kostirya@i11.co) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 49d7Wk6dsSz3yXD for ; Thu, 4 Jun 2020 14:31:46 +0000 (UTC) (envelope-from nikolay.kostirya@i11.co) Received: by mailman.nyi.freebsd.org (Postfix) id E3DC72F5C13; Thu, 4 Jun 2020 14:31:46 +0000 (UTC) Delivered-To: arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E3A6C2F5D96 for ; Thu, 4 Jun 2020 14:31:46 +0000 (UTC) (envelope-from nikolay.kostirya@i11.co) Received: from mx.i11.co (mx.i11.co [159.69.78.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49d7Wg42cGz3yX6; Thu, 4 Jun 2020 14:31:43 +0000 (UTC) (envelope-from nikolay.kostirya@i11.co) Received: from [178.93.57.97] (helo=localhost) by mx.i11.co with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jgqu8-00063a-EN; Thu, 04 Jun 2020 14:31:36 +0000 Date: Thu, 4 Jun 2020 17:31:33 +0300 From: Nick Kostirya To: Andriy Gapon Cc: arm@FreeBSD.org Subject: Re: upcoming change to iicbb Message-ID: <20200604173133.7cd5b4c0@i11.co> In-Reply-To: <0f177c25-7c18-86ab-51e4-718e8626734b@FreeBSD.org> References: <0f177c25-7c18-86ab-51e4-718e8626734b@FreeBSD.org> X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; i386-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 49d7Wg42cGz3yX6 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE]; REPLY(-4.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 14:31:47 -0000 Will it work on FreeBSD 12.1-STABLE as well? I have two sensors that do not work with gpioiic, but work with hardware ii= c... Perhaps this patch will be useful to them. On Thu, 4 Jun 2020 15:50:46 +0300 Andriy Gapon wrote: > If you are using the I=C2=B2C bit-banging driver (iicbb) in any form (e.g= ., via > gpioiic) you could be interested in a change that I am planning to commit= very > soon: https://reviews.freebsd.org/D22206 > This is quite a big change to the bit-banging is done. Its goals are to = improve > speeds and robustness. >=20 > I will appreciate any reviews, testing or other feedback. > Thank you. > --=20 > Andriy Gapon > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Thu Jun 4 14:45:39 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E39432F6527; Thu, 4 Jun 2020 14:45:39 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49d7ql02QZz412Y; Thu, 4 Jun 2020 14:45:38 +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 054EjdfS028266 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 4 Jun 2020 07:45:40 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id 054Ejdli028265; Thu, 4 Jun 2020 07:45:39 -0700 (PDT) (envelope-from fbsd) Date: Thu, 4 Jun 2020 07:45:39 -0700 From: bob prohaska To: bob prohaska Cc: freebsd-ports@freebsd.org, freebsd-arm@freebsd.org Subject: Re: 'asm/hwcap.h' file not found building chromium on Pi3 Message-ID: <20200604144539.GB26450@www.zefox.net> References: <20200601022208.GA15761@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 49d7ql02QZz412Y X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [1.43 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.31)[-0.314]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(0.38)[0.383]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.54)[-0.536]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 14:45:40 -0000 On Sun, May 31, 2020 at 09:05:36PM -0700, Mark Millard via freebsd-ports wrote: > > > On 2020-May-31, at 19:22, bob prohaska wrote: > > > Made another attempt to compile www/chromium on a Pi3B, this time using > > a mechanical hard disk for all storage (and boot). It stopped with > > > > ../../third_party/zlib/cpu_features.c:32:10: fatal error: 'asm/hwcap.h' file not found > > #include > > ^~~~~~~~~~~~~ > > 1 error generated. > > > > Ports are at Revision: 537041, uname -a reports 12.1-STABLE r361429 > > GENERIC arm64. All make commands used -DBATCH. > > > chromium does not seem to support FreeBSD of itself > so it seems the problem would be considered to be > in the port instead. > The ports were updated to 537591, which seems to have updated www/chromium to chromium-83.0.4103.61, but the error persists. Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Thu Jun 4 14:55:49 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7F83D2F60F5 for ; Thu, 4 Jun 2020 14:55:49 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49d83S5l0Vz42HZ for ; Thu, 4 Jun 2020 14:55:48 +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 054EtobW028301 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 4 Jun 2020 07:55:50 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id 054EtoJb028300; Thu, 4 Jun 2020 07:55:50 -0700 (PDT) (envelope-from fbsd) Date: Thu, 4 Jun 2020 07:55:50 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org Subject: Re: Ssh sessions running top keep disconnecting Message-ID: <20200604145550.GC26450@www.zefox.net> References: <20200604020250.GA26450@www.zefox.net> <7A0C9F2C-734E-49F8-B533-B3B487588D71@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7A0C9F2C-734E-49F8-B533-B3B487588D71@yahoo.com> X-Rspamd-Queue-Id: 49d83S5l0Vz42HZ X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [1.87 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.35)[-0.348]; NEURAL_SPAM_SHORT(0.13)[0.132]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.18)[0.182]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 14:55:49 -0000 On Wed, Jun 03, 2020 at 07:39:44PM -0700, Mark Millard wrote: > > > On 2020-Jun-3, at 19:02, bob prohaska wrote: > > > For some reason, ssh sessions running top seem to be quitting > > with > > packet_write_wait: Connection to 50.1.20.25 port 22: Broken pipe > > > > I'm in the habit of leaving an ssh session running top going on > > machines running long jobs like world or port builds. On my Pi3 > > running 12.1-stable those sessions keep disconnecting. No other > > ssh sessions, among the four open, seem to be affected. > > > > The client is a Pi3b+ running raspberry pi os. It has a dozen > > or so ssh sessions open, no others are affected. > > > top keeps its ssh connection in use on a rather > frequent basis, even if the mount of traffic is > not large. > > Try having some other ssh session into the 12.1 > Stable FreeBSD system that also keeps its ssh > connection in use on a rather frequent basis. > Does it get the same issue as the top sessions > do? (Need not be at the same times but if the > times were near each other for failures that > might indicate something.) > Tried leaving a gstat session running to keep the top session company while attempting to compile www/chromium. Both stayed up. The build of www/chromium failed, after running all night, with the missing asm/hwcap.h error. 8-( Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Thu Jun 4 15:05:05 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8FFA62F68EA for ; Thu, 4 Jun 2020 15:05:05 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 49d8G925Q8z42jR for ; Thu, 4 Jun 2020 15:05:05 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id 45A152F6AAB; Thu, 4 Jun 2020 15:05:05 +0000 (UTC) Delivered-To: arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 445B42F60ED for ; Thu, 4 Jun 2020 15:05:05 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lj1-f195.google.com (mail-lj1-f195.google.com [209.85.208.195]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49d8G76Bkmz42v2 for ; Thu, 4 Jun 2020 15:05:03 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lj1-f195.google.com with SMTP id c17so7690730lji.11 for ; Thu, 04 Jun 2020 08:05:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=6jPVcgAf0AKZ20jzcHU2KBfTLKA0DSBqJohoWkrwdQ4=; b=AKUs3XwwzKQI3Sh+TmLmRDq8lAgbqhlwOd8lb7P5j1b6P86pLEbWyr7ca1Yg4GlRAR B2qd9byp1UzWyemqQV1iNrW/Bh2nfJT64KFTyy3PCVt9vunKbxBQfFai2EMcJvKKbndj m3y5+ulkibTdeifOnea1SVZGAvtlKl3fPBdj2aCLYbyu6JtQpURbyJoWnJDFtbTajmxY TR1wEcTIk4iKBUjHzjZE7G3aquJ/JtPxusk59n9jMutI5Vcy+s1ORSGEG379QglV1CJi Da0xOMfNKBYAAJ1Hi03TBHKEbDvRGjRdjMNfnk3Ulc7x8C714K7TQkQdzFN+R3buEVU3 j7Yw== X-Gm-Message-State: AOAM5319AFIsF3hiwV6WJ/AW+TVx3zegCZJTjAO9FudOqmhArlAjUu9V 28atlQ29hm/WLVUWnRYxgTt6f8l1jIA= X-Google-Smtp-Source: ABdhPJzt1IYsvaUW3h1LyLAnmFrByOq2vCuXZOA9zR7TsDL46ziMPmNG2HLV7aHU3sxPjiSMJ2gAwA== X-Received: by 2002:a2e:968a:: with SMTP id q10mr2268643lji.192.1591283101830; Thu, 04 Jun 2020 08:05:01 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id c7sm1234087ljj.109.2020.06.04.08.05.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 04 Jun 2020 08:05:01 -0700 (PDT) Subject: Re: upcoming change to iicbb To: Nick Kostirya Cc: arm@FreeBSD.org References: <0f177c25-7c18-86ab-51e4-718e8626734b@FreeBSD.org> <20200604173133.7cd5b4c0@i11.co> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= mQINBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABtB5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz6JAlQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryLkCDQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAYkCPAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: Date: Thu, 4 Jun 2020 18:05:00 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Firefox/60.0 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20200604173133.7cd5b4c0@i11.co> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 49d8G76Bkmz42v2 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of agapon@gmail.com designates 209.85.208.195 as permitted sender) smtp.mailfrom=agapon@gmail.com X-Spamd-Result: default: False [-2.50 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-0.96)[-0.959]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[arm@freebsd.org]; ARC_NA(0.00)[]; DMARC_NA(0.00)[FreeBSD.org]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.59)[-0.594]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.195:from]; NEURAL_HAM_MEDIUM(-0.95)[-0.945]; FORGED_SENDER(0.30)[avg@FreeBSD.org,agapon@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.195:from]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[avg@FreeBSD.org,agapon@gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[93.72.151.96:received] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 15:05:05 -0000 On 04/06/2020 17:31, Nick Kostirya wrote: > Will it work on FreeBSD 12.1-STABLE as well? > > I have two sensors that do not work with gpioiic, but work with hardware iic... > Perhaps this patch will be useful to them. I think that the code should be close enough between branches for the patch to apply. If you could test it, that would be great! > On Thu, 4 Jun 2020 15:50:46 +0300 > Andriy Gapon wrote: > >> If you are using the I²C bit-banging driver (iicbb) in any form (e.g., via >> gpioiic) you could be interested in a change that I am planning to commit very >> soon: https://reviews.freebsd.org/D22206 >> This is quite a big change to the bit-banging is done. Its goals are to improve >> speeds and robustness. >> >> I will appreciate any reviews, testing or other feedback. >> Thank you. >> -- >> Andriy Gapon >> _______________________________________________ >> 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" -- Andriy Gapon From owner-freebsd-arm@freebsd.org Thu Jun 4 16:39:01 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 248D7329252 for ; Thu, 4 Jun 2020 16:39:01 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out0.migadu.com (out0.migadu.com [94.23.1.103]) (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 49dBLX0xy4z4FV0 for ; Thu, 4 Jun 2020 16:38:59 +0000 (UTC) (envelope-from greg@unrelenting.technology) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1591288732; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=RppyXD1n5LSoYkrzWULJpJMFhnQpbP0ib/i8qow+QMw=; b=bBwdisFv1WeGQ7CEt4l7iW9sSG4epnJqoFK/41g4DJNy6hdpPPtV3hTc+LQvQ49lRzxmdS UB1ZDyqWS36Fp7xYJ6JLC+UF1bemKB4CaNVQV9KQ/3qMltdF7fWAF3wT5LCnB2tFEh8Msq RoW5MO5gtAOE1YXiQV6eDl/4Zx+7Wgk= Date: Thu, 04 Jun 2020 16:38:51 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: greg@unrelenting.technology Message-ID: <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: "Dan Kotowski" Cc: "freebsd-arm" In-Reply-To: References: <49F29C72-F76C-46DA-920A-3148B4B0415A@unrelenting.technology> <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49dBLX0xy4z4FV0 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=bBwdisFv; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 94.23.1.103 as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.79 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.980]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; R_SPF_ALLOW(-0.20)[+ip4:94.23.1.103]; NEURAL_HAM_LONG(-1.01)[-1.008]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-0.81)[-0.805]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[94.23.1.103:from]; ASN(0.00)[asn:16276, ipnet:94.23.0.0/16, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 16:39:01 -0000 June 4, 2020 2:40 PM, "Dan Kotowski" wro= te:=0A=0A>> https://send.firefox.com/download/ae38fa35246497c1/#AVSGMsnrM= 0YB2MSL7rRJRQ=0A>> =0A>> - customized pcie driver=0A>> =0A>> - https://re= views.freebsd.org/D25121=0A>> - more interrupt debugging (stray interrupt= s, all GIC config writes)=0A> =0A> https://gist.github.com/agrajag9/484cd= d9c340a15f88be0fabbe2cf9b09=0A> =0A> With NVMe attached it no longer pani= cs, now it just hangs=0A> =0A> Loading mps still just loops=0A> =0A> And = anything attached via AHCI is still MIA=0A=0AOops, I've been adding some = debug prints to gicv2 not gicv3.=0A=0AOne thing I noticed is the interest= ing irq number the nvme admin queue gets..=0Ait's the same as gic_nirqs.= =0A=0Agic0: SPIs: 288, IDs: 65535=0Anvme0: attempting to allocate 17 MSI-= X vectors (33 supported)=0Anvme0: using IRQs 21-37 for MSI-X=0Aacpi0: all= ocating via sysres: res 0xfffffd0000726280, start 21 + count 1 - 1 =3D? e= nd 21=0Aintr_setup_irq(): irq 288 add handler error 0 on nvme0=0A=0Amaybe= that's just like.. the first ITS handled interrupt?=0A(funnily enough, N= etBSD lists MSIs as IRQs starting from 8192)=0A=0A=0AMore SATA debugging:= https://send.firefox.com/download/9de5357a2e58edd9/#s9ZaU_k2NHlO-tLdyGk5= iA From owner-freebsd-arm@freebsd.org Thu Jun 4 18:11:58 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A73A032BB11 for ; Thu, 4 Jun 2020 18:11:58 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-qt1-x842.google.com (mail-qt1-x842.google.com [IPv6:2607:f8b0:4864:20::842]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49dDPp0Zdfz4S7x for ; Thu, 4 Jun 2020 18:11:57 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-qt1-x842.google.com with SMTP id g18so6040317qtu.13 for ; Thu, 04 Jun 2020 11:11:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=SeYnsMNjVX5Sn8rZkxVk/7c8XZwUHck4DMtpxIBW4u0=; b=hTd72nTAxDSFkLbuItMCjnEKMKUHWEHTdCXqTxYt8jqoJPfezj6CgdU738fJJgodBA HFXPT+xYL3qYEW/IUIUQ0KA92pTdjJw8NjceQyDSEfKFt3eXaVw+DiH9wQ+LItcIkbs4 hThfl+gQW/BUC0ZDvICGz0/Y+86gTilDRVTYNLs3e+LbVsQcnUbvr1YwRSzh4asddcGs EqDhemClpLHXQa3NgeKNnzP4Hb7cUk5WJoj7ZBPxSHe/HHqLa2LwjFxDaP7XwNDDpw43 uf87gCl7jhBtZF55GKXglaCvbBcsKAvz3iA9SMV+B08cOvszIWqafnRYXMaVUNd/j1o1 Jgvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=SeYnsMNjVX5Sn8rZkxVk/7c8XZwUHck4DMtpxIBW4u0=; b=HDTFVn2L/TEDgkgUX6pqY68fNZ9B5G39ObKbzQU6AiyQ4JmjuoWxZUat/rZfjcYpUd uvZPJ00c9kSptjqnb3ik+Q8TSyp6NPl3creda6JF17Hl/Tn34o5C8ehRfMvKOL0lbCAx qkwl6rRoD9em3y7YCAY02zKKCxE9vNN3RfNnG5z82pX+MjHvaGZ4YhLhEie3Svg0Od4p fNKStdkAp7+OGWEKBf0ovSXYMLGNIE+ehgriOLQKZWQ2B+LotAIOcfnOW3jYEA39Za5k 4xbdh9kBzt2GNCLhHZUZ23kFX31cng94nT3jqfM+dy5wX7k2qaIU4KaV5rJSZLjhpb3l p1EA== X-Gm-Message-State: AOAM530ErgRgzSf/j6dW977WYXxF+HDnWeNXC9TOI/guVPdHsfsSmETW m+nncMj4kYDZkS4gTT8rHH+XkS4t+8w9yl0Kfm17kQ== X-Google-Smtp-Source: ABdhPJzTD6AVTkyJ6LM/IKeuVj/zWae8LHRcSa2A+c2pEjeOe7CfxmVdfgCJ5RQKLpVMPzlGjQlQIok0ZpPVsBnR7dw= X-Received: by 2002:ac8:42c3:: with SMTP id g3mr5741707qtm.313.1591294317112; Thu, 04 Jun 2020 11:11:57 -0700 (PDT) MIME-Version: 1.0 References: <0532198F-B7DE-46A2-B262-6358EE8370E1@FreeBSD.org> <9F7FB8F8-A29C-4F95-B0BB-CFEFEAFDDD5E@FreeBSD.org> <1039B382-2CA4-4F49-9F95-08BD1386A447@FreeBSD.org> <092721df6b1de3e75820acd32ba1b0e7@unrelenting.technology> <461d8d1da4ad0c03e0f3a256e4ff4b77@unrelenting.technology> <22fff3856f9f1b5c6e47119bd5eef376@unrelenting.technology> In-Reply-To: From: Marcin Wojtas Date: Thu, 4 Jun 2020 20:11:45 +0200 Message-ID: Subject: Re: Bootable image for Macchatobin Double Shot? To: Greg V Cc: Mark Murray , freebsd-arm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 49dDPp0Zdfz4S7x X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=semihalf-com.20150623.gappssmtp.com header.s=20150623 header.b=hTd72nTA; dmarc=none; spf=none (mx1.freebsd.org: domain of mw@semihalf.com has no SPF policy when checking 2607:f8b0:4864:20::842) smtp.mailfrom=mw@semihalf.com X-Spamd-Result: default: False [-1.05 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.981]; R_DKIM_ALLOW(-0.20)[semihalf-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.21)[0.214]; NEURAL_HAM_LONG(-0.98)[-0.978]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[semihalf.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[semihalf-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::842:from]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 18:11:58 -0000 Hi Greg, =C5=9Br., 29 kwi 2020 o 18:59 Marcin Wojtas napisa=C5=82(= a): > > Hi, > > pon., 27 kwi 2020 o 19:16 napisa=C5=82(a): > > > > April 27, 2020 7:24 PM, "Marcin Wojtas" wrote: > > > > > Mark, Greg, > > > > > > Let me chip in, as I noticed my home dir in the logs :) > > > > > > sob., 25 kwi 2020 o 21:21 Mark Murray napisa=C5= =82(a): > > >> On 25 Apr 2020, at 19:01, greg@unrelenting.technology wrote: > > >>> I've started an attempt at porting the onboard NIC driver last summ= er: > > >>> https://github.com/myfreeweb/pepevtwo-kmod > > > > > > As you might have noticed, the NIC is pretty complex - one controller > > > consists of a common part with 3 ports capable of working in multiple > > > 1/10G modes, common parsing and buffer management engines. All this > > > has to be put into iflib. I once evaluated expected effort - I'd love > > > to have it in FreeBSD, but it is too big for a hobby project... > > > > LinuxKPI helps with running some of the Linux driver code as-is, for wh= at > > that's worth. > > > > Last time I was looking at the code, what I really didn't understand > > is the mapping between iflib and Linux's API.. > > Maybe it's a path worth exploring, but not sure if it's feasible and I > didn't find examples for the network drivers. > > > > > > > About PCIE controller deficiency - with the Designware IP, the > > > endpoint is replicated on all 32 BUS#0 devices, only if it's a simple > > > present on BDF 0.0.0. This is why we need 'filtering' in the config > > > space accessors. As in Linux ACPI version of the pcie-host-generic fo= r > > > ARM is frozen and no quirks allowed, so the trick with iATU windows > > > was applied in ACPI. It works for cards, such as E1000e, GT730, SATA > > > controllers, etc., but for more complex ones or PCIE switches it's a > > > dead end - this is why the default ACPI settings does not work for > > > your cards. > > > > I've noticed that the "simple" card I have (SATA) is recognized by EFI'= s > > `pci` command as "legacy". Maybe the window quirk could be applied in E= DK2 > > only if it sees that flag? > > > > (Super fun case though: while most of the cards I have don't get replic= ated > > at all, the Radeon HD 7970 gets replicated as *two* devices.) > > Did you see any other issues with the 'pci' command in edk2? If yes, > let's take it offline (or move to edk2 list). > > > > > > There were multiple attempts to handle it in firmware > > > (address translation, address trapping in EL3), but none worked fine. > > > Same issue is problematic on the Socionext Synquacer platform, which > > > uses the same PCIE IP. > > > > Wasn't there some success with some kind of address magic on the Synqua= cer? > > > > > I would really prefer that everyone used the top of tree > > > edk2/edk2-platforms version of the MacchiatoBin port. IMO a good > > > compromise would be having a variable (preferably in the boot menu), > > > that allowed to set non-quirked PCIE ACPI description and SPCR, that > > > would work with the vanilla FreeBSD. I can provide you with the > > > binaries for testing, once submitting patches. What do you think? > > > > Yes, boot menu toggles are my preferred solution too > > (other than the "legacy" check above I guess), > > if you can do it upstream, that would be great! > > > > Not sure when exactly, but I'll inform you directly for testing/review. > > > --- > > > > My builds are already basically top of tree EDK2 + non-quirked tables: > > https://github.com/myfreeweb/edk2-platforms/commits/master > > https://github.com/myfreeweb/edk2/commits/master > > > > however, I still use Marvell's fork of TrustedFirmware-A, > > since TF-A upstream really doesn't work for me: > > - fails to start in weird ways when built with clang > > - fails checksum when booted from an SD card > > - otherwise, proceeds to EDK2, but then > > FreeBSD panics during boot, when sleeping CPUs or something > > (sometimes during "Root mount waiting for: CAM") > > > > And the Marvell version has *none* of these problems. > > I've studied the diff between them in Marvell-related directories, > > found no significant difference o_0 > > > > --- > > Well, I just built today's edk2/edk2-platforms + top of upstream > ARM-TF (a couple of commits above v2.3 tag) and it works flawlessly > with centos/debian and Marvell SDK Linux I have in hand. Afair, for > MacchiatoBin there was no outstanding, not upstreamed code. Update - I had a long debug, as it turned out that on top of the vanilla ATF, the FreeBSD crashes on the SMP boot (no issues with Linux though). But after merging my patch it finally works and can be used: https://github.com/ARM-software/arm-trusted-firmware/commit/03363af888 The SDK did extra modification in the generic psci code, which obviously couldn't be merged upstream, however with above all OSs boot just fine. My todos around McBin and FreeBSD, related to the edk2: - update device tree - with pure v5.6 DT, FreeBSD boots fine. With the older one that is currently in edk2-platforms, it fails to allocate irqs for some devices, so it seems like bindings do not match. - add boot options to withdraw ecam quirk in ACPI and the SPCR hack. Will keep you posted. Regards, Marcin > > > > > In other news, I have the PMU (pmcstat) working with ACPI: > > https://reviews.freebsd.org/D24423 > > > > > > Also, I've noticed suspend-to-RAM support in TF-A code :) > > Does that work on Linux? How would I tell it to wake up > > if there's no power button on the mcbin? > > No. > > > Would a USB keyboard interrupt wake it up? > > I didn't play with suspend to ram on it. For sure it works on A37xx, > I'd need to check the pmops in the EL3 firmware to make entirely sure. > > Best regards, > Marcin From owner-freebsd-arm@freebsd.org Thu Jun 4 21:37:38 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8706A333082 for ; Thu, 4 Jun 2020 21:37:38 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch [185.70.40.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49dJz34JJrz41s1 for ; Thu, 4 Jun 2020 21:37:33 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Thu, 04 Jun 2020 21:37:26 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1591306650; bh=yPNjIjZgmgwrpR5vjLkEzZFuxAKmBzGiLvXEsgxS3Qc=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=G1mrAEfSCwGzwddPm0rEexdRm8LE5PJacLEnyeYki9rQMASd7ZCoISZwUkWOAqDO0 9Wt2hukL1TL88CrqNuRrLl9jIe+u4mHybWQSSWNY1+Q9uFJ0a3yQf9Ksk2V98Bp1ei MBq/cZiHa591CWO5niJYH6C8iT1eaw+MeMnu8ET4= To: "greg@unrelenting.technology" From: Dan Kotowski Cc: freebsd-arm Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> References: <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49dJz34JJrz41s1 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=G1mrAEfS; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.131 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-4.13 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; NEURAL_HAM_LONG(-1.03)[-1.025]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[185.70.40.131:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_SHORT(-1.01)[-1.008]; NEURAL_HAM_MEDIUM(-1.00)[-0.995]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.131:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 21:37:39 -0000 > Oops, I've been adding some debug prints to gicv2 not gicv3. > > One thing I noticed is the interesting irq number the nvme admin queue ge= ts.. > it's the same as gic_nirqs. > > gic0: SPIs: 288, IDs: 65535 > nvme0: attempting to allocate 17 MSI-X vectors (33 supported) > nvme0: using IRQs 21-37 for MSI-X > acpi0: allocating via sysres: res 0xfffffd0000726280, start 21 + count 1 = - 1 =3D? end 21 > intr_setup_irq(): irq 288 add handler error 0 on nvme0 > > maybe that's just like.. the first ITS handled interrupt? > (funnily enough, NetBSD lists MSIs as IRQs starting from 8192) > > More SATA debugging: https://send.firefox.com/download/9de5357a2e58edd9/#= s9ZaU_k2NHlO-tLdyGk5iA https://gist.github.com/agrajag9/1aaf18f48ee883b917907dd417803711 We have SATA! NVMe and mps still cause hangs, but progress is progress! From owner-freebsd-arm@freebsd.org Fri Jun 5 00:18:27 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F387C3381BE for ; Fri, 5 Jun 2020 00:18:27 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out0.migadu.com (out0.migadu.com [IPv6:2001:41d0:2:267::]) (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 49dNXf2C4Dz4PBq for ; Fri, 5 Jun 2020 00:18:26 +0000 (UTC) (envelope-from greg@unrelenting.technology) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1591316297; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9lSH98E7N6guho+DDhhdVERrIatuLWeMnj0tToTcXjc=; b=BBgOD5u9CJDOyMoAVgG10/+PHUPJ2RW30YlkmFjT3YFLn0E4Ym7QhBjdOFGmu/0Ulfrkem vjRWVhtIq0oUvZYL+kpeLOUnh/57MazGxNDBD2irf30Ki67uwQ1I8rgvP4pYAxBkKvPGE6 LrdZRhZGN29ex4vDX35NjiSEPmrLXfI= Date: Fri, 05 Jun 2020 00:18:17 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: greg@unrelenting.technology Message-ID: Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: "Dan Kotowski" Cc: "freebsd-arm" In-Reply-To: References: <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49dNXf2C4Dz4PBq X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=BBgOD5u9; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:267:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.23 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.005]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:267::]; NEURAL_HAM_LONG(-1.00)[-1.003]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-0.22)[-0.217]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 00:18:28 -0000 June 5, 2020 12:37 AM, "Dan Kotowski" wr= ote:=0A=0A>> Oops, I've been adding some debug prints to gicv2 not gicv3.= =0A>> =0A>> One thing I noticed is the interesting irq number the nvme ad= min queue gets..=0A>> it's the same as gic_nirqs.=0A>> =0A>> gic0: SPIs: = 288, IDs: 65535=0A>> nvme0: attempting to allocate 17 MSI-X vectors (33 s= upported)=0A>> nvme0: using IRQs 21-37 for MSI-X=0A>> acpi0: allocating v= ia sysres: res 0xfffffd0000726280, start 21 + count 1 - 1 =3D? end 21=0A>= > intr_setup_irq(): irq 288 add handler error 0 on nvme0=0A>> =0A>> maybe= that's just like.. the first ITS handled interrupt?=0A>> (funnily enough= , NetBSD lists MSIs as IRQs starting from 8192)=0A>> =0A>> More SATA debu= gging: https://send.firefox.com/download/9de5357a2e58edd9/#s9ZaU_k2NHlO-t= LdyGk5iA=0A> =0A> https://gist.github.com/agrajag9/1aaf18f48ee883b917907d= d417803711=0A> =0A> We have SATA!=0A=0AWow that was silly.=0A=0AFreeBSD d= id not support multiple interrupts in an ACPI device, at all.=0ASince for= ever, nobody else has needed this, apparently.=0AIt's really stupid that = the error was returned this quietly >_<=0A=0AIn the build below, it would= try to attach all interrupts, not just the first one.=0AIf that succeeds= , I'll post that as a patch.=0A=0A> NVMe and mps still cause hangs, but p= rogress is progress!=0A=0AWell I didn't say I've tried to actually fix PC= Ie interrupts yet,=0Abut I did add some debug logging that seems to be us= eful.=0ANamely, IORT stuff. IORT is the ACPI table describing how interru= pts flow.=0A=0AAaaand this is concerning:=0A=0Aiort: Found PCI RC node wi= th segment and device ID. its? 1 smmu3? 0 smmu? 1 | nxtid 6400 rid 256=0A= iort: entry lookup fail=0A=0AWait a second, SMMU, that's not what IORT sa= ys the PCI nodes output to!=0A=0Ahttps://github.com/SolidRun/edk2-platfor= ms/blob/eec706c2d693be0b3793d9180e7d1a4813a526cf/Silicon/NXP=0ALX2160A/Ac= piTables/Iort.aslc=0A=0A.PciRcNode[0] =3D { .PciRcIdMapping =3D { ...=0A.= OutputReference =3D OFFSET_OF (NXP_EFI_ACPI_6_0_IO_REMAPPING_TABLE, ItsNo= de), },=0A=0ALooks like our IORT parsing might be busted!=0A=0AThe new bu= ild should output more info and force usage of the ITS node.=0ASo if that= was the issue, and I did the forcing correctly, you should have PCIe int= errupts working now :)=0A=0A(btw: NetBSD for now doesn't care about Outpu= tReference at all, lol)=0A=0Ahttps://send.firefox.com/download/d655b27c2b= d73021/#O9tR6di9HbS8FHp0isgFkA From owner-freebsd-arm@freebsd.org Fri Jun 5 11:46:06 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A8076328446 for ; Fri, 5 Jun 2020 11:46:06 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail-40134.protonmail.ch (mail-40134.protonmail.ch [185.70.40.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49dgp54F9Dz4pjx for ; Fri, 5 Jun 2020 11:46:05 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Fri, 05 Jun 2020 11:45:57 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1591357561; bh=kjfbwzQfr9awUkkv7qWPixl/CSmYEZZmuM7hNVHWu/U=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=cnlXV3Ch65ZCAc7IJMgGi6SQMFhqFNiT8kWgjOEZil4OeuKb77kGm1DxuQMzC/hIY 8JeCFZBjKonaZ3DqBFIgfvbZrdCMnRCwmvqIH3B+rgvMZCrue5RQOqmVWzVNRtqKTT EoohdRAihLcehCp7JHszvMiiPiKabFDFP7PKxbgo= To: "greg@unrelenting.technology" From: Dan Kotowski Cc: freebsd-arm Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: References: <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49dgp54F9Dz4pjx X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=cnlXV3Ch; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.134 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-3.60 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; NEURAL_HAM_LONG(-0.98)[-0.980]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.134:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_SHORT(-0.51)[-0.514]; NEURAL_HAM_MEDIUM(-1.01)[-1.009]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.134:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 11:46:06 -0000 > > > Oops, I've been adding some debug prints to gicv2 not gicv3. > > > One thing I noticed is the interesting irq number the nvme admin queu= e gets.. > > > it's the same as gic_nirqs. > > > gic0: SPIs: 288, IDs: 65535 > > > nvme0: attempting to allocate 17 MSI-X vectors (33 supported) > > > nvme0: using IRQs 21-37 for MSI-X > > > acpi0: allocating via sysres: res 0xfffffd0000726280, start 21 + coun= t 1 - 1 =3D? end 21 > > > intr_setup_irq(): irq 288 add handler error 0 on nvme0 > > > maybe that's just like.. the first ITS handled interrupt? > > > (funnily enough, NetBSD lists MSIs as IRQs starting from 8192) > > > More SATA debugging: https://send.firefox.com/download/9de5357a2e58ed= d9/#s9ZaU_k2NHlO-tLdyGk5iA > > > > https://gist.github.com/agrajag9/1aaf18f48ee883b917907dd417803711 > > We have SATA! > > Wow that was silly. > > FreeBSD did not support multiple interrupts in an ACPI device, at all. > Since forever, nobody else has needed this, apparently. > It's really stupid that the error was returned this quietly >_< > > In the build below, it would try to attach all interrupts, not just the f= irst one. > If that succeeds, I'll post that as a patch. > > > NVMe and mps still cause hangs, but progress is progress! > > Well I didn't say I've tried to actually fix PCIe interrupts yet, > but I did add some debug logging that seems to be useful. > Namely, IORT stuff. IORT is the ACPI table describing how interrupts flow= . > > Aaaand this is concerning: > > iort: Found PCI RC node with segment and device ID. its? 1 smmu3? 0 smmu?= 1 | nxtid 6400 rid 256 > iort: entry lookup fail > > Wait a second, SMMU, that's not what IORT says the PCI nodes output to! > > https://github.com/SolidRun/edk2-platforms/blob/eec706c2d693be0b3793d9180= e7d1a4813a526cf/Silicon/NXP > LX2160A/AcpiTables/Iort.aslc > > .PciRcNode[0] =3D { .PciRcIdMapping =3D { ... > .OutputReference =3D OFFSET_OF (NXP_EFI_ACPI_6_0_IO_REMAPPING_TABLE, ItsN= ode), }, > > Looks like our IORT parsing might be busted! > > The new build should output more info and force usage of the ITS node. > So if that was the issue, and I did the forcing correctly, you should hav= e PCIe interrupts working now :) > > (btw: NetBSD for now doesn't care about OutputReference at all, lol) > > https://send.firefox.com/download/d655b27c2bd73021/#O9tR6di9HbS8FHp0isgFk= A https://gist.github.com/agrajag9/749f504dcac741e902f87c2ea03ae9ac >From jnettlet: BEGIN QUOTE the V1 silicon has a SATA errata. I have partially worked around the errat= a moving some configuration into the firmware, but I still need to sort out= the remaining bits. Sometimes just unplugging and replugging your SATA ca= ble will help to reseat the connector and help. Also it is very sensitive= to marginal SATA cables. END QUOTE I played around a bit and could create and destroy GPTs, make filesystems, = read and write to said filesystems, and hot-plug even seems to work. But I'= m not sure if jon's comment really explains the AHCI error we're still seei= ng: ``` (aprobe3:ahcich3:0:15:0): NOP FLUSHQUEUE. ACB: 00 00 00 00 00 00 00 00 00 0= 0 00 00 (aprobe3:ahcich3:0:15:0): CAM status: Command timeout (aprobe3:ahcich3:0:15:0): Error 5, Retries exhausted ``` From owner-freebsd-arm@freebsd.org Fri Jun 5 12:01:59 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2643D3293ED for ; Fri, 5 Jun 2020 12:01:59 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49dh8Q1F7Gz4ryV for ; Fri, 5 Jun 2020 12:01:57 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-qk1-x72d.google.com with SMTP id g28so9366327qkl.0 for ; Fri, 05 Jun 2020 05:01:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=9eHXyqVp+1Nkh1MybQLHcVk5Z01kAQX6fGIfLkn/wMU=; b=XpJMmSw8KFsnPuJv08btRtskoV074L5izCX54jsdVBIqS4p5LeZMk28gOs65V3PUN5 xsjWbAGf4cGPVnUH8vei9yP0JSS5ovkvkoAQSBgd1DCo/IneR+q7Hw3/gDYLuqM87yye 4mktE6i9oL1cbuLLlGux3TRX5RoXTpGIFQaiSelOkPQ8f/GYMMlz/Mi5Wzaoc70mpwb6 CW3BCYl/VqLoWdxxBy2uDiqiGu0Z0hiQ44v+bzhKh3y33i+cacRlm41nmzGQUFThJglr f3ZwR/1IzFCLYdhMcKccusypmQz9gZ+Ofwnk6rZLs9ffTM/lpJfyT9mvAD7SSld/H7+0 0+7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=9eHXyqVp+1Nkh1MybQLHcVk5Z01kAQX6fGIfLkn/wMU=; b=chEY8BKjaPbwcdbyOB2EDnrAifsaaAO60K3oGRSgocId/2DVu2hhxkAflhd4aBtCBD jGOrvVqzrHNgePEewTPVCX/hxXZAMgeVZ6bOENrrerY+uEIX3xsi/qI617cq7yTUcPjK YWbjpHZugrOpUzMHYUs5Tazhqr/btQC0M9+CFs/aixeTb+KcOb8N5qSAtfWTci1OGOOH jYVJkGWj2wbEmunJ08xYjRAlOx2W8SsipVh8c6Ifvx1JtCPD2PfH4lJvN8bRBvvV+CcV WMPB5XBqt0CXzPYBpwVsRcXi2kAlWXeDsIJsmx/Uz5rIkw+F74+q4MM82EC/dOVT5p2F Nv5A== X-Gm-Message-State: AOAM532iPoxyFpHmm4qXc3PsYA0mcDZ6E78sVGv9NrFiqN3uBnWL6a1g WrbYqAsTptlTzFi1GlERqFc00/UG4/mH+AOkPBnVp9BgUd0= X-Google-Smtp-Source: ABdhPJwlt4MDa0SAMp6QTstefVzTn/0w3qnZEmftyFRpFP5tdsU1ubyzKN/gTo5iME7NGDbBWyPVyHXjl4kVuo3rztA= X-Received: by 2002:ae9:ed8f:: with SMTP id c137mr9104772qkg.109.1591358516379; Fri, 05 Jun 2020 05:01:56 -0700 (PDT) MIME-Version: 1.0 References: <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> In-Reply-To: From: Marcin Wojtas Date: Fri, 5 Jun 2020 14:01:44 +0200 Message-ID: Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: Dan Kotowski Cc: "greg@unrelenting.technology" , freebsd-arm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 49dh8Q1F7Gz4ryV X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=semihalf-com.20150623.gappssmtp.com header.s=20150623 header.b=XpJMmSw8; dmarc=none; spf=none (mx1.freebsd.org: domain of mw@semihalf.com has no SPF policy when checking 2607:f8b0:4864:20::72d) smtp.mailfrom=mw@semihalf.com X-Spamd-Result: default: False [-2.85 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[semihalf-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-0.99)[-0.991]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.94)[-0.941]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[semihalf.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[semihalf-com.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-0.61)[-0.613]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::72d:from]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 12:01:59 -0000 Hi Dan, pt., 5 cze 2020 o 13:46 Dan Kotowski napisa=C5=82(a): > > > > > Oops, I've been adding some debug prints to gicv2 not gicv3. > > > > One thing I noticed is the interesting irq number the nvme admin qu= eue gets.. > > > > it's the same as gic_nirqs. > > > > gic0: SPIs: 288, IDs: 65535 > > > > nvme0: attempting to allocate 17 MSI-X vectors (33 supported) > > > > nvme0: using IRQs 21-37 for MSI-X > > > > acpi0: allocating via sysres: res 0xfffffd0000726280, start 21 + co= unt 1 - 1 =3D? end 21 > > > > intr_setup_irq(): irq 288 add handler error 0 on nvme0 > > > > maybe that's just like.. the first ITS handled interrupt? > > > > (funnily enough, NetBSD lists MSIs as IRQs starting from 8192) > > > > More SATA debugging: https://send.firefox.com/download/9de5357a2e58= edd9/#s9ZaU_k2NHlO-tLdyGk5iA > > > > > > https://gist.github.com/agrajag9/1aaf18f48ee883b917907dd417803711 > > > We have SATA! > > > > Wow that was silly. > > > > FreeBSD did not support multiple interrupts in an ACPI device, at all. > > Since forever, nobody else has needed this, apparently. > > It's really stupid that the error was returned this quietly >_< > > > > In the build below, it would try to attach all interrupts, not just the= first one. > > If that succeeds, I'll post that as a patch. > > > > > NVMe and mps still cause hangs, but progress is progress! > > > > Well I didn't say I've tried to actually fix PCIe interrupts yet, > > but I did add some debug logging that seems to be useful. > > Namely, IORT stuff. IORT is the ACPI table describing how interrupts fl= ow. > > > > Aaaand this is concerning: > > > > iort: Found PCI RC node with segment and device ID. its? 1 smmu3? 0 smm= u? 1 | nxtid 6400 rid 256 > > iort: entry lookup fail > > > > Wait a second, SMMU, that's not what IORT says the PCI nodes output to! > > > > https://github.com/SolidRun/edk2-platforms/blob/eec706c2d693be0b3793d91= 80e7d1a4813a526cf/Silicon/NXP > > LX2160A/AcpiTables/Iort.aslc > > > > .PciRcNode[0] =3D { .PciRcIdMapping =3D { ... > > .OutputReference =3D OFFSET_OF (NXP_EFI_ACPI_6_0_IO_REMAPPING_TABLE, It= sNode), }, > > > > Looks like our IORT parsing might be busted! > > > > The new build should output more info and force usage of the ITS node. > > So if that was the issue, and I did the forcing correctly, you should h= ave PCIe interrupts working now :) > > > > (btw: NetBSD for now doesn't care about OutputReference at all, lol) > > > > https://send.firefox.com/download/d655b27c2bd73021/#O9tR6di9HbS8FHp0isg= FkA > > https://gist.github.com/agrajag9/749f504dcac741e902f87c2ea03ae9ac > > From jnettlet: > > BEGIN QUOTE > the V1 silicon has a SATA errata. I have partially worked around the err= ata moving some configuration into the firmware, but I still need to sort o= ut the remaining bits. Sometimes just unplugging and replugging your SATA = cable will help to reseat the connector and help. Also it is very sensiti= ve to marginal SATA cables. > END QUOTE > > I played around a bit and could create and destroy GPTs, make filesystems= , read and write to said filesystems, and hot-plug even seems to work. But = I'm not sure if jon's comment really explains the AHCI error we're still se= eing: > > ``` > (aprobe3:ahcich3:0:15:0): NOP FLUSHQUEUE. ACB: 00 00 00 00 00 00 00 00 00= 00 00 00 > (aprobe3:ahcich3:0:15:0): CAM status: Command timeout > (aprobe3:ahcich3:0:15:0): Error 5, Retries exhausted > ``` I experienced this issue on a cuple of targets (e.g. Zynq-MP or LS1046A). The port-multiplier quirk flag helped - please try adding: ahci->quirks |=3D AHCI_Q_NOPMP; Best regards, Marcin From owner-freebsd-arm@freebsd.org Fri Jun 5 15:03:55 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C7F2532E11D for ; Fri, 5 Jun 2020 15:03:55 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out1.migadu.com (out1.migadu.com [IPv6:2001:41d0:2:863f::]) (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 49dmBL4cx8z42j2 for ; Fri, 5 Jun 2020 15:03:54 +0000 (UTC) (envelope-from greg@unrelenting.technology) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1591369426; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=nu20UDD6oSabNyWD/WhQJjUS1NB0yCdtSLtBTCxquGs=; b=SCvn7XJ5MEKfd7zFoG/lFFIYofRugBxPHPBGvUXwRcfzfK2VVAksrUa4tIAzFBHc/0UGij yCCK6bjdJlQpTVBnNaB8JvkHUos6HpHAiFJok9unjpx9er7yUCQbPjJOQX8SCUELlN4xvR BuclSvc6wY94DyZP5GeA0M8i4r2kJ+M= Date: Fri, 05 Jun 2020 15:03:45 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: greg@unrelenting.technology Message-ID: Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: "Dan Kotowski" Cc: "freebsd-arm" , "Marcin Wojtas" In-Reply-To: References: <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49dmBL4cx8z42j2 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=SCvn7XJ5; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:863f:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.58 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.01)[-1.006]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:863f::]; NEURAL_HAM_LONG(-0.99)[-0.988]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-0.59)[-0.585]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 15:03:55 -0000 June 5, 2020 3:01 PM, "Marcin Wojtas" wrote:=0A=0A> pt.= , 5 cze 2020 o 13:46 Dan Kotowski =0A> na= pisa=C5=82(a):=0A>> https://gist.github.com/agrajag9/749f504dcac741e902f8= 7c2ea03ae9ac=0A>> =0A>> From jnettlet:=0A>> =0A>> BEGIN QUOTE=0A>> the V1= silicon has a SATA errata. I have partially worked around the errata mov= ing some=0A>> configuration into the firmware, but I still need to sort o= ut the remaining bits. Sometimes just=0A>> unplugging and replugging your= SATA cable will help to reseat the connector and help. Also it is=0A>> v= ery sensitive to marginal SATA cables.=0A>> END QUOTE=0A>> =0A>> I played= around a bit and could create and destroy GPTs, make filesystems, read a= nd write to said=0A>> filesystems, and hot-plug even seems to work. But I= 'm not sure if jon's comment really explains the=0A>> AHCI error we're st= ill seeing:=0A>> =0A>> ```=0A>> (aprobe3:ahcich3:0:15:0): NOP FLUSHQUEUE.= ACB: 00 00 00 00 00 00 00 00 00 00 00 00=0A>> (aprobe3:ahcich3:0:15:0): = CAM status: Command timeout=0A>> (aprobe3:ahcich3:0:15:0): Error 5, Retri= es exhausted=0A>> ```=0A> =0A> I experienced this issue on a cuple of tar= gets (e.g. Zynq-MP or=0A> LS1046A). The port-multiplier quirk flag helped= - please try adding:=0A> ahci->quirks |=3D AHCI_Q_NOPMP;=0A=0A=0ABuild w= ith this + more ITS logging:=0Ahttps://send.firefox.com/download/cf66ed7f= 48160529/#LpeMjccv7iqze5hAx_6BrQ=0A=0AThe patch that lets AHCI attach:=0A= https://reviews.freebsd.org/D25145 From owner-freebsd-arm@freebsd.org Fri Jun 5 19:18:22 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E497D334EAD for ; Fri, 5 Jun 2020 19:18:22 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49dsqx5WYjz4cXj for ; Fri, 5 Jun 2020 19:18:21 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Fri, 05 Jun 2020 19:18:17 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1591384698; bh=t5eLfkIMQ1CnxWe094HzqiHTbnuakdw9C5Cvk4yL4aE=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=awgafknE14Xz3Z+dXe0GhxJIz3P5wsz5TuuooegPzfsZP6sKdTvuuRiUnk95bBbFe x+fCal3cOmcCF8GwdGGMk/bV+up0OMivVVs+e5w5DKwdQgykLVDJe8evb7ki7uxTWU aq2kutVIdIehYaxmVK/iEL4W/1Ll/cUGC17E+Hww= To: "greg@unrelenting.technology" From: Dan Kotowski Cc: freebsd-arm , Marcin Wojtas Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: References: <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49dsqx5WYjz4cXj X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=awgafknE; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.22 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-3.77 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; NEURAL_HAM_LONG(-0.96)[-0.962]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.22:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_SHORT(-0.71)[-0.710]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.22:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 19:18:23 -0000 > > > https://gist.github.com/agrajag9/749f504dcac741e902f87c2ea03ae9ac > > > From jnettlet: > > > BEGIN QUOTE > > > the V1 silicon has a SATA errata. I have partially worked around the = errata moving some > > > configuration into the firmware, but I still need to sort out the rem= aining bits. Sometimes just > > > unplugging and replugging your SATA cable will help to reseat the con= nector and help. Also it is > > > very sensitive to marginal SATA cables. > > > END QUOTE > > > I played around a bit and could create and destroy GPTs, make filesys= tems, read and write to said > > > filesystems, and hot-plug even seems to work. But I'm not sure if jon= 's comment really explains the > > > AHCI error we're still seeing: > > > > > > (aprobe3:ahcich3:0:15:0): NOP FLUSHQUEUE. ACB: 00 00 00 00 00 00 = 00 00 00 00 00 00 > > > (aprobe3:ahcich3:0:15:0): CAM status: Command timeout > > > (aprobe3:ahcich3:0:15:0): Error 5, Retries exhausted > > > > > > > I experienced this issue on a cuple of targets (e.g. Zynq-MP or > > LS1046A). The port-multiplier quirk flag helped - please try adding: > > ahci->quirks |=3D AHCI_Q_NOPMP; > > Build with this + more ITS logging: > https://send.firefox.com/download/cf66ed7f48160529/#LpeMjccv7iqze5hAx_6Br= Q > > The patch that lets AHCI attach: > https://reviews.freebsd.org/D25145 https://gist.github.com/agrajag9/129585436f01876cc4d799382e1c0fac AHCI is looking better and better! I'm going to do a little bit of poking a= t that SATA HDD just to see how stable it really is. From owner-freebsd-arm@freebsd.org Fri Jun 5 20:23:53 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6F331336FA9 for ; Fri, 5 Jun 2020 20:23:53 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49dvHW5W71z3X63 for ; Fri, 5 Jun 2020 20:23:51 +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 055KNl9n033444 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 5 Jun 2020 13:23:47 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id 055KNkdJ033443; Fri, 5 Jun 2020 13:23:46 -0700 (PDT) (envelope-from fbsd) Date: Fri, 5 Jun 2020 13:23:46 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Ssh sessions running top keep disconnecting Message-ID: <20200605202346.GA32419@www.zefox.net> References: <20200604020250.GA26450@www.zefox.net> <7A0C9F2C-734E-49F8-B533-B3B487588D71@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7A0C9F2C-734E-49F8-B533-B3B487588D71@yahoo.com> X-Rspamd-Queue-Id: 49dvHW5W71z3X63 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [2.23 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.36)[-0.358]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.24)[0.239]; NEURAL_SPAM_SHORT(0.45)[0.451]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 20:23:53 -0000 On Wed, Jun 03, 2020 at 07:39:44PM -0700, Mark Millard wrote: > > > On 2020-Jun-3, at 19:02, bob prohaska wrote: > > > For some reason, ssh sessions running top seem to be quitting > > with > > packet_write_wait: Connection to 50.1.20.25 port 22: Broken pipe > > > > I'm in the habit of leaving an ssh session running top going on > > machines running long jobs like world or port builds. On my Pi3 > > running 12.1-stable those sessions keep disconnecting. No other > > ssh sessions, among the four open, seem to be affected. > > > > The client is a Pi3b+ running raspberry pi os. It has a dozen > > or so ssh sessions open, no others are affected. > > > > Any ideas what might be going on? > > > > No clue. But a possible kind of experiment . . . > > top keeps its ssh connection in use on a rather > frequent basis, even if the mount of traffic is > not large. > > Try having some other ssh session into the 12.1 > Stable FreeBSD system that also keeps its ssh > connection in use on a rather frequent basis. > Does it get the same issue as the top sessions > do? (Need not be at the same times but if the > times were near each other for failures that > might indicate something.) > > Of course, it may be that some of your other ssh > connections to the same system already do this > test --or it may be they all rarely put their > connection to use (compared to top). > In a couple of cases top sessions disconnected as described while gstat sessions kep running. The statistics aren't very good on this, with only three or four cases total and at least one where no disconnection occurred. The client machine from which all the sessions are observed is a Pi3B+ running Raspberry Pi Buster. It's been found that all ssh sessions are more stable if there's an ongoing ping -i 10 to the WAP. I don't see how that would be significant but maybe it is. Thanks for writing, bob prohaska From owner-freebsd-arm@freebsd.org Fri Jun 5 21:19:35 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 00AD7338091 for ; Fri, 5 Jun 2020 21:19:35 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out1.migadu.com (out1.migadu.com [IPv6:2001:41d0:2:863f::]) (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 49dwWn5XXwz3d6F for ; Fri, 5 Jun 2020 21:19:33 +0000 (UTC) (envelope-from greg@unrelenting.technology) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1591391972; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Pry+jsS3XAee3fPhUeCMS0WhsJgqnQyk6QGOrx5rhZ8=; b=FiBF5hpZAlrnkTrwhpk1wocB/yFdhi6BUk0iqS91OTSykk0SUoxEJ7R7ZzWYjd9+LbCzDU DMskLRD5LBkubEqyCxhNVi62Kt3yREYLb4JmCTzCti2gTv9f7h2P3XzDgoclycbifDPZfJ mA1mnfeSTVIH8eRILGbHbTM29STnVjs= Date: Fri, 05 Jun 2020 21:19:31 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: greg@unrelenting.technology Message-ID: Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: "Dan Kotowski" Cc: "freebsd-arm" , "Marcin Wojtas" In-Reply-To: References: <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49dwWn5XXwz3d6F X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=FiBF5hpZ; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:863f:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.93 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.01)[-1.006]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:863f::]; NEURAL_HAM_LONG(-0.99)[-0.989]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-0.94)[-0.940]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 21:19:35 -0000 June 5, 2020 10:18 PM, "Dan Kotowski" wr= ote:=0A=0A>>> https://gist.github.com/agrajag9/749f504dcac741e902f87c2ea0= 3ae9ac=0A>>> From jnettlet:=0A>>> BEGIN QUOTE=0A>>> the V1 silicon has a = SATA errata. I have partially worked around the errata moving some=0A>>> = configuration into the firmware, but I still need to sort out the remaini= ng bits. Sometimes just=0A>>> unplugging and replugging your SATA cable w= ill help to reseat the connector and help. Also it is=0A>>> very sensitiv= e to marginal SATA cables.=0A>>> END QUOTE=0A>>> I played around a bit an= d could create and destroy GPTs, make filesystems, read and write to said= =0A>>> filesystems, and hot-plug even seems to work. But I'm not sure if = jon's comment really explains=0A>> the=0A>>> AHCI error we're still seein= g:=0A>>> =0A>>> (aprobe3:ahcich3:0:15:0): NOP FLUSHQUEUE. ACB: 00 00 00 0= 0 00 00 00 00 00 00 00 00=0A>>> (aprobe3:ahcich3:0:15:0): CAM status: Com= mand timeout=0A>>> (aprobe3:ahcich3:0:15:0): Error 5, Retries exhausted= =0A>>> =0A>> =0A>> I experienced this issue on a cuple of targets (e.g. Z= ynq-MP or=0A>> LS1046A). The port-multiplier quirk flag helped - please t= ry adding:=0A>> ahci->quirks |=3D AHCI_Q_NOPMP;=0A>> =0A>> Build with thi= s + more ITS logging:=0A>> https://send.firefox.com/download/cf66ed7f4816= 0529/#LpeMjccv7iqze5hAx_6BrQ=0A>> =0A>> The patch that lets AHCI attach:= =0A>> https://reviews.freebsd.org/D25145=0A> =0A> https://gist.github.com= /agrajag9/129585436f01876cc4d799382e1c0fac=0A> =0A> AHCI is looking bette= r and better! I'm going to do a little bit of poking at that SATA HDD jus= t to=0A> see how stable it really is.=0A=0APosted quirk patch: https://re= views.freebsd.org/D25157=0A=0ABack to PCI: hmm, maybe the reason that IOR= T parsing weirdly picks SMMU up is that ranges with .NumIds=3D0 end up=0A= with end before the beginning..=0A=0Amapping->end =3D map_entry->InputBas= e + map_entry->IdCount - 1;=0A=0AThe ARM document DEN0049D says the field= is "The number of IDs in the range minus one".=0AIf my brain still works= at all: that means we have to do *plus* one when interpreting it, not mi= nus one more!! :D=0A=0AThis causes the *first* mapping on the PCIe root c= omplex to be used, when we clearly want the second one.=0A=0ASooo NOW pci= e should work! I promise:=0A=0Ahttps://send.firefox.com/download/05a4e22a= 349f611f/#azClkvNDfZU-PczXSmNvaQ From owner-freebsd-arm@freebsd.org Fri Jun 5 21:53:15 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 75B6D338672 for ; Fri, 5 Jun 2020 21:53:15 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch [185.70.40.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49dxGf1d2Lz3yD2 for ; Fri, 5 Jun 2020 21:53:13 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Fri, 05 Jun 2020 21:53:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1591393991; bh=r31Ue3DYkbyc8BansCuU1mD24L60nG/3K2/4HYyaexA=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=IxOw70mOo0nF/cqr1KrB2fKNLw5rbmKnkCjTIYNceXZBBpIGT7aNdduSnejIXm+Lk KY+V05Hqcz/XaqGkVcZd24uHOGdmEvryi8K9xj5YmXEczeidgRCACHtoLwqMx+NdGy ZJVOYtwMs7vGot3fSxKL4TlzZEFkoXH0zYR+z/CE= To: "greg@unrelenting.technology" From: Dan Kotowski Cc: freebsd-arm , Marcin Wojtas Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: References: <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49dxGf1d2Lz3yD2 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=IxOw70mO; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.131 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-4.14 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[185.70.40.131:from]; NEURAL_HAM_LONG(-0.96)[-0.956]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_SHORT(-1.09)[-1.088]; NEURAL_HAM_MEDIUM(-1.00)[-0.996]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.131:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 21:53:15 -0000 > > > > https://gist.github.com/agrajag9/749f504dcac741e902f87c2ea03ae9ac > > > > From jnettlet: > > > > BEGIN QUOTE > > > > the V1 silicon has a SATA errata. I have partially worked around th= e errata moving some > > > > configuration into the firmware, but I still need to sort out the r= emaining bits. Sometimes just > > > > unplugging and replugging your SATA cable will help to reseat the c= onnector and help. Also it is > > > > very sensitive to marginal SATA cables. > > > > END QUOTE > > > > I played around a bit and could create and destroy GPTs, make files= ystems, read and write to said > > > > filesystems, and hot-plug even seems to work. But I'm not sure if j= on's comment really explains > > > > the > > > > AHCI error we're still seeing: > > > > (aprobe3:ahcich3:0:15:0): NOP FLUSHQUEUE. ACB: 00 00 00 00 00 00 00= 00 00 00 00 00 > > > > (aprobe3:ahcich3:0:15:0): CAM status: Command timeout > > > > (aprobe3:ahcich3:0:15:0): Error 5, Retries exhausted > > > > > > I experienced this issue on a cuple of targets (e.g. Zynq-MP or > > > LS1046A). The port-multiplier quirk flag helped - please try adding: > > > ahci->quirks |=3D AHCI_Q_NOPMP; > > > Build with this + more ITS logging: > > > https://send.firefox.com/download/cf66ed7f48160529/#LpeMjccv7iqze5hAx= _6BrQ > > > The patch that lets AHCI attach: > > > https://reviews.freebsd.org/D25145 > > > > https://gist.github.com/agrajag9/129585436f01876cc4d799382e1c0fac > > AHCI is looking better and better! I'm going to do a little bit of poki= ng at that SATA HDD just to > > see how stable it really is. > > Posted quirk patch:https://reviews.freebsd.org/D25157 > > Back to PCI: hmm, maybe the reason that IORT parsing weirdly picks SMMU u= p is that ranges with .NumIds=3D0 end up > with end before the beginning.. > > mapping->end =3D map_entry->InputBase + map_entry->IdCount - 1; > > The ARM document DEN0049D says the field is "The number of IDs in the ran= ge minus one". > If my brain still works at all: that means we have to do plus one when in= terpreting it, not minus one more!! :D > > This causes the first mapping on the PCIe root complex to be used, when w= e clearly want the second one. > > Sooo NOW pcie should work! I promise: > > https://send.firefox.com/download/05a4e22a349f611f/#azClkvNDfZU-PczXSmNva= Q Sad trombone https://gist.github.com/agrajag9/eddb36ad44898c070e464e7add594= 26d From owner-freebsd-arm@freebsd.org Fri Jun 5 23:05:56 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AC91333A7BB for ; Fri, 5 Jun 2020 23:05:56 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out1.migadu.com (out1.migadu.com [IPv6:2001:41d0:2:863f::]) (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 49dytW1c7rz46VX for ; Fri, 5 Jun 2020 23:05:54 +0000 (UTC) (envelope-from greg@unrelenting.technology) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1591398352; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ye3w9YH1r2V3DSdUYf5VcGVFvroJvmDQajPoAinvJmw=; b=aa7n94p3RO0QSaasMWEvaDTDe6Q33sTfnQTI1XtHbavZWKVDwk+QteYAOymcvHzr5lHDMw mKxCKq6WvLRa2H5OkijmL7lhU2LrwY7iXBVbsPIbt/f+sEZU3XeSCr27BG6MPEhEkXLgmC dyzW/3zJNc114Ypd/IABGUeJRufu4Qo= Date: Fri, 05 Jun 2020 23:05:51 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: greg@unrelenting.technology Message-ID: <940a6099e971e01bd6d04564d0982b9d@unrelenting.technology> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: "Dan Kotowski" Cc: "freebsd-arm" In-Reply-To: References: <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49dytW1c7rz46VX X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=aa7n94p3; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:863f:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.43 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.01)[-1.012]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:863f::]; NEURAL_HAM_LONG(-1.01)[-1.008]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-0.41)[-0.409]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 23:05:56 -0000 June 6, 2020 12:53 AM, "Dan Kotowski" wr= ote:=0A=0A>>>> https://gist.github.com/agrajag9/749f504dcac741e902f87c2ea= 03ae9ac=0A>>>> From jnettlet:=0A>>>> BEGIN QUOTE=0A>>>> the V1 silicon ha= s a SATA errata. I have partially worked around the errata moving some=0A= >>>> configuration into the firmware, but I still need to sort out the re= maining bits. Sometimes=0A>> just=0A>>>> unplugging and replugging your S= ATA cable will help to reseat the connector and help. Also it=0A>> is=0A>= >>> very sensitive to marginal SATA cables.=0A>>>> END QUOTE=0A>>>> I pla= yed around a bit and could create and destroy GPTs, make filesystems, rea= d and write to=0A>> said=0A>>>> filesystems, and hot-plug even seems to w= ork. But I'm not sure if jon's comment really explains=0A>>>> the=0A>>>> = AHCI error we're still seeing:=0A>>>> (aprobe3:ahcich3:0:15:0): NOP FLUSH= QUEUE. ACB: 00 00 00 00 00 00 00 00 00 00 00 00=0A>>>> (aprobe3:ahcich3:0= :15:0): CAM status: Command timeout=0A>>>> (aprobe3:ahcich3:0:15:0): Erro= r 5, Retries exhausted=0A>>> =0A>>> I experienced this issue on a cuple o= f targets (e.g. Zynq-MP or=0A>>> LS1046A). The port-multiplier quirk flag= helped - please try adding:=0A>>> ahci->quirks |=3D AHCI_Q_NOPMP;=0A>>> = Build with this + more ITS logging:=0A>>> https://send.firefox.com/downlo= ad/cf66ed7f48160529/#LpeMjccv7iqze5hAx_6BrQ=0A>>> The patch that lets AHC= I attach:=0A>>> https://reviews.freebsd.org/D25145=0A>> =0A>> https://gis= t.github.com/agrajag9/129585436f01876cc4d799382e1c0fac=0A>> AHCI is looki= ng better and better! I'm going to do a little bit of poking at that SATA= HDD just to=0A>> see how stable it really is.=0A>> =0A>> Posted quirk pa= tch:https://reviews.freebsd.org/D25157=0A>> =0A>> Back to PCI: hmm, maybe= the reason that IORT parsing weirdly picks SMMU up is that ranges with= =0A>> .NumIds=3D0 end up=0A>> with end before the beginning..=0A>> =0A>> = mapping->end =3D map_entry->InputBase + map_entry->IdCount - 1;=0A>> =0A>= > The ARM document DEN0049D says the field is "The number of IDs in the r= ange minus one".=0A>> If my brain still works at all: that means we have = to do plus one when interpreting it, not minus=0A>> one more!! :D=0A>> = =0A>> This causes the first mapping on the PCIe root complex to be used, = when we clearly want the second=0A>> one.=0A>> =0A>> Sooo NOW pcie should= work! I promise:=0A>> =0A>> https://send.firefox.com/download/05a4e22a34= 9f611f/#azClkvNDfZU-PczXSmNvaQ=0A> =0A> Sad trombone https://gist.github.= com/agrajag9/eddb36ad44898c070e464e7add59426d=0A=0Ahmm. The device ID loo= ks correct to me.. but we can check against NetBSD just in case.=0A=0ACan= you boot NetBSD with debug messages (boot -x)?=0AIt should print 'ACPI: = IORT mapped devid' messages among other things.=0A=0AAlso.. about the fac= t that it's showing up as if the PCIe root is outputting to the SMMU,=0Am= aybe that really doesn't sound like a bug, more like the firmware modifyi= ng the table?=0A(and the interrupt is *actually* going to the SMMU?)=0ABu= t I can't find anything like that in the firmware code.=0A=0AAn ACPI tabl= e dump from running FreeBSD might help: /usr/sbin/acpidump -dt=0AAnd for = a full binary dump, install acpica-tools=0A(if you don't want to bother w= ith USB Ethernet and package installs,=0Ajust wget the package on another= machine and extract it onto the live image):=0Ahttps://pkg.freebsd.org/F= reeBSD:13:aarch64/latest/All/acpica-tools-20200430.txz=0Aand with that, r= un: /usr/local/bin/acpidump -b=0A(creates a bunch of binary files in the = current directory)=0A=0AAlso.. try using your self built firmware again? From owner-freebsd-arm@freebsd.org Fri Jun 5 23:56:44 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DA5DA33B7D3 for ; Fri, 5 Jun 2020 23:56:44 +0000 (UTC) (envelope-from crowston@protonmail.com) Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49f0176bmDz4CJg for ; Fri, 5 Jun 2020 23:56:43 +0000 (UTC) (envelope-from crowston@protonmail.com) Date: Fri, 05 Jun 2020 23:56:34 +0000 To: bob prohaska , Mark Millard From: Robert Crowston Cc: freebsd-arm@freebsd.org Reply-To: Robert Crowston Subject: Re: Ssh sessions running top keep disconnecting Message-ID: In-Reply-To: <20200605202346.GA32419@www.zefox.net> References: <20200604020250.GA26450@www.zefox.net> <7A0C9F2C-734E-49F8-B533-B3B487588D71@yahoo.com> <20200605202346.GA32419@www.zefox.net> MIME-Version: 1.0 X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49f0176bmDz4CJg X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.10 / 15.00]; HAS_REPLYTO(0.00)[crowston@protonmail.com]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[protonmail.com]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; DKIM_TRACE(0.00)[protonmail.com:+]; MIME_BASE64_TEXT(0.10)[]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; NEURAL_HAM_SHORT(-1.10)[-1.102]; FREEMAIL_TO(0.00)[www.zefox.net,yahoo.com]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.18:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.990]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.004]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FREEMAIL_REPLYTO(0.00)[protonmail.com]; HAS_PHPMAILER_SIG(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[185.70.40.18:from] Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 23:56:44 -0000 VG8gZGVidWcsIHlvdSBjYW4gbGF1bmNoIGEgZGVidWcgc3NoZCBpbnN0YW5jZSB3aXRoIOKAnHNz aGQgLWRkZCAtcCAxMjM0NeKAnSAob3Igd2hhdGV2ZXIgYWx0ZXJuYXRpdmUgcG9ydCB5b3UgbGlr ZSkgYW5kIHlvdXIgc3NoIGNsaWVudCB3aXRoIOKAnHNzaCAtdnZ2IC1wIDEyMzQ1IGJvYkB3aGF0 ZXZlcuKAnS4KClRoaXMgd2lsbCBwcm9kdWNlIGEgZ3JlYXQgZGVhbCBvZiBkZWJ1ZyBpbmZvIHdo aWNoIGNhbiBoZWxwIGZpZ3VyZSBvdXQgd2hhdCBpcyBnb2luZyBvbi4gWW91IGNhbiByZWR1Y2Ug dGhlIG51bWJlciBvZiDigJx24oCdcyBvciDigJxk4oCdcyB0byBkZWNyZWFzZSB2ZXJib3NpdHkg aWYgaXQgYmVjb21lcyB1bnVzYWJsZS4gU2VydmVyIHNpZGUgbG9ncyBhcmUgbW9yZSB1c2VmdWwg YnV0IGF0IG1heCBkZWJ1ZyBsZXZlbCBtYXkgaGF2ZSBjb21wcm9taXNpbmcgaW5mb3JtYXRpb24g aW4gdGhlbSwgc28gcmVhZCB0aGVtIGNhcmVmdWxseSBiZWZvcmUgc2hhcmluZy4gc3NoZCAtZCBj YW4gYmUgcnVuIGluIHBhcmFsbGVsIHdpdGggcmVndWxhciBzc2hkLCBqdXN0IHJ1biBpdCBmcm9t IHRoZSBjb21tYW5kIGxpbmUgd2l0aCBhIGRpZmZlcmVudCBwb3J0LiBJdCB3aWxsIHF1aXQgYXV0 b21hdGljYWxseSBhZnRlciB0aGUgY2xpZW50IGRpc2Nvbm5lY3RzLgoKT24gRnJpLCBKdW4gNSwg MjAyMCBhdCAyMToyMywgYm9iIHByb2hhc2thIDxmYnNkQHd3dy56ZWZveC5uZXQ+IHdyb3RlOgoK PiBPbiBXZWQsIEp1biAwMywgMjAyMCBhdCAwNzozOTo0NFBNIC0wNzAwLCBNYXJrIE1pbGxhcmQg d3JvdGU6Cj4+Cj4+Cj4+IE9uIDIwMjAtSnVuLTMsIGF0IDE5OjAyLCBib2IgcHJvaGFza2EgPGZi c2QgYXQgd3d3LnplZm94Lm5ldD4gd3JvdGU6Cj4+Cj4+ID4gRm9yIHNvbWUgcmVhc29uLCBzc2gg c2Vzc2lvbnMgcnVubmluZyB0b3Agc2VlbSB0byBiZSBxdWl0dGluZwo+PiA+IHdpdGgKPj4gPiBw YWNrZXRfd3JpdGVfd2FpdDogQ29ubmVjdGlvbiB0byA1MC4xLjIwLjI1IHBvcnQgMjI6IEJyb2tl biBwaXBlCj4+ID4KPj4gPiBJJ20gaW4gdGhlIGhhYml0IG9mIGxlYXZpbmcgYW4gc3NoIHNlc3Np b24gcnVubmluZyB0b3AgZ29pbmcgb24KPj4gPiBtYWNoaW5lcyBydW5uaW5nIGxvbmcgam9icyBs aWtlIHdvcmxkIG9yIHBvcnQgYnVpbGRzLiBPbiBteSBQaTMKPj4gPiBydW5uaW5nIDEyLjEtc3Rh YmxlIHRob3NlIHNlc3Npb25zIGtlZXAgZGlzY29ubmVjdGluZy4gTm8gb3RoZXIKPj4gPiBzc2gg c2Vzc2lvbnMsIGFtb25nIHRoZSBmb3VyIG9wZW4sIHNlZW0gdG8gYmUgYWZmZWN0ZWQuCj4+ID4K Pj4gPiBUaGUgY2xpZW50IGlzIGEgUGkzYisgcnVubmluZyByYXNwYmVycnkgcGkgb3MuIEl0IGhh cyBhIGRvemVuCj4+ID4gb3Igc28gc3NoIHNlc3Npb25zIG9wZW4sIG5vIG90aGVycyBhcmUgYWZm ZWN0ZWQuCj4+ID4KPj4gPiBBbnkgaWRlYXMgd2hhdCBtaWdodCBiZSBnb2luZyBvbj8KPj4gPgo+ Pgo+PiBObyBjbHVlLiBCdXQgYSBwb3NzaWJsZSBraW5kIG9mIGV4cGVyaW1lbnQgLiAuIC4KPj4K Pj4gdG9wIGtlZXBzIGl0cyBzc2ggY29ubmVjdGlvbiBpbiB1c2Ugb24gYSByYXRoZXIKPj4gZnJl cXVlbnQgYmFzaXMsIGV2ZW4gaWYgdGhlIG1vdW50IG9mIHRyYWZmaWMgaXMKPj4gbm90IGxhcmdl Lgo+Pgo+PiBUcnkgaGF2aW5nIHNvbWUgb3RoZXIgc3NoIHNlc3Npb24gaW50byB0aGUgMTIuMQo+ PiBTdGFibGUgRnJlZUJTRCBzeXN0ZW0gdGhhdCBhbHNvIGtlZXBzIGl0cyBzc2gKPj4gY29ubmVj dGlvbiBpbiB1c2Ugb24gYSByYXRoZXIgZnJlcXVlbnQgYmFzaXMuCj4+IERvZXMgaXQgZ2V0IHRo ZSBzYW1lIGlzc3VlIGFzIHRoZSB0b3Agc2Vzc2lvbnMKPj4gZG8/IChOZWVkIG5vdCBiZSBhdCB0 aGUgc2FtZSB0aW1lcyBidXQgaWYgdGhlCj4+IHRpbWVzIHdlcmUgbmVhciBlYWNoIG90aGVyIGZv ciBmYWlsdXJlcyB0aGF0Cj4+IG1pZ2h0IGluZGljYXRlIHNvbWV0aGluZy4pCj4+Cj4+IE9mIGNv dXJzZSwgaXQgbWF5IGJlIHRoYXQgc29tZSBvZiB5b3VyIG90aGVyIHNzaAo+PiBjb25uZWN0aW9u cyB0byB0aGUgc2FtZSBzeXN0ZW0gYWxyZWFkeSBkbyB0aGlzCj4+IHRlc3QgLS1vciBpdCBtYXkg YmUgdGhleSBhbGwgcmFyZWx5IHB1dCB0aGVpcgo+PiBjb25uZWN0aW9uIHRvIHVzZSAoY29tcGFy ZWQgdG8gdG9wKS4KPj4KPiBJbiBhIGNvdXBsZSBvZiBjYXNlcyB0b3Agc2Vzc2lvbnMgZGlzY29u bmVjdGVkIGFzCj4gZGVzY3JpYmVkIHdoaWxlIGdzdGF0IHNlc3Npb25zIGtlcCBydW5uaW5nLiBU aGUKPiBzdGF0aXN0aWNzIGFyZW4ndCB2ZXJ5IGdvb2Qgb24gdGhpcywgd2l0aCBvbmx5Cj4gdGhy ZWUgb3IgZm91ciBjYXNlcyB0b3RhbCBhbmQgYXQgbGVhc3Qgb25lIHdoZXJlCj4gbm8gZGlzY29u bmVjdGlvbiBvY2N1cnJlZC4KPgo+IFRoZSBjbGllbnQgbWFjaGluZSBmcm9tIHdoaWNoIGFsbCB0 aGUgc2Vzc2lvbnMgYXJlCj4gb2JzZXJ2ZWQgaXMgYSBQaTNCKyBydW5uaW5nIFJhc3BiZXJyeSBQ aSBCdXN0ZXIuIEl0J3MKPiBiZWVuIGZvdW5kIHRoYXQgYWxsIHNzaCBzZXNzaW9ucyBhcmUgbW9y ZSBzdGFibGUgaWYKPiB0aGVyZSdzIGFuIG9uZ29pbmcgcGluZyAtaSAxMCB0byB0aGUgV0FQLiBJ IGRvbid0Cj4gc2VlIGhvdyB0aGF0IHdvdWxkIGJlIHNpZ25pZmljYW50IGJ1dCBtYXliZSBpdCBp cy4KPgo+IFRoYW5rcyBmb3Igd3JpdGluZywKPgo+IGJvYiBwcm9oYXNrYQo+Cj4gX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiBmcmVlYnNkLWFybUBmcmVl YnNkLm9yZyBtYWlsaW5nIGxpc3QKPiBodHRwczovL2xpc3RzLmZyZWVic2Qub3JnL21haWxtYW4v bGlzdGluZm8vZnJlZWJzZC1hcm0KPiBUbyB1bnN1YnNjcmliZSwgc2VuZCBhbnkgbWFpbCB0byAi ZnJlZWJzZC1hcm0tdW5zdWJzY3JpYmVAZnJlZWJzZC5vcmci From owner-freebsd-arm@freebsd.org Sat Jun 6 00:29:09 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2734933C169 for ; Sat, 6 Jun 2020 00:29:09 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch [185.70.40.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49f0kX2KV1z4GQY for ; Sat, 6 Jun 2020 00:29:08 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Sat, 06 Jun 2020 00:28:59 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1591403343; bh=MDvciEzn46w16jyISDCS+McnTcZwzz1GyAnBfs/aHtI=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=WFy8J5dYCiz6CbDDZlsly9gIjai1+BIAaBILaI6/ypb7L+ZuuuOEo1oQqhWZ2YGUC u4MIvvuA0kHN3CISbyPcoa6bi58R23mvUbmva7QD3H0AuYKY3gOFMI2yb13z5i3rVx pUbhBrCkzkrSYLLzdhiY/IGhhs2px1oxWKM8NSoA= To: "greg@unrelenting.technology" From: Dan Kotowski Cc: freebsd-arm Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: <940a6099e971e01bd6d04564d0982b9d@unrelenting.technology> References: <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> <940a6099e971e01bd6d04564d0982b9d@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49f0kX2KV1z4GQY X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=WFy8J5dY; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.131 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-4.16 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[185.70.40.131:from]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; NEURAL_HAM_LONG(-0.98)[-0.976]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_SHORT(-1.08)[-1.084]; NEURAL_HAM_MEDIUM(-1.00)[-1.001]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.131:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 00:29:09 -0000 > > > https://gist.github.com/agrajag9/129585436f01876cc4d799382e1c0fac > > > AHCI is looking better and better! I'm going to do a little bit of po= king at that SATA HDD just to > > > see how stable it really is. > > > Posted quirk patch:https://reviews.freebsd.org/D25157 > > > Back to PCI: hmm, maybe the reason that IORT parsing weirdly picks SM= MU up is that ranges with > > > .NumIds=3D0 end up > > > with end before the beginning.. > > > mapping->end =3D map_entry->InputBase + map_entry->IdCount - 1; > > > The ARM document DEN0049D says the field is "The number of IDs in the= range minus one". > > > If my brain still works at all: that means we have to do plus one whe= n interpreting it, not minus > > > one more!! :D > > > This causes the first mapping on the PCIe root complex to be used, wh= en we clearly want the second > > > one. > > > Sooo NOW pcie should work! I promise: > > > https://send.firefox.com/download/05a4e22a349f611f/#azClkvNDfZU-PczXS= mNvaQ > > > > Sad trombone https://gist.github.com/agrajag9/eddb36ad44898c070e464e7ad= d59426d > > hmm. The device ID looks correct to me.. but we can check against NetBSD = just in case. > > Can you boot NetBSD with debug messages (boot -x)? > It should print 'ACPI: IORT mapped devid' messages among other things. > > Also.. about the fact that it's showing up as if the PCIe root is outputt= ing to the SMMU, > maybe that really doesn't sound like a bug, more like the firmware modify= ing the table? > (and the interrupt is actually going to the SMMU?) > But I can't find anything like that in the firmware code. > > An ACPI table dump from running FreeBSD might help: /usr/sbin/acpidump -d= t > And for a full binary dump, install acpica-tools > (if you don't want to bother with USB Ethernet and package installs, > just wget the package on another machine and extract it onto the live ima= ge): > https://pkg.freebsd.org/FreeBSD:13:aarch64/latest/All/acpica-tools-202004= 30.txz > and with that, run: /usr/local/bin/acpidump -b > (creates a bunch of binary files in the current directory) > > Also.. try using your self built firmware again? https://gist.github.com/agrajag9/bce229ac6527b21f91c8337d79e1dae9 Well, my own self-built firmware seems to be misbehaving - it's failing to = see the SD reader or throwing errors about `EFI ASSERT` or things like this= : `Synchronous Exception at 0x00000000ED7BD93C` So continuing to use Jon's for now... `acpidump -b` just spat back "Could not get ACPI table at index 1, AE_NOT_F= OUND" `acpidump -dt` worked just fine Also pulled the output of `acpiview` from the EFI shell again since we're u= sing Jon's latest tables. From owner-freebsd-arm@freebsd.org Sat Jun 6 00:44:11 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6656133CA41 for ; Sat, 6 Jun 2020 00:44:11 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out0.migadu.com (out0.migadu.com [IPv6:2001:41d0:2:267::]) (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 49f13s5lPbz4K0Y for ; Sat, 6 Jun 2020 00:44:09 +0000 (UTC) (envelope-from greg@unrelenting.technology) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1591404242; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=kRfHLXW80iH+hv1/8zQ2IRygB5FDgN1BcYr2sBhF0/A=; b=Po6BWMs045hkwkQEmh1yjBzTXgNMIWHbrd8M/I9pofAV5sFuhjFq9Oq4dUoAV8cLVkdp5W vtZ8E0eC0F5tqYHqVCDhLKhm5UN1Qd+u0BdtrM1PReyJ8sqevDgv3L9SSipB0/xzWxksr0 w+a7JgeYF2g7xq113zvYkdyIxdl7voc= Date: Sat, 06 Jun 2020 00:44:00 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: greg@unrelenting.technology Message-ID: Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: "Dan Kotowski" Cc: "freebsd-arm" In-Reply-To: References: <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> <940a6099e971e01bd6d04564d0982b9d@unrelenting.technology> X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49f13s5lPbz4K0Y X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=Po6BWMs0; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:267:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.71 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.01)[-1.012]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:267::]; NEURAL_HAM_LONG(-1.01)[-1.008]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-0.69)[-0.695]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 00:44:11 -0000 June 6, 2020 3:28 AM, "Dan Kotowski" wro= te:=0A=0A>>> https://gist.github.com/agrajag9/129585436f01876cc4d799382e1= c0fac=0A>>> AHCI is looking better and better! I'm going to do a little b= it of poking at that SATA HDD just=0A>> to=0A>>> see how stable it really= is.=0A>>> Posted quirk patch:https://reviews.freebsd.org/D25157=0A>>> Ba= ck to PCI: hmm, maybe the reason that IORT parsing weirdly picks SMMU up = is that ranges with=0A>>> .NumIds=3D0 end up=0A>>> with end before the be= ginning..=0A>>> mapping->end =3D map_entry->InputBase + map_entry->IdCoun= t - 1;=0A>>> The ARM document DEN0049D says the field is "The number of I= Ds in the range minus one".=0A>>> If my brain still works at all: that me= ans we have to do plus one when interpreting it, not minus=0A>>> one more= !! :D=0A>>> This causes the first mapping on the PCIe root complex to be = used, when we clearly want the=0A>> second=0A>>> one.=0A>>> Sooo NOW pcie= should work! I promise:=0A>>> https://send.firefox.com/download/05a4e22a= 349f611f/#azClkvNDfZU-PczXSmNvaQ=0A>> =0A>> Sad trombone https://gist.git= hub.com/agrajag9/eddb36ad44898c070e464e7add59426d=0A>> =0A>> hmm. The dev= ice ID looks correct to me.. but we can check against NetBSD just in case= .=0A>> =0A>> Can you boot NetBSD with debug messages (boot -x)?=0A>> It s= hould print 'ACPI: IORT mapped devid' messages among other things.=0A>> = =0A>> Also.. about the fact that it's showing up as if the PCIe root is o= utputting to the SMMU,=0A>> maybe that really doesn't sound like a bug, m= ore like the firmware modifying the table?=0A>> (and the interrupt is act= ually going to the SMMU?)=0A>> But I can't find anything like that in the= firmware code.=0A>> =0A>> An ACPI table dump from running FreeBSD might = help: /usr/sbin/acpidump -dt=0A>> And for a full binary dump, install acp= ica-tools=0A>> (if you don't want to bother with USB Ethernet and package= installs,=0A>> just wget the package on another machine and extract it o= nto the live image):=0A>> https://pkg.freebsd.org/FreeBSD:13:aarch64/late= st/All/acpica-tools-20200430.txz=0A>> and with that, run: /usr/local/bin/= acpidump -b=0A>> (creates a bunch of binary files in the current director= y)=0A>> =0A>> Also.. try using your self built firmware again?=0A> =0A> h= ttps://gist.github.com/agrajag9/bce229ac6527b21f91c8337d79e1dae9=0A> =0A>= Well, my own self-built firmware seems to be misbehaving - it's failing = to see the SD reader or=0A> throwing errors about `EFI ASSERT` or things = like this:=0A> =0A> `Synchronous Exception at 0x00000000ED7BD93C`=0A> =0A= > So continuing to use Jon's for now...=0A> =0A> `acpidump -b` just spat = back "Could not get ACPI table at index 1, AE_NOT_FOUND"=0A=0AThat's norm= al, it still creates files in the current directory..=0ABut okay, the acp= iview is good enough.=0A=0A> `acpidump -dt` worked just fine=0A> =0A> Als= o pulled the output of `acpiview` from the EFI shell again since we're us= ing Jon's latest=0A> tables.=0A=0Alol, 0x30 =3D=3D decimal 48. ITS node i= s at 0x30, SMMU at 0x48 (72). How not confusing!=0A=0AYeah so the PCIe ro= ot nodes are indeed pointing at the SMMU, while that's not supposed to be= the case in the public code:=0Ahttps://github.com/SolidRun/edk2-platform= s/blob/eec706c2d693be0b3793d9180e7d1a4813a526cf/Silicon/NXP/LX2160A/AcpiT= ables/Iort.aslc#L220=0A=0AHence my hypothesis that Jon was experimenting = with enabling the SMMU in that build :)=0A=0AMaybe try the firmware from = that google drive link?=0A=0A> [ 1.0000030] panic: Trap: Data Abort (EL= 1): Translation Fault L0 with read access for 0000000000000300: pc ffffc0= 00004aca34: opcode f8607a74: ldr x20, [x19,x0,lsl #3]=0A=0ARight, damn, J= on said that on the new firmware, OSes with the custom layerscape PCIe dr= iver won't work. From owner-freebsd-arm@freebsd.org Sat Jun 6 02:16:53 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6DE1C33F780 for ; Sat, 6 Jun 2020 02:16:53 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49f36r4TN2z4VTX for ; Sat, 6 Jun 2020 02:16:52 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Sat, 06 Jun 2020 02:16:43 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1591409809; bh=pZ3oQzMbLeAXkRKbP4rmA0YBKLu/anQFXBJ06o1+h10=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=W/DK88PxFwRtE7pTBvnN3HGJXrjw4U320KvUNCxw1fkbfxPRmC5J00Q65mk3qmU1v 5LHKwdes5Cc1hZk2SshtboS9YYrA4l186js20nhV7zu9+0WmcxOqRV4cj41FPTBSYJ YVyqGAeOT8e3RhYHC1L8sySRgL82BOGeqcdk6kNI= To: "greg@unrelenting.technology" From: Dan Kotowski Cc: freebsd-arm Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: References: <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> <940a6099e971e01bd6d04564d0982b9d@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49f36r4TN2z4VTX X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=W/DK88Px; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.18 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-4.01 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; NEURAL_HAM_LONG(-1.00)[-0.999]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_SHORT(-0.91)[-0.909]; NEURAL_HAM_MEDIUM(-1.01)[-1.005]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[185.70.40.18:from]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.18:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 02:16:53 -0000 > > > > https://gist.github.com/agrajag9/129585436f01876cc4d799382e1c0fac > > > > AHCI is looking better and better! I'm going to do a little bit of = poking at that SATA HDD just > > > > to > > > > see how stable it really is. > > > > Posted quirk patch:https://reviews.freebsd.org/D25157 > > > > Back to PCI: hmm, maybe the reason that IORT parsing weirdly picks = SMMU up is that ranges with > > > > .NumIds=3D0 end up > > > > with end before the beginning.. > > > > mapping->end =3D map_entry->InputBase + map_entry->IdCount - 1; > > > > The ARM document DEN0049D says the field is "The number of IDs in t= he range minus one". > > > > If my brain still works at all: that means we have to do plus one w= hen interpreting it, not minus > > > > one more!! :D > > > > This causes the first mapping on the PCIe root complex to be used, = when we clearly want the > > > > second > > > > one. > > > > Sooo NOW pcie should work! I promise: > > > > https://send.firefox.com/download/05a4e22a349f611f/#azClkvNDfZU-Pcz= XSmNvaQ > > > > > > Sad trombone https://gist.github.com/agrajag9/eddb36ad44898c070e464e7= add59426d > > > hmm. The device ID looks correct to me.. but we can check against Net= BSD just in case. > > > Can you boot NetBSD with debug messages (boot -x)? > > > It should print 'ACPI: IORT mapped devid' messages among other things= . > > > Also.. about the fact that it's showing up as if the PCIe root is out= putting to the SMMU, > > > maybe that really doesn't sound like a bug, more like the firmware mo= difying the table? > > > (and the interrupt is actually going to the SMMU?) > > > But I can't find anything like that in the firmware code. > > > An ACPI table dump from running FreeBSD might help: /usr/sbin/acpidum= p -dt > > > And for a full binary dump, install acpica-tools > > > (if you don't want to bother with USB Ethernet and package installs, > > > just wget the package on another machine and extract it onto the live= image): > > > https://pkg.freebsd.org/FreeBSD:13:aarch64/latest/All/acpica-tools-20= 200430.txz > > > and with that, run: /usr/local/bin/acpidump -b > > > (creates a bunch of binary files in the current directory) > > > Also.. try using your self built firmware again? > > > > https://gist.github.com/agrajag9/bce229ac6527b21f91c8337d79e1dae9 > > Well, my own self-built firmware seems to be misbehaving - it's failing= to see the SD reader or > > throwing errors about `EFI ASSERT` or things like this: > > `Synchronous Exception at 0x00000000ED7BD93C` > > So continuing to use Jon's for now... > > `acpidump -b` just spat back "Could not get ACPI table at index 1, AE_N= OT_FOUND" > > That's normal, it still creates files in the current directory.. > But okay, the acpiview is good enough. D'oh! > > `acpidump -dt` worked just fine > > Also pulled the output of `acpiview` from the EFI shell again since we'= re using Jon's latest > > tables. > > lol, 0x30 =3D=3D decimal 48. ITS node is at 0x30, SMMU at 0x48 (72). How = not confusing! > > Yeah so the PCIe root nodes are indeed pointing at the SMMU, while that's= not supposed to be the case in the public code: > https://github.com/SolidRun/edk2-platforms/blob/eec706c2d693be0b3793d9180= e7d1a4813a526cf/Silicon/NXP/LX2160A/AcpiTables/Iort.aslc#L220 > > Hence my hypothesis that Jon was experimenting with enabling the SMMU in = that build :) > > Maybe try the firmware from that google drive link? My old one worked this time? I really couldn't tell you what I did differen= tly, but this isn't the first time where I had seemingly non-deterministic = boot problems that go away when I swap firmwares. > > [ 1.0000030] panic: Trap: Data Abort (EL1): Translation Fault L0 with r= ead access for 0000000000000300: pc ffffc000004aca34: opcode f8607a74: ldr = x20, [x19,x0,lsl #3] > > Right, damn, Jon said that on the new firmware, OSes with the custom laye= rscape PCIe driver won't work. D'oh again! Now, here's something different - this time when loading the mps driver, it= failed back to the shell. In all prior testing it would just hang forever. Also, bye-bye ahci without Jon's ECAM fix :/ https://gist.github.com/agrajag9/64c7070a40135f397a9dc8d841954590 From owner-freebsd-arm@freebsd.org Sat Jun 6 17:54:21 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8B6DF33A709 for ; Sat, 6 Jun 2020 17:54:21 +0000 (UTC) (envelope-from luke@lukeross.name) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) (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 49fRwX2tsBz4SrB for ; Sat, 6 Jun 2020 17:54:20 +0000 (UTC) (envelope-from luke@lukeross.name) X-Originating-IP: 84.45.129.34 Received: from clara.lan (unknown [84.45.129.34]) (Authenticated sender: luke@lukeross.name) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id 377D31C0005 for ; Sat, 6 Jun 2020 17:54:18 +0000 (UTC) Message-ID: Subject: Re: Problems with cdce/cdceem as a USB-device on R-Pi From: Luke Ross To: freebsd-arm@freebsd.org Date: Sat, 06 Jun 2020 18:54:17 +0100 In-Reply-To: References: <75a918d07625de979e9995b3f01662c9deb0a9c1.camel@lukeross.name> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.2-0ubuntu1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49fRwX2tsBz4SrB X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of luke@lukeross.name designates 217.70.183.197 as permitted sender) smtp.mailfrom=luke@lukeross.name X-Spamd-Result: default: False [-2.42 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.88)[-0.883]; RWL_MAILSPIKE_POSSIBLE(0.00)[217.70.183.197:from]; DMARC_NA(0.00)[lukeross.name]; R_SPF_ALLOW(-0.20)[+ip4:217.70.183.192/28]; NEURAL_HAM_SHORT(-0.22)[-0.224]; NEURAL_HAM_MEDIUM(-0.91)[-0.912]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:29169, ipnet:217.70.176.0/20, country:FR]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[217.70.183.197:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 17:54:21 -0000 Hi, On Wed, 2020-06-03 at 20:13 +0200, Hans Petter Selasky wrote: > On 2020-06-03 19:51, Luke Ross wrote: > > cdceem0: WARNING: cdceem_bulk_read_callback: USB_ST_ERROR: > > USB_ERR_STALLED > > Try to have a look at the USB traffic using: > > usbdump -i usbusX -f Y -s 65536 > > At both client and server side. Might be a controller driver bug, or > the > chip is out of available endpoints, I.E. that you can only have > either > ethernet or serial, but not both. Thanks for the suggestion. I gave it a try, but unfortunately my knowledge of USB isn't enough to really understand what's going on; I'm rather out of my depth here. In cdce mode (no network traffic), when I start the ping there's a brief moment of USB activity at both ends, and no usbdump errors logged. After that, the USB activity completely stops at both ends (empty log) even though the ping is still running. In cdceem mode (network traffic passes, but regular stalls/timeouts) you can see the stalls in the usbdump logs on the host, but it doesn't seem to consistently affect one endpoint - several endpoints seem to be used during the cdceem communication and the stall typically affects more than one (at different times). There's no sign of errors in the dump on the device. One weird observation in cdceem mode - if I ssh into the device, the ssh process will eventually timeout when negotiating the connection (the login never completes). However if I leave a ping to the device running in the background, the USB stalls still happen but the ssh session works as normal (albeit with spikes in latency) - suggesting the extra traffic is able to somehow "unstall". Many thanks, Luke From owner-freebsd-arm@freebsd.org Sat Jun 6 18:15:22 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6348F33ADE9 for ; Sat, 6 Jun 2020 18:15:22 +0000 (UTC) (envelope-from crowston@protonmail.com) Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch [185.70.40.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49fSNn2bSyz4Vgs for ; Sat, 6 Jun 2020 18:15:20 +0000 (UTC) (envelope-from crowston@protonmail.com) Date: Sat, 06 Jun 2020 18:15:10 +0000 To: freebsd-arm From: Robert Crowston Reply-To: Robert Crowston Subject: Report: FreeBSD on Rpi4 8 GB model Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49fSNn2bSyz4Vgs X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.32 / 15.00]; HAS_REPLYTO(0.00)[crowston@protonmail.com]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[185.70.40.131:from]; FREEMAIL_FROM(0.00)[protonmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[protonmail.com]; NEURAL_HAM_LONG(-1.01)[-1.010]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_MEDIUM(-0.78)[-0.785]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[protonmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; NEURAL_HAM_SHORT(-0.43)[-0.430]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.131:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 18:15:22 -0000 What works: - FreeBSD SMP (see below) - All 8 GB of memory (less video RAM). What does not work on the 8 GB model (but does work on the 4 GB model): - xhci (with my driver, there has been a change in the way the firmware is = loaded) - ethernet (genet0 is detected fine, appears to be up, but no packets go ov= er the interface) - JTAG debugging (urgh) dmesg: https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5534 You will need the latest u-boot. The one in pkg doesn't work. I compiled fr= om head: https://github.com/u-boot/u-boot.git For SMP, you need also need to tell u-boot not to clobber over our processo= r start up function set up by armstub8-gic.bin. Edit board/raspberrypi/rpi/Kconfig, set RPI_EFI_NR_SPIN_PAGES to a larger n= umber (I picked 10, probably too big, but it was easier than doing the arit= hmetic). $ CROSS_COMPILE=3Daarch64-none-elf- gmake rpi_4_defconfig $ CROSS_COMPILE=3Daarch64-none-elf- gmake Overwrite the u-boot.bin file on your sdcard with the one just built. You will also need the latest versions of the pi4 firmware files on your MS= DOS partition, bcm2711-rpi-4-b.dtb, fixup4.dat, start4.elf, and the overlay= s/ directory. From owner-freebsd-arm@freebsd.org Sat Jun 6 18:41:25 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 51D5033B633 for ; Sat, 6 Jun 2020 18:41:25 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wr1-x442.google.com (mail-wr1-x442.google.com [IPv6:2a00:1450:4864:20::442]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49fSyr2j3Hz4Z6v for ; Sat, 6 Jun 2020 18:41:24 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: by mail-wr1-x442.google.com with SMTP id j10so13069980wrw.8 for ; Sat, 06 Jun 2020 11:41:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=jStPdXGBOm1zxRMvvYiJSPPTQu9YAJYeq9H2oq06I8c=; b=VJD8z1R4dVo4kv6lqXZl+zqkDB4M1UbLEV/yrd97KT0pEUgtiSelrUbEq/qz43OzMj JMQxeBWZTsOnkuUt4fuxHoTtfUsDWqFEjHrluzHv4iXax7UM1gmmS8CXPzw7KRnxQ26V AWiXWdYDhXRdj6NtiqO7Q7xFihv0Teid9ZDaWWVMTPECCYhWWtoUL7XizmSF+opdpvw9 oOh0AfXskCQjLtbtiUDegOV8OZd5BJSFfh68EpX8bhyOQ7TZ6vKQ7AaLpxfDNNCuTrVp cjD8j6gumFscoR4VWuAHDXG3/JfPMJ+7PxRHK8fKzPlzcjdtWVFxsIOAfxfecD/fZKhF bw+g== X-Gm-Message-State: AOAM530smG4tQo1THvwM22XXkwKnWk8IUpoQZfP1eu/MyWxg5hdq2MBs AaqKbwqfkKgl5wsWkWubsqL8HPjU X-Google-Smtp-Source: ABdhPJz8kudcUcNd2kKnYTpMS3wqoyauW433Z3k8RyhoNVhEIqTVOaAxK2pa7prESTwctwJgp4rmCw== X-Received: by 2002:a5d:4390:: with SMTP id i16mr14720610wrq.186.1591468882908; Sat, 06 Jun 2020 11:41:22 -0700 (PDT) Received: from [192.168.1.167] ([46.114.107.179]) by smtp.googlemail.com with ESMTPSA id v7sm12225530wro.76.2020.06.06.11.41.21 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Jun 2020 11:41:22 -0700 (PDT) From: =?utf-8?Q?Klaus_K=C3=BCchemann?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Report: FreeBSD on Rpi4 8 GB model Date: Sat, 6 Jun 2020 20:41:20 +0200 References: To: Robert Crowston , freebsd-arm@freebsd.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49fSyr2j3Hz4Z6v X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.24 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[googlemail.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; NEURAL_HAM_SHORT(-0.71)[-0.709]; FREEMAIL_TO(0.00)[protonmail.com,freebsd.org]; RECEIVED_SPAMHAUS_PBL(0.00)[46.114.107.179:received]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[googlemail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.01)[-1.011]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.02)[-1.017]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::442:from]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 18:41:25 -0000 Thanks Robert, can I or can you transfer your information into the wiki? My 8GB model was not bootable under UEFI. I didn't know that u-boot had a current patch. Could you provide a u-boot binary and/or your modified armstub8-gic.bin = for the wiki? I could upload that to a server and make it available for download . Do you know whether sysutils/u-boot.xx- port(not pkg) could be targeted = to 2020.07=20 to fix any issue with u-boot? Afaik u-boot 2020.07 has new patches for genet and pcie(!)=E2=80=A6 do = you know details about that? > Am 06.06.2020 um 20:15 schrieb Robert Crowston via freebsd-arm = : >=20 > What works: > - FreeBSD SMP (see below) > - All 8 GB of memory (less video RAM). >=20 > What does not work on the 8 GB model (but does work on the 4 GB = model): > - xhci (with my driver, there has been a change in the way the = firmware is loaded) > - ethernet (genet0 is detected fine, appears to be up, but no packets = go over the interface) > - JTAG debugging (urgh) >=20 > dmesg: https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5534 >=20 > You will need the latest u-boot. The one in pkg doesn't work. I = compiled from head: https://github.com/u-boot/u-boot.git >=20 > For SMP, you need also need to tell u-boot not to clobber over our = processor start up function set up by armstub8-gic.bin. >=20 > Edit board/raspberrypi/rpi/Kconfig, set RPI_EFI_NR_SPIN_PAGES to a = larger number (I picked 10, probably too big, but it was easier than = doing the arithmetic). >=20 > $ CROSS_COMPILE=3Daarch64-none-elf- gmake rpi_4_defconfig > $ CROSS_COMPILE=3Daarch64-none-elf- gmake >=20 > Overwrite the u-boot.bin file on your sdcard with the one just built. >=20 > You will also need the latest versions of the pi4 firmware files on = your MSDOS partition, bcm2711-rpi-4-b.dtb, fixup4.dat, start4.elf, and = the overlays/ directory. >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Sat Jun 6 19:13:29 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8ADF033BF68 for ; Sat, 6 Jun 2020 19:13:29 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49fTgr4mXvz4dyV for ; Sat, 6 Jun 2020 19:13:28 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: by mail-wm1-x32e.google.com with SMTP id u13so11463916wml.1 for ; Sat, 06 Jun 2020 12:13:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=2IjJwaMm+iFwGpEVXWIVscEC3o0dPtiPO5cbI5DqtgU=; b=J54nDmSACuM1P7BV7RqrLuwGkuDatX05ypQ0HBL6GZ4ByWEyW4Qbe5U/XnuHb73AFX ekc+KXCIOmVAIcvaPXOsh1jVprXPQ58XgdQZOfPXqigmDeh8dvGhyKtNZef1c5vC+91N LkHEYQe1i9vPVSSRcl4o6kp5mPp6+hwr5sdXlX6dyux/8TRwcKyc5k0zf6Ln2jNjI0Vc SA0Qy88FJ0DDwllG80PCfz7K/EkWbzFxgnPsrf0HKgX0uhFHvthuWZHxQLtLfyfuf1aX Nt65irlAFdoid0H1hGNe0qGJQE0yD2c73Aealxte4Bp2EIdlrHbGaHmnMlBV2bhibjLT FOPg== X-Gm-Message-State: AOAM530kXnB23koFBNImX204kOvWJTVVZMIQbcYHpDvnZwhQFgUcRP/t epEqiWJJaUAxX9D8/caKOcE= X-Google-Smtp-Source: ABdhPJy5s/dnt5RFBVWglySEDNAVm7JX5hgjjuHAzmY6mqQePaBfwLO+qfuclcgASmQa5k+YoNT3Yw== X-Received: by 2002:a7b:cbcc:: with SMTP id n12mr8061470wmi.127.1591470806568; Sat, 06 Jun 2020 12:13:26 -0700 (PDT) Received: from [192.168.1.167] ([46.114.107.179]) by smtp.googlemail.com with ESMTPSA id l17sm16567629wmi.16.2020.06.06.12.13.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Jun 2020 12:13:25 -0700 (PDT) From: =?utf-8?Q?Klaus_K=C3=BCchemann?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Report: FreeBSD on Rpi4 8 GB model Date: Sat, 6 Jun 2020 21:13:24 +0200 References: To: Robert Crowston , freebsd-arm@freebsd.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49fTgr4mXvz4dyV X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.24 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[googlemail.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; NEURAL_HAM_SHORT(-0.71)[-0.712]; FREEMAIL_TO(0.00)[protonmail.com,freebsd.org]; RECEIVED_SPAMHAUS_PBL(0.00)[46.114.107.179:received]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[googlemail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.01)[-1.011]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.02)[-1.015]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::32e:from]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 19:13:29 -0000 > Am 06.06.2020 um 20:15 schrieb Robert Crowston via freebsd-arm = : >=20 > =E2=80=A6... > Edit board/raspberrypi/rpi/Kconfig, set RPI_EFI_NR_SPIN_PAGES to a = larger number (I picked 10, probably too big, but it was easier than = doing the arithmetic). >=20 > =E2=80=A6=E2=80=A6 >=20 You mean that https://reviews.freebsd.org/D24085 rpi4_fragment has to = set SPIN_PAGES from 2 to 10 ? This could be done in sysutils/u-boot-rpi4 , perhaps with something like = an #ifdef RPI4/8GB=E2=80=9C for the first try . From owner-freebsd-arm@freebsd.org Sat Jun 6 19:20:09 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2B85F33C386 for ; Sat, 6 Jun 2020 19:20:09 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49fTqY0PCQz4fC5 for ; Sat, 6 Jun 2020 19:20:09 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qt1-f176.google.com (mail-qt1-f176.google.com [209.85.160.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id F0E6728A7F for ; Sat, 6 Jun 2020 19:20:08 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qt1-f176.google.com with SMTP id g62so8001791qtd.5 for ; Sat, 06 Jun 2020 12:20:08 -0700 (PDT) X-Gm-Message-State: AOAM533zXS3TVXYwf2XHkM67eA6Aa8yS8P2PZ043EuefiwTZXL4lSEQt 0QptME03rVaLSM7Jz0W7vleGX/WoOe13hBpTRpk= X-Google-Smtp-Source: ABdhPJyngZ8nVMUssurxuaqBlU+bKPDFIOsCY6iPG8b1CQsz+M/NfSPqfopIa4Z/ZbX2rZorc46ZzQd+mfIgnHZozLA= X-Received: by 2002:aed:3169:: with SMTP id 96mr15601556qtg.211.1591471208632; Sat, 06 Jun 2020 12:20:08 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kyle Evans Date: Sat, 6 Jun 2020 14:19:55 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Report: FreeBSD on Rpi4 8 GB model To: =?UTF-8?Q?Klaus_K=C3=BCchemann?= Cc: Robert Crowston , "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.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 19:20:09 -0000 On Sat, Jun 6, 2020 at 2:13 PM Klaus K=C3=BCchemann via freebsd-arm wrote: > > > > > Am 06.06.2020 um 20:15 schrieb Robert Crowston via freebsd-arm : > > > > =E2=80=A6... > > Edit board/raspberrypi/rpi/Kconfig, set RPI_EFI_NR_SPIN_PAGES to a larg= er number (I picked 10, probably too big, but it was easier than doing the = arithmetic). > > > > =E2=80=A6=E2=80=A6 > > > > You mean that https://reviews.freebsd.org/D24085 rpi4_fragment has to se= t SPIN_PAGES from 2 to 10 ? > This could be done in sysutils/u-boot-rpi4 , perhaps with something like = an #ifdef RPI4/8GB=E2=80=9C for the first try . > No, SPIN_PAGES=3D2 is fine; the default in upstream is 1 because they don't need any more, so he would've needed to manually bump it to 2. You should be able to just add CONFIG_NR_DRAM_BANKS=3D8 to sysutils/u-boot-rpi4's rpi4_fragment and it 'just work' -- this was tested on IRC a couple days ago, and should be safe for all variants as far as I'm aware (but needed to test on my 4GB variant). Even without this setting, it should still largely boot; you'll just only have half the memory you wanted. Thanks, Kyle Evans From owner-freebsd-arm@freebsd.org Sat Jun 6 19:29:29 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2A59C33C903 for ; Sat, 6 Jun 2020 19:29:29 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49fV2J4WdHz4gHM; Sat, 6 Jun 2020 19:29:28 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: by mail-wm1-x333.google.com with SMTP id l26so11465269wme.3; Sat, 06 Jun 2020 12:29:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=4+Lx8NMaMySmFUUbIn+aglH/i2YkoB/hUDifKN/Ywjw=; b=akwc+bcb9OrCcfk9Zr32CvvMqpeS+fFuMI/rpB2IVq3WgFEx5IhxaAi1W4EcPa4tdm 0wJP83Nic+p9a/QdO0zjUPfVGuuFBSxAWxHRav6HMqP+XUqspQme6J+SJ99HDDei4Y1g +I7tSRI5P8inlXNpCQqXwEdrAyZ7p8qkVVoQHL50EIEyyVrL6nCbsmPk2d1KrqXFqCF5 +yEv1cXWw3Bdya6iDXDBHJJ32h77odcD0F8S1RdPeHgv7G7oZvri1ylnxoILUSN9GfFi etkD39NygunBNL11nW+6dh9aXdE7UYLLCd79UF7BusVil2CBLfhHhA9kFldt1HBJ6Rjj V5Fw== X-Gm-Message-State: AOAM531hENFSdiJfD1xM40riu/pWzT7BlYJq0EzD6wt+/sp8R5BIG7xj Itpl0DVYsR/35S0FQSjPASJISAXs X-Google-Smtp-Source: ABdhPJzAGxw8As3oAiKbG08BZPRyNcxAR2oH8KoE9wmUoOKDMth26acLjvTSRfvbTwgF1WqxrA/YFQ== X-Received: by 2002:a1c:230f:: with SMTP id j15mr8924616wmj.100.1591471766745; Sat, 06 Jun 2020 12:29:26 -0700 (PDT) Received: from [192.168.1.167] ([46.114.107.179]) by smtp.googlemail.com with ESMTPSA id d16sm16810051wmd.42.2020.06.06.12.29.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Jun 2020 12:29:25 -0700 (PDT) From: =?utf-8?Q?Klaus_K=C3=BCchemann?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Report: FreeBSD on Rpi4 8 GB model Date: Sat, 6 Jun 2020 21:29:24 +0200 References: To: Kyle Evans , freebsd-arm@freebsd.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49fV2J4WdHz4gHM X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 19:29:29 -0000 > Am 06.06.2020 um 21:19 schrieb Kyle Evans : >=20 > On Sat, Jun 6, 2020 at 2:13 PM Klaus K=C3=BCchemann via freebsd-arm > wrote: >>=20 >>=20 >>=20 >>> Am 06.06.2020 um 20:15 schrieb Robert Crowston via freebsd-arm = : >>>=20 >>> =E2=80=A6... >>> Edit board/raspberrypi/rpi/Kconfig, set RPI_EFI_NR_SPIN_PAGES to a = larger number (I picked 10, probably too big, but it was easier than = doing the arithmetic). >>>=20 >>> =E2=80=A6=E2=80=A6 >>>=20 >>=20 >> You mean that https://reviews.freebsd.org/D24085 rpi4_fragment has = to set SPIN_PAGES from 2 to 10 ? >> This could be done in sysutils/u-boot-rpi4 , perhaps with something = like an #ifdef RPI4/8GB=E2=80=9C for the first try . >>=20 >=20 > No, SPIN_PAGES=3D2 is fine; the default in upstream is 1 because they > don't need any more, so he would've needed to manually bump it to 2. >=20 > You should be able to just add CONFIG_NR_DRAM_BANKS=3D8 to > sysutils/u-boot-rpi4's rpi4_fragment and it 'just work' -- this was > tested on IRC a couple days ago, and should be safe for all variants > as far as I'm aware (but needed to test on my 4GB variant). Even > without this setting, it should still largely boot; you'll just only > have half the memory you wanted. >=20 > Thanks, >=20 > Kyle Evans Ah, thanks a lot ! So it was too hasty from me to post to = https://reviews.freebsd.org/D24085 :-) Regards Klaus= From owner-freebsd-arm@freebsd.org Sat Jun 6 19:40:34 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 35F7233C82C for ; Sat, 6 Jun 2020 19:40:34 +0000 (UTC) (envelope-from crowston@protonmail.com) Received: from mail-40134.protonmail.ch (mail-40134.protonmail.ch [185.70.40.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49fVH51FNFz3SF8 for ; Sat, 6 Jun 2020 19:40:33 +0000 (UTC) (envelope-from crowston@protonmail.com) Date: Sat, 06 Jun 2020 19:40:25 +0000 To: =?UTF-8?Q?Klaus_K=C3=BCchemann?= From: Robert Crowston Cc: "freebsd-arm@freebsd.org" Reply-To: Robert Crowston Subject: Re: Report: FreeBSD on Rpi4 8 GB model Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49fVH51FNFz3SF8 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.08 / 15.00]; HAS_REPLYTO(0.00)[crowston@protonmail.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[protonmail.com]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; DKIM_TRACE(0.00)[protonmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; NEURAL_HAM_SHORT(-1.00)[-0.995]; FREEMAIL_TO(0.00)[googlemail.com]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.134:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.96)[-0.957]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.03)[-1.033]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[protonmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.134:from] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 19:40:34 -0000 > can I or can you transfer your information into the wiki? No objection. If you prefer me to do it, I'll get around to it eventually. > Do you know whether sysutils/u-boot.xx- port(not pkg) could be targeted t= o 2020.07 > to fix any issue with u-boot? It's still June isn't it??? Working from home for so many weeks I've lost a= ll sense of time, but I'm pretty sure it isn't July yet :-) (I haven't tried this branch but presumably it has whatever fixed the 8 GB = model.) > Could you provide a u-boot binary and/or your modified armstub8-gic.bin f= or the wiki? I'm using the armstub8-gic.bin from /usr/local/share/rpi-firmware/armstub8-= gic.bin. I don't believe the upstream Pi Foundation code has changed for th= e 8 GB model. I'll mail you the u-boot.bin directly. > Afaik u-boot 2020.07 has new patches for genet and pcie(!)=E2=80=A6 do yo= u know details about that? Don't see either working here, but I haven't investigated more than mashing= the keyboard on boot. :) (Also, if it were fixed, presumably the xhci cont= roller would have the right firmware loaded before FreeBSD started.) =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Saturday, 6 June 2020 19:41, Klaus K=C3=BCchemann wrote: > Thanks Robert, > can I or can you transfer your information into the wiki? > My 8GB model was not bootable under UEFI. > I didn't know that u-boot had a current patch. > Could you provide a u-boot binary and/or your modified armstub8-gic.bin f= or the wiki? > I could upload that to a server and make it available for download . > Do you know whether sysutils/u-boot.xx- port(not pkg) could be targeted t= o 2020.07 > to fix any issue with u-boot? > Afaik u-boot 2020.07 has new patches for genet and pcie(!)=E2=80=A6 do yo= u know details about that? > > > Am 06.06.2020 um 20:15 schrieb Robert Crowston via freebsd-arm freebsd-= arm@freebsd.org: > > What works: > > > > - FreeBSD SMP (see below) > > - All 8 GB of memory (less video RAM). > > > > What does not work on the 8 GB model (but does work on the 4 GB model): > > > > - xhci (with my driver, there has been a change in the way the firmwa= re is loaded) > > - ethernet (genet0 is detected fine, appears to be up, but no packets= go over the interface) > > - JTAG debugging (urgh) > > > > dmesg: https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5534 > > You will need the latest u-boot. The one in pkg doesn't work. I compile= d from head: https://github.com/u-boot/u-boot.git > > For SMP, you need also need to tell u-boot not to clobber over our proc= essor start up function set up by armstub8-gic.bin. > > Edit board/raspberrypi/rpi/Kconfig, set RPI_EFI_NR_SPIN_PAGES to a larg= er number (I picked 10, probably too big, but it was easier than doing the = arithmetic). > > $ CROSS_COMPILE=3Daarch64-none-elf- gmake rpi_4_defconfig > > $ CROSS_COMPILE=3Daarch64-none-elf- gmake > > Overwrite the u-boot.bin file on your sdcard with the one just built. > > You will also need the latest versions of the pi4 firmware files on you= r MSDOS partition, bcm2711-rpi-4-b.dtb, fixup4.dat, start4.elf, and the ove= rlays/ directory. > > > > 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 Sat Jun 6 19:45:05 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B392233C867 for ; Sat, 6 Jun 2020 19:45:05 +0000 (UTC) (envelope-from crowston@protonmail.com) Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch [185.70.40.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49fVNK06LWz3T32 for ; Sat, 6 Jun 2020 19:45:04 +0000 (UTC) (envelope-from crowston@protonmail.com) Date: Sat, 06 Jun 2020 19:44:58 +0000 To: =?UTF-8?Q?Klaus_K=C3=BCchemann?= From: Robert Crowston Cc: Kyle Evans , "freebsd-arm@freebsd.org" Reply-To: Robert Crowston Subject: Re: Report: FreeBSD on Rpi4 8 GB model Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49fVNK06LWz3T32 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.06 / 15.00]; HAS_REPLYTO(0.00)[crowston@protonmail.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24:c]; FREEMAIL_FROM(0.00)[protonmail.com]; RWL_MAILSPIKE_GOOD(0.00)[185.70.40.131:from]; DKIM_TRACE(0.00)[protonmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; NEURAL_HAM_SHORT(-0.95)[-0.955]; FREEMAIL_TO(0.00)[googlemail.com]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.131:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.97)[-0.967]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.04)[-1.035]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[protonmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 19:45:05 -0000 > No, SPIN_PAGES=3D2 is fine I confirm that CONFIG_RPI_EFI_NR_SPIN_PAGES 2 is sufficient. > Even without this setting, it should still largely boot; > you'll just only have half the memory you wanted. Without raising the spin pages limit, the kernel panics while trying to sta= rt the secondary CPUs. I don't have a working JTAG so I can't diagnose exac= tly why, but the spin table thing seemed like an obvious thing to check. Starting CPU 1 (1) panic: Failed to start CPU 1 (1), error 16 cpuid =3D 0 time =3D 1 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc =3D 0xffff00000075cd0c lr =3D 0xffff00000010a0ac sp =3D 0xffff000000010590 fp =3D 0xffff000000010790 db_trace_self_wrapper() at vpanic+0x194 pc =3D 0xffff00000010a0ac lr =3D 0xffff0000004185c0 sp =3D 0xffff0000000107a0 fp =3D 0xffff0000000107f0 vpanic() at panic+0x44 pc =3D 0xffff0000004185c0 lr =3D 0xffff000000418368 sp =3D 0xffff000000010800 fp =3D 0xffff0000000108b0 panic() at start_cpu+0x224 pc =3D 0xffff000000418368 lr =3D 0xffff00000076bd94 sp =3D 0xffff0000000108c0 fp =3D 0xffff0000000108c0 start_cpu() at cpu_init_fdt+0x34 pc =3D 0xffff00000076bd94 lr =3D 0xffff00000076b094 sp =3D 0xffff0000000108d0 fp =3D 0xffff000000010930 cpu_init_fdt() at ofw_cpu_early_foreach+0x180 pc =3D 0xffff00000076b094 lr =3D 0xffff00000020e0cc sp =3D 0xffff000000010940 fp =3D 0xffff000000010990 ofw_cpu_early_foreach() at mp_start+0x8c pc =3D 0xffff00000020e0cc lr =3D 0xffff000000472e98 sp =3D 0xffff0000000109a0 fp =3D 0xffff0000000109f0 mp_start() at mi_startup+0x12c pc =3D 0xffff000000472e98 lr =3D 0xffff0000003abfcc sp =3D 0xffff000000010a00 fp =3D 0xffff000000010a20 mi_startup() at virtdone+0x5c pc =3D 0xffff0000003abfcc lr =3D 0xffff00000000108c sp =3D 0xffff000000010a30 fp =3D 0x0000000000000000 KDB: enter: panic =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Saturday, 6 June 2020 20:29, Klaus K=C3=BCchemann via freebsd-arm wrote: > > > > Am 06.06.2020 um 21:19 schrieb Kyle Evans kevans@freebsd.org: > > On Sat, Jun 6, 2020 at 2:13 PM Klaus K=C3=BCchemann via freebsd-arm > > freebsd-arm@freebsd.org wrote: > > > > > > Am 06.06.2020 um 20:15 schrieb Robert Crowston via freebsd-arm free= bsd-arm@freebsd.org: > > > > =E2=80=A6... > > > > Edit board/raspberrypi/rpi/Kconfig, set RPI_EFI_NR_SPIN_PAGES to a = larger number (I picked 10, probably too big, but it was easier than doing = the arithmetic). > > > > =E2=80=A6=E2=80=A6 > > > > > > You mean that https://reviews.freebsd.org/D24085 rpi4_fragment has to= set SPIN_PAGES from 2 to 10 ? > > > This could be done in sysutils/u-boot-rpi4 , perhaps with something l= ike an #ifdef RPI4/8GB=E2=80=9C for the first try . > > > > No, SPIN_PAGES=3D2 is fine; the default in upstream is 1 because they > > don't need any more, so he would've needed to manually bump it to 2. > > You should be able to just add CONFIG_NR_DRAM_BANKS=3D8 to > > sysutils/u-boot-rpi4's rpi4_fragment and it 'just work' -- this was > > tested on IRC a couple days ago, and should be safe for all variants > > as far as I'm aware (but needed to test on my 4GB variant). Even > > without this setting, it should still largely boot; you'll just only > > have half the memory you wanted. > > Thanks, > > Kyle Evans > > Ah, thanks a lot ! > So it was too hasty from me to post to https://reviews.freebsd.org/D24085= :-) > Regards > Klaus > > 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 Sat Jun 6 19:55:17 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 174B133CD78 for ; Sat, 6 Jun 2020 19:55:17 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic311-24.consmr.mail.gq1.yahoo.com (sonic311-24.consmr.mail.gq1.yahoo.com [98.137.65.205]) (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 49fVc35RyZz3V9H for ; Sat, 6 Jun 2020 19:55:15 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: A1O7GxIVM1m2B5iPjoaOty.JtYSlWr14l1fe_T_3OfN0SP4YDT0QcJN0ukosrYN KaGs56_bA1Z9E5KEwMX4tB57uWF87PztRFucztEmQVZfjOpD_32qp6sprAr4sfKfXnVtcBTTbiub JusxXJWa4Gx0_CWhwMPbPbHX__5lgq1qsL7yxTu1ycXFui2w0UWPnhq5.IsWH1dKS7bN5daRxeUg FNkRSa21mbsFevEoMfk9zdDCr_z9cxatAPTQvEXtbGrA4PJGO7EECORo3JIlpjtvfymuXif7cExf kH3l08YGw2ZuQ2oJf3BgRAxJv3MG1FNCaqDhzwIjRIzUPM_XKSRHfBnWs2xw4DL3CLxusWSa9AU3 70bvKPmv7MWA.chVQbrDqWTygNbu7gAuLyQm997vBggwsf8XCTyYschF4RzBwDq8pe_jlywUd6EG BXTmGfQM_jGNQB79Va5UWd1ePU8ZAmolHgRZmJGOWlY3j..OL_2PepzlcWjuWPVS_Z91pkVVDS2. kStaB19Frm.taTL9uMf0zU0.pAMZKC10ZeJ4GSlbD1Cx.B6dctD6O7zP.tBAb11fLOi3EJ6_uNMz Pemo3DGPkrneqyCZD.KLf8JNlyCPu_jR.e8S_N.bK8bBybsszabdwfyO6WfPHyqIKeYS4FYp07Ys IHqgSDSdRYz_LbDMBE_Zi_i2OVMFQXnANNjPAjrizgjcA1gpRWB.QD8msSt4ZJcm23MJRUumQHn2 QS6dG6bvh8wGFXK_ZYAVS1_4RPj7tu.sfWjGAVVEuSepAjnilQDh23Obdxygk_LAJm6X.fxs8Kkn 4heXvwLwK5rumUX_pJsL_U9bmbjcpLN0pHbaQ6kZq2a640eAyAXKq_LgHpZlO2lwLuQOtc9soCTI pbOi2iKKiqdjuIKllAQc0yP265IQR4pzRw0p8NHRvMoxK1VBzZNj8lU46M1DF8_WFz9y3XmZ8Df7 V284sm8DDibsyRj.U4BM4kLDB7uBZueXqrFpqWTkDPPt30ZGyv1O7ZAVEThTtgLoWtINFKNKwmvc hLH3RJsCfQBl6Wzzb5iLiduslm6zbJoEQy_ZtNscPhqsMer0S4Oeej3J5xBD5kN9fU_GkYa3Jof0 lX4LUSO72dik6kfq.ad6857Y40xRcB15_9eBCS0lTjCCjCDRvHNNVB73eZSoMYyz982ooOmWtXDd w03iqZzGkJk6.snXvqYLfdxJCqjQWjQwBgRnmMWC8QNBFCpRVv8WOqs1.6ZaDKhlHM.R.PeSKY6D aPZonwzZqLP0cpvUNd3zs2IqKMtaBdxyJv14YtglM7VHcqHtv8ef2sVP_JFXg0qnwuoymIBqIriK TJykZ23i0jvnZ_.edzO9RiYs3YSUKlJc5mcOrTQNLdAm1GEIlgx39L7ZJoSxiBxvqtDfk05QgQGn A6LH_wKnU59ug.t3DK5Pxev.eWBNclVTZiJUWTclcEjw8JpGn2TWqmIbP Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.gq1.yahoo.com with HTTP; Sat, 6 Jun 2020 19:55:13 +0000 Received: by smtp427.mail.ne1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID c9554d7cec46d4ed8d49f86068ed9481; Sat, 06 Jun 2020 19:55:09 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Report: FreeBSD on Rpi4 8 GB model From: Mark Millard In-Reply-To: Date: Sat, 6 Jun 2020 12:55:08 -0700 Cc: =?utf-8?Q?Klaus_K=C3=BCchemann?= , "freebsd-arm@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Robert Crowston X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49fVc35RyZz3V9H X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.24 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-0.74)[-0.742]; FREEMAIL_TO(0.00)[protonmail.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.994]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.01)[-1.007]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.65.205:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.65.205:from]; FREEMAIL_CC(0.00)[googlemail.com,freebsd.org]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 19:55:17 -0000 > On 2020-Jun-6, at 12:44, Robert Crowston via freebsd-arm = wrote: >=20 >> No, SPIN_PAGES=3D2 is fine >=20 > I confirm that CONFIG_RPI_EFI_NR_SPIN_PAGES 2 is sufficient. >=20 >> Even without this setting, it should still largely boot; >> you'll just only have half the memory you wanted. "this setting" for that quote was referencing CONFIG_NR_DRAM_BANKS, not SPIN_PAGES . (See the later note.) So the following misses the point for the above quote. > Without raising the spin pages limit, the kernel panics while trying = to start the secondary CPUs. I don't have a working JTAG so I can't = diagnose exactly why, but the spin table thing seemed like an obvious = thing to check. >=20 > Starting CPU 1 (1) > panic: Failed to start CPU 1 (1), error 16 >=20 > cpuid =3D 0 > time =3D 1 > KDB: stack backtrace: > db_trace_self() at db_trace_self_wrapper+0x28 > pc =3D 0xffff00000075cd0c lr =3D 0xffff00000010a0ac > sp =3D 0xffff000000010590 fp =3D 0xffff000000010790 >=20 > db_trace_self_wrapper() at vpanic+0x194 > pc =3D 0xffff00000010a0ac lr =3D 0xffff0000004185c0 > sp =3D 0xffff0000000107a0 fp =3D 0xffff0000000107f0 >=20 > vpanic() at panic+0x44 > pc =3D 0xffff0000004185c0 lr =3D 0xffff000000418368 > sp =3D 0xffff000000010800 fp =3D 0xffff0000000108b0 >=20 > panic() at start_cpu+0x224 > pc =3D 0xffff000000418368 lr =3D 0xffff00000076bd94 > sp =3D 0xffff0000000108c0 fp =3D 0xffff0000000108c0 >=20 > start_cpu() at cpu_init_fdt+0x34 > pc =3D 0xffff00000076bd94 lr =3D 0xffff00000076b094 > sp =3D 0xffff0000000108d0 fp =3D 0xffff000000010930 >=20 > cpu_init_fdt() at ofw_cpu_early_foreach+0x180 > pc =3D 0xffff00000076b094 lr =3D 0xffff00000020e0cc > sp =3D 0xffff000000010940 fp =3D 0xffff000000010990 >=20 > ofw_cpu_early_foreach() at mp_start+0x8c > pc =3D 0xffff00000020e0cc lr =3D 0xffff000000472e98 > sp =3D 0xffff0000000109a0 fp =3D 0xffff0000000109f0 >=20 > mp_start() at mi_startup+0x12c > pc =3D 0xffff000000472e98 lr =3D 0xffff0000003abfcc > sp =3D 0xffff000000010a00 fp =3D 0xffff000000010a20 >=20 > mi_startup() at virtdone+0x5c > pc =3D 0xffff0000003abfcc lr =3D 0xffff00000000108c > sp =3D 0xffff000000010a30 fp =3D 0x0000000000000000 >=20 > KDB: enter: panic >=20 >=20 > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 = Original Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2= =80=90 > On Saturday, 6 June 2020 20:29, Klaus K=C3=BCchemann via freebsd-arm = wrote: >=20 >>=20 >>=20 >>> Am 06.06.2020 um 21:19 schrieb Kyle Evans kevans@freebsd.org: >>> On Sat, Jun 6, 2020 at 2:13 PM Klaus K=C3=BCchemann via freebsd-arm >>> freebsd-arm@freebsd.org wrote: >>>=20 >>>>> Am 06.06.2020 um 20:15 schrieb Robert Crowston via freebsd-arm = freebsd-arm@freebsd.org: >>>>> =E2=80=A6... >>>>> Edit board/raspberrypi/rpi/Kconfig, set RPI_EFI_NR_SPIN_PAGES to a = larger number (I picked 10, probably too big, but it was easier than = doing the arithmetic). >>>>> =E2=80=A6=E2=80=A6 >>>>=20 >>>> You mean that https://reviews.freebsd.org/D24085 rpi4_fragment has = to set SPIN_PAGES from 2 to 10 ? >>>> This could be done in sysutils/u-boot-rpi4 , perhaps with something = like an #ifdef RPI4/8GB=E2=80=9C for the first try . >>>=20 >>> No, SPIN_PAGES=3D2 is fine; the default in upstream is 1 because = they >>> don't need any more, so he would've needed to manually bump it to 2. The relevant "this setting" related text, separated to make it clearer: >>> You should be able to just add CONFIG_NR_DRAM_BANKS=3D8 to >>> sysutils/u-boot-rpi4's rpi4_fragment and it 'just work' -- this was >>> tested on IRC a couple days ago, and should be safe for all variants >>> as far as I'm aware (but needed to test on my 4GB variant). Even >>> without this setting, it should still largely boot; you'll just only >>> have half the memory you wanted. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Sat Jun 6 19:55:39 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4509133CBDC for ; Sat, 6 Jun 2020 19:55:39 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49fVcW1CS9z3V1J for ; Sat, 6 Jun 2020 19:55:39 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qk1-f181.google.com (mail-qk1-f181.google.com [209.85.222.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 1B206293CB for ; Sat, 6 Jun 2020 19:55:39 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qk1-f181.google.com with SMTP id w1so13405689qkw.5 for ; Sat, 06 Jun 2020 12:55:39 -0700 (PDT) X-Gm-Message-State: AOAM531ANeUSdKG+3kaUhDKRKy1CWNZ4Wet3b+L3YNH858EtXqsXN31G 3Lks4+90wJ+GSvC6nGIAb+RZTsnEvFkDjtY4U8g= X-Google-Smtp-Source: ABdhPJzKdNRPjxLiK5PY7270c/Q1bPdDcXv/vd3guR1W/DPcbn8KPuMB6DBcnJu0TOXmOwso2bgH1DJ6qbbNYcOMmns= X-Received: by 2002:a37:a3ce:: with SMTP id m197mr15843834qke.493.1591473338771; Sat, 06 Jun 2020 12:55:38 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kyle Evans Date: Sat, 6 Jun 2020 14:55:27 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Report: FreeBSD on Rpi4 8 GB model To: Robert Crowston Cc: =?UTF-8?Q?Klaus_K=C3=BCchemann?= , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 19:55:39 -0000 On Sat, Jun 6, 2020 at 2:45 PM Robert Crowston wrote: > > > No, SPIN_PAGES=2 is fine > > I confirm that CONFIG_RPI_EFI_NR_SPIN_PAGES 2 is sufficient. > Thanks for confirming. :-) > > Even without this setting, it should still largely boot; > > you'll just only have half the memory you wanted. > > Without raising the spin pages limit, the kernel panics while trying to start the secondary CPUs. I don't have a working JTAG so I can't diagnose exactly why, but the spin table thing seemed like an obvious thing to check. > Sorry, that was specifically referring to raising CONFIG_NR_DRAM_BANKS -- an unmodified sysutils/u-boot-rpi4 (which uses CONFIG_RPI_EFI_NR_SPIN_PAGES=2) should boot with half the RAM recognized, and bumping CONFIG_NR_DRAM_BANKS in our fragment should correct that. From owner-freebsd-arm@freebsd.org Sat Jun 6 20:01:30 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BC8CC33CBF2 for ; Sat, 6 Jun 2020 20:01:30 +0000 (UTC) (envelope-from crowston@protonmail.com) Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49fVlF5BVPz3Vvj; Sat, 6 Jun 2020 20:01:29 +0000 (UTC) (envelope-from crowston@protonmail.com) Date: Sat, 06 Jun 2020 20:01:15 +0000 To: Kyle Evans From: Robert Crowston Cc: =?UTF-8?Q?Klaus_K=C3=BCchemann?= , "freebsd-arm@freebsd.org" Reply-To: Robert Crowston Subject: Re: Report: FreeBSD on Rpi4 8 GB model Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49fVlF5BVPz3Vvj X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.46 / 15.00]; HAS_REPLYTO(0.00)[crowston@protonmail.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[protonmail.com]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; DKIM_TRACE(0.00)[protonmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; NEURAL_HAM_SHORT(-1.38)[-1.377]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.18:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.989]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-0.996]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[protonmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[185.70.40.18:from]; FREEMAIL_CC(0.00)[googlemail.com,freebsd.org] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 20:01:30 -0000 To reinstate some additional confusion, I only changed the SPIN_PAGE variab= le to 2 (didn't touch NR_DRAM_BANKS) and I see all 8 GB (well, 7.84 GB) in = htop. =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Saturday, 6 June 2020 20:55, Kyle Evans wrote: > On Sat, Jun 6, 2020 at 2:45 PM Robert Crowston crowston@protonmail.com wr= ote: > > > > No, SPIN_PAGES=3D2 is fine > > > > I confirm that CONFIG_RPI_EFI_NR_SPIN_PAGES 2 is sufficient. > > Thanks for confirming. :-) > > > > Even without this setting, it should still largely boot; > > > you'll just only have half the memory you wanted. > > > > Without raising the spin pages limit, the kernel panics while trying to= start the secondary CPUs. I don't have a working JTAG so I can't diagnose = exactly why, but the spin table thing seemed like an obvious thing to check= . > > Sorry, that was specifically referring to raising CONFIG_NR_DRAM_BANKS > -- an unmodified sysutils/u-boot-rpi4 (which uses > CONFIG_RPI_EFI_NR_SPIN_PAGES=3D2) should boot with half the RAM > recognized, and bumping CONFIG_NR_DRAM_BANKS in our fragment should > correct that. From owner-freebsd-arm@freebsd.org Sat Jun 6 20:50:04 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4351633E2E4 for ; Sat, 6 Jun 2020 20:50:04 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic301-22.consmr.mail.gq1.yahoo.com (sonic301-22.consmr.mail.gq1.yahoo.com [98.137.64.148]) (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 49fWqH1Lq6z3bQN for ; Sat, 6 Jun 2020 20:50:02 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: 4qeMygAVM1mCTk9JdmA_UbipBr3D_GzhZ.w137AazwuZ0kLybkQrFlxEQcizcVK Ftr_H5coDm8twso0bpgnpabW3edAd1uJEtIb.5gJs4MRNS2_zdSj3ZWhM23.ePzp1TzqcPyIFHCS jgOfbiusZoUf_NP3APsjCJNfPN3.QfAb8G.8orTqKy_H_1mvVnQbc80KkHBcox4jW2hvDYMV0XX9 626C0SqQ0OTUGzoxYwA8SgkQN_o0TBVkorDqr1aFtD8Q4WU0mmYA4bqffkKOK58N3HiZFX1Ct3Sy drLgeFNo1IfB3klFRfI8XnyFGraK6JAfmkuxAtRTMVLkKXbr4XOyXSooQFtrSDfGgIzGWdzT5qsI 7Dm5gWcIeRHrtorYO_1t27DapwAfm8C_3ayOVLDQnb3oIMsWH9gJA.slsplUZofx3CJitfU9jj9v 1uiZ54FviH5UOrzR4O80dEIDbarqD_hQVPxeHUlXKtDN35FeZ8bMtnvxDW8fUBcSTQWYaNYEh2Tu 2eiVNqpVbRxYZUGJsYfIihvcHS0nEjwRQ7YbhCIIjDYpLDp6y0fxdnStuVll3W0F3Bu883g0jN_r dak4dd2cLB_.Gf_6RYidymIxS_y93cDYQ5h4vsCqF0pJgLUIwJEE7kvr4gtO8nROSPcDQXusS0RF dcePuu074vp0iyA9OBumykhqy6bm26Bi9tYETrQyRs3pzjTelLUlENmnW5df9t2qb6wQic8qK9XB 5M8GMda.eFFLzx.FaZAV3bC7Q59Z8tszRFVosnCJXXS1kv1IVOlzF7gSHc7IicEfK2kn9MMQM3XJ N5nJwwzm9gkG4RC2oIo28ge_IXVbEPvhHKSxIiS3dBe7yfV1sD4uBjsMrgSKKXNlIra6MRm7LWI8 l8U2ktvqPbJpv0h7X.WKIUtjwk2YEaz7A3RxdFvZ7tmlt.AHnk4UzNP6p2asMFiKmC9S1CqviLpI xM_AoLbamVcQeP82D2yWB0NicNBI0b_RZT7p7psWbiNd3RnINivzTy3fU8N9na6x13VXuVFXGBNr 0z2s.urRz3ceBP0zQrk_jObwKTia2uL_KR63rI0RTt2bRmtV0.jWosqn9FdSML.xyh8iUhLNJPL1 L6hF0DE6v5TY8bvy_Nwbil2WOIWGML_qQYITuZKoCrN61vetpExa9Pplr79DkTXBUbCkCWfl3nt. hMnuxTNZDjrZDTr2ibT9IotHnB4eQfB0QqbkZtp16B_k1SBlY8I6aKC79ouogb0Dfr125uPiPRtC TiPCf16hmi23BqyU.PzxBRCIcocYDIDLn2lNOEd87AzFULFSpC4SNauFUTUf_qwy07Er1BgWm2H7 3RLfFvVyup1zxJbqGkeeqI6M_qL_.P_9itYM0mFTOC4M0.K98aoXW5ZqtvYKevA.g_Od.46iSO6i Kj1pFFlesG582j6db2yMD2NdVEMFUB3S8WU3fphv9ifipueauUOtldt76Z2w- Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.gq1.yahoo.com with HTTP; Sat, 6 Jun 2020 20:50:01 +0000 Received: by smtp404.mail.bf1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 1d038f6035919e7848c6458ea5def863; Sat, 06 Jun 2020 20:50:00 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Report: FreeBSD on Rpi4 8 GB model From: Mark Millard In-Reply-To: Date: Sat, 6 Jun 2020 13:49:58 -0700 Cc: Kyle Evans , "freebsd-arm@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <391212F2-6C54-48EE-812F-929B2948F57D@yahoo.com> References: To: Robert Crowston X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49fWqH1Lq6z3bQN X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.51 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-0.99)[-0.995]; FREEMAIL_TO(0.00)[protonmail.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.02)[-1.022]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.64.148:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.64.148:from]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 20:50:04 -0000 On 2020-Jun-6, at 13:01, Robert Crowston via freebsd-arm = wrote: > To reinstate some additional confusion, I only changed the SPIN_PAGE = variable to 2 (didn't touch NR_DRAM_BANKS) and I see all 8 GB (well, = 7.84 GB) in htop. sysutils/u-boot-rpi4 already has SPIN_PAGE set to 2. So you were likely not using the same vintage of materials as sysutils/u-boot-rpi4 produces to compile. Your context may already have had NR_DRAM_BANKS changed. I expect Kyle was talking about changes to make to sysutils/u-boot-rpi4 = . For that context, apparently NR_DRAM_BANKS does need to be changed in order for 8 GiByte to be found and used: sysutils/u-boot-rpi4 does not start with the updated material (yet). Such is my guess anyway, I do not have a test context. > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 = Original Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2= =80=90 > On Saturday, 6 June 2020 20:55, Kyle Evans wrote: >=20 >> On Sat, Jun 6, 2020 at 2:45 PM Robert Crowston = crowston@protonmail.com wrote: >>=20 >>>> No, SPIN_PAGES=3D2 is fine >>>=20 >>> I confirm that CONFIG_RPI_EFI_NR_SPIN_PAGES 2 is sufficient. >>=20 >> Thanks for confirming. :-) >>=20 >>>> Even without this setting, it should still largely boot; >>>> you'll just only have half the memory you wanted. >>>=20 >>> Without raising the spin pages limit, the kernel panics while trying = to start the secondary CPUs. I don't have a working JTAG so I can't = diagnose exactly why, but the spin table thing seemed like an obvious = thing to check. >>=20 >> Sorry, that was specifically referring to raising = CONFIG_NR_DRAM_BANKS >> -- an unmodified sysutils/u-boot-rpi4 (which uses >> CONFIG_RPI_EFI_NR_SPIN_PAGES=3D2) should boot with half the RAM >> recognized, and bumping CONFIG_NR_DRAM_BANKS in our fragment should >> correct that. >=20 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Sat Jun 6 22:38:59 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4909F34019F for ; Sat, 6 Jun 2020 22:38:59 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49fZDx5Zzyz44kq for ; Sat, 6 Jun 2020 22:38: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 056McrfG037818 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 6 Jun 2020 15:38:53 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id 056Mcrvi037817; Sat, 6 Jun 2020 15:38:53 -0700 (PDT) (envelope-from fbsd) Date: Sat, 6 Jun 2020 15:38:53 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Confusing USB device conflict Message-ID: <20200606223853.GA37281@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 49fZDx5Zzyz44kq X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [1.36 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.40)[-0.396]; NEURAL_HAM_LONG(-0.50)[-0.503]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(0.36)[0.357]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2020 22:38:59 -0000 Just got a disk, adapter and usb3 hub for use with freebsd-arm. When it's connected to a Pi2 running 12-stable, the console reports login: ugen0.6: at usbus0 uhub2 on uhub1 uhub2: on usbus0 uhub2: MTT enabled uhub2: 4 ports with 4 removable, self powered smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 02 06 20 50 00 00 30 00 Things then go from bad to worse, ending with (da0:umass-sim0:0:0:0): Periph destroyed umass0: detached ugen0.5: at usbus0 (disconnected) uftdi0: at uhub1, port 4, addr 5 (disconnected) uftdi0: detached ugen0.6: at usbus0 (disconnected) uhub2: at uhub1, port 5, addr 6 (disconnected) uhub2: detached uhub1: detached ugen0.2: at usbus0 (disconnected) Jun 6 15:20:00 www syslogd: /var/log/cron: Device not configured vm_fault: pager read error, pid 924 (sendmail) vm_fault: pager read error, pid 927 (sendmail) vm_fault: pager read error, pid 930 (sendmail) vm_fault: pager read error, pid 933 (sendmail) vm_fault: pager read error, pid 936 (sendmail) AFAIK, smsc is a (not-present) network device. Perhaps a case of mistaken identity? I've seen complaints from smsc0 before, but not lately. FWIW, when connected to a Pi3B+ running Raspberry Pi Buster, the hub, adapter and disk are recognized correctly, but dmesg reports: The driver for the USB controller dwc_otg_hcd does not support scatter-gather which is required by the UAS driver. Please try an other USB controller if you wish to use UAS. There's no crash, and it looks like the device file is created, though I haven't tried to talk with it yet. Thanks for reading, and any ideas..... bob prohaska