Displaying 4 results from an estimated 4 matches for "83a1".
Did you mean:
831
2018 Feb 05
0
[PATCH v3 1/2] drm/virtio: Add window server support
...sitor wrote to.
To be clear, I'm not against solving this via some form of restricted FD
passing in virtio-vsock, but Stefan (added to CC) thought that it would
be cleaner to do it all within virtio-gpu. This is the thread where it
was discussed:
https://lkml.kernel.org/r/<2d73a3e1-af70-83a1-0e84-98b5932ea20c at collabora.com>
Thanks,
Tomeu
2013 Jul 08
2
btrfs crashes
...62 found 475559
Jun 26 07:14:41 hsad-srv-03 kernel: [ 35.095814] parent transid verify
failed on 1750188515328 wanted 475562 found 475559
Jun 26 07:14:41 hsad-srv-03 kernel: [ 35.124511] btrfs: open_ctree failed
Jun 26 07:14:41 hsad-srv-03 kernel: [ 35.133282] device fsid
526356ed-9708-40c2-83a1-82f3dbc8b72f devid 2 transid 476583 /dev/sde
--------------------------------------------------------------------------------------------------------------------------------
when I want to mount the btrfs: mount: wrong fs type, bad option, bad
superblock on /dev/sde,
missing codepage or hel...
2018 Feb 05
2
[PATCH v3 1/2] drm/virtio: Add window server support
Hi,
> > Why not use virtio-vsock to run the wayland protocol? I don't like
> > the idea to duplicate something with very simliar functionality in
> > virtio-gpu.
>
> The reason for abandoning that approach was the type of objects that
> could be shared via virtio-vsock would be extremely limited. Besides
> that being potentially confusing to users, it would mean
2018 Feb 05
2
[PATCH v3 1/2] drm/virtio: Add window server support
Hi,
> > Why not use virtio-vsock to run the wayland protocol? I don't like
> > the idea to duplicate something with very simliar functionality in
> > virtio-gpu.
>
> The reason for abandoning that approach was the type of objects that
> could be shared via virtio-vsock would be extremely limited. Besides
> that being potentially confusing to users, it would mean