From owner-freebsd-arm@freebsd.org Fri Sep 25 08:07: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 C72633EEA35 for ; Fri, 25 Sep 2020 08:07:47 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic315-8.consmr.mail.gq1.yahoo.com (sonic315-8.consmr.mail.gq1.yahoo.com [98.137.65.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4ByPfV5Bj9z4nyB for ; Fri, 25 Sep 2020 08:07:46 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: Ci.uRJQVM1kJngclh5btCHSwRbQEM8GuZtovNtBf1pvpHuixYQrzFqFvh4vzZWr NmEfTBAzacfKWZHpsCQecDxxsh.xk4ZGZtAiOPtS.SLZD5XG9elMlvuKFuI_P.tjr4uWUxY8eUii VAWE311o4hlU6Rfnvn8IL_G9sFzUDcmwQyP4LwQDNMJj2sVxITZAoTwzwPtKlDs3WAJ7ojQwOkIb DaVrQiS.ZlapvNBWEUoqJ7fD3Q2roxEJXT_6kUolYP11MGGfkAmr73k_YL9507WDR6YVP7UIJPoa 7I_qsi0dPHN4ZGXjmGFFQvnr8tb79o5Njl7Eft1dUlwn7e4T4iwpuFKqbbW4ls1hOQPzrNGD.6ik qz8c.pAl4AYKYqlhRagZiunNQu7hnUiykTB4sJzgrsLjhI_nFTMhnGzkGzMXw7Fuw6vlIClZcXzk 2d8kIPGm_4d8FVexPnOm1dPJI5ZgGUcEeqSPoWCcy7mbUszNQxHgufcs.MgPKxxBngfR3bIodgef dn9U5S.whq2A3D5GIq37vvXVJZVNmZBLqlkZJI348Qfn0sC1.EPDbEwrbeUSjxTVtqTb2W5vANjs pT9ANtCxQwpITzhRbO8pDIkCVKjwcLnduxtSnkFH63oy2okIt5bNb81i3rsFfK8GfXzuW4coxJA4 rVPsDmyAMHA6p7wg1Hao6TH8Zw1aRL_J5by6agj8IqyMbY6YT5jvB7iLWtjE1YRIRYiJDWhaezNH HKq465k_5EH_eO5xuQkEQSXCvyhcyrQZwH05Gv0b1qpsxiWROEo3HtKNhPCu9ndQnw.oCmWBs2Sx 1RHEEbJS2a0SCA8xUow2u.uD.LuaW9us0ijl0rSu9dpMwpxXPw1kltXxQ0IVK7YlvZHwJtGKGIOG 61iAAG4zkGgQWw0dYoNrtzzOGt50j.KvfqT6f94F2c.dXCUIHcI4CxV_E6qLcUjmWtYOVlXSUtL3 DFHUiMoSALICsfUQpud4vMh8V2nXcXaUFJAqMeehhDTElzGeH3y3.JQtmbu922nsxIQTtbZUJeLS uXZmx1Ne102GmTG25I5_3pjYVcPT91OGWoOMw7qUElgtlvPE9gbqq2NqMK6LTOPcTG4UPjwoDMTE iZ.JeSQl8e5gcig50uzZ.DewX6o21acMfLLmaChVS_MMA74eJvBbMz4rUoz4hg5XICXO951e6nAI yiyaalRO2rIAR_rDc3x1Nd3z3anhgZ8xRZYsAU7cHLfjPni6uFZo6OTZAaRD29M8MSCQoDzE7lWi QMW4RajiTQZAuCCT3edFSUOkC0QJiDSY5_Ba8iBiVVpqG__YEqADFaNWg18ntHAmri5g5DwG6cwB NU1_1HeHn87WRwIiqsdnPPiXBYM68pXH0Ar8CaCHdFB_mgncCyPEPXc6MvNcNcOp25CUbd_TCTXT SloudvzpFFCr_XnferGRG5z0P5fHFh1C_mRPSr0ViQ1tkqOWGyR5syqHjixgT7eUeSyDHy1g9ws0 R_TgM5oeJR70DZ4doPShTpm1bMvF7gMrltMhI0hUHrNcVMdF4idGsg7RSLVo.tOzZPHLprMJTZsK H Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.gq1.yahoo.com with HTTP; Fri, 25 Sep 2020 08:07:44 +0000 Received: by smtp423.mail.ne1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID fd670871a06821a624df89a4f4846e29; Fri, 25 Sep 2020 08:07:40 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\)) Subject: Re: head -r365677 and later do not have the xhci related DMA problem fixed From: Mark Millard In-Reply-To: <20200925063418.GC54660@bastion.zyxst.net> Date: Fri, 25 Sep 2020 01:07:39 -0700 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <8084F606-D75B-42B3-A05F-724F7150F304@yahoo.com> 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> <20200925063418.GC54660@bastion.zyxst.net> To: tech-lists X-Mailer: Apple Mail (2.3608.120.23.2.1) X-Rspamd-Queue-Id: 4ByPfV5Bj9z4nyB X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.71 / 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:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-0.18)[-0.177]; 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/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.05)[-1.047]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-0.99)[-0.988]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.65.32:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.65.32:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-arm] 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 08:07:47 -0000 On 2020-Sep-24, at 23:34, tech-lists wrote: > Hi, Hello. > On Thu, Sep 24, 2020 at 05:53:06PM -0700, Mark Millard via freebsd-arm = wrote: >=20 >> 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. >=20 > 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. >=20 > 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, >=20 > replace u-boot.bin, fixup4.dat, start4.elf >=20 > wget = https://sourceforge.net/projects/rpi4-8gbram-boot-fbsdonly/files/u-boot.bi= n/download > -O u-boot.bin >=20 > fetch = https://github.com/raspberrypi/firmware/raw/1.20200717/boot/fixup4.dat > fetch = https://github.com/raspberrypi/firmware/raw/1.20200717/boot/start4.elf 1.20200717 is from back on 2020-Jul-17 and is too old to generally work with the modern eeprom for USB MSD use according to what the raspberry pi folks have published. The RPi4B will report that the firmware needs to be updated generally (possibly not universally). One would have to use an older vintage of the eeprom content that was in use with pre-2020-Aug-20 firmware in order to use that older firmware generally: https://github.com/raspberrypi/rpi-eeprom/commit/279eef4 ( firmware/beta/pieeprom-2020-08-31.bin ) looks to be the last that is before the versions that they eventually noted required 2020-Aug-20 or later firmware (microsd card date). Going the other direction, given the modern release of the eeprom content that was declared "critical" for most everyone as of 2020-09-04 (so general distribution), the only officially tagged firmware versions that are documented as compatible are those in: https://github.com/raspberrypi/firmware/tree/1.20200902/boot/ https://github.com/raspberrypi/firmware/tree/1.20200819/boot/ (so the first microsd cards were from 2020-Aug-20). All prior versions predate the 2020-Aug-20 criteria as far as I can tell. Looks to me like the u-boot based FreeBSD support currently requires the use of of-of-date BETA materials from the raspberry pi folks, both eeprom content and firmware. (Not surprising, there is normally a lag and the raspberry pi materials were prompted to being classified as "critical" for most folks to use only on 2020-Sep-14.) Folks need to be careful to not do a default upgrade of the firmware or eeprom content on their RPI4B's (and to avoid trying to use new RPI4B's as shipped, once the older RPi4B inventory has been sold off). [rpi4-uefi-devel's v1.20 has other tradeoffs but allows using the modern raspberry pi firmware and eeprom-content combination.] > unmount the partition >=20 > it should boot. By official raspbeery pi criteria it should not boot for the eeprom contents that I have in place: too new for 1.20200717 firmware because I have what was promoted to be the default EEPROM image for everyone. The RPi4B needs more recent firmware (2020-Aug-20 or later) if that modern eeprom content is to be used. >> 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. >=20 > 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, updated the eeprom, put back the freebsd card. It boots, just can't = touch config.txt or or I get the raspberry problem (happened before the = eeprom upgrade), if I try the different start4.elf & fixup4.dat, I get = the rainbow screen. Thanks for the notes. What I've learned is that the U-boot based context requires that I'd have to revert both the eeprom content and the rpi firmware before I could run u-boot based tests. I'm not sure that I want to do that so I'll likely wait on any testing of u-boot based operation until the following are supported via u-boot based booting: = https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/critical/pi= eeprom-2020-09-03.bin = https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/critical/vl= 805-000138a1.bin https://github.com/raspberrypi/firmware/tree/1.20200902/boot/ =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)