ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
melnary has quit [Remote host closed the connection]
melnary has joined #wayland
_rgallaispou has joined #wayland
rgallaispou has quit [Ping timeout: 480 seconds]
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
fmuellner has quit [Ping timeout: 480 seconds]
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
kabaka has joined #wayland
kabaka is now known as Guest9450
kts has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
kts has quit [Quit: Leaving]
mxz_ has joined #wayland
adamtajti has joined #wayland
mxz has quit [Ping timeout: 480 seconds]
mxz__ has quit [Ping timeout: 480 seconds]
mxz_ is now known as mxz
atticf has quit [Remote host closed the connection]
atticf has joined #wayland
bluetail has quit []
bluetail has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
kts has joined #wayland
_whitelogger_ has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
vincejv has joined #wayland
_whitelogger_ has joined #wayland
<RAOF>
Hm. Because I'm poking around in our relevant code, how is wp-fifo meant to interact with surfaces that span outputs with possibly-distinct refresh rates (and almost certainly not genlocked, even if they have the same refresh rate)?
<RAOF>
Or perhaps it doesn't really matter.
kts has quit [Ping timeout: 480 seconds]
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
mxz_ has joined #wayland
Guest9450 has quit [Ping timeout: 480 seconds]
abhimanyu1 has joined #wayland
sima has joined #wayland
coldfeet has joined #wayland
rv1sr has joined #wayland
rv1sr has quit []
rv1sr has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
garnacho has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
<daniels>
RAOF: same as pres-timing - pick one
tzimmermann has joined #wayland
_whitelogger_ has joined #wayland
chiku has joined #wayland
Sid127 has quit [Ping timeout: 480 seconds]
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
<MrCooper>
and same as frame events, yeah
<MrCooper>
mutter picks one with the highest refresh rate
adamtajti_ has joined #wayland
adamtajti has quit [Read error: Connection reset by peer]
leon-anavi has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
ade has joined #wayland
<ade>
guys, is there an alternative to wlroots with good documentation?
<ade>
cause wlroots seems to have like 0 docs
<ade>
or something simpler than wlroots
coldfeet has quit [Quit: leaving]
<MrCooper>
smithay maybe? Not sure (haven't used it myself)
<llyyr>
there's also simple compositors like dwl to more complex things like sway you can look at
<llyyr>
I don't believe any other library like it exists that has more documentation
<ade>
yea, reading a tons of source code is the only way :/
<emersion>
ade: what kind of documentation exactly are you missing?
<ade>
like, how to use it?
<emersion>
there is detailed API documentation (with missing pieces, linked above), high-level architecture (in docs/), and commented example compositor (tinywl)
<emersion>
the best place to start is probably tinywl
<ade>
how do i extend tinywl to support server-side decorations?
<ade>
bascially my end goal is to floating wm similar to mutter with server-side decorations
<ade>
*to write
<ade>
im trying to reinvent gnome with server-side decorations :p
rasterman has joined #wayland
<kennylevinsen>
xdg_decorations + you writing code to draw the type of decorations you want
<ade>
i've written a client which supports xdg_decorations, you define a global resource `xdg_decoration_manager` use it to get `get_toplevel_decoration`
<ade>
i imagine it's not the same for compositor side
davidre has joined #wayland
<davidre>
you implement it like any other protocol in the compositor
<davidre>
and then you need it to somehow drag decorations
<davidre>
*draw
<kennylevinsen>
but you need to do all the work of actually *making* the decorations
<ade>
i don't even know how to implement ANY protocol
<ade>
i should probably focus on that than server-side decorations
<ade>
also thanks again kenny
feaneron has joined #wayland
ade has left #wayland [ERC 5.6.1-git (IRC client for GNU Emacs 31.0.50)]
coldfeet has quit [Remote host closed the connection]
coldfeet has joined #wayland
lsd|2 has joined #wayland
coldfeet has quit [Remote host closed the connection]
adamtajti has joined #wayland
adamtajti_ has quit [Read error: Connection reset by peer]
kts has joined #wayland
<emersion>
jadahl: ah, you're familiar with varlink :)
<jadahl>
a bit
<jadahl>
not much though, just on a surface level :)
<jadahl>
(no pun intended :P)
<MrCooper>
casual puns are the best
<davidre>
What is the context of the issue?
<davidre>
Is it like "I have an app, and want to make sure it behaves correct when run in $compositor" when someone clicks on it?
<davidre>
testing the actual compositors?
<davidre>
Testing clicking on a button in an app?
<vyivel>
testing apps in every compositor kinda contradicts the idea of a standardized protocol
<vyivel>
it's for testing compositors themselves
Moprius has joined #wayland
paulk has quit [Read error: Connection reset by peer]
paulk has joined #wayland
Moprius has quit []
fmuellner has joined #wayland
Fxzxmic has joined #wayland
<kennylevinsen>
I can't help but think that a dedicated, automatable test compositor would be the solution for that...
kts has quit [Quit: Leaving]
<zamundaaa[m]>
The use case this came up with at XDC wasn't testing applications
<zamundaaa[m]>
But testing graphics drivers
<kennylevinsen>
hmm not sure I understand the involvement of window management then
_whitelogger_ has quit [Remote host closed the connection]
cmeissl[m] has joined #wayland
<cmeissl[m]>
I am currently trying to add support for wp-commit-timing-v1 in smithay. In set_timestamp the spec mentions "If a timestamp already exists on the surface, a timestamp_exists error is generated.".
<cmeissl[m]>
Just to make sure I get the expected commit cycle right. The timestamp is consumed on commit to generate the timer barrier for the commit. So only two calls to set_timestamp within a single commit would lead to this error?
<cmeissl[m]>
So a client, for example a video player, could commit multiple buffers in advance
_whitelogger_ has joined #wayland
<daniels>
yeah, though you need wp_fifo for the queue
<daniels>
ct lets you target a commit at a particular time, fifo lets you have n>1 commits pending
<zamundaaa[m]>
daniels: you don't need fifo for that
<emersion>
kennylevinsen: testing WSI in userspace drivers
<ManMower>
you don't need fifo for that, but fifo does do that. :)
<zamundaaa[m]>
Sure, but both syncobj and commit timing also allow you to queue multiple commits
<ManMower>
nod
abhimanyu1 has quit []
abhimanyu1 has joined #wayland
<cmeissl[m]>
<daniels> "yeah, though you need wp_fifo..." <- thanks! makes sense, I already have a mostly working impl of fifo.
<cmeissl[m]>
another thing I am not 100% sure I got right is what exactly the timestamp targets
<cmeissl[m]>
From reading the spec it sounds like it targets the estimated vblank timestamp. so every timestamp >= estimated vblank would be unblocked during latching the content for this retrace pahse
<ManMower>
sounds right to me
<cmeissl[m]>
thanks!
Brainium has joined #wayland
<cmeissl[m]>
<zamundaaa[m]> "Sure, but both syncobj and..." <- yeah, I was hoping to replace my obscure logic in a custom gstreamer sink with commit-timing
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
adamtajti has quit [Ping timeout: 480 seconds]
kabaka101 has joined #wayland
kts has joined #wayland
kabaka101 has quit [Ping timeout: 480 seconds]
kts has quit [Ping timeout: 480 seconds]
kabaka101 has joined #wayland
feaneron has quit [Quit: feaneron]
kabaka101 has quit [Ping timeout: 480 seconds]
feaneron has joined #wayland
Brainium has joined #wayland
feaneron has quit []
feaneron has joined #wayland
<MrCooper>
cmeissl[m]: timestamp <= estimated vblank timestamp, but yeah
<ManMower>
oh yeah, I read what I want to see instead of what was written. mrcooper is obviously correct.
<MrCooper>
some slop might be needed as well?
<cmeissl[m]>
<MrCooper> "cmeissl: timestamp <= estimated..." <- oh yeah, that's what I meant
<cmeissl[m]>
MrCooper: afaict the MR in mesa does that client side by subtracting 500us
<MrCooper>
right, let's keep that client-side
<ManMower>
yeah, client needs a little slop (500us is probably way too much)
<ManMower>
I think 10us is probably enough to deal with the hidden rounding of times in various components
<cmeissl[m]>
though iirc I have also seen some slop server side in jay?
<MrCooper>
that would be bad
<MrCooper>
slop must be handled either by the client or the compositor, not both
<cmeissl[m]>
yeah, doing it on both sides probably will mess up
<ManMower>
server side would violate the "not before" expectation
<MrCooper>
indeed
<cmeissl[m]>
can't find it, so maybe it was something else. But keeping it client side makes sense imo
iomari891 has joined #wayland
feaneron has quit [Quit: feaneron]
feaneron has joined #wayland
bindu has quit [Remote host closed the connection]
iomari891 has quit [Ping timeout: 480 seconds]
bindu has joined #wayland
kabaka101 has joined #wayland
tzimmermann has quit [Quit: Leaving]
Guest7968 is now known as FLHerne
kts has joined #wayland
Fxzxmic has quit [Remote host closed the connection]
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
mripard has quit [Quit: WeeChat 4.4.2]
kts has quit [Quit: Leaving]
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
kestrel has quit [Read error: Connection reset by peer]
kestrel has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
kabaka101 has quit [Ping timeout: 480 seconds]
abhimanyu1 has quit []
kestrel has quit [Read error: Connection reset by peer]
kestrel2 has joined #wayland
cyrinux has quit []
cyrinux has joined #wayland
leon-anavi has quit [Quit: Leaving]
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
kabaka101 has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
rasterman has joined #wayland
rasterman- has joined #wayland
rasterman has quit [Read error: Connection reset by peer]
rasterman- has quit []
rasterman has joined #wayland
Brainium has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
coldfeet has joined #wayland
_whitelogger_ has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
coldfeet has quit [Remote host closed the connection]
nerdopolis has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
Brainium has joined #wayland
_whitelogger_ has joined #wayland
rv1sr has quit []
_whitelogger_ has quit [Remote host closed the connection]
sima has quit [Ping timeout: 480 seconds]
Diamonditshe[m] has joined #wayland
lsd|2 has quit [Ping timeout: 480 seconds]
_whitelogger_ has joined #wayland
rasterman has quit [Read error: No route to host]
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
glennk has quit [Ping timeout: 480 seconds]
sima has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]