00:01krushia: can someone please remind me what the difference is between lower and upper case filenames in linux-firmware? for example, OLAND_ce.bin vs oland_ce.bin
00:06krushia: I'm just trying to figure out which ones needs to be built into a kernel with no initrdhttps://web.git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/radeon
00:06krushia: oops https://web.git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/radeon
00:18dwfreed: from a look at the code, it looks like different firmware formats; lowercase is the newer one
00:18dwfreed: you cannot mix and match lowercase and uppercase, but you only need one or the other; lowercase is tried first, of course
00:28krushia: thanks, i just saw that it tries new_chip_name (lowercase) and then chip_name (uppercase) but its not clear why. i'll try just the lowercase.
09:21MrCooper: krushia: the amdgpu driver supports only the lower-case variants, the upper-case variants are supported only by the radeon driver (presumably they're older)
09:22MrCooper: the radeon driver can't stop supporting the upper-case variants though, or it would break on systems which don't have the lower-case variants
13:30mupuf: MrCooper: so that means I can drop uppercase firmware for recent kernels then?
13:48MrCooper: AFAICT yes
13:55MrCooper: hmm, I'm hitting the issue where VRR remains active even though the VRR_ENABLED property value is 0, with an HDMI connection
15:22krushia: found out for oland i still need the uppercase TAHITI_uvd.bin, so its not as simple as it looks. there's a nice reference table at https://wiki.gentoo.org/wiki/Radeon#Built-in_kernel
18:40Venemo: mupuf: why do you even have any firmware for the radeon driver? don't you use amdgpu?
18:48mupuf: Venemo: The b2c kernel now includes radeon.ko, and its associated firmware. This was added for ondracka's r300 CI.
19:31Venemo: mupuf: ah, I see.