ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
nchery is now known as Guest107
nchery has joined #dri-devel
Guest107 has quit [Ping timeout: 480 seconds]
pcercuei has quit [Quit: dodo]
dllud_ has joined #dri-devel
dllud has quit [Read error: Connection reset by peer]
dllud has joined #dri-devel
dllud_ has quit [Read error: Connection reset by peer]
FireBurnUK has joined #dri-devel
FireBurn has quit [Quit: Konversation terminated!]
maxzor has quit [Ping timeout: 480 seconds]
columbarius has joined #dri-devel
co1umbarius has quit [Ping timeout: 480 seconds]
heat has joined #dri-devel
Emantor has quit [Quit: ZNC - http://znc.in]
Emantor has joined #dri-devel
ngcortes has quit [Remote host closed the connection]
nchery has quit [Read error: Connection reset by peer]
mbrost_ has quit [Ping timeout: 480 seconds]
mbrost has joined #dri-devel
sdutt has joined #dri-devel
<tarceri> How does on use virpipe?
<tarceri> I tried `LIBGL_ALWAYS_SOFTWARE=true GALLIUM_DRIVER=virpipe` but I just get a message `lost connection to rendering server on 8 read -1 22`
heat has quit [Ping timeout: 480 seconds]
sdutt has quit [Ping timeout: 480 seconds]
lemonzest has joined #dri-devel
<tarceri> airlied: any hints for me --^ I'm trying to debug the regression CI is showing for virpipe in https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15731
<tarceri> The regression only started to popup on the MR in the past week or so if I'm remembering correctly so something seems to have changed in the main branch thats causing it to trigger with this MR
mbrost_ has joined #dri-devel
mbrost has quit [Ping timeout: 480 seconds]
mclasen has quit [Ping timeout: 480 seconds]
Lucretia has quit []
Lucretia has joined #dri-devel
Company has quit [Quit: Leaving]
mclasen has joined #dri-devel
mclasen has quit [Ping timeout: 480 seconds]
dllud_ has joined #dri-devel
dllud has quit [Read error: Connection reset by peer]
dllud has joined #dri-devel
dllud_ has quit [Read error: Connection reset by peer]
dllud_ has joined #dri-devel
dllud has quit [Read error: Connection reset by peer]
<airlied> tarceri: you have to run the vtest_server for them virglrenderer project
<airlied> from the
Duke`` has joined #dri-devel
<tarceri> airlied: thanks! I installed the fedora package and ran the server and the test now runs :) But of course it passes just fine locally
<tarceri> airlied: thanks! I installed the fedora package and ran the server and the test now runs :) But of course it passes just fine locally
plombo has quit [Ping timeout: 480 seconds]
<tarceri> building the server from git I now get the piglit failure :)
nchery has joined #dri-devel
hch12907 has joined #dri-devel
mhenning has quit [Quit: mhenning]
hch12907_ has joined #dri-devel
hch12907 has quit [Ping timeout: 480 seconds]
Duke`` has quit [Ping timeout: 480 seconds]
dv_ has quit [Quit: WeeChat 2.8]
X512 has joined #dri-devel
X512 has quit []
X512 has joined #dri-devel
lumag_ has quit [Ping timeout: 480 seconds]
dj-death has joined #dri-devel
X512 has quit [Quit: Vision[]: i've been blurred!]
X512 has joined #dri-devel
X512 has quit []
mbrost_ has quit [Read error: Connection reset by peer]
nchery has quit [Read error: Connection reset by peer]
nchery has joined #dri-devel
pcercuei has joined #dri-devel
FireBurnUK has quit [Quit: Konversation terminated!]
karolherbst has quit [Remote host closed the connection]
gawin has joined #dri-devel
karolherbst has joined #dri-devel
Haaninjo has joined #dri-devel
gouchi has joined #dri-devel
gawin has quit [Ping timeout: 480 seconds]
mclasen has joined #dri-devel
flacks has quit [Quit: Quitter]
flacks has joined #dri-devel
maxzor has joined #dri-devel
gouchi has quit [Quit: Quitte]
icecream95 has quit [Ping timeout: 480 seconds]
jagan_ has joined #dri-devel
maxzor has quit [Ping timeout: 480 seconds]
Haaninjo has quit [Quit: Ex-Chat]
LaserEyess has quit [Quit: fugg]
gawin has joined #dri-devel
LaserEyess has joined #dri-devel
mareko_ has joined #dri-devel
glisse is now known as Guest140
glisse has joined #dri-devel
dri-logger has joined #dri-devel
Guest140 has quit [Ping timeout: 480 seconds]
mareko has quit [Ping timeout: 480 seconds]
dri-logg1r has quit [Ping timeout: 480 seconds]
mslusarz has quit [Ping timeout: 480 seconds]
mslusarz has joined #dri-devel
rasterman has joined #dri-devel
gawin has quit [Ping timeout: 480 seconds]
hch12907_ has quit [Ping timeout: 480 seconds]
jagan_ has quit [Remote host closed the connection]
<kisak> I'm eyeballing the newer PowerVR vulkan driver and was wondering if the hardware it covers exists in any traditional desktop/laptop or is Series6 entirely mobile-oriented and ARM only?
hch12907_ has joined #dri-devel
<bnieuwenhuizen> kisak: chromebooks (quite old ones though)
heat has joined #dri-devel
<kisak> ah okay, https://blog.imaginationtech.com/powervr-meets-google-chromebook/ has some details along those lines and it's the right generation. Thanks.
Company has joined #dri-devel
ella-0_ has joined #dri-devel
nchery has quit [Read error: Connection reset by peer]
nchery has joined #dri-devel
ella-0 has quit [Read error: Connection reset by peer]
plombo has joined #dri-devel
sdutt has joined #dri-devel
sdutt has quit [Ping timeout: 480 seconds]
jhli_ has joined #dri-devel
mdnavare_ has joined #dri-devel
rsripada_ has joined #dri-devel
aswar002_ has joined #dri-devel
Ryback_[WORK] has joined #dri-devel
sarnex has quit [Quit: Quit]
unerlige1 has joined #dri-devel
dolphin has quit [Ping timeout: 480 seconds]
Ryback_ has quit [Ping timeout: 480 seconds]
mdnavare has quit [Ping timeout: 480 seconds]
unerlige has quit [Ping timeout: 480 seconds]
aswar002 has quit [Ping timeout: 480 seconds]
jhli has quit [Ping timeout: 480 seconds]
rsripada has quit [Ping timeout: 480 seconds]
dolphin has joined #dri-devel
sarnex has joined #dri-devel
V has quit [Remote host closed the connection]
Ryback_ has joined #dri-devel
Duke`` has joined #dri-devel
V has joined #dri-devel
Ryback_[WORK] has quit [Ping timeout: 480 seconds]
dv_ has joined #dri-devel
mhenning has joined #dri-devel
hch12907 has joined #dri-devel
hch12907_ has quit [Ping timeout: 480 seconds]
hch12907_ has joined #dri-devel
mbrost has joined #dri-devel
hch12907 has quit [Ping timeout: 480 seconds]
shashank_sharma has quit [Ping timeout: 480 seconds]
maxzor has joined #dri-devel
deathmist1 has quit [Remote host closed the connection]
deathmist has joined #dri-devel
sdutt has joined #dri-devel
deathmist has quit [Remote host closed the connection]
deathmist has joined #dri-devel
flacks has quit [Quit: Quitter]
Haaninjo has joined #dri-devel
flacks has joined #dri-devel
mareko_ has quit [Ping timeout: 480 seconds]
dri-logger has quit [Ping timeout: 480 seconds]
glisse has quit [Ping timeout: 480 seconds]
glisse has joined #dri-devel
mareko has joined #dri-devel
dri-logger has joined #dri-devel
mslusarz_ has joined #dri-devel
mslusarz has quit [Ping timeout: 480 seconds]
gouchi has joined #dri-devel
gouchi has quit []
<karolherbst> what can one do if the hardware is too slow for ttm_bo_move_accel_cleanup and it times out? Just try again or?
<karolherbst> although the question is why does it timeout :)
<danvet> karolherbst, nouveau probably violating everything everwhere
<karolherbst> well
<karolherbst> we can't ramp up memory clocks
<danvet> or more specifically, your dma_fence are supposed to complete before bad things happen
<danvet> which they probably dont
<karolherbst> but I am also sure we missues the ttm API :)
<karolherbst> danvet: ohh, nothing bad happens
<karolherbst> the GPU is just slow
<karolherbst> I clcoked it up manually and things started to work
<danvet> otoh ttm should just blindly rely on your dma_fence, and not time out before those do
<danvet> karolherbst, eventually they should time out even on a slow gpu
<karolherbst> well it does hand an explicit timeout of 15 * HZ
<danvet> and ttm shouldn't have its own timeouts
<danvet> hm yeah that sounds wrong
<karolherbst> inside ttm_bo_wait
<daniels> kisak: yep, the reference hardware for the IMG Vulkan driver is the MT8183 Chromebook family
<danvet> because e.g. amgpu CS engine and amdgpu on sriov VF both have a dma_fence timeout of 60s
<danvet> karolherbst, I think we need a patch there to make that a forever timeout
<karolherbst> mhhh
<danvet> karolherbst, but also you need to make sure that there's something in nouveau which nukes jobs which take too long
<karolherbst> we fallback to software :(
<karolherbst> which makes it even worse
<danvet> we do have 60s timeout in kms, but that's because permanantly stuck kms is a shit debug experience
<danvet> not because it's really a bright idea to do that
<danvet> karolherbst, well it's fundamentally busted to have a timeout in ttm
<danvet> since that's supposed to be the driver's job
<karolherbst> right...
<karolherbst> but I am wondering if I can check for -EBUSY and retry
<danvet> that's just papering over ttm bugs with driver code
<karolherbst> ehh.. nouveau is the only user of nouveau_bo_move_m2mf
<karolherbst> ehh
<karolherbst> wrong function
<karolherbst> lol
<karolherbst> i915 handling is funny
<karolherbst> it just calls dma_fence_wait on error
rexbcchen has quit [Read error: Connection reset by peer]
rexbcchen has joined #dri-devel
<danvet> karolherbst, yeah that sounds like more driver code that shouldn't exist :-)
<karolherbst> amdgpu/radeon fallback to ttm_bo_move_memcpy as well
<karolherbst> mhhhh
<karolherbst> let me try hacking on it first though and hand it over to users, so this annoying bug is finally fixed
<karolherbst> I always suspected our fencing is busted or weirdo race conditions, but no....
<karolherbst> we are just slow
<karolherbst> at least now the android emulator runs without crashing on nv50 :)
<karolherbst> well.. doesn't seem to be perfect, but...
<karolherbst> danvet: I guess for now I'll just use whatever i915 is doing so it can get backported and we can think about some better fix, which potentially breaks stuff
<karolherbst> and push it through next and hope it's fine :D
<danvet> yeah
<cyrozap> Hi, all, I'm currently writing a DRM driver for some USB display adapters (MCT Trigger 5), and while the `/dev/dri/card1` device file gets created properly, neither X11 nor Wayland display/window managers want to recognize it. So, to try and debug this issue, I'd like to test to make sure all the API calls work properly for the device. To that end, is there a test program out there that already does
<cyrozap> this?
sdutt has quit [Ping timeout: 480 seconds]
<airlied> cyrozap: modetest from libdrm?
X512 has joined #dri-devel
<X512> Is it possible to statically link DRI drivers into libEGL_mesa.so when using libglvnd?
<cyrozap> airlied: Thanks, that'll work!
nchery is now known as Guest173
nchery has joined #dri-devel
Guest173 has quit [Read error: Connection reset by peer]
sdutt has joined #dri-devel
mbrost has quit [Ping timeout: 480 seconds]
sdutt has quit [Ping timeout: 480 seconds]
lemonzest has quit [Quit: WeeChat 3.4]
sdutt has joined #dri-devel
Anorelsan has joined #dri-devel
gouchi has joined #dri-devel
Haaninjo has quit [Quit: Ex-Chat]
mhenning has quit [Quit: mhenning]
gouchi has quit [Quit: Quitte]
maxzor has quit [Ping timeout: 480 seconds]
hch12907_ has quit [Ping timeout: 480 seconds]
jimjams has joined #dri-devel
Anorelsan has quit [Quit: Leaving]
nchery has quit [Read error: Connection reset by peer]
Duke`` has quit [Ping timeout: 480 seconds]
alanc has quit [Remote host closed the connection]
alanc has joined #dri-devel
mclasen has quit [Ping timeout: 480 seconds]
<karolherbst> danvet: yeah soo.. I think I fixed my issue with that :)
mclasen has joined #dri-devel
mbrost has joined #dri-devel
tobiasjakobi has joined #dri-devel
plombo has quit [Ping timeout: 480 seconds]
tobiasjakobi has quit []
dj-death has quit [Ping timeout: 480 seconds]
pcercuei has quit [Quit: dodo]
dj-death has joined #dri-devel
morphis has quit [Ping timeout: 480 seconds]
morphis has joined #dri-devel
danvet has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]