ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
gue45 has quit [Quit: Page closed]
iomari892 has quit [Ping timeout: 480 seconds]
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
nerdopolis has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
cool110 has quit [Remote host closed the connection]
cool110 has joined #wayland
kts has joined #wayland
<mooff>
could I ask some questions that'll help me with a potential project
<mooff>
does Wayland use a socket-compatible protocol, or more of a direct ABI?
<mooff>
how big is the surface area to hook something like GDK up to Wayland?
<mooff>
I'd like to hook GTK4/GDK up to an existing web Wayland compositor, called "greenfield", through a wasm interface
<RAOF>
mooff: It's not *entirely* clear what you're asking; particularly, GDK already *has* a Wayland backend.
sima has joined #wayland
<RAOF>
But for the question that is clear: yes, Wayland describes a (unix-)socket protocol; there's no* requirement that either end links to any particular library.
<RAOF>
The asterisk there is: if you want to use other libraries that talk Wayland - such as, say EGL or Vulkan - you'll need to be able to provide the types and the ABI that they use.
<mooff>
RAOF: i fear that connecting that Wayland backend to a JS Wayland compositor through the WASM bridge wil involve impl'ing a wide range of syscalls
<mooff>
i hoped someone Wayland-versed could allay or confirm those fears
<mooff>
or whether it can be as simple as hooking up a binary socket
<mooff>
i don't know much about the Wayland protocol
<RAOF>
If you want to connect a Wayland client to a compositor, that just requires that you provide a socket, yes.
<mooff>
ooh!
<RAOF>
Although that socket is going to need to be capable of passing file descriptors.
<mooff>
i didn't know there was an out-of-band way to send fds over POSIX sockets
<mooff>
is that the case? or do you just mean OS-defined file descriptor integers?
<RAOF>
man 7 unix, and SCM_RIGHTS.
<mooff>
(going through write() as normal data)
<mooff>
thanks..
<kennylevinsen>
mooff: it's a Unix domain socket which had the ability to send fds
<mooff>
that doesn't sound impossible to wire through Emscripten. better luck if it's already implemented, though.
<mooff>
alright that sounds much more doable than implementing a range of protocol-specific functions to cover a big C interface
<mooff>
that's exactly the help i was looking for, saves me lot of time trying to see through abstractions
i509vcb has quit [Quit: Connection closed for inactivity]
<mooff>
what's the minimum number of descriptors required to render a single client?
<mooff>
if 1, then it could be stubbed.
<dottedmag>
mooff: Unbounded.
<dottedmag>
Well, techncally the limit is ~2^32
<kennylevinsen>
well 1 for the display socket, but many fds will be transferred over it.
<emersion>
dottedmag: not even that, FDs can be closed and re-opened
<dottedmag>
emersion: Yeah, I meant ~2^32 active at any given time, due to protocol IDs.
rasterman has joined #wayland
<pq>
mooff, if I'm not totally confusing people here, you want to chat with zubzub.
kts has joined #wayland
<mooff>
thanks.
<mooff>
hey, zubzub (!)
iomari892 has joined #wayland
<mooff>
#gtk haven't balked at the idea, so maybe we can get this done.
iomari892 has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
rv1sr has joined #wayland
MrCooper has quit [Remote host closed the connection]
MrCooper has joined #wayland
rv1sr has quit []
rv1sr has joined #wayland
cmichael has joined #wayland
pochu has joined #wayland
kts has quit [Quit: Konversation terminated!]
___nick___ has joined #wayland
junaid has quit [Remote host closed the connection]
kts has joined #wayland
MrCooper has quit [Remote host closed the connection]
MrCooper has joined #wayland
kts has quit [Quit: Konversation terminated!]
fmuellner has joined #wayland
<mooff>
ah, zubzub, you are udevbe. checking your wares for first time since we emailed in 2021.
<DodoGTA>
Is it possible to use OpenGL pbuffers on Wayland?
<pq>
I do sense a slight confusion between pbuffer and pixmap EGL surfaces there, but using a FBO is a good idea anyway.
<pq>
OTOH, I did get pbuffer support added in Mesa for EGL Surfaceless by asking for it.
rasterman has quit [Quit: Gettin' stinky!]
* kennylevinsen
certainly had a degree of confusion there
<mooff>
i know "some" of these words..
<pq>
Pixmap is a some kind of winsys buffer, that the winsys can copy from or maybe draw into. Wayland has no draw operations at all, and it has no concept of such "pixmap" either.
<pq>
pbuffer OTOH is a purely client-side concept that needs nothing from the winsys, so it could exist on EGL Wayland platform if someone bothered to hook it up.
<kennylevinsen>
So we have neither, but the latter could exist...
<pq>
I don't know if someone hooked up pbuffers or not.
<pq>
The only thing pbuffers gives you AFAIK is the use of EGL SwapBuffers API.
<pq>
and an EGLSurface to play with
<pq>
it can be a workaround for cases where EGL implementation refuses to make a context current without any EGLSurface - that would be some proprietary EGL at most, not Mesa
<pq>
if you really have to have an EGLSurface off-screen, then pbuffer is fine, but otherwise I think it's useless nowadays.
<kennylevinsen>
aaah, fair enough. I do vaguely recall running into them inside firefox, but never dug into what the heck they were for. Thanks for explanation.
kts has joined #wayland
rv1sr has quit []
kts has quit [Quit: Konversation terminated!]
CME_ has joined #wayland
llyyrr has joined #wayland
CME has quit [Read error: Connection reset by peer]
andyrtr has quit [Read error: Connection reset by peer]