From nobody Sat Oct 22 19:18:05 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Mvrhh4HSnz4fZ0s for ; Sat, 22 Oct 2022 19:18:12 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic303-25.consmr.mail.gq1.yahoo.com (sonic303-25.consmr.mail.gq1.yahoo.com [98.137.64.206]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Mvrhg185jz4J3Q for ; Sat, 22 Oct 2022 19:18:11 +0000 (UTC) (envelope-from marklmi@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1666466289; bh=+cA+7iMcofnXp1Nb/HS/CS2I8RBh540lYS0lWWUiD54=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=T8r+0bEBQSk8WS06wfrsXxpf4HyM+kdaKLG6wKzOE3ry25FG5bnuaCOTm9KyGi2Ws0cfxoy8GpnGCov3HNFKPpGF1yciu5JIJRNknPAM7FXWWZZCCgJr2F37T5bwl/BkzvniKd8LLcD4oiJZpG0MhOnqb5IsbDAKHYIXzTVYO9hUMZFvQFx5fu1MXbBrgkJNAr3qiCy+vV3ubPulT5CYAQbmAJsdLqH8cd48BOkxicpEgwrfqCbdzqOVUhESpCZYxT2J7RDP9JEwHyhY3nWmtrP7g86XllfDWw/zAvu0H9QrcpqdLg8WICzCcxKh3MnmlUi7qzAcbr/s0cNpcNnWFw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1666466289; bh=Ge014aem4PsS1XCkXNxmfYFgYJpC768Bb3ayP7OPYsp=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=uIL3RgweW394E32Y40rdJmAEQvSY0vuPhjhtL+YgK059ZUBAHvXRblBb9MluO6TJoyNiAinIMVFsvYibr8ICguZCHQtlUQ8RLD3XmWMscxoJ2dk8Z2KFFZX+uaqi+NpBRiooNLu3PCitN6V7OYpYwx7FS350iMxLNmWKw4Y4X0gmx0KP0ICDDqnAZKm09UUMnxihAeFxt74KJgsGIKPLqP2bBcUTWaCYpXSorq/fag0qBlz+txDzRkXdDGDDIvHGFBYVLaj+ASgNdlAXA26ofD4F/k2qc5mKNmoi+K5yF9aDsZZS21WVlRep4dzoXhJUf1mhGyhSqpBEq1kpWUSlaA== X-YMail-OSG: n45g8C0VM1lpDinalW9BhZEcdDKmOYMZxWJKrDPPnTrZMYL.3ULIoDV7dHoA4vg Zf.XH3r0oQdkuW6GvA3hHLu972u0rebjccr76iqAhB9SVQoUcXgV4PGpNYPZD6.Z6t_esBFS948n qs.jM2bs_2l8dYWY5iWYoRBBEwS8UxW4Tea_BumLe6Jgvo1LmihvzSK5lOJ_qmF0itBU8sYZZfSp .zWGLqWbP32.YiDNoMUnaFo092rWpWwEWA3MX_EEVFQnSiGy7MyVbs77SHjWvkzUmnpbm6YSgiOI Oe.3eFV7BjCqY4jvzrGXBWVU1tPmGRTHE3toLrsJszKIiDg.LSEGekwN0XcR3SLsD5Hlxv8t4AYM AEA_hsQKKq7_JCREcnOneSfo_pgMtRhcg1IArfINf_j.zq.gkEQAzD3FUM0anMMMnWif8AtkRoYk DjXeRnyKT3.uirfP8nH6T7BqqvEfyjd.Ql8dvN0hYzG.ORecuiX5vPCwYo9OzO4SGkhgbgm.tMBB 5GHikMvoCqeC572rU2oBlQTMkUJNyc0Bz9L_zGnnJXZayIr528BOlpG.kTW7ZarOIvVYE2PWpax5 75IMUNSWBbd9TKKTD3ZpVtxNRTmHsIZVQnf45Y1OAFte3Q_XVZyPMdfoEfg3_BS02KEk66PzhzG4 8BIdDPeOFs6SoPXyqV1tBF0Oec0gKykN2mKGtr7im02qqlpPVFG5HkXozUQ1CL6ve7riYIL4TmQ3 5hjDzlAjLtw7Wt.5bkcWTkfsvMb8murmUzGFq0y3l2DHUkINy08wzYoWdQxiQ3CNbKVP8aC7TXIN HcdHzxOjkj45q4TCVCdd9Q5o9rQhwxOaQX2piBdscBkuVFGIiuTDTWrOl5lWTAEDDu2OzJzTOOXN 7ybG0of52HtRnOeR4SHK9qVzPn4vTEknBcDnoAi0wP4ZcSH30R_s4UnKQJHC1W8ApQkMBBJmGvIt fFPvKnEx8moh3BlWaCMlIGAa6z32g.OpS3tRR3DmdT5tJq9nDJeC7FOXSYpfUnyJdCnOZ_lVPRR4 st3dE3IZUrYXU_BdaTSwdNwFwTfeOA.rhMSFAsTrvRc1bPsbbqQloECuf4dNPbHbz98_dJzqiyGA 3lzp5UOAzQIU3SWiT6jy6SLw7j.xTxxn3_XgAIUHWDwcBoOehBOonJ5qSf50m41QIHswYErCrIJx Y8HUTikCo2TlcPsP0KrlwBP2zuIQFCs0b7sjEv18PFs_O0JG08w1Lh9lxxZR1P64jUu7NtFk10dK eIp4NCrcIVolt.oh4sclA8GIWpQs_Evv9LjO1mTsDK5TaBoI59C13pMHmlw4s8cAz3KOxX6oyP74 9OwXEFMWHMqfoevLWVwfMQ6svGi1x7JAqm81rq4uZCyPxyn2UmZvGqIfdEef.oU5QUsCH_nnp4do 2HYZXlr.77RdOOyt4ddgmcNn_AaV2C3qGFb9BTrQP6a3vya0xxIPrLboinmx9VaIIAlSYjr9Pyj3 YWaFe5XTvZHLENA.9SE09GIU1F9uEWnW74fw4mERr0YTM5zfOgiYZGoZGFTzyZVgQDdQ1YewTgbR tYxKmHq33YawErJogRUICpqPne563x26XBxEKoqj63cS5HbFOiWttriB7dd4SDklYEsj1U6wFA5a jUQbd1KhxwghRjOtZt3Eea.U6hx9RYijMnIT.2zmManp8UTS8y2mcQK5jv2T8QhRpsaDt4_VXQei 1pF_u118XH_R2_lchb.AVHO5wbaQc3n6kMLq.KRfCZZ5WgsUrj1poKkVBKRoqS6QC4qPDu.KvFCm KOi4bhfl5Sj5mHs4ybpWhJ7Y_9KoanXgvviSHpjl317oahwAI5WqvS3DnhpW2AxtR4LF_BMvd230 Gv5KQ4TiBcN4drTkSNF7F.edf6yCjZGocHVHyhYLNbja5Z_5qtw2EsTv3.h18rHuw_m4mQbLMg47 zMO3O029NnKFAe2j0IBTl1_v0XQ6e_YEukyL.QPZz8K55oeoQESRkd5uT9nj7FBg5hRtT1EezjR1 s_O8i8FxUkuL8CvjiPMwjJ2L0HikH2MAODLywdtew8A6gdUPu55O1UlWTM5Ty3HsMT5Ly.dwG0nT 5HSmVcMG1.ltjcTesj94CvKY7EH0m8J.C0c7yx8nDJ9PLTQh_ICv8YnK2eW99StDGrW7gIhld7_R o1LR2mFCTzG5i3zNEE46RU1g5EZweyhRJZp5L34oTf4qihY49p_yBEoTLPtcN8HTsrSMPjZR9_fC TIwBubihm1zPc0tjpMe8P_1vE5AL16a.eceoEGSFYdj6fKoLoxgNcPXpGbhbbrl.Wv_CxnJX8x8G llsxMsow- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.gq1.yahoo.com with HTTP; Sat, 22 Oct 2022 19:18:09 +0000 Received: by hermes--production-gq1-754cb59848-jk2dx (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 5dcc88b5c944778d452e6cfe97d482e6; Sat, 22 Oct 2022 19:18:06 +0000 (UTC) Content-Type: text/plain; charset=utf-8 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: Re: EDK2 on RPi3 was: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it From: Mark Millard In-Reply-To: <71AB9FAC-EB00-48F0-B0DD-0629C2D3C8C0@googlemail.com> Date: Sat, 22 Oct 2022 12:18:05 -0700 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <5719632F-8A92-4784-88D8-EAE3F20F2FA3@yahoo.com> References: <20221004001857.GA7109@www.zefox.net> <62F8D709-BBC3-41C4-B1A9-939B2001BA52@yahoo.com> <1DE565E3-3906-4C53-83C8-EBC20A4E3C95@yahoo.com> <20221005034608.GA12761@www.zefox.net> <1560695E-4D99-40A1-8D62-29EAB24C7997@yahoo.com> <20221005160737.GA15227@www.zefox.net> <136B9190-4C73-45FB-8B41-FEEF7C38A253@yahoo.com> <3A76826B-B4E6-4837-915E-C9E1172BEA20@yahoo.com> <20221021175142.GA62386@www.zefox.net> <0697DE1F-C626-4289-894A-4141CDF1B91B@yahoo.com> <71AB9FAC-EB00-48F0-B0DD-0629C2D3C8C0@googlemail.com> To: =?utf-8?Q?Klaus_K=C3=BCchemann?= , bob prohaska X-Mailer: Apple Mail (2.3696.120.41.1.1) X-Rspamd-Queue-Id: 4Mvrhg185jz4J3Q X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=T8r+0bEB; dmarc=pass (policy=reject) header.from=yahoo.com; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.64.206 as permitted sender) smtp.mailfrom=marklmi@yahoo.com X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; RCPT_COUNT_THREE(0.00)[3]; RCVD_IN_DNSWL_NONE(0.00)[98.137.64.206:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[yahoo.com]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_TO(0.00)[googlemail.com,www.zefox.net]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.64.206:from] X-ThisMailContainsUnwantedMimeParts: N On 2022-Oct-21, at 17:16, Klaus K=C3=BCchemann = wrote: >> Am 21.10.2022 um 22:21 schrieb Mark Millard : >>=20 >> On 2022-Oct-21, at 12:53, Mark Millard wrote: >>=20 >>> On 2022-Oct-21, at 10:51, bob prohaska wrote: >>>=20 >>>> Mixed success has been obtained using EDK2 on a pair of Pi3 >>>> systems, one running 13-stable and one running -current.=20 >>>>=20 >>>> The 13-stable machine is at stable/13-ef2aa7753 >>>> The -current machine is at main-n258665-e03b7883e97c >>>>=20 >>>> The 13-stable machine boots reliably with an EDK2 microSD card >>>> and will boot almost as reliably with no microSD card at all. >>>> This seems true with both JMS561 and JMS578 usb-serial bridges. >>>>=20 >>>> The -current machine uses an ASMT bridge and is unresponsive >>>> with either the EDK2 microSD or no microSD at all. It does boot >>>> reliably using the "special bootcode.bin" file from the Pi = foundation. >>>> It appears to be the newer of the two Pi3's, having a non-latching >>>> microSD receptacle.=20 >>>=20 >>> Which context does the "need bootcode.bin" problem follow? >>>=20 >>> A) Where the ASMT bridge is used vs. not? >>> B) Which RPi3B is used vs. not? >>> C) Which OS version is used vs. not? >>> D) It gets messier to specify if combinations of 2 or more >>> those need to be specified. I'll not list all the >>> possibilities. >>>=20 >>> Does the newer RPi3B indicate that its USB booting has >>> been enabled? (You may need to use the likes of a >>> RaspiOS variant to check this.) >>>=20 >>> I'm confused about the "special bootcode.bin": bootcoce.bin >>> is a normal part of the RPi* firmware, just ignored by >>> RPi4B related RPi*'s that have an alternate means of doing >>> things. Is this the bootcode.bin in the standard RPi* >>> firmware releases? Some other version? >>>=20 >>> bootcode.bin always has more recent, bugfixed USB boot code >>> than a RPi3B has built in, as far as I know. The RPi3B's >>> do not have a supported means of updating what is built-in >>> for such functionality. bootcode.bin is used instead. >>>=20 >>>=20 >>>> On balance EDK2 appears to be useful, or at least having some >>>> promise. >>>=20 >>> I'm glad it seems to have helped. But there are things to >>> know. >>>=20 >>> Point #0: EDK2 versions and testedness >>>=20 >>> The only tested RPi3B EDK2 versions are the ones that the >>> developers release. They do not test EDK2 updates after >>> they make an EDK2 release, at least until they again work >>> on making a new RPi3B EDK2 release. >>>=20 >>> Similarly, they do not test using newer RPi* firmware than >>> they bundle. Only a small subset of the overall RPi* >>> firmware is in their RPI3B release. For example, a lack of >>> most of the overlays. They do have references to at least >>> using one overlay that they do not include, as I remember. >>> But use of any other overlays is untested/not-supported as >>> far as I can tell. >>>=20 >>> The same goes for the RPi4B related EDK2 releases vs. later >>> EDK2 updates vs. overlays and such. >>>=20 >>> The RPi3B vs. RPi4B EDK2 releases are not based on the same >>> vintage of EDK2 materials --or on the same vintage of RPi* >>> materials. >>>=20 >>> This means that using the FreeBSD port will not pick out >>> the release-matching EDK2 materials as are in the RPi3B >>> or RPI4B EDK2 releases. Also, the RPi* firmware has to be >>> separately supplied. Overall: an untested combination >>> results, a combination that is unsupported by the RPi3B EDK2 >>> developers and the RPi4B EDK2 developers. >>>=20 >>> I've no clue if or how well the the port's builds might work. >>>=20 >>> Another issue is that some software that is upstream of >>> EDK2 tends to have problems staying inside the C language >>> definition and when this happens, EDK2 builds fail, despite >>> it not being EDK2's own code that needs the fix. >>>=20 >>> Point #1: RPi3B microsd slot use is messed up >>>=20 >>> In my RPi3B EDK2 related testing, trying to use a microsd >>> card in the RPi3B slot for such can corrupt the contents. >>> It does not even reliably lead to even correct file name >>> displays in ls output. >>>=20 >>> By contrast, using a USB reader/writer continued to work >>> just fine. >>>=20 >>> So just leave a RPi3B EDK2 microsd card in the slot >>> after booting. >>>=20 >>> I've no clue of the status for things like sound and such. >>>=20 >>> Point #2: RPi4B does not even start to use the microsd card >>>=20 >>> In my RPi4B EDK2 use, microsd card in the slot are not >>> supported --by being ignored as I remember. >>>=20 >>> By contrast, using a USB reader/writer continued to work >>> just fine. >>>=20 >>> So just leave a RPi4B EDK2 microsd card in the slot >>> after booting. >>>=20 >>> I've no clue of the status for things like sound and such. >>>=20 >>>=20 >>>> Bugzilla traffic suggests work is stalled, can it be >>>> unstuck? >>>>=20 >>>=20 >>> I expect that at some point that some variation on my >>> patches to allow the builds to at least complete will >>> be committed so the likes of aarch64 FreeBSD builds >>> become possible. (So long as EDK2+its-upstream stays >>> inside the language definition.) >>>=20 >>> But I do not know how useful builds are now when built >>> on amd64 or the like --that will also be true for the >>> aarch64 built ones. See the above "Point #0: EDK2 >>> versions and testedness" notes. >>>=20 >>> It may end up being more effective to stick to >>> downloading and using releases made by the RPi3B EDK2 >>> and RPi4B EDK2 folks if EDK2 is to be used for these >>> RPi* families. >>=20 >> Side note on what type of video interfaces are in use >> for EDK2, at least for RPi4B EDK2 . . . >>=20 >> =46rom https://bodhi.fedoraproject.org/updates/FEDORA-2022-1c6a1ca835 >>=20 >> QUOTE of jlinton >> It looks fine on my RPI4+PFTF UEFI as well, although it >> should be noted that it's running on the EFI framebuffer >> in both DT and ACPI mode with that firmware.. This >> shouldn't be unexpected. At some point, I will update >> the DT with one that has the vc4 bindings. >> END QUOTE >>=20 >> I do not know if RPi3B EDK2 also uses the EFI framebuffer >> for its Device Tree vs. ACPI vs. both modes. EFI >> framebuffer mode would likely be less performant. >>=20 >> =E2=80=A6=E2=80=A6=E2=80=A6. >=20 > FreeBSD will always run it`s framebuffer driver as long as > there is no VC4 driver implemented in FreeBSD. > So there=E2=80=99s nothing to bind to VC4 in DT nor ACPI. Not using more than console mode, other than rare tests that more is minimally possible, I'd never checked the detailed status of FreeBSD video drivers for the RPi*'s. Thanks for the background information, Mark =3D=3D=3D Mark Millard marklmi at yahoo.com