Date: Sat, 13 Jan 2024 11:54:09 -0800 From: Mark Millard <marklmi@yahoo.com> To: Jesper Schmitz Mouridsen <jsm@FreeBSD.org> Cc: Doug Rabson <dfr@rabson.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: <D5D3843D-088F-4A61-8FFD-A40832237A24@yahoo.com> In-Reply-To: <9e45c7d7-450c-48e5-8101-c6ea5cb3a023@FreeBSD.org> 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> <9e45c7d7-450c-48e5-8101-c6ea5cb3a023@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 13, 2024, at 11:22, Jesper Schmitz Mouridsen <jsm@FreeBSD.org> = wrote: >=20 > On 13.01.2024 19.32, Mark Millard wrote: >> On Jan 13, 2024, at 07:38, Doug Rabson <dfr@rabson.org> wrote: >>=20 >>> 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? >=20 > How does the sd card show up? Context below is via use of a aarch64 snapshot image dd'd to USB3 media and use of a microsd card to hold the EDK2: # uname -apKU FreeBSD generic 15.0-CURRENT FreeBSD 15.0-CURRENT #0 = main-n267507-a61d2c7fbd3c: Thu Jan 11 06:26:30 UTC 2024 = root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC = arm64 aarch64 1500008 1500008 # gpart show =3D> 40 249737136 mmcsd0 GPT (119G) 40 2008 - free - (1.0M) 2048 249733120 1 efi (119G) 249735168 2008 - free - (1.0M) # mount -onoatime -tmsdosfs /dev/mmcsd0p1 /mnt # ls -Tlod /mnt/* -rwxr-xr-x 1 root wheel uarch 2031616 Jan 5 18:20:18 2024 = /mnt/RPI_EFI.fd -rwxr-xr-x 1 root wheel uarch 76038 Jan 5 18:21:50 2024 = /mnt/bcm2712-rpi-5-b.dtb -rwxr-xr-x 1 root wheel uarch 388 Jan 5 18:18:24 2024 = /mnt/config.txt # dmesg -a | grep -E "(sdhci|mmc)" sdhci_acpi0: <Intel Bay Trail/Braswell SDXC Controller> iomem = 0x1000fff000-0x1000fff25f irq 3 on acpi0 mmc0: <MMC/SD bus> on sdhci_acpi0 sdhci_acpi1: <Intel Bay Trail/Braswell SDXC Controller> iomem = 0x1001100000-0x100110025f irq 4 on acpi0 mmc1: <MMC/SD bus> on sdhci_acpi1 mmcsd0: 128GB <SDHC SC128 8.0 SN REDACTED MFG 04/2018 by 3 SD> at mmc0 = 50.0MHz/4bit/65535-block mmc1: No compatible cards found on bus # more /mnt/config.txt=20 armstub=3DRPI_EFI.fd device_tree_address=3D0x1f0000 device_tree_end=3D0x210000 # Leave RP1 PCIe configured on hand-off. pciex4_reset=3D0 # Force 32 bpp framebuffer allocation. framebuffer_depth=3D32 # Disable compensation for displays with overscan. disable_overscan=3D1 # Force maximum USB power regardless of the power supply. usb_max_current_enable=3D1 # Force maximum CPU speed. force_turbo=3D1 > BTW i did put some stuff here [1] > I could not get bcm_dma to work anyone planning on getting that to = work? it should be similar to 2711 documented in [2] >=20 >>> 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 ? >>=20 >> I think Mike Karels plans on investigating getting Ethernet >> going based on cgem . I've no clue if this is ACPI, DeviceTree, >> or both. >>=20 >> My usage has been pure ACPI, no software adjustments specific >> to getting the RPi5 operational. Use of a USB3 Ethernet dongle. >>=20 >> =3D=3D=3D >> Mark Millard >> marklmi at yahoo.com >>=20 >>=20 > [1] https://github.com/jsm222/rpi5-stuff >=20 > [2] https://datasheets.raspberrypi.com/bcm2711/bcm2711-peripherals.pdf =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D5D3843D-088F-4A61-8FFD-A40832237A24>