07:32 DottorLeo: Hi!
07:37 DottorLeo: i've tested vulkaninfo with the local build of mesa devel and it works but launching steam give me this error:
07:37 DottorLeo: Running query: 1 - GpuTopology
07:37 DottorLeo: CVulkanTopology: failed create vulkan instance: -9
07:37 DottorLeo: CVulkanTopology: failed to create vulkan instanceFailed to query vulkan gpu topology
07:37 DottorLeo: Failed to query vulkan gpu topology
07:59 HdkR: DottorLeo: Did you build 32-bit mesa as well?
08:05 HdkR: Also, if you haven't installed the libraries globally I have no idea if that would work, since Steam runs inside of a container these days.
08:59 kode54: if you're on anything resembling Arch, I recommend mesa-tkg
08:59 kode54: it makes it really easy to build a system global mesa from any repo and any commit or branch or tag
09:27 DottorLeo: HdkR: i just cloned mesa and changed meson to enable rusticl compiling, nothing else so probably i haven't compiled the 32bit version, need to enable something on the meson file?
09:31 HdkR: DottorLeo: If you just did a basic meson compile then it'll be x86-64, you need a cross-compiling setup to build the 32-bit x86 binaries.
09:35 DottorLeo: sudo setarch i686 dnf builddep mesa on fedora 42 gives error 404 :/
09:38 DottorLeo: but if i understand "sudo dnf builddep mesa" should provide everything, just need to change some flags on the compiling file?
09:46 HdkR: Not sure if that provides i686 dependencies
09:46 HdkR: But you also need a cross-compile file to pass mesa.
09:46 HdkR: er, to pass meson
09:47 HdkR: I don't have the time to walk someone through the process but there should be information somewhere about it.
09:47 DottorLeo: https://docs.mesa3d.org/meson.html#cross-compilation-and-32-bit-builds
09:48 DottorLeo: the only thing i don't understand is the example part "32-bit build on x86 linux:" is that i need to use?
09:48 HdkR: Looks like it
09:48 HdkR: They're misusing "x86" to mean "x86-64" in that section name.
09:54 DottorLeo: ok i'm using "
09:54 DottorLeo: [binaries]
09:54 DottorLeo: c = '/usr/bin/gcc'
09:54 DottorLeo: cpp = '/usr/bin/g++'
09:54 DottorLeo: # ccache is not automatically used when specifying [binaries].
09:54 DottorLeo: # To accelerate cross-compilation as much as native compilation:
09:54 DottorLeo: # c = ['ccache', 'gcc']
09:54 DottorLeo: # cpp = ['ccache', 'g++']
09:54 DottorLeo: ar = '/usr/bin/gcc-ar'
09:54 DottorLeo: strip = '/usr/bin/strip'
09:54 DottorLeo: llvm-config = '/usr/bin/llvm-config32'
09:54 DottorLeo: pkg-config = '/usr/bin/pkg-config-32'
09:55 DottorLeo: # As of version 40, Fedora uses a full target platform prefix for
09:55 DottorLeo: # pkg-config instead, like the ARM and Windows examples below:
09:55 DottorLeo: # pkg-config = 'i686-redhat-linux-gnu-pkg-config'
09:55 DottorLeo: [built-in options]
09:55 DottorLeo: c_args = ['-m32']
09:55 DottorLeo: c_link_args = ['-m32']
09:55 DottorLeo: cpp_args = ['-m32']
09:55 DottorLeo: cpp_link_args = ['-m32']
09:55 DottorLeo: [host_machine]
09:55 DottorLeo: system = 'linux'
09:55 DottorLeo: cpu_family = 'x86'
09:55 DottorLeo: cpu = 'i686'
09:55 DottorLeo: endian = 'little'
09:55 DottorLeo: whops
09:55 DottorLeo: sorry,
09:56 DottorLeo: i'm using a meson32.build file together with the command line "meson setup builddir/ --cross-file meson32.build", it kinda works but stops saying "meson.build:768:2: ERROR: 'rust' compiler binary not defined in cross file [binaries] section". I suppose i need to add it to the meson32.build file?
10:06 kode54: amazing, you didn't get spamkicked
10:06 kode54: kent got spamkicked from the server from his own channel for pasting 3 lines with unicode block characters
10:07 DottorLeo: kode54: yeah, next time i'll triple check before pasting ^^"
10:09 kode54: he still hasn't heard from oftc staff, either
10:09 kode54: had to come back by direct connection instead of his bouncer
10:09 kode54: surprised channel ops aren't exempt from the spam kicker
13:58 pixelcluster: kode54: it isn't just improvements for gfx12, some of the stuff also affects (and improves) gfx11
15:37 fililip: agd5f: would it be viable to write a VCN ring reset handler using the stop() and start() functions that each VCN version has in their corresponding files (ie vcn_v2_0_stop and vcn_v2_0_start) for each vcn enc/dec instance, or would multi-instance not work? Mario wrote a patch that correctly resets the VCN after a timeout on VCN 4.0.5 but that only has one unified/enc instance
15:39 agd5f: fililip, yes. The start and stop functions are per IP instance already
15:42 fililip: is there a reliable way to "force" a VCN timeout or would I need to find some kind of corrupted stream and older firmware first? I could try doing something like that for VCN 3.0
15:44 agd5f: Ideally we'd have an IGT test like we have for other IPs
15:44 agd5f: also need to deal with the scheduler and saving the ring contents
18:58 DottorLeo: @karolherbst i'm the user from the Bugreport about Rusticl on GFX6. That command NIR_DEBUG=print i have to put it before "meson devenv -C builddir clpeak", right?
18:59 karolherbst: uhh... I think that should work
18:59 DottorLeo: let me try ;D
19:06 DottorLeo: karolherbst: yeah it works, almost 1MB of text file :D
19:06 DottorLeo: compressing and uploading to the bugreport
19:11 DottorLeo: Ok done
19:18 DottorLeo: Night guys!
20:45 kode54: pixelcluster: which branch though? there are several that appear to do different things