ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
c7s has joined #wayland
GentooPhysicist393 has joined #wayland
GentooPhysicist39 has quit [Remote host closed the connection]
Hypfer has quit [Ping timeout: 480 seconds]
WhizzWr has quit [Quit: Bye!]
ahartmetz has quit [Quit: Konversation terminated!]
maxzor has quit [Remote host closed the connection]
maxzor has joined #wayland
maxzor has quit [Remote host closed the connection]
duxsco has joined #wayland
tzimmermann has joined #wayland
naveenk2 has quit [Ping timeout: 480 seconds]
rgallaispou has joined #wayland
flacks_ has quit [Quit: Quitter]
flacks has joined #wayland
naveenk2 has joined #wayland
slattann has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
rgallaispou has quit [Read error: Connection reset by peer]
fmuellner has joined #wayland
slattann has joined #wayland
Major_Biscuit has quit [Ping timeout: 480 seconds]
Major_Biscuit has joined #wayland
duxsco has quit [Ping timeout: 480 seconds]
sstiller has joined #wayland
shankaru has quit [Quit: Leaving.]
MajorBiscuit has joined #wayland
Major_Biscuit has quit [Ping timeout: 480 seconds]
slattann has quit [Ping timeout: 480 seconds]
duxsco has joined #wayland
rgallaispou has joined #wayland
shankaru has joined #wayland
duxco has joined #wayland
duxsco has quit [Read error: Connection reset by peer]
duxco is now known as duxsco
ManMower has quit [Read error: Connection reset by peer]
ManMower has joined #wayland
duxsco has quit [Quit: duxsco]
ppascher has quit [Ping timeout: 480 seconds]
ppascher has joined #wayland
pnowack has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #wayland
sstiller has quit [Quit: Leaving]
agd5f has quit [Read error: Connection reset by peer]
agd5f has joined #wayland
<pq>
shashanks, no, NULL blob as GAMMA or any other LUT is defined to be identity pass-through. It's up to the driver to ensure the hardware gets what it needs to realize that.
<pq>
emersion, thank you very much for the new repo!
<shashanks>
pq: I was talking about NULL gamma, not NULL blob
<pq>
It's actually good that you "hosted" it, because filing MRs against your own project is awkward. You can't clone something that is already in your personal namespace.
<pq>
*fork
<pq>
shashanks, what's the difference? The GAMMA API only takes a blob id, AFAIK.
<shashanks>
A NULL blob is still a valid blob, with 0 values for gamma LUT. This will blank the CRTC output on Intel and AMD
<pq>
oh, the legacy gamma API actually takes pointers
<shashanks>
* NULL gamma blob
<shashanks>
Yep, CRTC gamma is still the old one
<pq>
I would not call that "NULL blob". A NULL blob is blob ID 0.
<pq>
A LUT with all-zero entries is so special and rare that it never even occurred to me someone might use it, or even name it.
<pq>
c.f. "NULL pointer"
<shashanks>
We wrote some IGTs to test the gamma boundary conditions, that used to have a NULL gamma blob, A max gamma blob, and a green only, red only and blue only blobs. It might be still existing.
<kennylevinsen>
And such a LUT with all zeroes would be an explicit request to make all possible input values result in black, so nothing surprising in what AMD and Intel does there...
<pq>
shashanks, I see your access request to libdisplay-info, but if you don't mind, I'd like to wait with accepting that until you have created and landed a merge request first.
<shashanks>
pq: really ?
<pq>
shashanks, this is just to ensure you get familiar with the contribution process, e.g. cannot accidentally push a branch into the upstream repository.
<pq>
or accidentally push something to main
<pq>
shashanks, even when you get Developer access, that would not change how you contribute. You still push branches to your own fork, create MR upstream, and wait for reviews.
<pq>
Developer access only means you can push the merge button yourself, after you got positive review.
<pq>
I'll have a look at the MRs Simon created tomorrow. If they don't already contain contribution guidelines, I might propose some, similar to what color-and-hdr has.
<emersion>
pq, i've been lazy and i've just linked to the wayland contribution guidelines
<emersion>
pq, no problem!
<pq>
heh, cool
<emersion>
we can import these guidelines if need be, or even write our owns, but i figured it would be a pretty uncontroversial take to start things off
<pq>
sure
<pq>
shashanks, are you ok? This is really just to get the process right, not having Developer access protects you from pushing into a wrong repository at first.
<shashanks>
I guess I am just having a bad day today, will call it an early day.
shashanks has quit [Quit: Leaving]
caseorum has joined #wayland
jgrulich has quit [Ping timeout: 480 seconds]
naveenk2 has quit []
rgallaispou has left #wayland [#wayland]
Major_Biscuit has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
caseorum has left #wayland [#wayland]
<emersion>
thanks for the comments swick!
<swick>
thanks for doing everything else :P
<swick>
hope the others chime in as well
<swick>
and I really want to get rid of the EDID code in mutter ;)
<emersion>
ahah
<emersion>
what's the EDID used for in mutter rn? the usual vendor/product/serial? anything else?
<swick>
the usual basic block stuff
<swick>
but for HDR that's changing
<emersion>
right
<swick>
also ICC profile generation is moving from g-c-c to mutter
duxsco has joined #wayland
ecloud has quit [Ping timeout: 480 seconds]
zebrag has joined #wayland
ecloud has joined #wayland
unknown__ has joined #wayland
shankaru has quit [Quit: Leaving.]
creich_ has quit [Ping timeout: 480 seconds]
kenny has joined #wayland
___nick___ has joined #wayland
colordrops has joined #wayland
___nick___ has quit []
___nick___ has joined #wayland
jmdaemon has joined #wayland
duxsco has quit [Remote host closed the connection]
duxsco has joined #wayland
slumm has joined #wayland
slumm has left #wayland [#wayland]
agd5f has quit [Remote host closed the connection]