Re: Attempting to install on RPi4B w/ UEFI, having some problems
Klaus Cucinauomo via freebsd-arm <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]> |
Lol :-) > > >>> > On 2020-Sep-11, at 04:42, Robert Clausecker <fuz at fuz.su> wrote: >> >> The Wiki page (arm/Raspberry Pi) does say explicitly: >> >>> RPI4-UEFI, allows us to triple-boot FreeBSD on the RPi4 from either >>> Device Tree or ACPI or ACPI&Device-tree(both). > Am 11.09.2020 um 20:25 schrieb Mark Millard via freebsd-arm <[email protected]>: > Ahh. I do not expect that the Wiki is being maintained by > someone involved in implementing such things. So somewhat > more guess work is involved in the WIki's production. Mark, you joker :-) lol Ha Ha I assume you know the RP4-Wiki-page is maintained by me and I assume that (from my last knowledge) NOBODY is implementing anything for RPI4-UEFI-dev- compatibility at the moment (except GregV who’s work was published by me in the Wiki). While not everybody knows that it’s a dev`s Wiki and not a release-information-website for working environments and user-support, it should be clear that things being in development(or not) are NOT marked as production ready in the Wiki. Aarch64 will hold it’s Tier2-status in Fbsd 13, so many devs are busy on Tier1 or other platforms & things. I know since months that RPI-UEFI-dev has a triple boot-option and that A lot oft things(including the kernel hang if booted(it boots!) in DeviceTree mode) DO NOT WORK. At the time I wrote about rpi4-uefi-dev RPI4-UEFI-dev didn’t even boot to the root-prompt in FreeBSD in ACPI-mode. Again: the Wiki ISN`T a user’s support-site for working environments but I’m happy if it expands it`s popularity for all kind of users/devs, for everybody. (in best case people who want to help in developing or even of course in extending the Wiki) . Klaus _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "[email protected]"