ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
X-Scale` has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
Luc has joined #dri-devel
sdutt has joined #dri-devel
<Luc> hi, could someone please tell me what the 'U' in ARM_16x16_BLOCK_U_INTERLEAVED stands for? and how exactly pixels in the block are reordered in this layout? thanks in advance
tursulin has quit [Read error: Connection reset by peer]
kevintang_ has joined #dri-devel
pcercuei has quit [Quit: dodo]
<anarsoul> luc: see src/panfrost/shared/pan_tiling.c in mesa repo
<anarsoul> I'm not sure what the 'U' stands for though :)
<Luc> anarsoul: the comment is so detailed and helpful, thx!
columbarius has joined #dri-devel
co1umbarius has quit [Ping timeout: 480 seconds]
alatiera has quit [Read error: Connection reset by peer]
alatiera has joined #dri-devel
JohnnyonFlame has quit [Ping timeout: 480 seconds]
imre has quit [Remote host closed the connection]
Emantor has quit [Quit: ZNC - http://znc.in]
Emantor has joined #dri-devel
drawat_ has quit [Ping timeout: 480 seconds]
drawat has joined #dri-devel
sdutt has quit [Ping timeout: 480 seconds]
alatiera has quit [Read error: Connection reset by peer]
alatiera has joined #dri-devel
Luc has quit [Remote host closed the connection]
boistordu_ex has quit [Ping timeout: 480 seconds]
Luc has joined #dri-devel
Lightsword has quit [Quit: ZNC]
vivijim has quit [Ping timeout: 480 seconds]
Luc has left #dri-devel [#dri-devel]
Lightsword has joined #dri-devel
kevintang_ has quit [Quit: Connection closed for inactivity]
jernej has quit [Ping timeout: 480 seconds]
kevintang_ has joined #dri-devel
lemonzest has joined #dri-devel
Company has quit [Read error: Connection reset by peer]
mattrope has quit [Ping timeout: 480 seconds]
mclasen has quit []
jernej has joined #dri-devel
OftenTimeConsuming has quit [Remote host closed the connection]
OftenTimeConsuming has joined #dri-devel
aravind has joined #dri-devel
ella-0 has joined #dri-devel
ella-0_ has quit [Ping timeout: 480 seconds]
kevintang_ has quit [Quit: Connection closed for inactivity]
sdutt has joined #dri-devel
aravind has quit [Ping timeout: 480 seconds]
YuGiOhJCJ has joined #dri-devel
alanc has quit [Remote host closed the connection]
alanc has joined #dri-devel
mlankhorst has joined #dri-devel
Duke`` has joined #dri-devel
danvet has joined #dri-devel
X-Scale` has joined #dri-devel
X-Scale has quit [Ping timeout: 480 seconds]
JohnnyonFlame has joined #dri-devel
imre has joined #dri-devel
oneforall2 has quit [Remote host closed the connection]
oneforall2 has joined #dri-devel
sdutt has quit [Ping timeout: 480 seconds]
mlankhorst has quit []
gouchi has joined #dri-devel
pcercuei has joined #dri-devel
Duke`` has quit [Ping timeout: 480 seconds]
kevintang_ has joined #dri-devel
flacks has quit [Quit: Quitter]
Duke`` has joined #dri-devel
flacks has joined #dri-devel
pcercuei has quit [Quit: brb]
pcercuei has joined #dri-devel
Haaninjo has joined #dri-devel
yogesh_m1 has joined #dri-devel
rasterman has joined #dri-devel
yogesh_mohan has quit [Ping timeout: 480 seconds]
X-Scale has joined #dri-devel
X-Scale` has quit [Ping timeout: 480 seconds]
gouchi has quit [Remote host closed the connection]
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
imre is now known as Guest6943
imre has joined #dri-devel
mszyprow has joined #dri-devel
lj_ has quit []
kevintang_ has quit [Quit: Connection closed for inactivity]
pekkari has joined #dri-devel
Haaninjo has quit [Quit: Ex-Chat]
gouchi has joined #dri-devel
gouchi has quit []
mszyprow has quit [Ping timeout: 480 seconds]
nuh^ has joined #dri-devel
Danct12 has quit [Quit: Quitting]
aravind has joined #dri-devel
Danct12 has joined #dri-devel
imirkin has quit [Quit: Leaving]
Daanct12 has joined #dri-devel
JohnnyonFlame has quit [Ping timeout: 480 seconds]
Danct12 has quit [Ping timeout: 480 seconds]
Company has joined #dri-devel
haagch has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
haagch has joined #dri-devel
Daanct12 is now known as Danct12
gouchi has joined #dri-devel
aravind has quit [Ping timeout: 480 seconds]
Imporntant[info] has joined #dri-devel
mszyprow has joined #dri-devel
JohnnyonFlame has joined #dri-devel
mclasen has joined #dri-devel
lj has joined #dri-devel
Duke`` has quit []
Duke`` has joined #dri-devel
pekkari has quit [Quit: Konversation terminated!]
<javierm> danvet: I think that hit a bug in dim (or one of the git tools)
<javierm> danvet: I fetched the mbox for https://patchwork.kernel.org/project/dri-devel/patch/20211112133230.1595307-4-javierm@redhat.com/ and applied to drm-misc-next with dim apply-branch
<javierm> then dim push-branch drm-misc-next
<javierm> but for some reasons the new file drivers/gpu/drm/drm_nomodeset.c was created in gpu/drm/drm_nomodeset.c wrongly
<javierm> both the posted patched and the mbox patch have the correct path but the branch after drm-misc-next apply has the wrong one
<javierm> and I didn't notice before the push so drm-misc-next is broken :(
mszyprow has quit [Ping timeout: 480 seconds]
zf has quit [Quit: Segmentation fault (core dumped)]
imirkin has joined #dri-devel
sdutt has joined #dri-devel
JohnnyonFlame has quit [Read error: Connection reset by peer]
<javierm> danvet: figured out what happend and posted a patch. Sorry for missing that the patches weren't applied correctly...
<javierm> wonder if dim should not attempt to do 3-way merges since it seems to be fragile and not handling when need to use -p0 instead
<danvet> javierm, you should build test before pushing, not after :-)
<danvet> because yes mbox patches is very lossy sometimes
<javierm> danvet: yes, sorry about that. I did built test v5 before posting and wrongly assumed that the end result would be correct
<danvet> javierm, yeah no worries, r-b stamped
<javierm> danvet: thanks!
<javierm> danvet: diff.noprefix true is a convenient config that I found not long before because allows you to copy & paste paths without having to strip the a/ b/ prefixes
<javierm> but I've disabled now in all my dev machines since it seems to be a not that common setup and confusing our tools
X-Scale has quit [Ping timeout: 480 seconds]
sdutt has quit []
sdutt has joined #dri-devel
alatiera has quit [Quit: The Lounge - https://thelounge.chat]
mszyprow has joined #dri-devel
Haaninjo has joined #dri-devel
alatiera has joined #dri-devel
danvet has quit [Ping timeout: 480 seconds]
mszyprow has quit [Ping timeout: 480 seconds]
lemonzest has quit [Quit: WeeChat 3.3]
Haaninjo has quit [Quit: Ex-Chat]
tagr has quit [Remote host closed the connection]
tagr has joined #dri-devel
rpigott has quit [Remote host closed the connection]
rpigott has joined #dri-devel
mclasen has quit []
mclasen has joined #dri-devel
gouchi has quit [Remote host closed the connection]
sdutt has quit [Ping timeout: 480 seconds]
Duke`` has quit [Ping timeout: 480 seconds]
tarceri has quit [Ping timeout: 480 seconds]
Net147_ has joined #dri-devel
Net147 has quit [Remote host closed the connection]
rcf has quit [Ping timeout: 480 seconds]
jewins has joined #dri-devel
Net147_ has quit []
Net147 has joined #dri-devel
tobiasjakobi has joined #dri-devel
tobiasjakobi has quit [Read error: Connection reset by peer]
Net147 has quit [Quit: Quit]
Net147 has joined #dri-devel
jewins has quit [Quit: jewins]
jewins has joined #dri-devel
<anarsoul> hey, how does mesa/gallium handle implicit multisample buffer and resolve described in https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_multisampled_render_to_texture.txt ?
<anarsoul> I actually can't find a way in gallium driver to tell whether I need to do implicit resolve or not
<imirkin> anarsoul: there's a PIPE_CAP, as always
<imirkin> iirc you can do the implicit resolve when storage_samples == 1
<imirkin> or something along those lines
<imirkin> otherwise you have to store the full data, in theory
<imirkin> i'm less well-versed in what ES says about all this, which might allow tilers to drop MSAA info
<imirkin> (esp pre-ES3)
<anarsoul> imirkin: thanks, alyssa already helped me on #panfrost :)
<imirkin> hopefully alyssa didn't say anything too conflicting with what i said above?
<anarsoul> nope, pretty much what you said
<imirkin> i'm double-checking some stuff in the ES2 spec
<imirkin> i'm pretty sure you should be allowed to throw away the extra info for the "default" framebuffer
<anarsoul> it's PIPE_CAP_SURFACE_SAMPLE_COUNT cap and EXT_multisampled_render_to_texture for ES2
<anarsoul> imirkin: yeah, I hope mesa is smart enough to set surf->texture->nr_samples for render target to 1 to avoid extra blit
<anarsoul> also I guess it's time to implement lima-specific blit, I'm not sure if util_blitter() can do resolve properly for lima
<anarsoul> since it doesn't support texop_txf_ms
Imporntant[info] has quit []