Change Details

I've used this type of variation of D25219 for my occasional UEFI/ACPI RPi4B activity since my comments on D25219 not passing my large-file-copy-and-diff testing on RPi4B's with the B0T stepping, Rev 1.4, and >= 4 GiBytes of RAM while using https://github.com/pftf/RPi4 , tracking as I've updated FreeBSD. The intent vs. D25219 is to, for example, change 0xc0000000 for hw.busdma.zone0.lowaddr to the value shown in: ``` # sysctl hw.busdma.zone0.lowaddr hw.busdma.zone0.lowaddr: 0xbfffffff ``` That matches the kind of values that I've seen in other contexts for hw.busdma.zoneN.lowaddr values. See my notes in D25219 and comments in the submitted code. The diff presented is against: ``` # ~/fbsd-based-on-what-commit.sh -C /usr/main-src/ branch: main merge-base: 4d1ba6febfa7c7808027fd1ef60b3bffadd17853 merge-base: CommitDate: 2022-03-22 23:58:48 +0000 4d1ba6febfa7 (HEAD -> main, freebsd/main, freebsd/HEAD) bsdinstall hardening: Replace dialog with bsddialog n253904 (--first-parent --count for merge-base) ``` Note: I was far from sure that this form of submittal of a variant was reasonable. It is my second ever submittal here. I simply duplicated the Reviewers and Subscribers lists. I've no problem if someone that knows what they are doing for this context wants to just make it more appropriate in any way. My view of things is rather narrow/limited.

I've used earlier variations of D25219 for my occasional UEFI/ACPI RPi4B activity since my comments on D25219 not passing my large-file-copy-and-diff testing on RPi4B's with the B0T stepping, Rev 1.4, and >= 4 GiBytes of RAM while using https://github.com/pftf/RPi4 (EDK2 RPi4B UEFI/ACPI testing), tracking as I've updated FreeBSD. The intent vs. D25219 is to, for example, change 0xc0000000 for hw.busdma.zone0.lowaddr to the value shown in: ``` # sysctl hw.busdma.zone0.lowaddr hw.busdma.zone0.lowaddr: 0xbfffffff ``` That matches the kind of values that I've seen in other contexts for hw.busdma.zoneN.lowaddr values. See my notes in D25219 and comments in the submitted code. # ~/fbsd-based-on-what-commit.sh -C /usr/main-src/ f83db6441a2f (HEAD -> main, freebsd/main, freebsd/HEAD) sctp: minor changes due to upstreaming of Glebs recent changes branch: main merge-base: f83db6441a2f4f925a169c7ddf844589cb73c9b5 merge-base: CommitDate: 2022-11-06 22:06:40 +0000 n259064 (--first-parent --count for merge-base) ```

I've used this type ofearlier variations of D25219 for my occasional UEFI/ACPI RPi4B activity since my comments on D25219 not passing my large-file-copy-and-diff testing on RPi4B's with the B0T stepping, Rev 1.4, and >= 4 GiBytes of RAM while using https://github.com/pftf/RPi4 (EDK2 RPi4B UEFI/ACPI testing), tracking as I've updated FreeBSD. The intent vs. D25219 is to, for example, change 0xc0000000 for hw.busdma.zone0.lowaddr to the value shown in: ``` # sysctl hw.busdma.zone0.lowaddr hw.busdma.zone0.lowaddr: 0xbfffffff ``` That matches the kind of values that I've seen in other contexts for hw.busdma.zoneN.lowaddr values. See my notes in D25219 and comments in the submitted code. The diff presented is against: ``` # ~/fbsd-based-on-what-commit.sh -C /usr/main-src/ f83db6441a2f (HEAD -> main, freebsd/main, freebsd/HEAD) sctp: minor changes due to upstreaming of Glebs recent changes branch: main merge-base: 4d1ba6febfa7c7808027fd1ef60b3bffadd17853f83db6441a2f4f925a169c7ddf844589cb73c9b5 merge-base: CommitDate: 2022-03-22 23:58:4811-06 22:06:40 +0000 4d1ba6febfa7 (HEAD -> main, freebsd/main, freebsd/HEAD) bsdinstall hardening: Replace dialog with bsddialogn259064 (--first-parent --count for merge-base) n253904 (--first-parent --count for merge-base) ``` Note: I was far from sure that this form of submittal of a variant was reasonable. It is my second ever submittal here. I simply duplicated the Reviewers and Subscribers lists. I've no problem if someone that knows what they are doing for this context wants to just make it more appropriate in any way. My view of things is rather narrow/limited.