commit 49495cc234309f997be1d1f4767f8fa993a56301
Author: lucascouts <lucascs@protonmail.com>
Date: Sat Aug 22 23:57:21 2026 -0300

mod(net-wireless/mt7927-dkms/metadata.xml), rm(sys-firmware/edk2/files/{edk2-202408-binutils-2.41-textrels, edk2-202411-gcc15, edk2-202411-loong, edk2-202411-werror, edk2-202502-nasm-3, edk2-202511-werror}.patch), up(net-wireless/mt7927-dkms-2.14 -> 2.14-r1)

mt7927-dkms-2.14-r1 fixes a defect introduced in 2.14: the MT6639 Bluetooth
firmware was gated behind USE=btmtk, which is off by default.

Nothing else on the system carries that blob -- linux-firmware only accepts
vendor blobs from the copyright holder, so MR !946 was closed, and qfile
confirms this package is its only owner here. But the firmware is not needed
only by the modules this package rebuilds: the kernel's OWN btmtk, the in-tree
one that runs precisely when the flag is off, asks for the same
mediatek/mt7927/BT_RAM_CODE_MT6639_2_<n>_hdr.bin. So the default configuration
shipped a machine whose native Bluetooth stack had no firmware to load.

The blob is now fetched and installed unconditionally, and the flag gates only
the out-of-tree btusb/btmtk rebuild. LICENSE and RESTRICT=mirror go back to
being unconditional, since the proprietary file is always part of the package.

Verified by staging both configurations: USE=-btmtk now yields 7 modules, 7
depmod overrides and the firmware; USE=btmtk yields 9, 9 and the same firmware.
The bug was only visible once the package was actually installed -- inspecting
the -btmtk image alone showed a missing file, not a broken Bluetooth stack.

Also drops six patches under sys-firmware/edk2/files/ that no ebuild in the
overlay references any more, left behind by earlier bumps because the applier
renames the ebuild but never the patches. The two the 202608 ebuild does use
are untouched; git history keeps the rest.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

commit ba5ee02456f40d842a879e85fe73324ea72db044
Author: lucascouts <lucascs@protonmail.com>
Date: Sat Aug 22 21:56:52 2026 -0300

add(app-portage/bentoolkit/bentoolkit-0.27.0.ebuild, net-wireless/mt7927-dkms/mt7927-dkms-2.14.ebuild, metadata/md5-cache/{app-portage/bentoolkit-0.27.0, net-wireless/mt7927-dkms-2.14}), rm(sys-firmware/edk2/{edk2-202605.ebuild, files/edk2-202605-werror.patch}), mod(net-wireless/mt7927-dkms/metadata.xml, .autoupdate/packages.toml), up(app-portage/bentoolkit-0.26.0 -> 0.27.0, net-wireless/mt7927-dkms-2.13 -> 2.14)

app-portage/bentoolkit 0.27.0: no dependency or USE change -- the release adds
the --depth=install rung and an unwired terminal design system. Two inherited QA
findings fixed in passing: IUSE now precedes RESTRICT, and the ldflags line no
longer runs past 120 columns.

net-wireless/mt7927-dkms 2.14 is a rebase, not a version bump. Upstream moved
MT76_KVER from 7.1.3 to 7.2, where Sean Wang's MT7927 series landed in mainline,
which is why the numbered WiFi patch set collapsed from 32 to the 4 AP-mode
additions still out of tree. Three consequences:

- The mini source tarball for the new base did not exist. Repacked from the
official linux-7.2.tar.xz (sha256 verified against sha256sums.asc) with the
same deterministic recipe as 7.1.3, and published to R2. Verified end to
end: portage fetched it from distfiles.obentoo.org and the Manifest
checksum matched, byte for byte identical to what was uploaded. The recipe
now lives in the .autoupdate record, because a base move makes every fetch
404 until someone repacks.

- The WiFi firmware is no longer installed, following upstream 2.14-4. The
collision is real and was measured here with qfile: sys-kernel/linux-firmware
owns .../mt7927/WIFI_RAM_CODE_MT6639_2_1.bin.zst (MR !1055) while this
package owned the uncompressed name, which the kernel loader tries first --
so a June 2025 blob out of a Windows driver ZIP shadowed the April 2026
vendor build. pkg_postinst now warns when neither form is present, since
dropping ours on a host with an older linux-firmware would take out the
connection needed to fix it.

- The Bluetooth side is now USE=btmtk, default off, mirroring the gate
upstream added in 2.14-6: from kernel 7.1 the MT6639 is native, so the
rebuild adds only the HP EliteMini ID 0489:e156 while replacing the in-tree
Bluetooth stack for every device on the machine. The flag is deliberately
NOT named "bluetooth" -- that is a global Gentoo USE flag enabled by most
desktop profiles, and emerge -pv confirmed it would have turned this opt-in
into an opt-out. It also gates the firmware SRC_URI, the proprietary half of
LICENSE and RESTRICT=mirror, so USE=-btmtk fetches nothing proprietary.

Validated by running the real phases (no sudo on this host: PORTAGE_TMPDIR of
our own, USE=-modules-sign, PORTAGE_INST_UID/GID overridden). bentoolkit built
and installed, and the binary reports 0.27.0. mt7927-dkms went through a full
clean install on both paths against the running 7.1.9 kernel, which exercises
the pre-7.2 EML compat shim: with btmtk, 9 modules plus BT_RAM_CODE and 9 depmod
overrides; without, 7 modules, 7 overrides and no firmware at all. The 0489:e156
ID is present in both binaries -- modinfo does not show it because the patch
puts it in quirks_table, which generates no MODULE_DEVICE_TABLE entry.

sys-firmware/edk2 202605 removed: 202608 landed in e0d40c2fc and the registry
already pinned it, leaving the old ebuild, its werror patch, its cache entry and
two now-orphaned DIST lines (11 -> 9) behind.

Not verified: edk2-202608 itself still has not been compiled or merged anywhere,
and no MT7927 module was loaded on real hardware -- both builds were staged into
an image and inspected, never installed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

commit 5a252f4c434534158751fa472b83b787d0609a0f
Author: lucascouts <lucascs@protonmail.com>
Date: Fri Aug 21 14:21:09 2026 -0300

fix(net-wireless/mt7927-dkms-2.13): track the upstream packaging revision, mod(.autoupdate/packages.toml)

MY_PV was hardcoded to "$-1", but upstream re-tags one version many times
(v2.14-1 through v2.14-6) and the CONTENT differs between those tags: Makefile,
the mt76/mt7925 Kbuilds and the shipped tree all change, and -6 carries a
linux-stable/ directory that -1 does not have. A bump to 2.14 would therefore
have fetched the OLDEST revision of the series -- and it downloads fine, so
nothing downstream would have caught it.

The revision now lives in its own MY_BUILD variable, kept in sync by the
autoupdate record via aux_var/aux_pattern. Same pattern, and same class of
problem, as net-misc/nxplayer's build number.

Recorded in the record's doc comment: a new -N with an UNCHANGED version stays
invisible to the checker, which compares PV, so v2.14-1 -> v2.14-6 needs a
hand-made -rN revbump.

No revbump here: MY_PV still resolves to 2.13-1, so the refactor changes nothing
that ships. Verified with ebuild fetch (exit 0, 3 distfiles), pkgcheck (clean,
after pkgcheck cache --update --force), tomllib (451 records intact) and the
aux_pattern probed against the live API body (path reads v2.14-6, aux reads 6).

Also drops two stale "Live [0]=..." lines from the mt7927-dkms and
frei0r-plugins doc comments, which still quoted long-superseded versions.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

commit 8354355157b5a3dcea998e267fcc07ac759fc8da
Author: lucascouts <lucascs@protonmail.com>
Date: Fri Jul 24 18:52:07 2026 -0300

fix(net-wireless/mt7927-dkms-2.13): corrige DIST do mt7927-kernel-src-7.1.3

O distfile mt7927-kernel-src-7.1.3.tar.xz nunca foi publicado no R2 (404); só
existia o mini-source 7.0. Reconstruído deterministicamente a partir do kernel
7.1.3 real (linux-7.1 + patch-7.1.3), extraindo os subtrees drivers/net/wireless/
mediatek/mt76 e drivers/bluetooth (paths preservados como linux-7.1.3/...).
Manifest atualizado para o novo tarball (590964 bytes).

Pendente: upload de mt7927-kernel-src-7.1.3.tar.xz ao bucket R2.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

commit 523cc190aab63d966c2582ba8d991595f155a028
Author: lucascouts <lucascs@protonmail.com>
Date: Sat Jul 18 15:05:01 2026 -0300

mod(net-wireless/mt7927-dkms-2.13), mod(metadata/md5-cache/net-wireless/mt7927-dkms-2.13)

commit 1f56cab4eaa46e17e1bf4b2c6d2fccbf9c0dd0bb
Author: lucascouts <lucascs@protonmail.com>
Date: Fri Jul 17 22:12:48 2026 -0300

add(metadata/{md5-cache/dev-libs/wayland-1.26.0, md5-cache/dev-util/wayland-scanner-1.26.0, md5-cache/net-wireless/mt7927-dkms-2.13}), mod(.autoupdate/packages.toml), up(dev-libs/wayland-1.25.91 -> 1.26.0, dev-util/wayland-scanner-1.25.91 -> 1.26.0, net-wireless/mt7927-dkms-2.11-r3 -> 2.13)

commit 19d3ec9cd5ad19e36c3a4ea7d37e56217bc2ee3e
Author: lucascouts <lucascs@protonmail.com>
Date: Sat Jun 27 14:29:23 2026 -0300

add(metadata/md5-cache/net-wireless/mt7927-dkms-2.11-r3), del(metadata/md5-cache/net-wireless/mt7927-dkms-2.11-r2), up(net-wireless/mt7927-dkms-2.11-r2 -> 2.11-r3)

commit 5c4632c75ec36d3fe3c3ccf5bca1e1e1018a3cb0
Author: lucascouts <lucascs@protonmail.com>
Date: Thu Jun 25 13:25:54 2026 -0300

add(metadata/{md5-cache/media-libs/vulkan-loader-1.4.354_p20260625, md5-cache/net-misc/postman-bin-12.16.3, md5-cache/net-wireless/mt7927-dkms-2.11-r2}), up(media-libs/vulkan-loader-1.4.354_p20260624 -> 1.4.354_p20260625, net-misc/postman-bin-12.16.2 -> 12.16.3, net-wireless/mt7927-dkms-2.11-r1 -> 2.11-r2)

commit 0cc6f4b35085c0d745e1f9a2f924df2bffdc9f05
Author: lucascouts <lucascs@protonmail.com>
Date: Sun Jun 14 00:12:13 2026 -0300

mod(net-wireless/mt7927-dkms): keep WiFi-only -r1, drop -r2 + stale md5-cache

-r2 bundled the patched btusb/btmtk for MT6639 BT, which does not initialise
on this board's 13d3:3588 (hci0: Failed to get device id -108). Keep the
WiFi-only -r1 build; BT stays on a USB dongle until mainline support lands.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

commit 7fba05ac00e561951e529430b7c80852470a21e5
Author: lucascouts <lucascs@protonmail.com>
Date: Sat Jun 13 23:35:55 2026 -0300

add(metadata/md5-cache/net-wireless/mt7927-dkms-2.11-r2), up(net-wireless/mt7927-dkms-2.11-r1 -> 2.11-r2)

commit 7337f60099c51ede1cbdc34f92a24ddef6f50aee
Author: lucascouts <lucascs@protonmail.com>
Date: Sat Jun 13 22:11:29 2026 -0300

add(metadata/md5-cache/net-wireless/mt7927-dkms-2.11-r1), up(net-wireless/mt7927-dkms-2.11 -> 2.11-r1)

commit a94ac1206a4687cdacda10f35bd08a076be82c88
Author: lucascouts <lucascs@protonmail.com>
Date: Sat Jun 13 21:34:35 2026 -0300

mod(net-wireless/mt7927-dkms-2.11), mod(metadata/md5-cache/net-wireless/mt7927-dkms-2.11)

commit ffc62d9fa099a38c1943002bbf57e4811d0053f8
Author: lucascouts <lucascs@protonmail.com>
Date: Sat Jun 13 20:30:01 2026 -0300

add(net-wireless/mt7927-dkms-2.11), add(metadata/{md5-cache/app-editors/cursor-3.7.36, md5-cache/app-editors/vim-9.2.0640, md5-cache/app-editors/vim-core-9.2.0640, md5-cache/dev-util/mesa_clc-26.2.0_pre20260613, md5-cache/mail-client/betterbird-bin-140.12.0, md5-cache/media-libs/mesa-26.2.0_pre20260613, md5-cache/media-libs/vulkan-layers-1.4.352_p20260613, md5-cache/net-wireless/mt7927-dkms-2.11}), del(metadata/md5-cache/mail-client/betterbird-bin-140.11.0), mod(.autoupdate/packages.toml), up(app-editors/{cursor-3.7.27 -> 3.7.36, vim-9.2.0623 -> 9.2.0640, vim-core-9.2.0623 -> 9.2.0640}, dev-util/mesa_clc-26.2.0_pre20260612 -> 26.2.0_pre20260613, mail-client/betterbird-bin-140.11.0 -> 140.12.0, media-libs/{mesa-26.2.0_pre20260612 -> 26.2.0_pre20260613, vulkan-layers-1.4.352_p20260612 -> 1.4.352_p20260613})