ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
mblenc has quit [Read error: Connection reset by peer]
mblenc1 has quit [Ping timeout: 480 seconds]
tzimmermann has joined #wayland
tzimmermann has quit [Remote host closed the connection]
tzimmermann has joined #wayland
i509vcb has quit [Quit: Connection closed for inactivity]
leon-anavi has joined #wayland
glennk has joined #wayland
lanodan has quit [Quit: config test]
lanodan has joined #wayland
mvlad has joined #wayland
rasterman has joined #wayland
qyliss has joined #wayland
mblenc has joined #wayland
mblenc1 has joined #wayland
mblenc has quit [Read error: Connection reset by peer]
kts has quit [Ping timeout: 480 seconds]
garnacho has joined #wayland
mblenc has joined #wayland
mblenc1 has quit [Read error: Connection reset by peer]
Fxzxmic has quit [Remote host closed the connection]
Fxzxmic has joined #wayland
Fxzxmic has quit [Remote host closed the connection]
Fxzxmic has joined #wayland
Fxzxmic has quit [Read error: Connection reset by peer]
Fxzxmic has joined #wayland
Consolatis has quit [Ping timeout: 480 seconds]
Consolatis has joined #wayland
Consolatis_ has joined #wayland
Consolatis is now known as Guest6257
Consolatis_ is now known as Consolatis
Guest6257 has quit [Ping timeout: 480 seconds]
cptaffe has quit [Ping timeout: 480 seconds]
Fxzxmic has quit [Read error: Connection reset by peer]
cptaffe has joined #wayland
Fxzxmic has joined #wayland
fmuellner has joined #wayland
Consolatis_ has joined #wayland
Consolatis is now known as Guest6258
Consolatis_ is now known as Consolatis
kts has joined #wayland
Guest6258 has quit [Ping timeout: 480 seconds]
cmichael has joined #wayland
<pq>
JoshuaAshton, leasing overlay planes would also be horrible for update timings, either causing unexpected random full refresh cycle delays or maybe just everything tears if the hardware can tear. Or both.
<pq>
I suppose it would also be accompanied by random EBUSY errors from atomic commits.
<pq>
It'd also make atomic test commits unreliable, but I guess that applies to KMS leasing in general.
nerdopolis has joined #wayland
<daniels>
pq: unless I’m very wrong, test commits aren’t subject to EBUSY
gallo_ is now known as gallo
Moprius has joined #wayland
<pq>
daniels, no, but they become unreliable.
<pq>
someone else can change the device KMS state between test and real commit
<emersion>
test something, then something changes on the lease, then test again, and results are different
<emersion>
yea
nerdopolis has quit [Ping timeout: 480 seconds]
<daniels>
ah yeah, iswym
Fxzxmic has quit [Read error: Connection reset by peer]
Fxzxmic has joined #wayland
nerdopolis has joined #wayland
<JoshuaAshton>
pq: Why would it be horrible for update timings?
<JoshuaAshton>
on hw where there are 4 planes per-head, I don't see the problem
<JoshuaAshton>
if the planes are shared across multiple heads then yes... it's a problem then
Fxzxmic has quit [Quit: Konversation exit!]
<zamundaaa[m]>
I think you're all talking about different things
<zamundaaa[m]>
JoshuaAshton: you mean leasing overlay planes *with* crtc and connector, right?
<pq>
I've been talking about leasing *only* an overlay plane for a CRTC that is driven by the lessor.
<pq>
You would have two independent processes both updating planes on the same CRTC, and that causes all the problems I mentioned.
<emersion>
ah, right, that sounds pretty dangerous and broken
<pq>
JoshuaAshton, which scenario did you mean?
<emersion>
i was thinking leasing more planes alongside a CRTC+connector
<JoshuaAshton>
Yes, I was thinking overlay with crtc and connector
Fxzxmic has joined #wayland
<JoshuaAshton>
and obviously a primary
<emersion>
(not so obvious, because it's possible to only light up an overlay on some hw :P )
<emersion>
(without a primary)
<pq>
ok, nothing strange with that.
<pq>
I've heard that embedded product developers like to drive each plane of one CRTC from different independent processes, so I jumped to conclusions. We got requests to make that work with e.g. Weston.
<pq>
as in "Weston's primary plane needs to be able to see through to the underlay planes we drive with video player"
<JoshuaAshton>
i see
<pq>
*KMS video players
<daniels>
you could lease entire outputs (connector+crtc+(n*plane)) to fullscreen clients but I'm not sure what benefit it would bring
rasterman has quit [Quit: Gettin' stinky!]
<emersion>
you're no longer able to interact with the mouse with such clients, so less game addiction as a benefit?
<JoshuaAshton>
daniels: Gamescope has a branch where I tried to make that work but something falls over kernel side on AMDGPU at least since a recent-ish kernel
<JoshuaAshton>
I think I want to try doing a thing where we re-make the scene graph on wayland commit/commit done and push it up with subsurfaces instead of compositing ourselves at some point soon
<pq>
subsurfaces is a good idea
<pq>
well, again depending on what actually have in your scenegraph
<JoshuaAshton>
yeah, really for our side it would be the same as our existing logic for VRR but just pushing up the scene graph with subsurfaces instead
<JoshuaAshton>
some cases we'd still need to composite for eg. FSR though
<JoshuaAshton>
zamundaaa[m]: Would KDE handle mixed HDR and SDR with subsurfaces right now?
<pq>
subsurfaces are good for buffers that are potentially scanout-able
nerdopolis has quit [Ping timeout: 480 seconds]
<zamundaaa[m]>
JoshuaAshton: yeah
<JoshuaAshton>
and would it also take advantage of overlay planes there if available?
<zamundaaa[m]>
Not yet, no
<JoshuaAshton>
I guess it cant without color mgmt drm kernel side stuff
<pq>
How does VRR vs. FSR make a difference to sub-surface usage? What's FSR?
<JoshuaAshton>
For VRR I mean like, us committing up the scene graph to the compositor would be very similar logic to what we do for VRR on the DRM side
<JoshuaAshton>
FSR is just an upscaling method
<pq>
oh, nothing to compare to fixed-rate refreesh, ok
<JoshuaAshton>
ye
Fxzxmic has quit [Read error: Connection reset by peer]
Fxzxmic has joined #wayland
chris- has joined #wayland
leon-anavi has quit [Quit: Leaving]
wv has joined #wayland
chris_ has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
Moprius has quit [Quit: bye]
<wv>
Hello, I seem to have something odd on my imx53/freedreno platform. I'm on 1920x1080, but it seems only 1919x1079 is written to the screen. Although all logs mention 1920x1080. But if I take a screenshot using weston-screenshooter, it appears the bottem row (1080) and right column (1920) are just black. Even with the normal weston background of the desktopshell
rasterman has quit []
rasterman has joined #wayland
<wv>
And to extend, when I run my cog/wpewebkit instance on top, with a size of 1920x1080, with a box inside of 1 pixel on the outer edges, also the bottom and right are just black
<daniels>
wv: please start weston with --debug and pastebin the output of 'weston-debug scene-graph' whilst it's running somewhere
<wv>
daniels, and as reference, this shows the issue -> https://pasteboard.co/FjLNo7CEEY0q.png It's a snip of the screenshot. As you can see, the lower pixelrow is just black, as is the right pixelcolumn
Company has quit [Read error: Connection reset by peer]
<wv>
and it's just the default background of desktopshell. Nothing fancy at this moment
Company has joined #wayland
nerdopolis has joined #wayland
rgallaispou has quit [Read error: Connection reset by peer]
rgallaispou has joined #wayland
Consolatis has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
Consolatis has joined #wayland
Fxzxmic has quit [Remote host closed the connection]
Fxzxmic has quit [Remote host closed the connection]
Fxzxmic has joined #wayland
Consolatis has quit [Ping timeout: 480 seconds]
lsd|2 has joined #wayland
Consolatis has joined #wayland
garnacho has left #wayland [#wayland]
rasterman has quit [Ping timeout: 480 seconds]
garnacho has joined #wayland
rasterman has joined #wayland
i509vcb has joined #wayland
lsd|2 has quit [Quit: test, disconnecting]
quantun` has joined #wayland
<quantun`>
I have a herd of KVM virtual machines and need remote desktop access to them. I knw this has been blocked in Wayland. What do you guys do?
kts has quit [Ping timeout: 480 seconds]
lsd|2 has joined #wayland
lsd|2 has quit []
lsd|2 has joined #wayland
fossdd_ has joined #wayland
<kennylevinsen>
What? Wayland does not block remote desktop access
<pq>
quantun`, I suppose the usual answers are RDP and VNC for full desktop, and waypipe for individual apps.
<pq>
assuming there are not virtual display hardware for the virtual machines, and a viewer for that
<quantun`>
kennylevinsen: It sure used to. I haven't been able to use it as a result.
<daniels>
it works
<quantun`>
pq: VNC has always been jittery and weird, like putting many copies of the screen bertically. Haven't tried RDP
<daniels>
if you're using GNOME, there's built-in support for VNC/RDP; if you're using KDE then I believe they also have something similar; if you're using stuff built on wlroots then there's wayvnc; if you're using Weston it has built-in VNC and RDP backends
<daniels>
if those aren't working then please file bug reports with the appropriate projects
<quantun`>
KDE here. I'll look into it when I have time.
fossdd has quit [Ping timeout: 480 seconds]
<d_ed[m]>
KDE's server is unimaginative named "krdp". It might not be shipped by default, as it's a relatively new venture
<quantun`>
Thx d_ed[m].
AnuthaDev has joined #wayland
neniagh has joined #wayland
neniagh_ has quit [Ping timeout: 480 seconds]
AnuthaDev has quit [Quit: AnuthaDev]
quantun` has quit [Quit: Konversation terminated!]
Fxzxmic has quit [Read error: Connection reset by peer]
Fxzxmic has joined #wayland
Fxzxmic has quit [Read error: Connection reset by peer]
Fxzxmic has joined #wayland
Fxzxmic has quit [Read error: Connection reset by peer]
Fxzxmic has joined #wayland
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
JEEB has quit [Quit: ブーン～]
agd5f_ has quit []
agd5f has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
AnuthaDev has joined #wayland
mblenc has quit [Ping timeout: 480 seconds]
JEEB has joined #wayland
cmichael_ has joined #wayland
Fxzxmic has quit [Quit: Konversation exit!]
cmichael has quit [Ping timeout: 480 seconds]
flom84 has joined #wayland
cmichael_ has quit []
flom84 has quit [Remote host closed the connection]
flom84 has joined #wayland
saumon has quit [Remote host closed the connection]
Company has quit [Quit: Leaving]
saumon has joined #wayland
tent4051 has quit [Ping timeout: 480 seconds]
mort_6 is now known as mort_
mblenc has joined #wayland
tzimmermann has quit [Quit: Leaving]
mblenc1 has joined #wayland
lsd|2 has quit [Read error: Connection reset by peer]
Moprius has joined #wayland
mblenc has quit [Ping timeout: 480 seconds]
Moprius has quit []
Moprius has joined #wayland
Moprius has quit []
lsd|2 has joined #wayland
tent405 has joined #wayland
flom84 has quit [Ping timeout: 480 seconds]
rv1sr has quit []
mblenc has joined #wayland
AnuthaDev has quit []
mblenc1 has quit [Ping timeout: 480 seconds]
mblenc has quit [Ping timeout: 480 seconds]
mblenc has joined #wayland
mblenc1 has joined #wayland
mblenc has quit [Read error: Connection reset by peer]
mblenc1 has quit [Ping timeout: 480 seconds]
mvlad has quit [Remote host closed the connection]
mblenc has joined #wayland
mblenc1 has joined #wayland
mblenc has quit [Ping timeout: 480 seconds]
mblenc1 has quit [Ping timeout: 480 seconds]
mblenc has joined #wayland
mblenc has quit [Ping timeout: 480 seconds]
mblenc has joined #wayland
sima has quit [Ping timeout: 480 seconds]
mblenc has quit [Ping timeout: 480 seconds]
mblenc has joined #wayland
mblenc1 has joined #wayland
lsd|2 has left #wayland [No boundaries on the net!]