From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id B64FB26B6A for ; Sun, 4 Aug 2024 21:27:15 +0200 (CEST) Received: from srv1.howhill.co.uk ([85.95.36.12]) by 9front; Sun Aug 4 15:26:14 -0400 2024 Received: from [192.168.1.223] (Ellychnia-corrusca.howhill.co.uk [192.168.1.223]) (Authenticated sender: willow) by srv1.howhill.co.uk (Postfix) with ESMTPSA id 449F03A04E03 for <9front@9front.org>; Sun, 4 Aug 2024 20:26:11 +0100 (BST) DKIM-Filter: OpenDKIM Filter v2.11.0 srv1.howhill.co.uk 449F03A04E03 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=howhill.com; s=default; t=1722799571; bh=DNM1JyGaXF67le0jGVnxd4AIDkXhHDEGQm2672gXtqU=; h=Date:To:From:Subject:From; b=NXD+QGnwR2e8BkTDD82Yh31jLTTFdX0Nx9I9xLpodaL3R4abaEZrIciLANSsFUZOI SzJN4l1aiDNCMRuIr6YTI0dlrJg4yHSyfkYmGithMNeTqFEeYa/ntAXHQ993s2ZayS 4BNlD0Jd7wJMvCwSrlY/GcL6RvVib4emIQJsl4Mx7FvQIqRHIBYfPp6raPkeoKIDT0 hz1dFbSBid0VRoPMnvh5yOdelsZbk33rRQzZYJTaOX2ZNmMXGLHXjyqx4gcAW9ls5e wEnGwXRLqDBCzr/4LEvA03sZp9yx4yeEjYMYlYAbal/jpsNDLWS1lIEZAPD+RY03ps eccvJorrCOzlw== Message-ID: Date: Sun, 4 Aug 2024 20:26:10 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-GB To: 9front@9front.org From: Willow Liquorice Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-2.71 / 20.00]; BAYES_HAM(-2.94)[99.76%]; SUBJECT_ENDS_QUESTION(1.00)[]; GENERIC_REPUTATION(-0.68)[-0.67770026433643]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1] X-Rspamd-Queue-Id: 449F03A04E03 X-Rspamd-Server: srv1.howhill.co.uk List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: extensible self-healing SOAP scripting plugin-based backend Subject: [9front] Thoughts on Wayland? Reply-To: 9front@9front.org Precedence: bulk Hello again 9front, (Warning: long email is long) I've been leafing through the Wayland protocol, comparing it to rio and /dev/draw. To me, a system that could speak Wayland sounds much more compatible with the wider software ecosystem. Has there been much thought put into Wayland in 9front? I'd poke around in the list archives, but I haven't figured out how to 9P on my Linux machine yet. Here are my thoughts: 1. The Wayland compositor and clients talk to each other over a Unix domain socket. I'm guessing Plan 9 doesn't have those (and doesn't want them) as there's nothing in sys/man on the subject. Could pipe(3) do the trick? 2. Shared memory (where wl_buffers are stored) is achieved by passing a file descriptor from the client to the compositor, which the compositor mmaps as needed. If I understand correctly, that already sounds pretty plan9-y, though I'm not sure whether you could then treat the file *like* shared memory under 9front. Again, couldn't find any references to "mmap" in the manuals, so I guess there's no direct analogue. Could you achieve the same (or similar) effect with a ramfs? 3. protocol/wayland.xml is apparently used to generate all of the function prototypes you need to speak Wayland. If the underlying components (shared memory and a domain socket lookalike) work, making a Wayland library for Plan 9 (Way 9?) *might* boil down to a paint-by-numbers exercise. Wayland's been around a while, so maybe none of these observations are new. I don't know! I'm a novice. Regards, Willow