Date: Sat, 10 Jul 2021 16:52:52 -0700 From: Mark Millard via freebsd-arm <freebsd-arm@freebsd.org> To: "Herbert J. Skuhra" <herbert@gojira.at> Cc: freebsd-arm@freebsd.org Subject: Re: git: 1dec3639fd0c - main - sysutils/u-boot: Update to 2021.07 Message-ID: <0D08E03C-87CD-4567-A10A-F548BFD6469F@yahoo.com> In-Reply-To: <87im1idnh2.wl-herbert@gojira.at> References: <202107071618.167GIvXd048504@gitrepo.freebsd.org> <874kd3390q.wl-herbert@gojira.at> <YOhlJgmDUlKiMUS%2B@mail.bsd4all.net> <D59DADD5-A5EA-4D6A-8D2B-3A0A480E13CE@yahoo.com> <87k0lye13y.wl-herbert@gojira.at> <87im1idnh2.wl-herbert@gojira.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Jul-10, at 11:37, Herbert J. Skuhra <herbert at gojira.at> = wrote: > On Sat, 10 Jul 2021 15:42:57 +0200, "Herbert J. Skuhra" wrote: >>=20 >> My RPi2 boots with U-Boot 2021.01. So does it with: >>=20 >> U-Boot 2021.04-rc1 OK efipart_readwrite: rw=3D1, blk=3D62518264 = size=3D8 status=3D2 >> U-Boot 2021.04-rc2 OK efipart_readwrite: rw=3D1, blk=3D62518264 = size=3D8 status=3D2 >> U-Boot 2021.04-rc3 OK >> U-Boot 2021.04-rc4 OK >> U-Boot 2021.04-rc5 OK >> U-Boot 2021.04 OK >> U-Boot 2021.07 OK >>=20 >> But starting with 2021.04-rc4 it only works if you do a soft/warm >> boot. >=20 > The problem starts with commit = "78af81c345430a9088235f48d302922955d2499f". >=20 > = https://github.com/u-boot/u-boot/archive/63af92e837f3d7c21ab5fc4a96ffcbf20= 2efaf90.zip > =3D=3D> OK = https://github.com/u-boot/u-boot/commit/63af92e837f3d7c21ab5fc4a96ffcbf202= efaf90 shows it as: master v2021.07 ... v2021.07-rc1 committed on Mar 2 but clicking the ... shows the other tags that include the commit: =E2=80=A2 v2021.07-rc5 =20 =E2=80=A2 v2021.07-rc4 =20 =E2=80=A2 v2021.07-rc3 =20 =E2=80=A2 v2021.07-rc2 =20 =E2=80=A2 v2021.07-rc1 In other words, not added to master until fairly recently (v2021.07-rc1). (The commit to some branch was on Mar 2, not the merge to main. I do not know how to find the original branch.) > = https://github.com/u-boot/u-boot/archive/78af81c345430a9088235f48d30292295= 5d2499f.zip > =3D=3D> NOK = https://github.com/u-boot/u-boot/commit/78af81c345430a9088235f48d302922955= d2499f shows it as: master v2021.07 ... v2021.07-rc4 committed on Mar 2 (The commit to some branch was on Mar 2, not the merge to main. The Mar 2 commit was to some different branch than 63af92e837f3 was originally committed to. I do not know how to find the original branches.) but clicking the ... shows the other tags that include the commit: =E2=80=A2 v2021.07-rc5 =20 =E2=80=A2 v2021.07-rc4 =20 =E2=80=A2 v2021.07-rc3 =20 =E2=80=A2 v2021.07-rc2 =20 =E2=80=A2 v2021.07-rc1 =20 =E2=80=A2 v2021.04 =20 =E2=80=A2 v2021.04-rc5 =20 =E2=80=A2 v2021.04-rc4 In other words, added to master earlier than 63af92e837f3 was added to master --by a fair amount. = https://github.com/u-boot/u-boot/commits/63af92e837f3d7c21ab5fc4a96ffcbf20= 2efaf90 does not show 78af81c34543 in the history. = https://github.com/u-boot/u-boot/commit/78af81c345430a9088235f48d302922955= d2499f does not show 63af92e837f3 in the history. (The 2 displays are not based on the ordering of commits to master but based on the original branches from what I can tell.) So, relative to master, there are a lot of commits between the two --and the "good" one comes after the "bad" one on master. I'm guessing that the the bisect should be based on the order of inclusion into master instead of spanning multiple parallel/independent branches from before the merge to master. (Such complications are part of why my time allocation has not gone into this bisect so far.) =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0D08E03C-87CD-4567-A10A-F548BFD6469F>