00:04 fdobridge: <a​irlied> I'd guess primary but ont sure
00:11 skeggsb: Privileged Register Interface
00:11 skeggsb: (i think)
00:13 airlied: ah makes more sense :-)
00:13 fdobridge: <m​arysaka> oh that would make ton of sense yeah
18:20 rmckeever: Is anyone familiar with the NV9097_TEXHEAD0_*_SOURCE_IN_* nvidia headers? I'm trying to add VK_FORMAT_B4G4R4A4_UNORM_PACK16 to the nil_format_info table, and there's something wrong with my entry.
18:24 rmckeever: My entry is:
18:24 rmckeever: C4(A, A4R4G4B4_UNORM, NONE, A, R, G, B, UNORM, A4B4G4R4, T),
18:25 rmckeever: It's making all the dEQP-VK.pipeline.monolithic.sampler.view_type.2d_unnormalized.format.b4g4r4a4_unorm_pack16.* tests fail.
18:27 karolherbst: rmckeever: soo weird idea: you might have to reverse the channels
18:27 karolherbst: like you see it done in "C4(A, B5G5R5A1_UNORM, A1R5G5B5, B, G, R, A, UNORM, A1B5G5R5, TD),"
18:28 rmckeever: So B, G, R, A?
18:28 karolherbst: nvidia seems to declare in big endian order for normal formats, but if it's packed, it's little endian or something
18:28 rmckeever: Okay, I'll try that.
18:28 karolherbst: "C4(A, B4G4R4A4_UNORM, NONE, B, G, R, A, UNORM, A4B4G4R4, T),"
18:28 karolherbst: there you also see it being reverse
18:44 rmckeever: Actually, that makes it identical to an existing entry for a different format.
18:52 karolherbst: rmckeever: which one?
19:00 rmckeever: I believe it's VK_FORMAT_A4R4G4B4_UNORM_PACK16
19:01 fdobridge: <j​ekstrand> Watch out for channel orders
19:01 fdobridge: <j​ekstrand> `VK_FORMAT` and nvidia are the same but they're backwards from `PIPE_FORMAT`
19:01 fdobridge: <j​ekstrand> The one on the left in the format table is a `PIPE_FORMAT_*` and the one on the right is nvidia
19:03 fdobridge: <k​arolherbst🐧🦀> but for packed ones it's reversed, no?
19:04 fdobridge: <j​ekstrand> I'm talking about packed
19:04 fdobridge: <k​arolherbst🐧🦀> ahh
19:04 fdobridge: <j​ekstrand> They're all the same for array formats
19:04 fdobridge: <k​arolherbst🐧🦀> I see
19:06 fdobridge: <j​ekstrand> But `VK_FORMAT_B4G4R4A4` is `PIPE_FORMAT_A4R4G4B4` and the nvidia hardware format would be `B4G4R4A4` if that format existed. Except it doesn't. Theo only one that exists is `A4B4G4R4` so it needs a GBAR swizzle.
19:06 fdobridge: <j​ekstrand> Yeah, that's a weird swizzle
19:07 fdobridge: <j​ekstrand> rmckeever ^^
19:11 fdobridge: <j​ekstrand> That format ending up in the Vulkan spec as required was a mistake. 😕
19:11 fdobridge: <k​arolherbst🐧🦀> I think some games use it though 🙃
19:22 fdobridge: <j​ekstrand> Only because the right format isn't required
19:22 fdobridge: <j​ekstrand> The format NV has in hardware is also the one Intel has in hardware which is also the one that's in DX. We totally just got it wrong in Vulkan 1.0.
19:23 fdobridge: <k​arolherbst🐧🦀> annoying :/
19:23 fdobridge: <j​ekstrand> Very
20:36 rmckeever: GBAR works:
20:36 rmckeever: C4(A, A4R4G4B4_UNORM, NONE, G, B, A, R, UNORM, A4B4G4R4, T),
21:00 hdzki[m]: Speaking of texture formats, i have some weird texture format that i need some IDing for
21:00 hdzki[m]: Have y'all seen a planar ycbcr 4:2:0 like texture format in the wild?
21:01 fdobridge: <j​ekstrand> Yeah, Intel has one
21:02 hdzki[m]: hdzki[m]: luma (sometimes with alpha) is on its own plane. meanwhile cb and cr are interlaced in a different plane that's half the res of the first (hence the 4:2:0 ilke part)
21:05 hdzki[m]: i found it in a game before but the FourCC was just ATI2 (that's BC5) which isn't useful
21:17 fdobridge: <j​ekstrand> PSA: Just rebased nvk/main on mesa/main
21:18 fdobridge: <j​ekstrand> rmckeever: Feel free to rebase your VK_KHR_device_groups MR and we can probably merge it this afternoon.
21:20 airlied:wonders if we will ever do device groups properly for anyone
21:20 fdobridge: <j​ekstrand> I doubt it
21:20 fdobridge: <j​ekstrand> I'm unaware of any apps that use it
21:20 fdobridge: <j​ekstrand> NVIDIA supports it and AMD might.
21:22 airlied: AMDVLK does
21:22 airlied: lots of loops
21:36 fdobridge: <j​ekstrand> heh
21:56 fdobridge: <n​anokatze> q2rtx uses device groups
21:56 fdobridge: <n​anokatze> but eh who cares about device groups
22:03 pendingchaos: strange brigade too
22:03 pendingchaos: and maybe some other game that I don't really remember
22:35 fdobridge: <k​arolherbst🐧🦀> @jekstrand your lut stuff is fun 😄
22:38 fdobridge: <k​arolherbst🐧🦀> but why aren't you just doing what we do in codgen?
23:07 fdobridge: <j​ekstrand> IDK what you do in codegen
23:07 fdobridge: <j​ekstrand> I'm not doing all that much copy+paste