From owner-freebsd-arm@freebsd.org Fri Sep 25 06:34:51 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 0A8153EC83E for ; Fri, 25 Sep 2020 06:34:51 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (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 4ByMbG18jmz4hjW for ; Fri, 25 Sep 2020 06:34:49 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 0516E7B5 for ; Fri, 25 Sep 2020 02:34:47 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 25 Sep 2020 02:34:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=vVuIFodQwHrwUqX+BZGbtDZRdrb WXJteYppUryfUQus=; b=O3M0IgCWPXK198lDTH7fvgT9TEngTh2YRJy2ZoD3fzl pbdecgmZh0v3L7ocdJG04rwSTYVoUgJoCirdI2yELyd+aKWsEVsRXAYTA5q/9dW7 JY0FDyDzublWESKnJwFZLbgBELKZVd3pIQSQfhKRT4wLz8mgctYqb50ffwONBokD c3H+jbm+eCprwmVOl0GcbN3cMMhJME+9iJGZBVq4aG2iP2msFV+aU2bwCDWUdOvR DnZypkQhjkBgxf8Vd2yu6X4DVBMeEpV0zEQLqQaBHd9O8/17ALOzSXmA57x6oLbh 75yqa8BjdK9rKp3aZXZHExOj+UvSNRCOBTgypmHczww== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=vVuIFo dQwHrwUqX+BZGbtDZRdrbWXJteYppUryfUQus=; b=YkWunPKZgEv7XdzZPeHNSK WJf9LzNJAwX7SBVzR15HQtJa4MrjJ7OiAI3G0xMMuyAB+8T3YQ/i3Gv8OHeB1JeO cPIdA95QK8Sh2cLKCvA6c48l/iC4zFfn2Ju4DItaEDmg/2BjmHsD7eMAR6SftNfn G+BGb5JdgAQbOInG3vVMiIAw+EsA6cjjdIXE9Va+6wIft4PusvPKM7kIVqGd1E7V CaCOBXoXUeUZG52OSy9zmydOUKxneszN0IbQ30GPmMJ5gxXFcDqX2MkLnec3IH0u 1fuvB045FkVRBr1SMfTRQxuC6XEqRVTNc/N9CJGTbfVuWTW/SmJrd/DWZ7xkurHg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudelgddutdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesghdtre ertddtvdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseii hiigshhtrdhnvghtqeenucggtffrrghtthgvrhhnpeeigefhffefleekjeeiffegudevie eijeevheffheevleeujeduvdegieehtdevgeenucffohhmrghinhepshhouhhrtggvfhho rhhgvgdrnhgvthdpghhithhhuhgsrdgtohhmpdiihiigshhtrdhnvghtnecukfhppeekvd drjedtrdeluddrleelnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhepthgvtghhqdhlihhsthhsseiihiigshhtrdhnvght X-ME-Proxy: Received: from bastion.zyxst.net (bastion.zyxst.net [82.70.91.99]) by mail.messagingengine.com (Postfix) with ESMTPA id E85113280060 for ; Fri, 25 Sep 2020 02:34:46 -0400 (EDT) Date: Fri, 25 Sep 2020 07:34:18 +0100 From: tech-lists To: freebsd-arm@freebsd.org Subject: Re: head -r365677 and later do not have the xhci related DMA problem fixed Message-ID: <20200925063418.GC54660@bastion.zyxst.net> Mail-Followup-To: freebsd-arm@freebsd.org References: <5A60B29E-0D24-480C-807D-4A5E92D9C92A.ref@yahoo.com> <5A60B29E-0D24-480C-807D-4A5E92D9C92A@yahoo.com> <231B8A1B-7F61-4868-B9E6-F8DD824079CA@yahoo.com> <39346C6E-CF29-42E8-BCAB-B04E73F909F7@googlemail.com> <04531BA7-F7A6-498B-BB8E-D3AAA53E15E3@yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="GZVR6ND4mMseVXL/" Content-Disposition: inline In-Reply-To: <04531BA7-F7A6-498B-BB8E-D3AAA53E15E3@yahoo.com> X-Rspamd-Queue-Id: 4ByMbG18jmz4hjW X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zyxst.net header.s=fm3 header.b=O3M0IgCW; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=YkWunPKZ; dmarc=none; spf=pass (mx1.freebsd.org: domain of tech-lists@zyxst.net designates 64.147.123.21 as permitted sender) smtp.mailfrom=tech-lists@zyxst.net X-Spamd-Result: default: False [-4.96 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm3,messagingengine.com:s=fm3]; RWL_MAILSPIKE_POSSIBLE(0.00)[64.147.123.21:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.21]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.01)[-1.006]; RCVD_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[zyxst.net]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-0.21)[-0.215]; NEURAL_HAM_MEDIUM(-1.04)[-1.038]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MAILMAN_DEST(0.00)[freebsd-arm]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.21: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, 25 Sep 2020 06:34:51 -0000 --GZVR6ND4mMseVXL/ Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Thu, Sep 24, 2020 at 05:53:06PM -0700, Mark Millard via freebsd-arm wrot= e: >So far I'm unable to figure out how to have a u-boot environment >that boots the RPi4B's: figuring out what needs to be different >than the rather modern raspberry pi files that I have in place. >Also: fully modern eeprom content. As stands I've not been using >a microsd card at all: it uses the msdos file system from the >USB3 SSD. Mine *will* boot, even after the eeprom upgrade. What it won't do (what was always the case) is boot after I modify config.txt in any way at all. I used these files, and the last time I made a working image I used FreeBSD-13.0-CURRENT-arm64-aarch64-RPI3-20200917-17bd0444d91.img=20 mount the msdos partition, replace u-boot.bin, fixup4.dat, start4.elf wget https://sourceforge.net/projects/rpi4-8gbram-boot-fbsdonly/files/u-boo= t.bin/download -O u-boot.bin fetch https://github.com/raspberrypi/firmware/raw/1.20200717/boot/fixup4.dat fetch https://github.com/raspberrypi/firmware/raw/1.20200717/boot/start4.elf unmount the partition it should boot. >It hangs with the rainbow screen up and having reported starting >start4.elf in every attempt that I've made. As near as I can >tell the overall behavior matches what tech-lists at zyxst.net >has been reporting. I am using the same image (subsequently rebuilt world, kernel so it's at r365898 now), I took out this sdcard, wrote raspios-64bit to another one,= =20 updated the eeprom, put back the freebsd card. It boots, just can't touch= =20 config.txt or or I get the raspberry problem (happened before the eeprom up= grade),=20 if I try the different start4.elf & fixup4.dat, I get the rainbow screen. --=20 J. --GZVR6ND4mMseVXL/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl9tj3sACgkQs8o7QhFz NAVbcw/+Jyl8AbYqvmkEpEmeo1ZfhVt/diHCp49avcLtI3MCeYaVzIw1RJrmyrGM AFN27qMPljZ0KZrImrEyX5j1HIyGhpoylFY+fAURNLKQ5IawvhUEC8evjATYUKeV ySqB8RbMGD4ZtMSMN6baYYPnszW82whICN9qKI00iZ4lTKZCNB7QoFzEWjjaT9il 7x2s9mMOriaWnUIBgV6Z609Xl2rIwhkNUXPQ2ZAr6D+HgZIwR/nFY2MbdUV2zrL6 GyHkuVHInlqQd9fKG5VQJpGG+j66z0pIbLuFJdU0xymWfbDhGhXGAImLRlMLMLVA RUo/6jC+AhNjEC/FcUHDkcNc63/oZ1kbQgOtC5Fu9NT5hUJjMnGxGfInpwe31bh2 fqGQznZljn5TiUn7/pCpLYxGgYN6CaqyxycV8TUcQb8zSpzpxWQquVIMa/g8jJ5O mXDaPqWy424OIO2rIyA+h7kmWxW1wFWPYVgs7HmPUzvVU6j074RSEujp99ObLNxy ITTND6g+0FhyMbpMurl96uYbE89791W8Rwy1kkaooAUB7m+SI8Kg4VwyOJOufQ/Y FZ/mlrXfL6n7jC0LvFsNJ53todrtA+2tTgjv+aPGPCmRQ5D65vP2vmvhzSX+6Twv T2TpQ1vkz7WI7u2vIT9HR4S4Gz6YfKgzhWjGVTMR9VACJ9Tv2Q0= =aRGP -----END PGP SIGNATURE----- --GZVR6ND4mMseVXL/--