<puck>
qyliss: so "virtwl-dmabuf" is the one where the dmabuf that the client gives the compositor is passed into the host, "virtwl" means that sommelier copies the buffer's contents into a special virtwl buffer
<puck>
wl_shm is the protocol used to get shared memory to work, wl_compositor is the protocol to get surfaces (which you can see) from a buffer, and xdg_wm_base shrug
<puck>
i think you need to have a wayland compositor listening on the host side too maybe?
<qyliss>
I'm just forwarding my sway socket (I think?)
<puck>
hmm, right
<qyliss>
crosvm run --wayland-sock=/run/user/1000/wayland-0 ...
<puck>
yeah, it seems sommelier has its own wl_compositor bit
<qyliss>
Should sommelier be putting something into XDG_RUNTIME_DIR?
<qyliss>
It should be, right?
<puck>
yeah, it is, $XDG_RUNTIME_DIR/wayland-0
<qyliss>
If I run sommelier ls -l $XDG_RUNTIME_DIR there's nothing there
<qyliss>
So I guess that's the problem I need to look at
<puck>
try stracing it maybe
<qyliss>
good plan
<puck>
also it should set $WAYLAND_DISPLAY inside the runprog thing
<puck>
no worries lol, this is going pretty swimmingly, i think i almost have a patch (most of it is just renaming zxdg_shell_v6 to xdg_shell, and a abit of logic to pass through the version numbers properly)
<puck>
i think i have it working
<puck>
need to properly test it tho
<puck>
oh, it needs a virtwl device, lol
<qyliss>
puck: I can send you my test thing
<puck>
it's compiled on uhura again, i can send you a nixpkgs patch, that might be easier?
<qyliss>
Would probably be useful for you to be able to test anyway
<puck>
i honestly suspect nothing is broken
<puck>
except maybe negotiation
<qyliss>
Okay, then. Send it to devel@spectrum-os.org an CC me?
<puck>
there are no functional changes mainly between v1 and v2, and most of it is passthrough
<puck>
actually yeah, if you can send me the testing setup that'd be nice
<qyliss>
On it
<qyliss>
puck: start-vm.nix in the crosvm-demo branch
<puck>
hrmm
<puck>
why does crosvm have its *own* sommelier
<qyliss>
Does it?
<puck>
crosvm is trying to compile sommelier itself
<qyliss>
???
<puck>
oh it isn't
<puck>
i was misreading
<qyliss>
Was gonna say -- if it was it wouldn't have worked because it wouldn't have the patch it needs
<puck>
here we go
<qyliss>
is it working?
<puck>
i had a few mistakes in the sommelier build lmao
<puck>
i am currently building the crosvm kernel
<qyliss>
that's on uhura, surely?
<puck>
yes
<puck>
or well
<puck>
compiling it on, not yet there?
<qyliss>
I should have compiled it already
<qyliss>
Did you have to change something?
<puck>
no? idk
<qyliss>
whatever
<qyliss>
maybe i did
<puck>
anyways it's compiling currently
<puck>
bbiab, need to eat
<puck>
qyliss: "failed to fork and create pty (No such file or directory)"
<qyliss>
puck: well that's a good sign
<puck>
yeah, i'm trying again
<qyliss>
That might be it working!
<puck>
yeah, it negotiated xdg_wm_base
<qyliss>
I probably haven't done whatever I need to do to make ptys work
<puck>
yeah, you need some nodes and/or udev
<qyliss>
Let me send you the hello-wayland package
<puck>
yeah, trying hello-wayland maybe would give you better result (also probably remove the --shm-driver=none thing)
<qyliss>
if I can get to the point where I have a cat picture that's good enough for today
<qyliss>
I don't see that?
<qyliss>
IT WORKS
<qyliss>
PUCK
<puck>
oooh
<puck>
hrmm
<qyliss>
(with hello-wayland)
<puck>
so what if sommelier crashed because it closed during initalization
<puck>
... probably
<puck>
anyways \o/
<qyliss>
what does /dev/shm do btw?
<puck>
weston seems to support unstable xdg-shell v6
<puck>
qyliss: probably just used as a place to create files for shared memory
<puck>
anyways \o/
<puck>
yes that's two \o/s
<qyliss>
:D
<qyliss>
happy
<qyliss>
you're probably sick of being told you're a genius at this point, right?
<Shell>
qyliss: it is used for POSIX shared memory I think. It used to be the bane of getting Postgres to run under a container.
<puck>
qyliss: ftr i just compared the zxdg-shell v6 protocol with xdg-shell and used a lot of s///
<puck>
i wonder if the chromium window manager just doesn't support xdg-shell
<Shell>
Probably, lol
<qyliss>
How does it run applications then?
<puck>
it supports zxdg-shell_v6 most probaby
<puck>
and a bunch of apps will support both this and xdg_shell, but i think xdg-shell is the one most people want to support (it's more recent than v6)
<qyliss>
right
<qyliss>
so you just couldn't run weston-terminal with their wm, you reckon?