alyssa changed the topic of #panfrost to: Panfrost - FLOSS Mali Midgard & Bifrost - https://gitlab.freedesktop.org/panfrost - Logs https://freenode.irclog.whitequark.org/panfrost - <daniels> avoiding X is a huge feature
<alyssa> ld_color_buffer_8 r1.xy, actually seems to do
<alyssa> ld_color_buffer_16 hr1.xyzw
<alyssa> Yay misnomers :P
<HdkR> Makes sense when your 16bit registers alias to the 32bit ones
<alyssa> So I guess that means that op actually is a color_buffer_32 kinda thing
afaerber has quit [Remote host closed the connection]
afaerber has joined #panfrost
vstehle has quit [Ping timeout: 272 seconds]
_whitelogger has joined #panfrost
tlwoerner has quit [Ping timeout: 245 seconds]
tlwoerner has joined #panfrost
tomeu has quit [Ping timeout: 258 seconds]
gtucker has quit [Ping timeout: 252 seconds]
davidlt has joined #panfrost
herbmillerjr has quit [Quit: Konversation terminated!]
vstehle has joined #panfrost
tomeu has joined #panfrost
<tomeu> jcureton: hi, that's the plan indeed, and I plan to get back to it in 1-2 weeks
<tomeu> if summer holidays don't get in the way :)
fysa has quit [Ping timeout: 245 seconds]
fysa has joined #panfrost
davidlt has quit [Remote host closed the connection]
davidlt has joined #panfrost
davidlt has quit [Remote host closed the connection]
davidlt has joined #panfrost
davidlt has quit [Ping timeout: 258 seconds]
maciejjo has joined #panfrost
raster has joined #panfrost
davidlt has joined #panfrost
raster has quit [Remote host closed the connection]
raster has joined #panfrost
afaerber has quit [Quit: Leaving]
yann has quit [Ping timeout: 272 seconds]
afaerber has joined #panfrost
<tomeu> bbrezillon: what you have sent conflicts massively with what I was doing, which I guess means this was sorely needed :)
<tomeu> bbrezillon: no change in test results though?
<bbrezillon> tomeu: nope, still green
<bbrezillon> tomeu: and yes, I was expecting some conflicts
<tomeu> bbrezillon: I was hoping that some tests could be fixed
<bbrezillon> after you told me you were working on BO caching
<bbrezillon> tomeu: nope, we still have this dangling swizzle test
<bbrezillon> which I can't reproduce on my end
<tomeu> well, we have all the flip-flops that we don't run
<tomeu> see gitlab-ci.yml
<bbrezillon> tomeu: oh, I thought they were still run
<tomeu> they are run, but don't end up in what is diffed
theperfectpunk has joined #panfrost
<theperfectpunk> Hi
<theperfectpunk> I built mesa using the instructions
<bbrezillon> tomeu: hm, I'll have to check then
<tomeu> bbrezillon: well, guess as long as things don't break, you don't need to do anything else regarding CI
<bbrezillon> tomeu: can we add them back to the diff and keep ignoring the result for arm32?
<theperfectpunk> but I get an error when running kmscube : failed to load driver: kms_swrast
<theperfectpunk> I'm using Ubuntu 18.04 LTS server running on Khadas VIM2 (Amlogic S912)
<tomeu> bbrezillon: should be fine I think
<tomeu> maybe run without any flip-flop in the list, and see what happens?
<tomeu> theperfectpunk: what do strace say when the /dev/dri devices are attempted to be opened/
<theperfectpunk> @tomeu there are no erros when, /dev/dri/card0 is opened
<theperfectpunk> which is present, but then it tries to open /dev/dri/renderD128, which is not present
<theperfectpunk> and it gives -1 ENONET (No such file or directory)
<tomeu> ah, then you don't have the panfrost kernel driver open
<tomeu> s/open/probed
<theperfectpunk> modprobe panfrost gives me no errors, and it is present when i lsmod
<jcureton> anything interesting in a `dmesg | grep panfrost`?
<theperfectpunk> yep
<theperfectpunk> @jcureton https://pastebin.com/LkVQtqxE
<tomeu> haven't seen that before
<tomeu> are there any pending patches in lkml?
yann has joined #panfrost
<theperfectpunk> @tomeu I'm on Linux Mainline 5.2.0-rc7
<tomeu> sorry, don't know about amlogic SoCs myself
<tomeu> theperfectpunk: maybe someone in #linux-amlogic ?
<theperfectpunk> @tomeu this issue is due to missing kernel patches?
<tomeu> I think this has to be an amlogic-specific issue
<theperfectpunk> @tomeu thanks
adjtm has quit [Ping timeout: 248 seconds]
adjtm has joined #panfrost
<alyssa> I've heard about weird amlogic issues
<alyssa> narmstrong: ^^?
<narmstrong> yep, seems broken, was working when submitted :-/
<narmstrong> has 0 time to debug it
<bbrezillon> tomeu: are modifiers attached to dmabuf objs now?
<tomeu> bbrezillon: nope
<tomeu> have to be sent OOB
<bbrezillon> ok, then I guess the modifier would be stored in panfrost_resource, like other BO meta-data
<bbrezillon> s/would/could/
<tomeu> bbrezillon: we can infer it from pan_layout
<bbrezillon> yep
<bbrezillon> so the import/export BO funcs shouldn't be impacted
<bbrezillon> or am I missing something
<bbrezillon> ?
jernej has quit [Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net]
<tomeu> oh, with the move of fields to resource, we might not
<tomeu> I will find it soon enough :)
<tomeu> bbrezillon: do you have push permission?
<bbrezillon> tomeu: nope
theperfectpunk has quit [Quit: Leaving.]
<tomeu> you have this series plus that single patch to push?
<bbrezillon> yep
<tomeu> ok, I will push
<bbrezillon> thx
<tomeu> bbrezillon: the branch that passed the CI has the same patches sent to the ml?
<bbrezillon> tomeu: yes
<tomeu> awesome
jernej has joined #panfrost
<tomeu> pushed
BenG83 has joined #panfrost
<alyssa> bbrezillon: If you want push, you can get that now I think.
<bbrezillon> alyssa: hehe, what if I like to bother you everytime I have something to merge? :-)
<alyssa> bbrezillon: rephrase. I will shortly be asking other maintainers to give you push and then will refuse to merge anything you don't push yourself...? =P
<bbrezillon> alyssa: ok ok, will ask for write permissions, but I must admit it was a comfortable situation being a regular contributor, especially when the maintainer is reviewing/merging patching so quickly
<alyssa> bbrezillon: Hm? I don't think there'll be a difference?
<alyssa> We'll still do the same review cycles at the same speed
<alyssa> It's just that now if I/Tomeu say R-b, you can merge it yourself (rather than waiting for one of us to do it)
yann has quit [Ping timeout: 246 seconds]
<alyssa> Aside: render target stuff coming along alright. RGBA16F rendering now works
tgall_foo has quit [Remote host closed the connection]
tgall_foo has joined #panfrost
<alyssa> Of course, there's a whole bucket of ldst ops specifically dedicated to unpacking weird pixel formats in blend shaders, fun
stikonas has joined #panfrost
stikonas has quit [Read error: Connection reset by peer]
stikonas_ has joined #panfrost
<alyssa> on their own all the simple float/integer formats now work for rendering
<alyssa> More refactoring necessary to get the keying work so they work together in harmony
raster has quit [Remote host closed the connection]
<alyssa> Erg, I didn't think about how blend constants fit into this..
<alyssa> I guess we want to make panfrost_blend_state a hashmap
<alyssa> With (format, constant) keys
<alyssa> And either a blend_equation/constant or blend shader/meta as the value (unioned)
<alyssa> Then when any of the blend state / blend constant / framebuffer changes, we generate new blend state (but keyed so it's not stupidly slow)
* alyssa tries to think of potential pitfalls
<alyssa> One obvious one is that updating constants is.. slow
<alyssa> But that's kind of inevitable with this sort of scheme I feel like
<alyssa> Better would be to key by:
<alyssa> (format, fast_constant)
<alyssa> where fast_constant is merely a *boolean*
<alyssa> If it's true, there is no blend constant or the blend constant has only a single channel
<alyssa> If it's false, there is a blend constant and it has multiple distinct channels
<alyssa> (False always maps to a blend shader)
<alyssa> That saves a *lot* of recompiles, since we now only have (at most) 2 blend values per format
<alyssa> I also question the wisdom of doing it per format when lots of formats intersect, but I digress.
<alyssa> It might actually be better to have a single blend_equation pulled out
<alyssa> And then a hashmap of formats (that need a shader for various reasons) -> blend shaders
sravn has quit [Quit: WeeChat 2.4]
sravn has joined #panfrost
BenG83 has quit [Quit: Leaving]
jcureton has quit [Remote host closed the connection]
jesse48 has joined #panfrost
jesse48 has left #panfrost [#panfrost]
jcureton has joined #panfrost
NeuroScr has joined #panfrost
jcureton has quit [Remote host closed the connection]
davidlt has quit [Ping timeout: 245 seconds]
afaerber has quit [Quit: Leaving]
afaerber has joined #panfrost
NeuroScr has quit [Quit: NeuroScr]
* robher guesses no one runs drm-misc-next because it is broken...
<anarsoul> :(
<alyssa> robher: I haven't updated for a while since it's kind of a pain with all the weirdness I have..
<robher> alyssa: the problem is mmap on imported buffers now fails. Before it was a silent bug that maybe worked if we import our own buffers.
stikonas_ has quit [Ping timeout: 272 seconds]
<alyssa> That doesn't sound good
<robher> alyssa: the question is why is everything mmap'ed? Most buffers shouldn't need to be.
<alyssa> robher: Hmm, imported/exported buffers logically shouldn't need an mmap, no
<alyssa> I think the current pan_drm.c code just assumes everything is CPU R/W to keep things simple
<alyssa> With kbase we were a lot more careful, but a lot of those flags (execute, no CPU map, growable..) got lost in transition
<robher> alyssa: I'm testing whether we can drop it on the imports.
<alyssa> robher: I *think* that would be ok?
<alyssa> I can't think of a case when we would need to mmap an import legitimately
<robher> alyssa: But still, we have the compatibility issue so either the kernel change has to be reverted or we have to support mmap on imports...
<alyssa> Oh, shoot, I didn't think of that
<alyssa> robher: I wonder if we can just have mmap silently fail again...?
HdkR has quit [Remote host closed the connection]
HdkR has joined #panfrost