summaryrefslogtreecommitdiffstats
path: root/meta-ti-bsp/conf/machine
Commit message (Collapse)AuthorAgeFilesLines
...
* linux-ti-staging: Drop systest kernelAndrew Davis2025-01-121-1/+0
| | | | | | | | | This was used when the kernel had a different configuration for the testing kernel. This has not been the case since v5.10 so drop the systest kernel package as it will be the same as the normal kernel package now. Signed-off-by: Andrew Davis <afd@ti.com>
* ti-bsp: Change to 6.12 as the defaultRyan Eatmon2025-01-121-1/+1
| | | | | | | | | | | | | | | | | We are moving to 6.12 to be our new LTS, so we are switching the default BSP to that. You can still access the 6.6 kernel if you need to by using the BSP system and setting TI_PREFERRED_BSP = "ti-6_6" in your local.conf. Current known issues: - Hardware graphics is disabled until we get a patch that updates the patches to work with the 6.12 kernel. Falling back to software rendering. - am62xxsip-evm and j742s2-evm are not supported in the 2025.01 u-boot yet. They will fail to build until the u-boot recipe is updated to point to a commit that fixes their support. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti-staging: Move 2024.10 to 2025.01 for ltsprepRyan Eatmon2024-12-201-2/+2
| | | | | | | We are moving to 2025.01 for the next LTS, so rename the previous ltsprep recipe and update it. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine: move remaining Beagle platforms to meta-beagleDenys Dmytriyenko2024-12-194-134/+0
| | | | | | | Include beagle-bsp.inc to define "bb_org" BSP settings and select that as a default. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* conf/machine: split beagleplay config between meta-ti-bsp and meta-beagleDenys Dmytriyenko2024-12-192-50/+2
| | | | | | | | | | | Extract "bb_org" BSP specific settings from beagleplay-ti in meta-ti-bsp and move them to own beagleplay machine config in meta-beagle. The differences between 2 configs are minimal, hence beagleplay in meta-beagle inherits beagleplay-ti from meta-ti-bsp as a base and only adjusts what's needed. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* conf/machine: move "bb_org" BSP settings to meta-beagleDenys Dmytriyenko2024-12-191-20/+1
| | | | | | | Define "bb_org" default BSP settings in meta-beagle layer that all Beagle platforms will use. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* conf/machine: rename beagleplay machine to beagleplay-tiDenys Dmytriyenko2024-12-192-0/+0
| | | | | | | | | | | | | BeaglePlay is officially supported by TI "ti-6_6" BSP and is part of the TI-SDK releases. Switching BSP to BeagleBoard.org "bb_org" settings for the same machine is possible within the same layer. But having different machine configs for the same machine name in multiple layers can be confusing and prone to errors. Hence rename the config to indicate BeaglePlay with official TI support in order to re-use the canonical name in a separate layer. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* conf: machine: omap-a15.inc: include ipu1 firmware in the boot partitionAniket Limaye2024-12-111-1/+2
| | | | | | | | | | Early Boot of remote processors is supported at the SPL stage of the bootloader. Currently, SPL looks for the remoteproc firmwares in the boot partition. Therefore, add the rproc firmware to the boot partition of wic images. Signed-off-by: Aniket Limaye <a-limaye@ti.com>
* conf: machine: am62xx-lp-evm: Add PWM overlaysJudith Mendez2024-12-061-0/+2
| | | | | | | Add the PWM overlays: k3-am62x-sk-dmtimer-pwm and k3-am62x-sk-pwm for AM62 LP SK. Signed-off-by: Judith Mendez <jm@ti.com>
* conf: machine: am62pxx: Pick overlays for V3Link camerasRishikesh Donadkar2024-11-211-0/+1
| | | | | | | | | | | | | The V3Link camera fusion board [1] can be used to connect upto 4 OV5640 sensors to SK-AM62A. Overlays for interfacing OV5640 sensor with V3Link are built as part of the TI linux kernel. Pick these in the BSP filesystem. [1]: https://www.arducam.com/product/arducam-v3link-camera-kit-for-ti-development-boards/ Signed-off-by: Rishikesh Donadkar <r-donadkar@ti.com> Acked-by: Chirag Shilwant <c-shilwant@ti.com>
* sgx: bump version for kernel 6.6 / mesa 23.2.1Randolph Sapp2024-11-071-1/+3
| | | | | | | | | | Bump versions of mesa-pvr and ti-sgx-ddk-km to support SGX with kernel 6.6 and the same version of mesa rogue is using. Enable SGX by default in the 6.6 BSP provider section logic. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: Tighten up versions for PREFERRED_VERSIONRyan Eatmon2024-10-311-3/+3
| | | | | | | | | | PREFERRED_VERSION matches against the PV in the recipe, not against the file name. With the upcoming 6.12, the 6.1 kernel version string was a little too loose. The "6.1%" could glob onto the 6.12 recipe. Take this time to also clean up a couple of the other versions and narrow them down. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Add support for bsp-ti-6_12 in beagleplayChirag Shilwant2024-10-242-0/+2
| | | | | | | | Add bsp-ti-6_12 overrides in A53 & R5 machine configuration to ensure it picks the appropriate u-boot configs for beagleplay Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* uboot-ti-next: Add new recipe to track master-nextRyan Eatmon2024-10-241-1/+1
| | | | | | | | | Our upstream testing needs to point to both master and master-next and we need two different recipes to track that. This recipe mirrors the linux-ti-next recipe and points to the master-next branch for the latest bleeding edge changes. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-mainline: Update to version: v6.11LCPD Automation Script2024-10-247-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | Updated the value(s) for: am57xx-evm: KERNEL_DEVICETREE am62axx-evm: KERNEL_DEVICETREE am62pxx-evm: KERNEL_DEVICETREE am62xx-evm: KERNEL_DEVICETREE am62xx-lp-evm: KERNEL_DEVICETREE am68-sk: KERNEL_DEVICETREE am69-sk: KERNEL_DEVICETREE beagleplay: KERNEL_DEVICETREE am64xx-evm: KERNEL_DEVICETREE am65xx-evm: KERNEL_DEVICETREE am335x-evm: KERNEL_DEVICETREE am437x-evm: KERNEL_DEVICETREE j7200-evm: KERNEL_DEVICETREE j721e-evm: KERNEL_DEVICETREE j721e-sk: KERNEL_DEVICETREE j721s2-evm: KERNEL_DEVICETREE j722s-evm: KERNEL_DEVICETREE j784s4-evm: KERNEL_DEVICETREE linux-ti-mainline: PV,SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: Add RT and systest supportRyan Eatmon2024-10-091-0/+2
| | | | | | | | | | | | We were missing controlling the versions for linux-ti-staging-rt and linux-ti-staging-systest using the BSP framework. Since the PREFERRED_VERSION is not tied to the virtual/kernel we need two additional settings for those alternate kernel package names. For BSPs that do not have the -rt and -systest recipes then the two new variable settings should effectively be ignored and cause no issues. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: Add ti-6_12Ryan Eatmon2024-10-081-1/+14
| | | | | | Add new BSP for the 6.12 kernel and u-boot 2024.10 versions. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Remove multiconfig compulsion for k3 platformsChirag Shilwant2024-09-1216-3/+31
| | | | | | | | | | | | | | | - While implementing k3.inc, there was an assumption that all k3 based TI SOC's would always have a Cortex-R5F core [1]. This assumption is not true. - Hence, create a new mc_k3r5 include file & move the multiconfig dependencies to it. Also, include this file only in those k3 platforms which needs the R5 multiconfig support. [1]: https://git.ti.com/cgit/arago-project/meta-ti/commit/conf/machine/include/k3.inc?h=scarthgap&id=f814840465358a6b5429ad20165742ac6e6e6a29 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "conf: machine: Breakout IMAGE_BOOT_FILES into new variables"Ryan Eatmon2024-09-1217-95/+43
| | | | This reverts commit cada5eb9a6e69e5548024d930945834c2ffc6ab2.
* Revert "conf: machine: am62xx-unified: Create new common am62xx machine"Ryan Eatmon2024-09-128-76/+29
| | | | This reverts commit a1eb263dd30789cb2044360cd509d68ab63e2f47.
* Revert "conf: machine: Move to new UBOOT_FRAGMENTS"Ryan Eatmon2024-09-127-20/+19
| | | | This reverts commit fc52833b3423d9a11bc85739c08c753977666e39.
* conf: machine: Move to new UBOOT_FRAGMENTSRyan Eatmon2024-08-227-19/+20
| | | | | | Migrate the machine configs to use the new UBOOT_FRAGMENTS methodology. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62xx-unified: Create new common am62xx machineRyan Eatmon2024-08-228-29/+76
| | | | | | | | | | To reduce the number of required builds for testing purposes, create a common unified am62xx machine target that can produce all of the files for all of the variant platforms related to am62xx (sip and lp). Additionally, continue to support building the specific target if desired. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Breakout IMAGE_BOOT_FILES into new variablesRyan Eatmon2024-08-2217-43/+95
| | | | | | | | | | | | | | | | | The IMAGE_BOOT_FILES variable has been overloaded to include additional files that should be included in the boot partition but are not boot loaders themselves (images, etc...). There is also a need to generate a report in the deploy directory for the list of actual bootloader files that were constructed as part of the build. Solution, break the IMAGE_BOOT_FILES into two new variables TI_BOOTLAODERS and TI_MULTICONFIGS and default IMAGE_BOOT_FILES to TI_BOOTLOADERS. This way we can stick additional boot loaders into a new variable and they will will end up in the IMAGE_BOOT_FILES list. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: omapl138-lcdk: Update KERNEL_DEVICETREERyan Eatmon2024-08-041-2/+2
| | | | | | | Update the entry for KERNEL_DEVICETREE to match what is in the 6.10 kernel. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-mainline: Update to version: v6.10LCPD Automation Script2024-08-0217-14/+120
| | | | | | | | | | | | | | | | | | | | | | | | | | Updated the value(s) for: am57xx-evm: KERNEL_DEVICETREE am62axx-evm: KERNEL_DEVICETREE am62pxx-evm: KERNEL_DEVICETREE am62xx-evm: KERNEL_DEVICETREE am62xx-lp-evm: KERNEL_DEVICETREE am68-sk: KERNEL_DEVICETREE am69-sk: KERNEL_DEVICETREE beagleplay: KERNEL_DEVICETREE am64xx-evm: KERNEL_DEVICETREE am65xx-evm: KERNEL_DEVICETREE am335x-evm: KERNEL_DEVICETREE am437x-evm: KERNEL_DEVICETREE j7200-evm: KERNEL_DEVICETREE j721e-evm: KERNEL_DEVICETREE j721e-sk: KERNEL_DEVICETREE j721s2-evm: KERNEL_DEVICETREE j722s-evm: KERNEL_DEVICETREE j784s4-evm: KERNEL_DEVICETREE linux-ti-mainline: PV,SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: j742s2: add Rogue GPU driver to machine definitionAniket Limaye2024-07-181-1/+1
| | | | | | | | Add ti-img-rogue-driver as the preferred provider and enable the gpu driver in the image. Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: Add support for j742s2-evmAniket Limaye2024-07-183-0/+52
| | | | | | | | | - Add A72 and R5 machine configurations for j742s2-evm - Add firmware overrides. - Add u-boot overrides. Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j722s: Update IMAGE_BOOT_FILES for mainline buildsRyan Eatmon2024-07-171-0/+1
| | | | | | | As this is still a new platform, the bsp-mainline also does not have the hs-fs boot files. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "conf: machine: am62*-evm-k3r5.conf: apply fragment for enabling USB DFU"cicd.scarthgap.20240712094310.00.06Ryan Eatmon2024-07-125-9/+1
| | | | | | | | This reverts commit fa94effc26a8678a5400291a3ca0ef1000eea7b1. There are boot issues with SD card booting with this change. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62*-evm-k3r5.conf: apply fragment for enabling USB DFUSiddharth Vadapalli2024-07-115-1/+9
| | | | | | | | | | The config fragment "am62x_r5_usbdfu.config" is applicable to AM62x, AM62x-SIP, AM62x-LP-EVM, AM62Ax and AM62Px devices and enables USB DFU boot support at the R5 stage of boot. Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com> Acked-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Update am62pxx-evm for multi-BSP supportChirag Shilwant2024-07-041-2/+4
| | | | | | | | | | | | | | | | | | - In ti-u-boot-2024.04, the config fragment to disable splashscreen is now renamed to am62x_evm_prune_splashscreen.config [1] Hence, update UBOOT_CONFIG_FRAGMENTS for the same. - Add UBOOT_CONFIG_FRAGMENTS:bsp-ti-6_1 which ensures that am62pxx-evm machine configuration still supports Display Cluster usecase [2] with ti-u-boot-2023.04 [1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2024.04&id=981eddc83dfdbbf176a4984977f9779dc1d56f87 [2]: https://software-dl.ti.com/mcu-plus-sdk/esd/AM62PX/09_01_00_39/exports/docs/api_guide_am62px/EXAMPLES_DRIVERS_DSS_DISPLAY_SHARE.html Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Reviewed-by: Devarsh Thakkar <devarsht@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am69-sk: Pick overlays for IMX219 and FPD-LinkVaishnav Achath2024-06-281-0/+3
| | | | | | | | | | J721E SK, AM68 SK and AM69 SK have similar connectivity for CSI2 RPi connector and the same overlays can be reused, thus pick the J721E SK CSI2 IMX219, fusion overlay and AM68 SK V3Link fusion overlay for AM69 SK also. Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am68-sk: Pick overlays for IMX219 and FPD-LinkVaishnav Achath2024-06-281-0/+2
| | | | | | | | | J721E SK and AM68 SK have similar connectivity for CSI2 RPi connector and the same overlays can be reused, thus pick the J721E SK CSI2 IMX219 and fusion overlays for AM68 SK also. Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j784s4-evm: Pick overlays for CSI2 and FPD-LinkVaishnav Achath2024-06-281-0/+2
| | | | | | | | | J784S4 and J721S2 EVM has similar connectivity for MIPI CSI2 connector and the same overlays can be reused, thus pick the J721S2 CSI2 OV5640 and J721S2 EVM fusion overlays for J784S4. Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* j722s: next BSP doesn't support all SR and HS variantsRyan Eatmon2024-06-201-1/+3
| | | | | | | Adjust IMAGE_BOOT_FILES list as next BSP does not support all combinations of SR1.0, HS-FS and HS-SE variants. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine, ti-bsp: Add support for next BSP providerRyan Eatmon2024-06-201-1/+14
| | | | | | | For our upstream testing flow we have the need to have a "next" BSP for configuring various settings based on building the latest kernel/uboot. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* j7200: mainline BSP doesn't support all SR and HS variantsDenys Dmytriyenko2024-06-191-2/+6
| | | | | | | | | Adjust IMAGE_BOOT_FILES list as mainline BSP does not support all combinations of SR1.0, SR2.0, HS-FS and HS-SE variants. Suggested-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* beaglebone-ai64: BB.org does not support all SR and HS variantsDenys Dmytriyenko2024-06-191-0/+3
| | | | | | | | Adjust IMAGE_BOOT_FILES list as BB.org BSP does not support all combinations of SR1.1, SR2.0, HS-FS and HS-SE variants, same as J721e EVM in mainline. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Update am62xxsip-evm for multi-BSP supportChirag Shilwant2024-06-182-0/+6
| | | | | | | | Update am62xxsip-evm machine configuration to support TI kernel 6.1 & ti-u-boot-2023.04 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: add j721e-sk machine-configurationAniket Limaye2024-06-182-0/+27
| | | | | | | | | | | | As of commit [1] there will be a separate defconfig to build u-boot for j721e-evm and j721e-sk. Hence, introduce new yocto machine configs for j721e-sk. [1]: https://source.denx.de/u-boot/u-boot/-/commit/c9507f07a1d6c92bd1f73fd64384f8c5994be9c2 Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti: remove MACHINE_KERNEL_PR globallyDenys Dmytriyenko2024-06-154-12/+0
| | | | | | | | MACHINE_KERNEL_PR is a remnant of the early OE days and hasn't been needed for quite some time. Let's finally remove it completely. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine: use the default TI BSP for BeaglePlayDenys Dmytriyenko2024-06-157-7/+8
| | | | | | | | | | | BeaglePlay gains official support from latest TI lts-6.6 baseline, so set it as the default. Other Beagle platforms will still use BB.org as default. And these defaults can still be changed with TI_PREFERRED_BSP setting in a distro config or by end user in the local.conf Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine/beagle*, linux-bb.org: update for multi-BSP supportDenys Dmytriyenko2024-06-156-36/+100
| | | | | | | Update all Beagle platform configurations to support multiple BSPs. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine/j721e: some BSPs don't support all SR and HS variantsDenys Dmytriyenko2024-06-151-8/+10
| | | | | | | | Adjust IMAGE_BOOT_FILES list as some BSPs do not support all combinations of SR1.1, SR2.0, HS-FS and HS-SE variants. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine, ti-bsp: add support for multiple BSP providersDenys Dmytriyenko2024-06-1520-43/+131
| | | | | | | | | This adds a facility to define multiple supported BSPs with their own preferences for individual components, as well as lets machine configs specify conditional configurations for different BSPs. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Update UBOOT_MACHINE for am62xxsip-evmChirag Shilwant2024-06-152-7/+2
| | | | | | | | | | Modify the U-Boot defconfig names for A53 and R5 machine configurations based on ti-u-boot-2024.04 [1] [1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2024.04&id=df5181f8c6c41bf018ec043d565581b5d8a291c5 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine, linux-bb.org: re-org DT lists for Beagle platformsDenys Dmytriyenko2024-06-075-104/+24
| | | | | | | | | | | | | | | | | | | | | In order to be able to switch between different kernel providers, as well as different versions of kernel LTS (e.g. 6.1 vs. 6.6), let's re-organize Device Tree lists as follows: * Move all Beagle-specific DTBs and overlays into corresponding linux-bb.org recipe for now, to be used when building beagleboard.org baseline * Update KERNEL_DEVICETREE in the machine configs to only list what already exists in the upstream/mainline kernel * Update KERNEL_DEVICETREE_PREFIX to match the list when building TI baseline With this change it is now very easy to switch the kernel between providers supported by meta-ti - linux-ti-mainline, linux-ti-staging and linux-bb.org Please note that 6.6 LTS has moved to "vendored" device tree layout even for 32-bit platforms, while BB.org still uses 6.1 LTS and flat DT layout. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: add AM68-SK machine configurationAniket Limaye2024-06-063-0/+50
| | | | | | | | | | | | | | As of commit [1] there will be a separate defconfig to build u-boot for j721s2-evm and am68-sk. Hence, introduce new yocto machine configs for am68-sk. This is done through a new am68.inc file as the am68-sk platform does not support GP. So j721s2-evm.inc is copied to am68.inc and updated accordingly. [1]: https://source.denx.de/u-boot/u-boot/-/commit/a96be9b8c05ea835d27f7c9bae03279b8bd5dcf2 Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: update BeagleBoard.org BSP to the latestDenys Dmytriyenko2024-05-312-0/+17
| | | | | | | | | * Update linux-bb.org to 6.1.80 for both 32 and 64 bit platforms * Update DTB/DTBO lists to include latest renames and additions * Re-enable vendored DTB layout by default Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-08 07:47:18 +0000