Config.in

menu "MiSTer external options"

menu "MiSTer profiles (ADR 0030 -- one symbol selects a documented package set)"
	# THE ONE DEPARTURE FROM A PLAIN BUILDROOT DEFCONFIG. In a plain project
	# every package is a line in configs/<board>_defconfig. Here the shared
	# sets are Kconfig profiles that `select` their members, so two boards
	# share a userspace by selecting one symbol and cannot drift apart on
	# it. "Why is package X in my image?" -> the profile's Config.in, whose
	# section headers mirror docs/buildroot-config.md §5.
	source "$BR2_EXTERNAL_MISTER_PATH/package/mister-firmware/Config.in"
	source "$BR2_EXTERNAL_MISTER_PATH/package/mister-drivers/Config.in"
	source "$BR2_EXTERNAL_MISTER_PATH/package/mister-userspace/Config.in"
endmenu

menu "USB WiFi drivers (out-of-tree)"
	# MAINLINE-FIRST policy (ADR 0016). The rule is "use the in-kernel driver
	# for every chip the kernel can drive; keep an out-of-tree driver ONLY
	# where mainline still has no USB driver for the chip at all". Exactly two
	# chips meet that bar today, and both are ENABLED in the defconfig:
	#
	#   rtl8852cu-morrownr -- RTL8852CU/RTL8832CU (Wi-Fi 6E). rtw89 has the
	#   8852C chip HAL but only a PCIe bus file (rtw8852ce.c; there is no
	#   rtw8852cu.c), and RTW89_8852CE "depends on PCI" which this board has
	#   not got.
	#
	#   aic8800 -- AICSemi AIC8800 family (Wi-Fi 6 + BT). Mainline has no
	#   aic8800 driver over ANY bus, in any tree checked (6.18, 7.2, 7.3-rc):
	#   no chip HAL, no staging entry, no MAINTAINERS line. Ships its own
	#   firmware, which the driver is inert without.
	#
	# THE DESELECTED REALTEK FORKS WERE REMOVED on 2026-09-10. Seven packages
	# -- rtl8188eu-aircrack-ng, rtl8188fu, rtl8812au, rtl8814au-morrownr,
	# rtl8821au-morrownr, rtl8821cu-morrownr and rtl88x2bu -- sat here sourced
	# but permanently `is not set`, because mainline had caught up on every one
	# of their chips (8188eu/8188fu/8710bu -> rtl8xxxu; 8821cu ->
	# rtw88_8821cu; 8822bu -> rtw88_8822bu; 8812au -> rtw88_8812au;
	# 8811au/8821au -> rtw88_8821au; 8814au -> rtw88_8814au, all enabled in
	# board/mister/de10nano/linux.config). They were kept as a "one-line
	# revert" fallback; in practice the fallback was never used and each one
	# cost a Renovate PR stream, a hash-sync entry and a CI path filter for a
	# package the image does not build. Owner decision, 2026-09-10: delete
	# them. `git log -- package/rtl8812au` restores any of them in full if a
	# mainline driver ever does disappoint on specific hardware -- that is the
	# fallback now, and it costs nothing to keep.
	#
	# NAMING: rtl8852cu-morrownr takes its suffix for a uniform morrownr
	# naming scheme; upstream Buildroot has no rtl8852cu package to collide
	# with (re-checked against the pinned tree 2026-07-27). aic8800 needs no
	# suffix -- upstream Buildroot has no aic8800 package either. Checked
	# against the ACTUAL pinned tree on 2026-09-10: Buildroot 2026.08
	# (Makefile's BUILDROOT_VERSION, and work/buildroot's own BR2_VERSION),
	# whose only package/ai* entries are `aichat` (BR2_PACKAGE_AICHAT) and
	# `aircrack-ng`. No BR2_PACKAGE_AIC8800 symbol and no AIC8800_ Make
	# namespace to collide with.
	#
	# Note the 2026.05.1 dates further up this file are NOT stale in the same
	# way: each records a check made while 2026.05.x really was the pin. This
	# one is dated after the 2026.08 bump, so it has to name 2026.08.
	source "$BR2_EXTERNAL_MISTER_PATH/package/rtl8852cu-morrownr/Config.in"
	source "$BR2_EXTERNAL_MISTER_PATH/package/aic8800/Config.in"
endmenu

menu "USB controller drivers (out-of-tree, P3.2)"
	# xow-firmware has its own "depends on BR2_PACKAGE_XONE", so it must be
	# sourced after xone or menuconfig shows it (correctly) greyed out with
	# no visible reason until xone is toggled on first -- order matters here
	# only for menu readability, not for correctness.
	source "$BR2_EXTERNAL_MISTER_PATH/package/xone/Config.in"
	source "$BR2_EXTERNAL_MISTER_PATH/package/xow-firmware/Config.in"
endmenu

menu "Input-device userspace tooling"
	# Deliberately NOT folded into the "USB controller drivers" menu above:
	# everything there is an out-of-tree KERNEL MODULE, and these are plain
	# userspace CLIs. Upstream Buildroot has neither package (checked against
	# the pinned 2026.05.1 tree).
	#
	# This menu is for tools that reach input-device functionality the
	# in-kernel drivers expose no interface for. It is NOT the place for
	# anything that substitutes for a carried kernel patch -- the DualSense
	# patches (0033/0037/0042) back Main_MiSTer's sysfs-LED and input-event
	# ABIs, which no userspace process can serve. See
	# docs/dualsense-tooling.md.
	#
	# Titled "Input-device", not "Controller": ltunify is about keyboards and
	# mice on a Logitech receiver, and squeezing it under a gamepad-shaped
	# heading would have been the wrong shape for the next tool too. Both
	# entries satisfy the same one-line contract above; only the class of
	# peripheral differs.
	source "$BR2_EXTERNAL_MISTER_PATH/package/dualsensectl/Config.in"
	# ltunify: pairing for Logitech Unifying/Nano receivers. hid-logitech-dj
	# drives every ALREADY-paired device perfectly and has no interface for
	# the pairing handshake itself -- there is no sysfs knob and no ioctl, so
	# this is a genuine gap and not a duplicate of anything in the kernel.
	# See docs/logitech-pairing.md.
	source "$BR2_EXTERNAL_MISTER_PATH/package/ltunify/Config.in"
endmenu

menu "Firmware infra gap-fill (P3.3, P3.14)"
	# Fills the handful of stock firmware.md entries that Buildroot's own
	# linux-firmware package Config.in has no sub-option for, even though
	# upstream linux-firmware ships them. See docs/firmware-parity.md.
	source "$BR2_EXTERNAL_MISTER_PATH/package/linux-firmware-extra/Config.in"
	# P3.14: Broadcom BCM20702 BT dongle firmware -- not in mainline
	# linux-firmware; hash-pinned vendor firmware, same posture as xow
	# (ADR 0003). See docs/firmware-parity.md.
	source "$BR2_EXTERNAL_MISTER_PATH/package/bcm20702-firmware/Config.in"
endmenu

menu "MIDI / MT-32 (P3.8)"
	# munt (mt32d) + MidiLink reproduce stock's MIDI/MT-32 softsynth stack;
	# neither exists in upstream Buildroot. munt sourced first only for menu
	# readability (midilink's help references it); both toggle independently.
	# See docs/midi-mt32-parity.md.
	source "$BR2_EXTERNAL_MISTER_PATH/package/munt/Config.in"
	source "$BR2_EXTERNAL_MISTER_PATH/package/midilink/Config.in"
endmenu

menu "Main_MiSTer shared libraries"
	# These back the Main_MiSTer shared-lib refactor (no task ID exists for
	# this work -- it is referenced by name): Main_MiSTer stops vendoring
	# lib/{lzma,zstd,miniz,libchdr} in its own tree and links Buildroot-
	# provided shared libraries instead. Only half the refactor lives here:
	# the upstream halves (zstd, minizip-ng) are plain Buildroot packages
	# enabled straight from the defconfig; the two packages upstream Buildroot
	# does not carry are the ones sourced in this menu. See
	# docs/main-shared-libs.md for the full provider/SONAME map.
	#
	# lzma-sdk is sourced first because libchdr's Config.in selects
	# BR2_PACKAGE_LZMA_SDK -- depended-on before dependent, the same
	# menu-readability note as xone/xow-firmware above; both packages remain
	# independently selectable.
	source "$BR2_EXTERNAL_MISTER_PATH/package/lzma-sdk/Config.in"
	source "$BR2_EXTERNAL_MISTER_PATH/package/libchdr/Config.in"
	# rcheevos (RetroAchievements client library) is the ODD ONE OUT in this
	# menu and is sourced last to keep that visible. lzma-sdk and libchdr are
	# here to REPLACE code Main_MiSTer already vendors -- that is what "the
	# Main_MiSTer shared-lib refactor" means. rcheevos replaces nothing:
	# neither Main nor this tree references it yet. It is in this menu anyway
	# because the menu's actual contract is "shared libraries this tree
	# authors for Main_MiSTer to link, which upstream Buildroot does not
	# carry", and a second menu holding one library would say less. It has no
	# dependency on either sibling and toggles independently.
	source "$BR2_EXTERNAL_MISTER_PATH/package/rcheevos/Config.in"
endmenu

menu "Archival / on-device update tooling"
	# 7zip is upstream 7-Zip (`7zz`), sourced here rather than taken from
	# upstream Buildroot because upstream Buildroot has NO 7zip package --
	# only package/p7zip, the dead-since-2016 Unix port (re-confirmed absent
	# on the pinned 2026.05.1 tree, 2026-07-27). It REPLACES the p7zip
	# selection this image used to carry.
	#
	# It is in its own menu, not in "Main_MiSTer shared libraries" above,
	# because it is neither a library nor Main_MiSTer's: its reason for
	# existing is the UPDATE PATH. The static copy it drops in
	# $(BINARIES_DIR)/7za ships on the exFAT data partition as
	# /media/fat/linux/7za, displacing the p7zip 16.02 binary the Downloader
	# otherwise fetches off the internet on first use. ADR 0023.
	#
	# NOTE the package dir/symbol start with a digit -- BR2_PACKAGE_7ZIP and
	# the 7ZIP_ Make namespace. That is fine and has upstream precedent
	# (package/4th -> BR2_PACKAGE_4TH, package/18xx-ti-utils ->
	# 18XX_TI_UTILS_VERSION); pkg-generic's UPPERCASE derivation and GNU
	# Make's variable naming both accept a leading digit. No collision with
	# upstream's P7ZIP_ namespace either way.
	source "$BR2_EXTERNAL_MISTER_PATH/package/7zip/Config.in"
endmenu

menu "Off-device backup"
	# azcopy is Microsoft's Azure Storage CLI. Upstream Buildroot has no
	# azcopy package (re-confirmed absent on the pinned 2026.05.1 tree,
	# 2026-08-17 -- the only "az*" package there is azure-iot-sdk-c), so
	# this tree authors one.
	#
	# Its own menu rather than a line in "Archival / on-device update
	# tooling" above: that menu is about the UPDATE PATH -- 7zip exists to
	# put a working `7za` at /media/fat/linux/7za so the Downloader never
	# fetches a 2016 binary off the internet. azcopy is the opposite
	# direction of travel, pushing the data partition OFF the board, and
	# shares neither that menu's rationale nor its constraints.
	#
	# THE ONE THING TO KNOW BEFORE ENABLING IT: ~39 MiB installed, which
	# makes it the second-largest package in this image (samba4, ~49 MiB,
	# is first). docs/azcopy.md carries the measurement and the effect on
	# the 15% free-space budget; docs/size-budget.md carries the budget.
	#
	# It is also the image's first and only Go package, so selecting it
	# pulls host-go into the build. See package/azcopy/azcopy.mk for what
	# that costs and why host-go is left at its from-source default.
	source "$BR2_EXTERNAL_MISTER_PATH/package/azcopy/Config.in"
endmenu

menu "Kernel variants (ADR 0021)"
	# A second kernel built beside the main one in this same tree (ADR 0030
	# Phase C): PREEMPT_RT on the 7.2.y line -> images/zImage_dtb-rt, with
	# its module tree in the ONE rootfs. Same shape as Buildroot's own
	# barebox-aux. Requires the stage-1 extension below (it embeds the same
	# cpio).
	source "$BR2_EXTERNAL_MISTER_PATH/package/linux-rt/Config.in"
endmenu

menu "Stage-1 initramfs (ADR 0002)"
	# The cpio the kernel embeds, built as a package of this configuration
	# (ADR 0030): a static BusyBox and a static fsck.exfat from the main
	# toolchain, plus board/mister/common/initramfs-overlay/init. The
	# kernel side -- CONFIG_INITRAMFS_SOURCE pointing at the cpio -- is the
	# linux extension BR2_LINUX_KERNEL_EXT_MISTER_INITRAMFS (Kernel ->
	# Linux Kernel Extensions), which selects the package. The two
	# sub-packages have no prompt of their own.
	source "$BR2_EXTERNAL_MISTER_PATH/package/mister-initramfs/Config.in"
	source "$BR2_EXTERNAL_MISTER_PATH/package/mister-initramfs-busybox/Config.in"
	source "$BR2_EXTERNAL_MISTER_PATH/package/mister-initramfs-exfatprogs/Config.in"
endmenu

endmenu