aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/x86
Commit message (Collapse)AuthorAgeFilesLines
...
* x86: add preinit hook for bootloader upgradeTomasz Maciej Nowak2020-03-012-1/+21
| | | | | | | | | | | | | | | | This commit fills the void for current OpenWrt installations which will be still on old bootloader version even after "x86: add bootloader upgrade on sysupgrade", since it performs bootloader upgrade only on sysupgrade. To keep all OpenWrt deploynents on the same GRUB version, add preinit hook, which will perform upgrade of the bootloader on first boot after sysupgrade. It's temporary solution and should be deleted, when the first release including this hook will no longer be supported by OpenWrt team. We can assume that all installations should be on current bootolader version and from there sysupgrade routine will be sufficient. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* x86: add bootloader upgrade on sysupgradeTomasz Maciej Nowak2020-03-012-3/+28
| | | | | | | | | | | | | | Currently bootloader always stays on the same version as when first written to boot medium (not true if partition layout changed, which will trigger sysupgrade process to write full disk image). That creates inconveniences as it always stays with same features or/and bugs. Users wishing to add support to additional modules or new version, would need to write the whole image, potentially destroying previous system configuration. To fix these, this commit adds additional routine to sysupgrade which upgrades unconditionally the bootloader to the latest state provided by OpenWrt. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* x86: image: cleanup before creating imageTomasz Maciej Nowak2020-03-011-0/+2
| | | | | | | | | There can be some leftovers from other image recipes, if the same directory names are used and multiply image types are selected. Therefore remove directories used in the recipe, before contents for the image are prepared. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* treewide: move commonly disabled symbols to generic configDavid Bauer2020-03-012-2/+0
| | | | | | | Move new commonly disabled kernel 5.4 symbols to the generic kernel configuration. Signed-off-by: David Bauer <mail@david-bauer.net>
* x86: Update configurationHauke Mehrtens2020-02-283-99/+44
| | | | | | | The configuration was refreshed and KERNEL_TESTING_PATCHVER was set to make it easy to compile for kernel 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: Refresh patches on kernel 5.4Hauke Mehrtens2020-02-284-32/+120
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: copy kernel patches from 4.19 to 5.4Hauke Mehrtens2020-02-289-0/+1920
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: x86_64: drop CALGARY properlyKevin Darbyshire-Bryant2020-02-251-2/+2
| | | | | | | Use correct config syntax of 'is not set' instead of just commenting the line Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* kernel: x86_64: drop CALGARY IOMMUKevin Darbyshire-Bryant2020-02-251-2/+2
| | | | | | | | | | | | The calgary IOMMU was only used on high-end IBM systems in the early x86_64 age. This is an unlikely OpenWrt target and in fact upstream are looking to drop the driver entirely with the bonus that we no longer see: [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing! Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* x86: avoid underscore in package nameSungbo Eo2020-02-231-3/+3
| | | | | | | As 07e1d88d7beb ("kernel: avoid underscore in *6lowpan package names") shows, underscores might cause build failures. Replace underscore with dash. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* x86: Add missing kernel option CONFIG_X86_DECODER_SELFTESTHauke Mehrtens2020-02-222-0/+2
| | | | | | | | | This option has now a different dependency and can be activated, set a default value. Fixes: 20b5a4ca01ca ("kernel: bump 4.19 to 4.19.101") Signed-off-by: Hauke Mehrtens <hauke.mehrtens@intel.com> Tested-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* kernel: bump 4.19 to 4.19.90Koen Vandeputte2019-12-241-1/+1
| | | | | | | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 010-dmaengine-dw-dmac-implement-dma-prot.patch - 950-0148-Increase-firmware-call-buffer-size-to-48-bytes.patch - 950-0206-Mailbox-firmware-calls-now-use-kmalloc-2749.patch - 402-leds-trigger-netdev-fix-handling-on-interface-rename.patch Fixes: - CVE-2019-19332 Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> [Add 010-dt-bindings-dmaengine-dw-dmac-add-protection-control.patch] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* build: build proper VMDK formats for ESXI 6.5John Sommerville2019-12-231-0/+6
| | | | | | | | | | | | | | | | | | | | | VMWare ESXI 6.5 and above is not compatible with subformat=monolithicSparse (The default qemu-img convert -O VMDK option). Monolithic Sparse vmdk can be imported, but issues occur when running sysupgrade with new images and other tasks that modify the file system (issues like Kernel panics, reboot loops, sometimes crashing the Host ESXI box). This change creates an additional VMDK output file for ESXI that sets the subformat to monlithicFlat, and the adapter_type to the SCSI lsilogic controller. This change existed back on: 25e36d379e73d64d6316fae9dc841c5ef28980f1 But it looks like the change was removed when refactoring occurred with: 5f6a2732f892b6229473576d89cc963ae9c97d5d Signed-off-by: John Sommerville <jsommerville@untangle.com>
* kernel: bump 4.19 to 4.19.84Koen Vandeputte2019-11-191-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 950-0748-net-bcmgenet-Workaround-for-Pi-4B-network-issue.patch - 950-0754-Revert-net-bcmgenet-Workaround-for-Pi-4B-network-iss.patch - 902-debloat_proc.patch Remove upstreamed: - 150-MIPS-bmips-mark-exception-vectors-as-char-arrays.patch New symbols: X86_INTEL_MPX X86_INTEL_MEMORY_PROTECTION_KEYS X86_INTEL_TSX_MODE_OFF X86_INTEL_TSX_MODE_ON X86_INTEL_TSX_MODE_AUTO Compile-tested on: cns3xxx, x86_64 Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.154Koen Vandeputte2019-11-191-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 902-debloat_proc.patch - 040-dmaengine-qcom-bam-Process-multiple-pending-descript.patch - 807-usb-support-layerscape.patch - 809-flexcan-support-layerscape.patch - 816-pcie-support-layerscape.patch Remove upstreamed: - 150-MIPS-bmips-mark-exception-vectors-as-char-arrays.patch - 303-spi-nor-enable-4B-opcodes-for-mx66l51235l.patch New symbols: X86_INTEL_MPX X86_INTEL_MEMORY_PROTECTION_KEYS X86_INTEL_TSX_MODE_OFF X86_INTEL_TSX_MODE_ON X86_INTEL_TSX_MODE_AUTO SGL_ALLOC Compile-tested on: cns3xxx, x86_64 Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* x86,tegra,mvebu: image: use common reproducible IMG_PART_SIGNATUREPaul Spooren2019-11-111-3/+2
| | | | | | | | | | | | | These targets are currently using more or less same SIGNATURE variable which provides unique partition ID/signature, so it makes sense to refactor it out into common IMG_PART_SIGNATURE variable which could be reused by all targets. This is another step in the direction of reproducible OpenWrt images. Signed-off-by: Paul Spooren <mail@aparcar.org> [split into separate commit, renamed to IMG_PART_SIGNATURE] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: delete empty Makefile introduced by accidentAdrian Schmutzler2019-11-041-0/+0
| | | | | | | | | When changing profile titles for this target, an empty Makefile has been added by accident. Fixes: 14d17306bc73 ("x86: make profile titles more verbose") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* x86: make profile titles more verbosePaul Spooren2019-11-036-12/+12
| | | | | | | | | | | | | | | | So far (nearly) all x86 profiles are called "Generic" which makes it hard to distinguish them in special cases, like searching for a specific profile (without pre-selecting target/subtarget). To make this change locally working, remove the tmp/ folder to force reload of menuconfig. As these files are infrequently touched, the Copyright was updated as well. Signed-off-by: Paul Spooren <mail@aparcar.org> [changed commit title] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: use new procd sysupgrade $UPGRADE_BACKUP variableRafał Miłecki2019-09-051-1/+1
| | | | | | | | | | It's a variable set by procd that should replace hardcoded /tmp/sysupgrade.tgz. This change requires the most recent procd with the commit 0f3c136 ("sysupgrade: set UPGRADE_BACKUP env variable"). Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* treewide: when copying a backup file always specify dest nameRafał Miłecki2019-09-051-1/+1
| | | | | | | $CONF_TAR shouldn't be assumed to always point to the sysupgrade.tgz. This change makes code more generic and allows refactoring $CONF_TAR. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* treewide: don't hardcode "sysupgrade.tgz" file nameRafał Miłecki2019-09-051-2/+2
| | | | | | | | 1) Add BACKUP_FILE and use it when copying an archive to be restored after sysupgrade (on the next preinit). 2) Use CONF_TAR for copying backup prepared by the /sbin/sysupgrade Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: bump 4.19 to 4.19.67Koen Vandeputte2019-08-274-0/+4
| | | | | | | | | | | | Refreshed all patches. Also add a missing symbol for x86 which got used now in this bump. - ISCSI_IBFT Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.139Koen Vandeputte2019-08-274-0/+4
| | | | | | | | | | | | Refreshed all patches. Also add a missing symbol for x86 which got used now in this bump. - ISCSI_IBFT Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* treewide: sysupgrade: pass "save_partitions" option to the "sysupgrade" methodRafał Miłecki2019-08-221-1/+1
| | | | | | | This explicitly lets stage2 know if partitions should be preserved. No more "touch /tmp/sysupgrade.always.overwrite.bootdisk.partmap" hack. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* target/x86/image: use qemu-img from STAGING_DIR_HOSTFlorian Eckert2019-08-171-2/+2
| | | | | | | | | | The host tool package qemu is build for the target x86. The installed tool qemu-img is needed to build vdi or vmdk images. In the image Makefile we use however the host installed qemu-img command and not the tool from the buildsystem. This commit force to use the already build qemu-img command from the openwrt toolchain. Signed-off-by: Florian Eckert <fe@dev.tdt.de>
* x86: add modern network modules to Generic targetAlberto Bursi2019-07-171-1/+2
| | | | | | | | | | | | | | | Many Atom-based embedded/industrial x86 boards can't run 64bit operating systems due to either processor or board firmware limitations, but they have modern interfaces (PCIe) or have modern Intel gigabit controllers onboard. With the current default package selection for x86 Generic target their network won't work. Add the modern gigabit network modules needed or most likely going to be used as add-in cards, similar to what is the list on x86_64 target. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it> [fixed whitespace issue] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: x86: enable NVME support for 64 bit targetLucian Cristian2019-07-092-0/+3
| | | | | | | | Newer motherboards support NVMe U.2 connectors but also NVMe storage can be used on add-on pcie adapters. Enable kernel driver on x86 for now so the NVMe flash storage can be used Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* x86: fix missing led variable warning during bootPetr Štetiar2019-06-251-0/+2
| | | | | | | | Fixes following warning during the boot: WARNING: Variable 'led' does not exist or is not an array/object Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: image: fix small disk space in squashfs overlayPetr Štetiar2019-06-251-12/+1
| | | | | | | | | | | | | Current squashfs snapshot images are improperly padded by just 128k, which doesn't correspond with TARGET_ROOTFS_PARTSIZE=128 default config option, leading to following: Filesystem Size Used Available Use% Mounted on /dev/root 2.5M 2.5M 0 100% /rom /dev/loop0 85.0K 9.0K 71.0K 11% /overlay overlayfs:/overlay 85.0K 9.0K 71.0K 11% / Signed-off-by: Petr Štetiar <ynezz@true.cz>
* rb532,x86: image: use new IMG_COMBINED and IMG_ROOTFS varsPetr Štetiar2019-06-251-12/+12
| | | | | | | In `build: image: Add IMG_ROOTFS and IMG_COMBINED variables` we've added this new variables so switch to them now. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: image: remove TARGET_IMAGES_PAD option and force paddingPetr Štetiar2019-06-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | Currently we're producing unusable x86 combined squashfs images (18.06.1, 18.06.2 and snapshots) as we don't enable TARGET_IMAGES_PAD, thus providing very small space for the overlay filesystem, leading to the following with OpenWrt 18.06.1 r7258-5eb055306f images on x86 QEMU: root@(none):/# mount | egrep 'root|overlay' /dev/root on /rom type squashfs /dev/loop0 on /overlay type ext4 overlayfs:/overlay on / type overlay root@(none):/# df -h | egrep 'root|overlay|Size' Filesystem Size Used Available Use% Mounted on /dev/root 2.5M 2.5M 0 100% /rom /dev/loop0 113.0K 8.0K 97.0K 8% /overlay overlayfs:/overlay 113.0K 8.0K 97.0K 8% / We should rather ensure proper image padding in image generation code and we shouldn't rely on config options in order to generate usable images. So this patch removes TARGET_IMAGES_PAD config option and enforces padding on combined images. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: package Broadcom BNX2X driverPetko Bordjukov2019-06-202-0/+2
| | | | | | | | | | bnx2x driver support for the x86 architecture. Includes module and firmware for Broadcom QLogic 5771x/578xx 10/20-Gigabit ethernet adapters. Signed-off-by: Petko Bordjukov <bordjukov@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [added +kmod-lib-zlib-inflate as well]
* treewide: kernel: bump some targets to 4.19Petr Štetiar2019-06-181-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Lets bump kernel to 4.19 on targets which were run tested or got ACKed so we've enough time to make it ready for next release: armvirt/32 (runtested in qemu) armvirt/64 (runtested in qemu) ath79/generic (runtested on Carambola2) gemini/generic (runtested on DIR-685, DNS-313, SQ201, SL93512R) imx6/generic (runtested on Apalis) ipq40xx/generic (runtested on nbg6617) malta/be64 (runtested in qemu) malta/be (runtested in qemu) malta/le (runtested in qemu) malta/le64 (runtested in qemu) mpc85xx/generic (runtested on TL-WDR4900) mpc85xx/p2020 (runtested on P2020RDB) mvebu/cortexa53 mvebu/cortexa72 mvebu/cortexa10 octeon/generic (runtested on EdgeRouter Lite) sunxi/cortexa53 (build tested only) sunxi/cortexa7 (runtested on Lime2-K) sunxi/cortexa8 (build tested only) tegra/generic x86/64 (runtested in qemu) Acked-by: Zoltan HERPAI <wigyori@uid0.hu> [sunxi] Tested-by: Linus Walleij <linus.walleij@linaro.org> [gemini] Tested-by: Tomasz Maciej Nowak <tomek_n@o2.pl> [mvebu, tegra] Tested-by: Daniel Engberg <daniel.engberg.lists@pyret.net> [octeon] Tested-by: Pawel Dembicki <paweldembicki@gmail.com> [mpc85xx/generic mpc85xx/p2020] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* Revert "base-files: add console to inittab"Alexander Couzens2019-05-251-1/+0
| | | | | | | This reverts commit cde52cb4866fe8cf4a19bb2bb32ff7802e542e19. When using OpenWrt in qemu, the shell is unsuable Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* base-files: add console to inittabPaul Spooren2019-05-211-0/+1
| | | | | | | | | | | When running OpenWrt inside an LXC container no shell is opend as LXC defaults to a virtual /dev/console. This patch allows to enter a shell after starting the container via `lxc-start`, without it is only posible to access a shell on tty1 via `lxc-console`. Signed-off-by: Paul Spooren <mail@aparcar.org>
* kernel: bump 4.19 to 4.19.44Koen Vandeputte2019-05-211-1/+1
| | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 103-MIPS-perf-ath79-Fix-perfcount-IRQ-assignment.patch Compile-tested on: cns3xxx, imx6 Runtime-tested on: cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.120Koen Vandeputte2019-05-211-1/+1
| | | | | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 103-MIPS-perf-ath79-Fix-perfcount-IRQ-assignment.patch - 060-fix-oxnas-rps-dt-match.patch Altered patches: - 0067-generic-Mangle-bootloader-s-kernel-arguments.patch - 006-mvebu-Mangle-bootloader-s-kernel-arguments.patch - 996-generic-Mangle-bootloader-s-kernel-arguments.patch Compile-tested on: ar71xx, cns3xxx, imx6, mvebu, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6, x86_64 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* x86: Activate CONFIG_X86_SMAPHauke Mehrtens2019-05-112-2/+2
| | | | | | | | This activates "Supervisor Mode Access Prevention". modern CPUs will prevent the kernel code from accessing any data from the userspace without the usage of copy_to_user() or copy_from_user() Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Deactivate CONFIG_BINFMT_MISCHauke Mehrtens2019-05-112-2/+0
| | | | | | | | | | CONFIG_BINFMT_MISC allows it to add support for new executable formats to the kernel from user space, the kernel will then detect for example a java binary and call the java execution program automatically. I am not aware that this feature is used in OpenWrt and this could be used to exploit something. Deactivate it for all targets for now. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* build: add a config option for enabling a testing version of the target kernelFelix Fietkau2019-05-111-0/+1
| | | | | | | If the target supports a newer kernel version that is not used by default yet, it can be enabled with this option Signed-off-by: Felix Fietkau <nbd@nbd.name>
* x86: video: disable buildtin amdgpu DRM driverLucian Cristian2019-02-174-4/+5
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* x86: DRM: add x64 subtarget supportLucian Cristian2019-02-172-4/+117
| | | | | | copy settings from generic subtarget Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* x86: video: disable builtin radeon DRM driverLucian Cristian2019-02-172-2/+2
| | | | | | | builtin driver can't access the /lib/firmware while booting, module driver will be able to read and load the firmware files Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* x86: image: add test module to bootloaderTomasz Maciej Nowak2019-02-171-2/+2
| | | | | | | | | | | | It was previously added in 546fced, which was part of "intel-microcode: load as early as possible" series. Unfortunately the conditionals added to GRUB config caused error on boot, because on sysupgrade, bootloader is not updated and is left with old features/modules. Since this module is needed for early microcode load and transition to this needs to be done step by step, enable the test module now, so that every newly created image has it already embedded. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* build: remove leftovers from previous x86 commitsTomasz Maciej Nowak2019-02-172-9/+1
| | | | | | | | | | | | | | | | | VBoxManage is not used and the image is created with proper permisions: 0f5d0f6 image: use internal qemu-img for vmdk and vdi images drop host dependencies on qemu-utils and VirtualBox Unreachable config symbols: 9e0759e x86: merge all geode based subtargets into one No need to define those symbols since x86_64 is subtarget of x86: 196fb76 x86: make x86_64 a subtarget instead of a standalone target Unreachable config symbols, so remove GRUB_ROOT: 371b382 x86: remove the xen_domu subtarget Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* x86: Add support for kernel 4.19Hauke Mehrtens2019-01-129-0/+1847
| | | | | | | | | | | | This adds initial support for kernel 4.19 to the x86 target. The patches and the kernel configurations were copied from kernel 4.14 and then refreshed. The legacy and the genode target will not support PAE any more because they use a CPU type which does not support PAE, the generic sub target still supports PAE. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: Refresh kernel 4.14 configurationHauke Mehrtens2019-01-125-26/+11
| | | | | | | | | | | | This refreshes the kernel configuration for kernel 4.14. First this was run for the legacy target: make kernel_oldconfig Then for all targets including the legacy target this was run: make kernel_oldconfig CONFIG_TARGET=subtarget The option CONFIG_104_QUAD_8 was added to the generic configuration because it would have been automatically removed. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: Use kernel specific subtarget configurationsHauke Mehrtens2019-01-124-0/+0
| | | | | | | | | | This makes it possible to use different sub target configurations for kernel 4.19 for example. To support kernel 4.9 and kernel 4.14 with the same configuration file already needed some extra work this will not be needed for kernel 4.19 any more. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: enable kmod-bnx2 on 64-bit by defaultAlberto Bursi2019-01-021-1/+1
| | | | | | | Gigabit ethernet adapters using BCM5706/5708/5709/5716 chipset are common on servers and as easy/cheap to get as Intel based ones. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* x86: make sysupgrade.tgz reachable againTomasz Maciej Nowak2018-12-031-1/+1
| | | | | | | | | Moving binding mount before check for saved sysupgrade configuration made it unreachable. Fix it by moving binding mount after the check. Fixes: f78b2616 (x86: mount writable bootfs) Reported-by: Lucian Cristian <luci@powerneth.ro> Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-30 03:13:14 +0000