Date: Sun, 8 Jan 2023 18:57:32 +0100 From: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> To: Mark Millard <marklmi@yahoo.com>, "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, freebsd-arm@freebsd.org Subject: Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware Message-ID: <1EE321BB-6738-4931-BA75-4675C0D297E2@googlemail.com> In-Reply-To: <FC75A32C-B839-4699-AA15-5232CF3B1FC1@yahoo.com> References: <9C037D3F-A440-4708-993D-117F313691BB@yahoo.com> <374EC3E5-4CB4-4336-A8B9-7A9CF6151691@yahoo.com> <BCCBE0D7-8BEB-4D6D-A017-9A59000F1E2B@yahoo.com> <9E9C739E-8308-472A-B797-05A37559DD00@googlemail.com> <EAD84A57-E8F0-4149-BCFC-8A06FF03B11B@yahoo.com> <E1A6057C-4E0F-45B7-9278-86A09426DE49@googlemail.com> <217ACD33-A466-4A01-AD36-5D4A0C1B3CF0@yahoo.com> <3BE72ED7-8787-45E8-8341-FE9CF4CFB84F@googlemail.com> <FC75A32C-B839-4699-AA15-5232CF3B1FC1@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 08.01.2023 um 09:26 schrieb Mark Millard <marklmi@yahoo.com>: >=20 > I=E2=80=A6=E2=80=A6 ... > listed 4 kinds that sysutils/rpi-firmware does not have > .dtb files for. None of the 4 are considered supported > at this stage, so far as I know. But someone might work > on making one of them somewhat supported. Such a person > might like to avoid dealing with the > bcm_dma-lack-of-initialization related crashes. =E2=80=A6=E2=80=A6=E2=80= =A6=E2=80=A6=E2=80=A6... Thanks, Mark for detailed clarification=20 I think that's about what I expected in terms of the decision if=20 touching the firmware-upstream makes sense or not . I guess it doesn=E2=80=99t make sense (for now) .=20 For the cm4 I can say that =E2=80=9A unload=E2=80=98 of modules in = loader or for persistence disabling =E2=80=9Adevmatch' in rc.conf will get the machine to boot, newer FW not needed and it would spam = dmesg with unsupported features(for now).. No clue what the devmatch does in =E2=80=9Epre=E2=80=9C-boot because = =E2=80=9Estarting devd=E2=80=9C seems to do the job short before the = root login.. So for now of course unsupported machine type(while not bad once = booted), since pcie is buggy(and that=E2=80=99s a seeminglybig task to = fix that). What wasn=E2=80=99t clear for me is whether crashes like those from = Bj=C3=B6rn Zeeb have any relation to firmware/u-boot/eeprom, but reading closer I guess he=E2=80=99s probably using an unsupported = bootloader that could cause problems, What was also unclear for me is if there=E2=80=99s a similar boot issue = as with CM4 on the 4bC0T, Thanks for clarifying that there isn=E2=80=99t such an issue on 4bC0T. of course, it is important to examine all of this on a regular basis , thanks for that effort! Regards K.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1EE321BB-6738-4931-BA75-4675C0D297E2>