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
ybogdano is now known as Guest2113
Guest2113 has quit [Remote host closed the connection]
<wlb>
weston/main: Pekka Paalanen * backend-drm: set connector max bpc https://gitlab.freedesktop.org/wayland/weston/commit/d24adbbe258a include/libweston/backend-drm.h libweston/backend-drm/drm-internal.h libweston/backend-drm/drm.c libweston/backend-drm/kms.c
<daniels>
ManMower, mvlad, pq: so, uh, what exactly is the 'XWAYLAND' window state?
<ManMower>
seems like override redirect
<ManMower>
an "ignore me" for the shell
<daniels>
yeah, makes sense
<ManMower>
no it doesn't, it's horribly named. ;)
<daniels>
haha, agree
<ManMower>
at first I thought it was some transitionary state or something
<daniels>
would be good to change that to OVERRIDE_REDIRECT or CLIENT_POSITIONED or something
<daniels>
since yeah, it looks like it's O-R + tooltip + dnd + etc
<ManMower>
agreed. might do that in the not too distant future
<daniels>
<3
<ManMower>
since I seem to stomping around in those parts
shankaru has quit [Quit: Leaving.]
<pq>
I literally just now learnt about enum weston_desktop_xwayland_surface_state if that's what you're talking about.
<daniels>
pq: yeah, that one
<pq>
I don't tend to wander in libweston-desktop.
<ManMower>
it's one of those neighbourhoods you have to cross with purpose. act like you belong, have a mean glare. else you might get stabbed.
<daniels>
either that or napalm
<zubzub>
when I rewrote weston's Xwayland code so it could run in the browser, I also wondered wth that was but figured you guys knew what you were doing
<zubzub>
and now I read things like idklol
<ManMower>
we always know what we're doing it. we just don't know why we're doing it.
<zubzub>
ah like a giant ant colony
devilhorns has quit []
<pq>
I wonder who reviewed it, but I'm too scared to look, and who cares anyway.
<zubzub>
"who the hell approved this sh*t.. oh it was me"
<ManMower>
the number of times I go down that rabbit hole only to find out I reviewed it is a strong disincentive to doing that kind of forensics
<ManMower>
zubzub: ^5
<pq>
ManMower, think of the bright side: the you now is clearly smarter than the old you.
<zubzub>
I guess that's still better then the occasional "who the hell wrote this sh*t... oh it was me"
<pq>
..or at least different
<ManMower>
definitely different
<pq>
me, I tend to get the opposite: "I wrote that code, but I bet I never thought about *this* corner case I just found out. Oh, I did. How clever."
<ManMower>
"and the two other corner cases I hadn't thought about just now... wait, I used to be smarter."
ayaka_ has joined #wayland
<pq>
that
<ayaka_>
When we have a compositor and opengl es driver is running in aarch64, do I just need a aarch32 libweston to make a aarch32 wayland client work ?
<emersion>
no
<ayaka_>
if I want to use opengl es in an aarch32 client, do I need a 32bits opengl driver library ?
<emersion>
a 64-bit compositor should work with a 32-bit client
<emersion>
and the other way around, too
<pq>
ayaka_, no. All libraries loaded by one process must be of the same architecture.
<emersion>
yeah, the opengl impl is loaded as a dynamic library, so needs to be of the same bit-ness
<ayaka_>
pq, I know that, I think a client in wayland need the libwayland_client to communicate the compositor ?
<pq>
ayaka_, yes, and the OpenGL drivers are libraries loaded by the client, too.
<ayaka_>
emersion, btw, I am using the powervr for wayland, which we thought powervr doesn't have any linux platform
rv1sr has joined #wayland
<emersion>
oh, i don't want to know about powervr's proprietary stuff
Company has quit [Read error: Connection reset by peer]
<ayaka_>
I just want to show there would be a proprietary driver, although its frontend is mesa
<ayaka_>
the current pvr driver would offer a mesa backend, I just wondering whether I could not compiling the mesa twice if there is a wayland client library offering those gl symbols
<pq>
wayland client library has nothing to do with OpenGL at all
fmuellner has quit [Remote host closed the connection]
<pq>
If you have a 32-bit app, you need 32-bit libraries for it. If you have 64-bit, then you need 64-bit. There's no way around that, that I know and would be relevant here.
rv1sr has quit []
<pq>
Wayland does not carry OpenGL commands, so Wayland does not work around the need to have both 32-bit and 64-bit builds of OpenGL drivers, if you intend to run both kinds of apps or compositors.
fmuellner has joined #wayland
shankaru has joined #wayland
neonking_ has quit []
neonking has joined #wayland
Company has joined #wayland
Seirdy has quit []
Seirdy has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
cyberpear has quit [Quit: Connection closed for inactivity]
zebrag has joined #wayland
Seirdy has quit []
shankaru has quit [Quit: Leaving.]
slattann has quit []
droshan has joined #wayland
droshan has quit [Read error: Connection reset by peer]
cool110 has quit [Remote host closed the connection]
cool110 has joined #wayland
tzimmermann has quit [Quit: Leaving]
cool110 has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
cool110 has joined #wayland
cool110 has quit [Remote host closed the connection]
cool110 has joined #wayland
<emersion>
pq: for the second time i've been asked how would one specify whether YCbCr limited or full range is used for a buffer with the color management ext?
<ayaka_>
pq, I see thank you
<ayaka_>
and emersion thank you
ayaka_ has quit [Quit: Leaving]
systwi_ has joined #wayland
systwi has quit [Ping timeout: 480 seconds]
systwi_ has quit []
systwi has joined #wayland
mvlad has quit [Remote host closed the connection]
dcz has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
bluebugs has quit [Quit: Leaving]
AlephOne_ has left #wayland [#wayland]
hardening has quit [Ping timeout: 480 seconds]
cool110_ has joined #wayland
cool110 has quit [Ping timeout: 480 seconds]
cool110_ has quit [Remote host closed the connection]