9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Arne Meyer <meyer.arne83@netcologne.de>
To: 9front@9front.org
Subject: Re: [9front] [patch] nusb/audio /dev entries fix v2
Date: Fri, 29 Dec 2023 18:34:41 +0100 (CET)	[thread overview]
Message-ID: <1214862762.3763294.1703871281266@comcenter.netcologne.de> (raw)
In-Reply-To: <AA087FE63A6B60E0A4B0145EC6665CE5@felloff.net>


> cinap_lenrek@felloff.net hat am 29.12.2023 18:10 CET geschrieben:

> one catch i can see is what happens when you dont have a built-in
> soundcard (#A) at all?
> 
> then you have no place to bind it to :(
> 
This is up to the user. Either use aux/stub and bind on that or use the script I attached which takes care of that.

> maybe a solution could be to have this handled by mixfs?
> 
I liked Sigrid's solution: There should be a new program that sits between the devices like #A, nusb and mixfs and supplies a file system compatible with a #A. Something like this:

provide a file system like #A
try to access #A and use that as the default audio device. If not, discard all data.
Listen on usbevent and add all found devices to a  list.
Change the default audio device via some ctl command.

  reply	other threads:[~2023-12-29 17:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29 16:00 Arne Meyer
2023-12-29 17:10 ` cinap_lenrek
2023-12-29 17:34   ` Arne Meyer [this message]
2023-12-29 21:54     ` cinap_lenrek
2023-12-30  1:53       ` hiro
2023-12-30 13:25       ` Arne Meyer
2024-01-06 16:04         ` Arne Meyer
2024-01-06 19:43           ` cinap_lenrek
2024-01-06 20:41             ` Arne Meyer
2024-01-06 19:58           ` cinap_lenrek

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=1214862762.3763294.1703871281266@comcenter.netcologne.de \
    --to=meyer.arne83@netcologne.de \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).