Date: Tue, 16 Jan 2024 17:32:05 +0100 From: Emmanuel Vadot <manu@bidouilliste.com> To: Doug Rabson <dfr@rabson.org> Cc: Mike Karels <mike@karels.net>, Mark Millard <marklmi@yahoo.com>, FreeBSD ARM List <freebsd-arm@freebsd.org> Subject: Re: When will FreeBSD support RPI5? Message-ID: <20240116173205.41b4e0ebaacc42581a0d408d@bidouilliste.com> In-Reply-To: <CACA0VUgYZk1yqOVnEGGdjyX9GZyOV6XjwbjdZq8S9h-nz7jwCg@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> <1C02D1FA-5BF0-4C82-AD0E-6F9E5EB8A0B9@karels.net> <CACA0VUgYZk1yqOVnEGGdjyX9GZyOV6XjwbjdZq8S9h-nz7jwCg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 16 Jan 2024 14:57:40 +0000 Doug Rabson <dfr@rabson.org> wrote: > On Sat, 13 Jan 2024 at 19:05, Mike Karels <mike@karels.net> wrote: > > > On 13 Jan 2024, at 12:32, Mark Millard 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. > > > > The cadence/cgem driver uses FDT. I haven't looked at details yet. The > > addition > > might be as simple as adding a compat string. Hopefully it doesn't > > require major > > surgery. I just ordered an RPi 5 (8 GB); it will take a while to be > > delivered. > > > > The existing driver has the correct compat string but we don't get that far > since the rp1 node doesn't get probed and attached. This node is nested > under pcie@120000 and the whole subtree never gets explored. Interestingly, > if I hack the 2711 driver a little (based on reading Linux sources), I can > get that to attach and the rp1 southbridge is visible on the PCI bus with > vendor id 0x1de4, device id 0x0001. I made a stub driver for it but that > isn't particularly helpful since we need an FDT device to get simplebus to > attach and discover all the rp1 sub-devices. Why is there FDT children under a pci device ??? > I could try to add any ofw children to the pcie device, I guess. By the > looks of things, that just needs me to implement ofw_bus_get_devinfo and > maybe bus_get_resource_list in the pcie driver. Reading the DTB sources, > the 2711 pcie separates out the MSI part as a separate node in the DTB > which will need a driver before we can get much further. -- 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?20240116173205.41b4e0ebaacc42581a0d408d>