ChanServ changed the topic of #zink to: official development channel for the mesa3d zink driver || https://docs.mesa3d.org/drivers/zink.html
ced117 has quit [Ping timeout: 480 seconds]
ced117 has joined #zink
pbsds12 has quit []
pbsds has joined #zink
pbsds has quit []
pbsds has joined #zink
pbsds has quit []
pbsds has joined #zink
pbsds has quit []
pbsds has joined #zink
sinanmoh- has joined #zink
sinanmohd has quit [Ping timeout: 480 seconds]
bnieuwenhuizen has quit [Quit: Bye]
bnieuwenhuizen has joined #zink
<zmike> cc kusma
<kusma> quickly acked.
<zmike> thx
<kusma> I guess
<kusma> (that's a yes)
<zmike> 👍
<zmike> kusma: have I mentioned how much I hate pipe caps recently
<kusma> Heh, what's the problem now? :)
<zmike> the need for that MR at all
<zmike> spent way too long debugging to figure it out :/
<kusma> Ah, well. Not all HW can do it I suppose?
<zmike> sure, but it feels like there should be some way to grep for caps like "your driver may get 1fps without this one"
<kusma> But yeah, I think there's way too many "I don't bother fixing up the other drivers, so I'll just add a cap for it"-caps
<zmike> at least for perf-related caps a ticket should be opened imo
<kusma> Haha, I get what you mean, yeah. I guess it's hard to know the perf impact on all important apps out there, though. But yeah, you're not wrong.
<kusma> Yeah, opening a ticket is probably a good idea in those cases.
<zmike> well this is an old cap too
<zmike> 2016
<zmike> but I had no idea