ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
unevenrhombus[m] has joined #dri-devel
tzimmermann has quit [Ping timeout: 480 seconds]
gnustomp[m] has joined #dri-devel
T_UNIX has joined #dri-devel
zamundaaa[m] has joined #dri-devel
nchery has quit [Ping timeout: 480 seconds]
nchery has joined #dri-devel
ngcortes has quit [Remote host closed the connection]
dllud_ has joined #dri-devel
dllud has quit [Read error: Connection reset by peer]
sdutt has quit [Ping timeout: 480 seconds]
dllud has joined #dri-devel
dllud_ has quit [Read error: Connection reset by peer]
JosExpsito[m] has joined #dri-devel
Andy[m] has joined #dri-devel
reactormonk[m] has joined #dri-devel
jekstrand[m] has joined #dri-devel
<karolherbst>
okay..... let's get cracking.......
rpigott has quit [Ping timeout: 480 seconds]
mhenning has quit [Quit: mhenning]
mhenning has joined #dri-devel
<karolherbst>
don't we have like int8 lowering?
<karolherbst>
lower_bit_size
nchery has quit [Ping timeout: 480 seconds]
adjtm is now known as Guest11
adjtm has joined #dri-devel
Guest11 has quit [Ping timeout: 480 seconds]
co1umbarius has joined #dri-devel
columbarius has quit [Ping timeout: 480 seconds]
chivay has joined #dri-devel
<graphitemaster>
Can someone explain to me what these OpenGL warnings mean. I'm so confused and Google shows up nothing.
<graphitemaster>
"Pixel-path detailed info: The current pixel-path operation converts data from 2-bit integer to 1-bit integer, and may exhibit data loss"
<graphitemaster>
There's another that does 4-bit to 1-bit immediately after and it's when calling glNamedFramebufferDrawBuffer
kallisti5[m] has joined #dri-devel
icecream95 has quit [Remote host closed the connection]
icecream95 has joined #dri-devel
bmodem has joined #dri-devel
Wally has joined #dri-devel
heat has quit [Remote host closed the connection]
heat has joined #dri-devel
mbrost_ has joined #dri-devel
mbrost has quit [Read error: Connection reset by peer]
Wally has quit [Remote host closed the connection]
Wally has joined #dri-devel
<airlied>
tomeu: the build tasks seem to be failing due to git am failing
Wally has quit [Remote host closed the connection]
OftenTimeConsuming has quit [Remote host closed the connection]
OftenTimeConsuming has joined #dri-devel
mbrost_ has quit [Ping timeout: 480 seconds]
neobrain[m] has joined #dri-devel
egalli has joined #dri-devel
sigmoidfunc[m] has joined #dri-devel
neonking has joined #dri-devel
mbrost has joined #dri-devel
danvet has joined #dri-devel
Duke`` has joined #dri-devel
mclasen has quit [Ping timeout: 480 seconds]
Sheilabillyinvest[m] has joined #dri-devel
unrelentingtech has joined #dri-devel
mbrost has quit [Ping timeout: 480 seconds]
mbrost has joined #dri-devel
<tomeu>
airlied: looks like there are stale files in the git checkout in that builder, will add code to start from a cleaner state
jasuarez has joined #dri-devel
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
thaytan has quit [Ping timeout: 480 seconds]
mhenning has quit [Quit: mhenning]
<airlied>
danvet: is there some fbdev patches I was meant to get for fixes do you remember? I pinged people earlier, but might be good to get them to Linus if they are sitting somewhere
mszyprow has joined #dri-devel
dj-death has joined #dri-devel
itoral has joined #dri-devel
mvlad has joined #dri-devel
itoral has quit [Remote host closed the connection]
itoral has joined #dri-devel
<tomeu>
airlied: should work now
sdutt has joined #dri-devel
Duke`` has quit [Ping timeout: 480 seconds]
lemonzest has joined #dri-devel
Sheilabillyinvest[m] has quit [autokilled: This host violated network policy and has been banned. Mail support@oftc.net if you think this is in error. (2022-05-13 06:07:05)]
Daanct12 has joined #dri-devel
plombo has quit [Ping timeout: 480 seconds]
Daanct12 has quit [Read error: Connection reset by peer]
<javierm>
airlied: yes, the fbdev patches in drm-misc-fixes are supposed to go in this -rc cycle
<javierm>
tzimmermann: sure, I'll take a look at them later today
<airlied>
mlankhorst: can you send a PR for that asap?
icecream95 has quit [Quit: rcirc on GNU Emacs 28.1]
<airlied>
mripard: or if you could
<danvet>
airlied I guess mlankhorst forgot to send you the -fixes pull, they're in there waiting
<danvet>
ah should have scrolled down
dj-death has joined #dri-devel
dj-death has quit [Ping timeout: 480 seconds]
tursulin has joined #dri-devel
mbrost has quit [Ping timeout: 480 seconds]
Daanct12 has quit [Quit: Leaving]
morphis has quit [Read error: No route to host]
morphis has joined #dri-devel
Daanct12 has joined #dri-devel
i-garrison has quit [Ping timeout: 480 seconds]
neonking has quit [Remote host closed the connection]
neonking has joined #dri-devel
lynxeye has joined #dri-devel
dj-death has joined #dri-devel
dj-death_ has joined #dri-devel
ahajda has joined #dri-devel
rasterman has joined #dri-devel
gouchi has joined #dri-devel
gpiccoli has quit [Quit: Bears...Beets...Battlestar Galactica]
gouchi has quit [Remote host closed the connection]
gpiccoli has joined #dri-devel
Haaninjo has joined #dri-devel
pcercuei has joined #dri-devel
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]
<tjaalton>
is there anything intel/anv specific in intel-nullhw layer? at least I couldn't find any
bmodem has joined #dri-devel
nchery has joined #dri-devel
FireBurn has joined #dri-devel
rkanwal has joined #dri-devel
thaytan has joined #dri-devel
guru_ has joined #dri-devel
bmodem has quit [Ping timeout: 480 seconds]
oneforall2 has quit [Ping timeout: 480 seconds]
i-garrison has joined #dri-devel
flacks has quit [Quit: Quitter]
flacks has joined #dri-devel
jagan_ has joined #dri-devel
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #dri-devel
sdutt has quit [Ping timeout: 480 seconds]
icecream95 has joined #dri-devel
mclasen has joined #dri-devel
gawin has joined #dri-devel
mszyprow_ has joined #dri-devel
gawin has quit [Ping timeout: 480 seconds]
mszyprow has quit [Ping timeout: 480 seconds]
tobiasjakobi has joined #dri-devel
tobiasjakobi has quit [Remote host closed the connection]
jagan_ has quit [Remote host closed the connection]
<javierm>
tzimmermann: I'll push then the patch you mentioned, but I'll add to the commit message a paragraph explaining that it's also safer to drop the lock than calling drivers' .remove callbacks with a lock held
<javierm>
tzimmermann: since the core can't really control what the drivers do on removal
<tzimmermann>
ok, sure
<javierm>
tzimmermann: and thanks for the thoughtful answer
i-garrison has quit [Remote host closed the connection]
i-garrison has joined #dri-devel
<tzimmermann>
i was thinking that we might have appraoched the problem from the wrong direction
<tzimmermann>
managing ownership at the device-level migth be an approach
<javierm>
tzimmermann: yeah
<javierm>
tzimmermann, danvet: I wonder if we shouldn't just revert commit fb561bf9abde ("fbdev: Prevent probing generic drivers if a FB is already registered") and push danvet's fbdev patches
<javierm>
even before fixing this race. It's really a corner case
<tzimmermann>
javierm, maybe if you want to comment on my reply, i'd really like to here your take on it
<javierm>
tzimmermann: I already did. Didn't hit the list yet ?
<tzimmermann>
ah, there it is
jagan_ has joined #dri-devel
<javierm>
tzimmermann: so I think we should make sysfb, dt, etc to devm_aperture_acquire_from_firmware() and make the detach callback more generic and operate on a struct device instead of a struct drm_device
<tomeu>
robclark: danvet: airlied: not sure what to do with the checkpatch job not that we have moved up to the drm subsys, I need a way to know the target branch, so I can check the right commits
<tomeu>
guess we could come up with a convention based on the branch name
<tzimmermann>
javierm, sounds good
<tzimmermann>
javierm, i'm making a replacement for offb. i can fill the firmware FB manually. but the DRM framework doesn't want to. i don't know why yet
<javierm>
tzimmermann: oh, interesting
mszyprow_ has quit [Ping timeout: 480 seconds]
Daanct12 has quit [Quit: Leaving]
<tzimmermann>
it's mostly the same code as in simpledrm, but for different DT nodes. it's most certainly some really stupid bug
<javierm>
since I'm already doing a push, I would like to add that one too
<tzimmermann>
javierm, a-b: tzimmermann
<javierm>
I noticed when posting the fbdev fixes since was building for aarch64
<javierm>
tzimmermann: thanks!
<danvet>
tomeu, only check what's not yet in linux-next?
<danvet>
not perfect, but maybe good enough in practice ...
<danvet>
tomeu, or make checkpatch a warning level thing only
* danvet
not a big fan of that bikeshed
<danvet>
tomeu, maybe if "not in linux-next" isn't good enough you could manually encode the drm pull train
<danvet>
i.e. exclude drm-next/fixes if it's not drm.git
<danvet>
and for drm.git, exclude linus' tree
<danvet>
it's a bit manual but not the worst
ppascher has quit [Ping timeout: 480 seconds]
itoral has quit [Remote host closed the connection]
rdltromw^ has joined #dri-devel
ppascher has joined #dri-devel
devilhorns has joined #dri-devel
dj-death has quit [Ping timeout: 480 seconds]
dj-death has joined #dri-devel
<robclark>
danvet: the checkpatch job only enables a limited # of commit-msg checks.. things like valid fixes tags, which dim also checks
<robclark>
tomeu: perhaps you could check for first patch that doesn't touch any files in drm?
ondracka has joined #dri-devel
<ondracka>
How do I fix "deqp-gles2: undefined symbol: glGetInternalformativ"?
devilhorns has quit [Remote host closed the connection]
devilhorns has joined #dri-devel
<danvet>
robclark, ah ok
devilhorns has quit []
<danvet>
robclark, first patch that doesn't touch any drm files
<danvet>
is probably too much
<danvet>
if you have a drm-next backmerge in your tree e.g.
<danvet>
also too little because dma-buf :-)
<danvet>
iirc dim uses --first-parent and then excludes what's already there
<danvet>
for that linux-next might be good
<danvet>
or hard-coded upstream pull train (it's only two levels so not that awful)
devilhorns has joined #dri-devel
sdutt has joined #dri-devel
<mlankhorst>
airlied: will send, probably too late
<mlankhorst>
forgot to actually send it after merging rc6
<robclark>
danvet, tomeu: I guess copying what dim does isn't horrible? This is really just for non-MR fallback (when there is an MR gitlab tells us the base commit).. and I guess in the !MR case we can make that job only warn instead of fail, in case it gets it wrong?
bmodem has quit []
devilhorns has quit []
ella-0 has joined #dri-devel
ella-0_ has quit [Read error: Connection reset by peer]
jfalempe has quit [Quit: Leaving]
tzimmermann has quit [Quit: Leaving]
heat has joined #dri-devel
guru_ has quit []
oneforall2 has joined #dri-devel
hch12907 has joined #dri-devel
hch12907_ has joined #dri-devel
hch12907 has quit [Ping timeout: 480 seconds]
jfalempe has joined #dri-devel
hch12907__ has joined #dri-devel
bmodem has joined #dri-devel
hch12907_ has quit [Ping timeout: 480 seconds]
hch12907_ has joined #dri-devel
Wally has joined #dri-devel
mbrost has joined #dri-devel
hch12907__ has quit [Ping timeout: 480 seconds]
hch12907 has joined #dri-devel
hch12907_ has quit [Ping timeout: 480 seconds]
Wally has quit [Remote host closed the connection]
hch12907 has quit [Read error: Connection reset by peer]
hch12907 has joined #dri-devel
Wally has joined #dri-devel
hch12907_ has joined #dri-devel
Android has joined #dri-devel
Android is now known as Guest66
hch12907__ has joined #dri-devel
bmodem has quit []
bmodem has joined #dri-devel
hch12907 has quit [Ping timeout: 480 seconds]
ppascher has quit [Ping timeout: 480 seconds]
hch12907_ has quit [Ping timeout: 480 seconds]
mclasen has quit []
dllud_ has joined #dri-devel
dllud has quit [Read error: Connection reset by peer]
bmodem has quit [Ping timeout: 480 seconds]
dllud has joined #dri-devel
dllud_ has quit [Read error: Connection reset by peer]
<agd5f>
is there a reason __drm_mode_object_add() uses idr_alloc() rather than idr_alloc_cyclic()?
mclasen has joined #dri-devel
<karolherbst>
old passively cooled GPUs are seriously dangerous
Duke`` has joined #dri-devel
Wally has quit [Remote host closed the connection]
kts has joined #dri-devel
ahajda has quit [Ping timeout: 480 seconds]
gouchi has joined #dri-devel
gouchi has quit [Remote host closed the connection]
karolherbst has quit [Remote host closed the connection]
karolherbst has joined #dri-devel
heat has quit [Remote host closed the connection]
Ryback_ has quit [Remote host closed the connection]
Ryback_ has joined #dri-devel
heat has joined #dri-devel
ramaling has quit [Remote host closed the connection]
ramaling has joined #dri-devel
sdutt has quit [Ping timeout: 480 seconds]
sdutt has joined #dri-devel
sdutt has quit [Ping timeout: 480 seconds]
sdutt has joined #dri-devel
jagan_ has joined #dri-devel
Wally has joined #dri-devel
jagan_ has quit [Remote host closed the connection]
Wally has quit [Remote host closed the connection]
lynxeye has quit [Quit: Leaving.]
sdutt has quit [Ping timeout: 480 seconds]
<jekstrand>
bnieuwenhuizen: Any way I can get a command stream and descriptor dump out of RADV?
<bnieuwenhuizen>
RADV_DEBUG=hang ?
<bnieuwenhuizen>
should be a directory in your homedir after a hang
dj-death has quit [Ping timeout: 480 seconds]
<graphitemaster>
I'm curious, for those of you doing hardware bringup device stuff, like the m1 reverse engineering and what not, how often is it to brick a gpu these days?
<jekstrand>
Totally brick? That's pretty hard. Hang and have to reboot? Hopefully not often. Hang up the system for a few seconds? All the time.
<graphitemaster>
like, has the fail safes for these devices gotten quite good or is it still possible to write code that just kills a gpu permanently
<karolherbst>
graphitemaster: would it help you that it's not known that anybody ever bricked an nvidia gpu working on nouveau?
<bnieuwenhuizen>
jekstrand: for some of us the second and third are really the same thing since GPU reset doesn't work :(
<jekstrand>
graphitemaster: It's really hard to brick a GPU.
<graphitemaster>
wow, i'm very surprised because as a non-driver developer i have bricked a gpu
<karolherbst>
what did you do?
<jekstrand>
You might brick your M1 by running sketchy bootloaders or something, but you won't brick the GPU.
<jekstrand>
I mean, maybe if you upload a REALLY bad firmware....
<jekstrand>
bnieuwenhuizen: What directory? I'm not seeing anything with "radv" or "hang" in the name.
<karolherbst>
I'd say the most likely thing to happen is overheating the GPU and causing physical damage, but then you still need to know what to do to actually prevent the GPU from not shutting itself
<karolherbst>
*down
<jekstrand>
bnieuwenhuizen: What I really want to do is compare batches and states from a good run with the busted one so I can figure out what wrong.
<jekstrand>
bnieuwenhuizen: I'm getting faults on my "use vk_image_view" branch.
<karolherbst>
on nvidia you can configure thermal thresholds (which are defaulted to something sany by the vbios) for extra protection
<graphitemaster>
i reverse engineered evga's precision x software to figure out nvapi and it's realtime reclocking stuff with the intention of automatically overclocking a gpu when someone ran my program, and i discovered forcing the clocks up and down fast totally kills 900 series gpus
<karolherbst>
graphitemaster: could have burned the GPU with that
<jekstrand>
graphitemaster: Oh, sure. If you cause massive thermal expansion and contraction, that can totally brick the hardware. You can break solder connections etc.