11:28 AndrewR: karolherbst, congratulations for finally landing your OpenCL work!
11:47 karolherbst: thanks
12:56 AndrewR: karolherbst, "../src/gallium/state_trackers/clover/nir/invocation.cpp:73:4: sorry, unimplemented: non-trivial designated initializers not supported" - with gcc 5.5.0 ....
12:57 karolherbst: uff.. do we even support gcc-5.5 in mesa still?
12:58 karolherbst: mhh, 4.4.6
13:00 karolherbst: AndrewR: mhh, which distribution is still using gcc-5.5 btw?
13:00 AndrewR: karolherbst, I picked up gcc from Slackware 14.2
13:00 karolherbst: AndrewR: I think I will have a more or less trivial patch for it.. just checking if it doesn't break
13:28 karolherbst: AndrewR: mind checking if this fixes it? https://github.com/karolherbst/mesa/commit/7216ee98517ac3ace1321a4008b616ec0b64d0c8
13:40 AndrewR: karolherbst, nope :/ (i just saved whole file into mesa tree) : "../src/gallium/state_trackers/clover/nir/invocation.cpp:65:23: sorry, unimplemented: non-trivial designated initializers not supported
13:40 AndrewR: spirv_options.caps = {
13:40 AndrewR: "
13:40 karolherbst: ufff
13:40 karolherbst: I hate gcc-5.5
13:41 AndrewR: karolherbst, I think i already run into same error with another project compilation, may be just setting g++ to clang will workaround this?
13:43 karolherbst: AndrewR: https://github.com/karolherbst/mesa/commit/026c9495b251ab788ddc295cfe6f50f556f2a9ea :/
13:44 karolherbst: AndrewR: ohh wait.. this is an C++ issue actually
13:44 karolherbst: *double sigh*
13:44 AndrewR: karolherbst, compilation finished OK, it seems
13:44 karolherbst: mhh
13:44 karolherbst: I found something
13:44 karolherbst: "the order of initialization needs to be in the exact order of declaration."
13:44 karolherbst: uff
13:46 karolherbst: it's in order
13:46 karolherbst: eh
13:46 karolherbst: nvm then
13:48 karolherbst: AndrewR: https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2079
13:48 AndrewR: karolherbst, https://stackoverflow.com/questions/31215971/non-trivial-designated-initializers-not-supported - i found this few days ago, but was unable to figure out where this struct was defined, so, just compiled with clang ...
13:48 AndrewR: karolherbst, moment ..
13:50 AndrewR: karolherbst, I'll re-run mesa compilation as fast as this land, just in case ..(while I don't have nvc0 hw)
14:02 stahlsau: servus all
14:02 stahlsau: got a problem starting X with nouveau, is this the right place to ask for help?
14:04 stahlsau: running nouveaudrmfb in console, but X says "nouveau ..... unknown chipset NV166"
14:08 stahlsau: kernel 5.3.0, xf86-video-nouveau 1.0.16, other stuff same versions as on the website (git or something). xorg.0.log shows nouveau reporting a lot of chipsets, but not nv166.
14:10 stahlsau: please answer if possible, i'll be back in a while
14:18 karolherbst: stahlsau: nothing we can do about right now. nv166 sounds like turing and for that we don't have the firmware to turn on any kind of hw acceleration
14:18 karolherbst: so all you've got is modesetting for now
14:20 karolherbst: maybe I could talk with imirkin about supporting volta, so that turning on turing is simple .... oh well, but maybe that's a lot of work... who knows
14:25 jjsa: Karolherbst are you also involved with the audio part of the nouveau driver?
14:26 karolherbst: there is no audio (well, there is, but totally boring stuff) part in the nouveau driver
14:26 karolherbst: all we do in nouveau is device link stuff and making sure the audio device is enabled
14:27 karolherbst: Lyude might know more, but I think there really isn't
14:27 karolherbst: jjsa: asking because of an issue in particular?
14:28 jjsa: If I boot with an external device connected to the hdmi port the audio part of the nvidia card is recognized but the digital output device appear as not connected.
14:29 karolherbst: mhhh
14:29 karolherbst: HDMI audio is a total mess in linux
14:29 karolherbst: jjsa: you usually get like tons of HDMi outputs and one of them should work
14:30 karolherbst: if not... then something is messed up as it seems
14:32 jjsa: Right. I had soung output with the same external devices on an raspberry but on the geforce card nothing happen.
14:32 karolherbst: I really don't know how and why all of that happens, but with my Intel GPU I get like 5 HDMI audio devices
14:33 karolherbst: and only one of those work
14:33 karolherbst: and I assume it might be similiar in this case...
14:33 karolherbst: dunno if there is just one exported or multiple
14:33 karolherbst: or if something messes it up
14:33 karolherbst: but if the display is on, then there should everything be setup already
14:34 karolherbst: otherwise I would file a bug against the alsa HDMI/DP driver
14:35 karolherbst: "snd_hda_codec_hdmi" is the driver
14:35 jjsa: It is installed.
14:36 karolherbst: right, otherwise it wouldn't be listed
14:36 karolherbst: but apparently there is something odd
14:36 karolherbst: maybe the device is muted...
14:36 karolherbst: or something
14:36 karolherbst: the audio stuff is really just a different PCIe device we don't have any control over
14:36 karolherbst: that's all alsa
14:39 jjsa: I will try to discover the reason, but it is an hard job. If, at boot time, no external hdmi device is attached the nvidia audio device ist not recognized. May this be an intializing problem within noveau drm ?
14:40 karolherbst: jjsa: no
14:40 karolherbst: we have a fix for that in the kernel though
14:41 karolherbst: but maybe it's not inside 5.3
14:41 jjsa: I had seen anythings for the 5.3 kernel.
14:42 karolherbst: Lyude: check the git log of the pci quirks... you won't like it
14:43 karolherbst: but maybe it's fine to do the device links in pci core... oh well
15:59 stahlsau: karolherbst: thanks...I thought it would work in X since it is supported? I dont need 3D, only plain 2D X
16:00 stahlsau: i tried with vesa, but it only works in 1024x768 which is kinda....well
16:01 joepublic: 1988's latest technology-ready
16:02 karolherbst: stahlsau: efifb
16:02 karolherbst: stahlsau: but, you can use nouveau
16:02 karolherbst: you can't use the nouveau ddx
16:02 karolherbst: only modesetting
16:04 stahlsau: so..i should run X on efifb? sry, i'm kinda noob ;-)
16:04 karolherbst: I am wondering why X doesn't work for you though
16:04 karolherbst: X should jus work
16:04 stahlsau: ah ok
16:04 karolherbst: the log will report the error... but it should still work nonetheless
16:04 karolherbst: limited
16:04 karolherbst: but still
16:05 karolherbst: stahlsau: so you should be able to change the resolution, but you won't be able to use OpenGL or so
16:08 stahlsau: yes, i understand, but X wont start with nouveau (the conf from the installation instructions, or without config)
16:14 stahlsau: thanks anyway, I'll try again after a reboot. cu & thx
21:12 karolherbst: pmoreau: by any chance, do you know how SVM pointers and constant memory behaves?
21:12 karolherbst: like when one sets an SVM pointer on a constant kernel parameter, when does the runtime have to take a snapshot of the data and upload it