Date: Sun, 14 Jan 2024 16:11:55 +0100 From: Emmanuel Vadot <manu@bidouilliste.com> To: Doug Rabson <dfr@rabson.org> Cc: Mark Millard <marklmi@yahoo.com>, Jesper Schmitz Mouridsen <jsm@freebsd.org>, John Kennedy <warlock@phouka.net>, ykla <yklaxds@gmail.com>, FreeBSD ARM List <freebsd-arm@freebsd.org> Subject: Re: When will FreeBSD support RPI5? Message-ID: <20240114161155.e82b64f2b0cf82fea0e606e4@bidouilliste.com> In-Reply-To: <CACA0VUifmu=dhX0RFev30CXaHNhYQ=h6W%2BwYPG_rMiX-NZYBgw@mail.gmail.com> References: <CA%2BPGaYC6__AZUgHqfv3PO-o=7FnEzRzTPGPhMuahFNdcN0D69A@mail.gmail.com> <ddbf131c-1f2c-424b-9a3f-54ded16c5123@FreeBSD.org> <ZZHC_SjrPgs3DMKe@phouka1.phouka.net> <5a39810c-5fd8-4969-a222-2561b050b035@FreeBSD.org> <CACA0VUjoTTVje7tQe%2BVHXPco_xs4C8vSB3P3eDnhuYJYSqc7Sw@mail.gmail.com> <A2CA16F2-9894-41F2-8035-A5E8BE271B58@yahoo.com> <CACA0VUg7XHtQ7nviXVUZ_dZGaPe2uhbT-eGRbMAOajqZLGDmew@mail.gmail.com> <ECBFBAEF-C35B-4C68-B9BF-C3B62E5A4DFE@yahoo.com> <347FE009-A470-4765-A9B9-7C9AB5E954DA@yahoo.com> <CACA0VUh_X5nudWGOCeupW_34=aUewmwvOWmp61ONm=PtNr9wFw@mail.gmail.com> <76FA010A-338F-4E32-B381-37C7BA63CAFC@yahoo.com> <CACA0VUifmu=dhX0RFev30CXaHNhYQ=h6W%2BwYPG_rMiX-NZYBgw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 14 Jan 2024 13:52:51 +0000 Doug Rabson <dfr@rabson.org> wrote: > On Sat, 13 Jan 2024 at 18:32, Mark Millard <marklmi@yahoo.com> wrote: > > > On Jan 13, 2024, at 07:38, Doug Rabson <dfr@rabson.org> wrote: > > > > > Getting back to the RPI 5, with a tweak to > > arm/broadcom/bcm2835bcm2835_vcbus.c to treat the memory config the same as > > RPI 4 and to dev/sdhci/sdhci_fdt.c to treat the RPI 5 sdhci controllers as > > generic, I can boot to multiuser mode using the EDK2 firmware from > > https://github.com/worproject/rpi5-uefi with ACPI/Device Tree mode set to > > Both. > > > > What does FreeBSD do with "Both"? Does it actually use some ACPI > > and some Device Tree? Or does it just use ACPI? Does your > > combination do anything different than just using ACPI? > > > > > This does not have working PCIe or ethernet yet - I think ethernet ought > > to work since we seem to have a matching driver in the tree in dev/cadence. > > > > Sounds like the same status as booting just ACPI with no such > > adjustments too bcm2835bcm2835_vcbus.c or sdhci_fdt.c ? > > > > I think Mike Karels plans on investigating getting Ethernet > > going based on cgem . I've no clue if this is ACPI, DeviceTree, > > or both. > > > > My usage has been pure ACPI, no software adjustments specific > > to getting the RPi5 operational. Use of a USB3 Ethernet dongle. > > > > As far as I can tell, 'Both' works almost exactly the same as 'Devicetree' > - I don't think the acpi device is attached to nexus at all. 'Both' for EDK2 mean that dt and acpi table are exposed, and by default on FreeBSD we use dt and only fallback to acpi if dt wasn't found. > Ethernet should be supported by cgem(4). This device is on the rp1 > southbridge. In the DTB, rp1 is a simplebus under pcie@120000 > and ethernet@100000 is a child of rp1. I think it doesn't match for me > because there is no driver matching pcie@ yet. The existing bcm2838 pci > driver could be adapted for RPI 5 - reading the linux driver shows some > smallish differences in device initialisation. > > I have attached verbose dmesg dumps for all three EDK2 acpi modes. > > > > -- Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240114161155.e82b64f2b0cf82fea0e606e4>