<kode54>
I already have mesa-git built after that was merged
lumidify has joined #dri-devel
Vanfanel has joined #dri-devel
<Vanfanel>
Hi. I am deciding on a SOC and RK3588 seems a good choice, but MESA support is a must.
<Vanfanel>
Is official MALI G610 support coming to MESA?
smilessh has quit [Remote host closed the connection]
<psykose>
buy around what exists not what theoretically might show up or not
<psykose>
currently it is not supported
smilessh has joined #dri-devel
<psykose>
(for the "must" part)
Danct12 is now known as Guest2083
Danct12 has joined #dri-devel
Danct12 has quit []
Guest2027 has quit [Quit: Guest2027]
<Vanfanel>
<psykose> "buy around what exists not..." <- That's indeed a very good advice. Looking at MESA commits, I don't see anything related to G610 anyway.
fab has joined #dri-devel
fab has quit []
fab has joined #dri-devel
sarnex has quit [Read error: Connection reset by peer]
sarnex has joined #dri-devel
cath has joined #dri-devel
<daniels>
Vanfanel: it’s being actively worked on; branches are available but unmerged
<psykose>
also tangentially the whole rk3588 is not quite there yet for mainline, so you'd have to use the 5.10 vendor kernel with it for most things on the board (even sdcard last i checked)
<psykose>
incidentally my girlfriend just bought a rockpi 5b before checking any of this at all
<psykose>
(quite funny)
tarceri has quit [Remote host closed the connection]
tarceri has joined #dri-devel
kasper93 has quit [Ping timeout: 480 seconds]
heat_ has joined #dri-devel
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
Net147 has quit [Quit: Quit]
Net147 has joined #dri-devel
heat_ has quit [Read error: No route to host]
heat has joined #dri-devel
sassefa has joined #dri-devel
sassefa has quit []
sassefa has joined #dri-devel
kzd has joined #dri-devel
kasper93 has joined #dri-devel
sassefa has quit [Ping timeout: 480 seconds]
cphealy has quit [Quit: Leaving]
fab_ has joined #dri-devel
fab_ is now known as Guest2099
fab has quit [Ping timeout: 480 seconds]
Guest2099 is now known as fab
fab is now known as Guest2100
<cwabbott>
gfxstrand: the more I work with it, the more I'm convinced the `vk_graphics_pipeline_state` design where everything has to be in an indirectly-allocated struct was a mistake
<cwabbott>
tracking dynamic instead of set state was probably also a mistake
<cwabbott>
there have been a few cases where I just wanna split out a few pieces from an indirect struct and I can't because of the design
<cwabbott>
like the one I'm hitting now is `vi->bindings_valid`, which is the only part of the vertex state that turnip actually needs in `vk_graphics_pipeline_state` (the rest is precompiled)
<cwabbott>
apparently I was accidentally including the entire vertex input state in pipeline libraries even though it's been precompiled, which isn't what I wanted, and in trying to fix that I realized that it's impossible to do because of the design
<Vanfanel>
<daniels> "Vanfanel: it’s being actively..." <- Hmm, do you mean Panfork? I fear that will never be merged, there's a strange story behind it but I believe it won't be developed further
<Vanfanel>
if there are other branches I would love to hear from them :)
<daniels>
Vanfanel: no, panfork will never be merged and I’m not sure if it’s still being developed or not. there’s work against upstream Panfrost tho
<Vanfanel>
(i meant forks, sorry)
<Vanfanel>
daniels: ah!! Very good news then, really! :)
<Vanfanel>
In the first link, the one to look for is pancsf branch, right?
kts has quit [Remote host closed the connection]
kts has joined #dri-devel
<cwabbott>
gfxstrand: if we fixed that, we could probably also move the view_mask and a few of the pipeline flags to the top-level `vk_graphics_pipeline_state` and remove all the ugly "non-complete" renderpass state stuff
gouchi has joined #dri-devel
<daniels>
Vanfanel: yep
kts has quit [Quit: Konversation terminated!]
alanc has quit [Remote host closed the connection]
alanc has joined #dri-devel
sassefa has joined #dri-devel
kts has joined #dri-devel
sassefa has quit [Ping timeout: 480 seconds]
heat_ has joined #dri-devel
heat has quit [Read error: No route to host]
sassefa has joined #dri-devel
heat has joined #dri-devel
heat_ has quit [Read error: No route to host]
columbarius has quit [Ping timeout: 480 seconds]
columbarius has joined #dri-devel
sassefa has quit [Ping timeout: 480 seconds]
Guest2083 has quit [Remote host closed the connection]
Daanct12 has joined #dri-devel
gouchi has quit [Remote host closed the connection]
heat has quit [Remote host closed the connection]
heat_ has joined #dri-devel
Daaanct12 has joined #dri-devel
Daanct12 has quit [Ping timeout: 480 seconds]
Danct12 has joined #dri-devel
Daanct12 has joined #dri-devel
Daaanct12 has quit [Ping timeout: 480 seconds]
kasper93 has quit [Remote host closed the connection]
Danct12 has quit [Ping timeout: 480 seconds]
<Vanfanel>
<daniels> "Vanfanel: yep" <- Can you please point me to the right kernel to go with it? I guess it has to be some kind of midstream kernel...
kasper93 has joined #dri-devel
sravn has quit []
djbw_ has quit [Read error: Connection reset by peer]
konstantin has joined #dri-devel
konstantin_ has quit [Ping timeout: 480 seconds]
Duke`` has quit [Ping timeout: 480 seconds]
Guest2100 has quit [Quit: Guest2100]
Akari has joined #dri-devel
Akari is now known as Guest2117
<Guest2117>
question about the d3d12 backend: what d3d "feature level" capability is required from the hardware for OpenGL 3.3?
dliviu has quit [Remote host closed the connection]
dliviu has joined #dri-devel
djbw_ has joined #dri-devel
<jenatali>
No special requirements. 4.1 is available for all D3D GPUs, you only start to need optional stuff if you want 4.2 (and eventually beyond)
<kisak>
Roughly, DirectX 10 era hardware and OpenGL 3 hardware are the same thing, but there can be edge cases, and the Windows drivers might have missing features from the driver vendor. (I don't know much about the Windows driver landscape.)
<jenatali>
Specifically, typed UAV (storage image) load for a bunch of formats is needed for 4.2. for 4.3 you need the newly-added format casting but, but we haven't hooked that up to the Mesa driver yet
<kisak>
jenatali: right, but I expect that there's a minimum compatible version from each hardware vendor, and that same vendor most likely isn't doing updates to GL3 era hardware.
<jenatali>
(contributions welcome :P)
<kisak>
(driver version)
<jenatali>
kisak: D3D12's min-spec is so far beyond GL3. All D3D12 drivers are capable of supporting our mapping layer at 4.1
<jenatali>
Guest2117: FYI in case you didn't see without being tagged
<Guest2117>
jenatali: thanks. I'm just wondering if this thing will run on pre-D3D12 era hardware (that can do GL 4.2+)
<Guest2117>
something like a GTX 680 or (more importantly) older intel iGPUs
<jenatali>
It needs a D3D12 driver, which means at least feature level 11
<Guest2117>
i see
<jenatali>
For NV that's Fermi, for Intel it's Broadwell
<Guest2117>
jenatali: is ivybridge (HD4000) not FL11? IIRC Mesa can do GL 4.something with it
<jenatali>
Intel never shipped DX12 drivers before Haswell, and they recently disabled those drivers leaving Broadwell as the oldest supported gen
<Guest2117>
:(
<Guest2117>
i guess vulkan drivers for zink isn't even worth asking about
<jenatali>
Someone could probably build a d3d11-based backend for 3.3 but the lack of swizzles on sampler views would be... Oof
<kisak>
^which aligns with what I was trying to say about minimum vendor driver version being the important detail.
<Guest2117>
i was looking forward to replacing ANGLE for my windows builds. It's a nightmare to build (typical googleware)
<Guest2117>
>lack of swizzles
<Guest2117>
oh yeah
<Guest2117>
they gutted those from WebGL for that reason LOL
<jenatali>
I think that's the only real feature we use from 12 that's not in 11 in that backend
<Guest2117>
what's funny is, i think ANGLE emulates them somehow anyway. probably not very optimally