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
ahartmetz has quit [Quit: Konversation terminated!]
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
slattann has joined #wayland
eroux has joined #wayland
Company has quit [Quit: Leaving]
tm512 has quit [Server closed connection]
emersion has quit [Server closed connection]
emersion has joined #wayland
vyivel has quit [Server closed connection]
vyivel has joined #wayland
bl4ckb0ne has quit [Server closed connection]
bl4ckb0ne_ has joined #wayland
jekstrand has quit [Server closed connection]
jekstrand has joined #wayland
rektide has quit [Server closed connection]
rektide has joined #wayland
dri-logger has quit [Server closed connection]
dri-logger has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
glisse has quit [Server closed connection]
glisse has joined #wayland
ManMower has quit [Server closed connection]
ManMower has joined #wayland
quantum5 has quit [Server closed connection]
quantum5 has joined #wayland
yongxiang__ has quit [Server closed connection]
yongxiang__ has joined #wayland
Cwiiis_ has quit [Server closed connection]
Cwiiis_ has joined #wayland
evon377 has quit [Server closed connection]
evon377 has joined #wayland
naveenk2 has joined #wayland
tlwoerner has quit [Server closed connection]
tlwoerner has joined #wayland
nurupo has quit [Server closed connection]
nurupo has joined #wayland
novakane has quit [Server closed connection]
novakane has joined #wayland
kennylevinsen has quit [Server closed connection]
kennylevinsen has joined #wayland
elibrokeit has quit [Server closed connection]
elibrokeit has joined #wayland
dnkl has quit [Server closed connection]
dnkl has joined #wayland
Guest2117 has quit [Server closed connection]
raghavgururajan has joined #wayland
raghavgururajan is now known as Guest2810
milesrout has quit [Server closed connection]
milesrout has joined #wayland
leon-p has quit [Server closed connection]
leon-p has joined #wayland
abcdw has quit [Server closed connection]
abcdw has joined #wayland
sumoon has quit [Server closed connection]
sumoon has joined #wayland
slattann has quit []
patwid has quit [Server closed connection]
patwid has joined #wayland
ifreund has quit [Server closed connection]
ifreund has joined #wayland
staceee has quit [Server closed connection]
staceee has joined #wayland
zebrag has quit [Quit: Konversation terminated!]
slattann has joined #wayland
reillybrogan_ has quit [Server closed connection]
reillybrogan has joined #wayland
slattann has quit []
Arnavion has quit [Server closed connection]
ecloud has quit [Ping timeout: 480 seconds]
Arnavion has joined #wayland
agd5f has quit [Server closed connection]
agd5f has joined #wayland
dcz has joined #wayland
ecloud has joined #wayland
pnowack has joined #wayland
jgrulich has joined #wayland
danvet has joined #wayland
anarsoul has quit [Server closed connection]
anarsoul has joined #wayland
rpigott has quit [Server closed connection]
rpigott has joined #wayland
soreau has quit [Server closed connection]
soreau has joined #wayland
flacks has quit [Server closed connection]
pochu has joined #wayland
flacks has joined #wayland
hardening has joined #wayland
dontlaugh has quit [Server closed connection]
dontlaugh has joined #wayland
ofourdan has quit [Quit: leaving]
mvlad has joined #wayland
ofourdan has joined #wayland
radu242 has quit [Server closed connection]
radu242 has joined #wayland
Major_Biscuit has joined #wayland
tzimmermann has joined #wayland
Major_Biscuit has quit [Ping timeout: 480 seconds]
<any1>
This thing has started gathering some dust... :)
<rgallaispou>
hi. Is there any way to test gamma correction on wayland-weston ? (not looking for igt here, which is only based on libdrm)
WhizzWr has quit [Server closed connection]
WhizzWr has joined #wayland
bluebugs has quit [Server closed connection]
bluebugs has joined #wayland
slattann1 has joined #wayland
slattann has quit [Ping timeout: 480 seconds]
pieguy128 has quit [Server closed connection]
caseif has quit [Server closed connection]
caseif has joined #wayland
pieguy128 has joined #wayland
<rgallaispou>
"drm_output_set_gamma" in the drm backend eventually leads me to the cms-helper in the compositor
wangledorf_____ has quit [Server closed connection]
wangledorf_____ has joined #wayland
daz has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
melissawen has quit [Server closed connection]
melissawen has joined #wayland
naveenk2 has left #wayland [#wayland]
d42 has joined #wayland
caveman has joined #wayland
jpnurmi has quit [Server closed connection]
jpnurmi has joined #wayland
<pq>
rgallaispou, what do you mean by "gamma correction"?
mcf has quit [Server closed connection]
mcf has joined #wayland
<pq>
rgallaispou, the only support for the KMS legacy gamma UAPI in Weston is limited to what you found: loading a VCGT from an ICC profile and setting that up as the gamma table.
<pq>
I don't know of anything or anyone testing that feature, so it might as well be broken too.
<pq>
by accidental, not on purpose
rgallaispou has quit [Read error: Connection reset by peer]
davidre has quit [Server closed connection]
davidre has joined #wayland
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
d42 has quit [Ping timeout: 480 seconds]
sychill has quit [Server closed connection]
sychill has joined #wayland
caveman has quit [Remote host closed the connection]
duxsco has quit [Quit: duxsco]
maxzor has quit [Ping timeout: 480 seconds]
dreda has quit [Server closed connection]
dreda has joined #wayland
dreda is now known as Guest6
d42 has joined #wayland
duxsco has joined #wayland
slattann1 has quit [Ping timeout: 480 seconds]
tzimmermann has quit [Quit: Leaving]
fmuellner has quit []
fmuellner has joined #wayland
rgallaispou has joined #wayland
<rgallaispou>
pq: I meant the gamma applied on a pipe after the degamma/CSC transformation (which are not supported on my hardware), directly within the crtc
Satan7 has quit [Server closed connection]
Satan7 has joined #wayland
bodiccea has quit [Server closed connection]
bodiccea has joined #wayland
AJ_Z0 has quit [Server closed connection]
AJ_Z0 has joined #wayland
<rgallaispou>
pq: doing so won't pass the gamma lut to the gpu instead of the crtc ?
slattann has joined #wayland
Lyude has quit [Server closed connection]
Lyude has joined #wayland
rgallaispou has left #wayland [#wayland]
rgallaispou has joined #wayland
Company has joined #wayland
lagash has quit [Server closed connection]
lagash has joined #wayland
<rgallaispou>
sorry, I disconnected... wrong shortcut
fmuellner has quit []
fmuellner has joined #wayland
adia has quit [Server closed connection]
adia has joined #wayland
Seirdy has quit [Server closed connection]
Seirdy has joined #wayland
Shimmy0 has quit [Server closed connection]
Shimmy0 has joined #wayland
creich has quit [Server closed connection]
creich has joined #wayland
<pq>
rgallaispou, KMS API affects the display hardware pipeline, not a GPU, so yes.
erc_ has quit [Server closed connection]
<pq>
rgallaispou, you are looking at the right API, but in order to use it Weston, you'd have to hack on weston or craft an ICC profile with the LUT you want in the VCGT tag.
erc_ has joined #wayland
slattann has quit [Ping timeout: 480 seconds]
<rgallaispou>
pq: yes, that's what I thought
<rgallaispou>
pq: okay, I had the feeling that I was heading toward a hacky profile
<hardening>
playing with libweston, I'm figuring that there seems to have something rotten with the wet_compositor struct: it is defined "privately" in weston/compositor/main.c, but weston modules use it indirectly by calling wet_get_config
<hardening>
like in ivi-shell.c:386
<hardening>
so if you wanna use libweston and use weston shells you have to have exactly the same wet_compositor definition
rektide has quit [Server closed connection]
rektide has joined #wayland
<daniels>
hardening: if you're using libweston, you need to stick what's in libweston/ and include/libweston/
<daniels>
not the frontend bits which are in compositor/
<daniels>
compositor/ is only for the binary called 'weston'
<daniels>
libweston is a stable API defined by libweston.so.*, the libweston/ source folders, and the headers in include/libweston/ and include/libweston-desktop/
<hardening>
thank you for the link, I was just about to ask for a project that was using libweston
<daniels>
weston is a binary which uses libweston, adding things like a configuration interface, another plugin interface, pluggable UI 'shells', output management, etc
<daniels>
anything which is not defined in include/libweston/ or include/libweston-desktop/ or present in libweston/ or libweston-desktop/ and libweston.so, is not a part of libweston
<daniels>
(ivi-shell is not a good example of anything btw)
<hardening>
ok so libweston is just about backend then
<daniels>
it's the backend and renderer, input, core surface management, etc
<daniels>
anything which is required to work rather than being policy per se
<daniels>
then policy is provided by the frontend (either weston + shells, or any other libweston user)
<daniels>
e.g. window management, output configuration
<hardening>
agl compositor is interesting, I did quite the same job of coyping the needed code from weston
<hardening>
I should have asked before that would have saved my time
creich_ has joined #wayland
reillybrogan has quit [Server closed connection]
reillybrogan has joined #wayland
caveman has joined #wayland
jgrulich has quit [Ping timeout: 480 seconds]
duxsco has joined #wayland
creich has quit [Ping timeout: 480 seconds]
Arnavion has quit [Server closed connection]
Arnavion has joined #wayland
<LaserEyess>
for drm leasing, what actually determines if a connector is leaseable?
<LaserEyess>
can any connectors be leased? even ones currently in use by the compositor?
agd5f has quit [Server closed connection]
agd5f has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
<LaserEyess>
been trying to read the whole protocol but don't fully understand the nuance of the DRM terminology
<LaserEyess>
it kind of seems like it's up to the compositor to determine what is leaseable
<LaserEyess>
so in theory you could lease a regular monitor, but maybe some compositors don't allow that?
soreau has quit [Server closed connection]
soreau has joined #wayland
<emersion>
yes
<emersion>
compositor policies restrict DRM leasing to VR headsets
<emersion>
for good reason
<LaserEyess>
what good reason
<LaserEyess>
I mean, besides obviously that monitor is in use
<LaserEyess>
but say if it was "reserved" through some mechanism to be leaseable
<LaserEyess>
also, somewhat unrelated, but how does it know it's a VR headset?
<emersion>
there aren't good use-cases for DRM leasing apart from VR headsets
radu242 has quit [Server closed connection]
<emersion>
with DRM leasing you don't get any more input events
<LaserEyess>
I had one, though sketchy at best
radu242 has joined #wayland
<LaserEyess>
a sort of "exclusive fullscreen" type thing
<emersion>
most use-cases are around trying to re-implement direct scan-out which is already in the compositor
<LaserEyess>
it would also allow clients to do HDR, since that is at best years away
<LaserEyess>
years away in wayland*
<emersion>
instead of working around the compositor, what about doing things right?
<emersion>
HDR which only works in fullscreen doesn't seem great user experience
<LaserEyess>
well, two answers to that: 1) windows-like exclusive fullscreen is not implementable, and will never be, on wayland
<emersion>
why do you need "exclusive fullscreen"?
<LaserEyess>
2) HDR and color management in general is complex and currently stalled on wayland
<emersion>
not stalled, actively worked on
<emersion>
and help is welcome i'm sure
<LaserEyess>
I'm not disagreeing that the correct way is a protocol to handle CM/HDR and allow the compositor to handle it and clients to send metadata
<LaserEyess>
I'm saying that you could, right now, lease a monitor for a full screen video and allow that video player to use DRM to send HDR metadata
<emersion>
and you could, right now, run a video player directly on KMS
<LaserEyess>
yes that's right, and mpv does that
<emersion>
that's fine for some use-cases
<LaserEyess>
but it would be nice to do it from my compositor
<LaserEyess>
I acknowledge it is a hack
<LaserEyess>
but I see nothing in the drm lease protocol that prevents it
<emersion>
that's correct, nothing prevents it
<emersion>
up to compositors
<LaserEyess>
and wlroots doesn't do it for monitors :')
<LaserEyess>
well, that answers that I guess
<emersion>
wlroots doesn't care either
<LaserEyess>
oh?
<emersion>
sway/etc decide what to lease
<LaserEyess>
ah, right, well, sway doesn't then
<LaserEyess>
as for "why would you want exclusive fullscreen", well I think in 99% of cases I would not care at all, but it is an interesting use case
<emersion>
i don't understand what you get with "exclusive fullscreen", and don't get with regular fullscreen
<LaserEyess>
I know some windows users who swear by it, but tbh fullscreen with direct scanout is 99% of what exclusive fullscreen does
<LaserEyess>
emersion: pretty much the ability to modeset, that's it
<LaserEyess>
but as I said I don't care, I'm just curious if drm lease could enable that usecase
<emersion>
oh yeah black screens for seconds when sswitching betweens apps, yay
<LaserEyess>
and it sounds like the answer is "yes it can, but why?" which is fair
<LaserEyess>
yes I figure that would be a side effect
<emersion>
i wouldn't be against a config option to make an arbitrary output available for lease, i think, but it may be more complicated because the compositor needs to give up rendering on said output right before leasing to clients, and restart when the client destroys the lease
<emersion>
so not sure it's really worth the complexity
<LaserEyess>
I think in niche setups it would be useful
<LaserEyess>
but right now the only real niche I can think of is HDR passthrough
<emersion>
the compositor uses the KMS non_desktop prop to recognize VR headsets
<LaserEyess>
which, again, will be eventually solved within wayland itself
eroux has quit [Server closed connection]
eroux has joined #wayland
remanifest has joined #wayland
Guest2810 has quit [Server closed connection]
raghavgururajan has joined #wayland
raghavgururajan is now known as Guest35
staceee has quit [Server closed connection]
staceee has joined #wayland
pnowack has quit [Server closed connection]
pnowack has joined #wayland
pochu has quit [Server closed connection]
pochu has joined #wayland
hardening has quit [Server closed connection]
hardening has joined #wayland
ahartmetz has quit [Server closed connection]
ecloud has quit [Server closed connection]
ecloud has joined #wayland
ahartmetz has joined #wayland
<emersion>
zamundaaa: thanks for handling that fractional scaling discussion…!
remanifest has quit []
Guest6 is now known as dreda
rgallaispou has quit [Read error: Connection reset by peer]
mergen has joined #wayland
pochu has quit [Quit: leaving]
luc4 has joined #wayland
erc_ has quit []
erc has joined #wayland
d42 has quit [Read error: Connection reset by peer]
tzimmermann has joined #wayland
zebrag has joined #wayland
dontlaugh has quit [Quit: Leaving]
spstarr has joined #wayland
c7s has joined #wayland
d42 has joined #wayland
maxzor has joined #wayland
maxzor has quit [Remote host closed the connection]
maxzor has joined #wayland
mergen has quit []
tzimmermann has quit [Quit: Leaving]
<swick>
LaserEyess: I'm pretty sure some kind of HDR support will materialize this year
<swick>
KMS connectors have a "non-desktop" property and the kernel just sets is based on the EDID (don't ask me why this needed to be a KMS property…)
<swick>
for mutter I plan on marking displays as non-desktop in the monitors.xml file, mainly for testing display features like HDR
pnowack has quit [Quit: pnowack]
<LaserEyess>
swick: I would love to believe that
<LaserEyess>
well, that was rude
<LaserEyess>
I appreciate the work you've done on it, and are continuing to do, and I know it's a hard problem
<swick>
no worries, the trick here is to get HDR working without the whole color management mess
<swick>
eventually that should converge again but taking that shortcut should give us something to work with
rasterman has quit [Quit: Gettin' stinky!]
fmuellner has quit [Ping timeout: 480 seconds]
maxzor has quit [Ping timeout: 480 seconds]
pnowack has joined #wayland
<swick>
pq: I've been looking at the EDID mess and I don't really understand why we're trying to use edid-decode. it seems focused on dumping the edid, littered with printf, no support for quirks, no high level interface but also throws away parsed extension data
<swick>
definitely a handy tool and some a good collection of EDIDs to test again but to me it seems like writing a new library would be easier
mvlad has quit [Remote host closed the connection]
<emersion>
that was my impression as well
trashing has joined #wayland
trashing has left #wayland [#wayland]
<swick>
we also might want to start collecting EDIDs somehow
<emersion>
there is edid.tv with a collection
<emersion>
i _think_ i grab EDIDs in drmdb
<swick>
neat
<emersion>
hm, no, it gets stripped :/
<emersion>
actually it doesn't get stripped, but drm_info doesn't include it
<emersion>
iirc I asked them and they just said "write a script"
caveman has quit [Ping timeout: 480 seconds]
<emersion>
ah nice
spstarr has quit []
pnowack has quit [Quit: pnowack]
duxco has joined #wayland
duxsco has quit [Ping timeout: 480 seconds]
duxco is now known as duxsco
ahartmetz has quit [Remote host closed the connection]
ahartmetz has joined #wayland
maxzor has joined #wayland
danvet has quit [Ping timeout: 480 seconds]
flacks has quit [Ping timeout: 480 seconds]
dcz has quit [Ping timeout: 480 seconds]
maxzor has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
luc4 has quit []
flacks has joined #wayland
ofourdan has quit [Ping timeout: 480 seconds]
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
WhyNotHugo has joined #wayland
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
fmuellner has quit [Remote host closed the connection]
<WhyNotHugo>
If a client tries to resize itself, can the compositor in any way indicate to it that this is not possible (or that the resize won't happen)?