Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Oct 2022 19:55:06 -0700
From:      Mark Millard <marklmi@yahoo.com>
To:        Warner Losh <imp@bsdimp.com>
Cc:        freebsd-arm <freebsd-arm@freebsd.org>
Subject:   Re: FYI: FreeBSD-14.0-CURRENT-arm-armv7-GENERICSD-20220930-42dc8696df5-258315.img is broken for RPi2 v1.1 (so: armv7)
Message-ID:  <6A679278-69E0-4592-BFED-48ED8598C2F1@yahoo.com>
In-Reply-To: <CANCZdfom2TLLHD1SzY8_1TuxTC8GoWwNMGYHvaT-XefHgHmJcw@mail.gmail.com>
References:  <6B46F46A-2CAF-42C9-9A04-63567D7DB9B2@yahoo.com> <D9B791B7-106A-402E-AD8C-F811EB315560@yahoo.com> <CANCZdfoJ=E=ef86PRaYsvgXWLAu=AdbN%2B_kiv0vPhKVksqPY%2Bg@mail.gmail.com> <FC871551-7C49-4751-8763-2E8F82C1480A@yahoo.com> <CANCZdfoU2Ln2vqymT66Yu6ZdxSrZLAx1%2BA_hstLYSrzBmduHBw@mail.gmail.com> <28D78C89-E195-4EF1-BB7B-E7F75060BDC7@yahoo.com> <5B631C27-E68C-4F38-96B5-B311110A8F86@yahoo.com> <6EF84694-7CD7-4A9F-BF9C-DFFB52F557AD@yahoo.com> <CANCZdfrdnxUyBtj0cvAwiX%2BNJZppqrtButU48jiUVgW4op%2B-FQ@mail.gmail.com> <CANCZdfom2TLLHD1SzY8_1TuxTC8GoWwNMGYHvaT-XefHgHmJcw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Oct-11, at 12:10, Warner Losh <imp@bsdimp.com> wrote:

> On Tue, Oct 11, 2022 at 1:03 PM Warner Losh <imp@bsdimp.com> wrote:
>>=20
>>=20
>> On Tue, Oct 11, 2022 at 12:50 PM Mark Millard <marklmi@yahoo.com> =
wrote:
>> . . .
>>=20
>> For:
>>=20
>> boot-2022-09-16-15-45-b44869cba1b3-good
>> boot-2022-09-16-18-02-dd2b9c296776-bad
>>=20
>> there are no armv7 artifacts available between.
>>=20
>> The range is:
>>=20
>>         A) =E2=80=A2 git: b44869cba1b3 - main - sound: add patch for =
Lenovo Legion 5 Intel Nuno Teixeira=20
>>         B) =E2=80=A2 git: a705c72f2142 - main - stand: use =
archsw.arch_copyin instead of i386_copyin Warner Losh=20
>>         C) =E2=80=A2 git: 4c670b53a000 - main - stand: use =
archsw.arch_copyin instead of direct call Warner Losh=20
>>         D) =E2=80=A2 git: 8b19d28d68a3 - main - stand: Create =
MOD_ALIGN macro and use it everywhere Warner Losh=20
>>         E) =E2=80=A2 git: bca9c87b6104 - main - stand: Create =
common/modinfo.h Warner Losh=20
>>         F) =E2=80=A2 git: 5d1531d9d4e7 - main - stand: Move =
md_copymodules into modinfo.c and reduce copies Warner Losh=20
>>         G) =E2=80=A2 git: 2e6ed47a4609 - main - stand: Move MOD_xxx =
macros from modinfo.h to .c Warner Losh=20
>>         H) =E2=80=A2 git: fc352701ff3a - main - stand: collapse all =
copies of *copyenv into md_copyenv Warner Losh=20
>>         =E2=80=A2 git: e895ab3fbdc1 - main - stand: Remove dead store =
to bi_kernelname Warner Losh=20
>>         =E2=80=A2 git: d43bcf62a218 - main - stand: Stop support =
booting 4.x and earlier kernels Warner Losh=20
>>         =E2=80=A2 git: 59b1d074280d - main - i386: Mark the obsolete =
fields in bootinfo with _was_ Warner Losh=20
>>         =E2=80=A2 git: 4134f677eb39 - main - i386: Make boot loader =
smaller by reducing size of bootinfo Warner Losh=20
>>         =E2=80=A2 git: 9758dd3de1cd - main - stand: Allocate bootinfo =
rather than have it be static Warner Losh=20
>>         =E2=80=A2 git: c0ecae78abbe - main - stand/elf: Only support =
swapping headers on powerpc. Warner Losh=20
>>         =E2=80=A2 git: dd2b9c296776 - main - stand: fix mismerge =
Warner Losh
>>=20
> Yea, I did a bunch of refactoring. I'm surprised that this produced a =
change at all. Would be nice to
> know which one of these caused the problems.

5d1531d9d4e7 has the stand/common/metadata.c "align"
removal that the later dd2b9c296776 fixes as the
"mismerge". So it appears that most of the stages
would not build without adjustment for that.

So presume I've made the adjustment for any such
such cases below.

H) fc352701ff3a Bad
D) 8b19d28d68a3 Good
F) 5d1531d9d4e7 Bad
E) bca9c87b6104 Good

So the good -> bad back-to-back sequence pair is:

git: bca9c87b6104 - main - stand: Create common/modinfo.h Warner Los
git: 5d1531d9d4e7 - main - stand: Move md_copymodules into modinfo.c and =
reduce copies Warner Losh


Note: I cross build armv7 via aarch64 normally.
There is no "buildstand" analogous to buildworld
or buildkernel that takes TARGET and TARGET_ARCH
for cross builds. Thus I ended up with a full
buildworld to establish a context for the cross
builds.

=3D=3D=3D
Mark Millard
marklmi at yahoo.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6A679278-69E0-4592-BFED-48ED8598C2F1>