9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] [drawterm] Wayland support and misc patches
Date: Fri, 15 Oct 2021 02:22:22 +0000	[thread overview]
Message-ID: <7FEB9E7D-5E25-49FD-A29D-3086A061C8B3@stanleylieber.com> (raw)
In-Reply-To: <edc88a07-5108-ab05-458b-12710966c8ed@posixcafe.org>

On October 14, 2021 1:59:54 AM UTC, Jacob Moody <moody@mail.posixcafe.org> wrote:
>I've written a wayland graphical backend for drawterm and have been dogfooding it for
>a little bit now. I think most of the larger bugs have been worked out of it.
>There is also a patch for adding pipewire support for devaudio.
>For both of these there is a patch for adding a CONF=linux target
>While working on these I found that there is code in libc/ that expects
>to be compiled with -DPTHREAD to avoid resorting to spin locks.
>I think we might want to add -DPTHREAD to the unix target CFLAGS.
>However adding the define on my machine caused gcc to get confused about
>the ordering of the members for kern/devmouse.c:/^Cursorinfo\tarrow/
>There is a patch that specifies the members, which seemed to fix the issue. But I am sure what is causing this.
>Also I am not sure why there was a sleep within the kern/term.c:/^resizeproc/ loop, but I noticed the delay
>when working on the wayland backend. There is a patch for removing that sleep.
>Not sure which, if any, of these are desirable to have upstream but wanted to offer them up.
don't have a machine to test with yet but this will come in handy around december.



  reply	other threads:[~2021-10-15  2:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14  1:59 Jacob Moody
2021-10-15  2:22 ` Stanley Lieber [this message]
2021-10-15 11:20 ` cinap_lenrek
2021-10-17  3:49 ` Stephen Gregoratto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7FEB9E7D-5E25-49FD-A29D-3086A061C8B3@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).