9front - general discussion about 9front
 help / color / mirror / Atom feed
From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] [PATCH] Fix nusb/audio /dev entries
Date: Thu, 21 Dec 2023 00:10:44 +0100	[thread overview]
Message-ID: <C3E191AE5BF9934F377F8AE5C2A2AE67@wopr.sciops.net> (raw)
In-Reply-To: <1235011938.3556150.1703098437964@comcenter.netcologne.de>

On Wed Dec 20 19:54:05 +0100 2023, meyer.arne83@netcologne.de wrote:
> Hello qwx,
> 
> > qwx@sciops.net hat am 20.12.2023 17:44 CET geschrieben:
> > 
> > Thanks for the patch.  One could argue against the previous behavior
> > -- what is your use case?
> 
> I have a thin client with hda audio that is not quite working with the 9front driver. So
> I use a cheap usb sound card to get audio. In this case I could probably do
> 'unmount #A' in a namespace file and have it work as intended?

There's a few ways in which you can achieve this, but yeah I imagine
that something like `unmount '#A' /dev` at the right place is enough
for your purposes (eg.  /cfg/$sysname/termrc, $home/lib/profile,
etc.).  You can also disable the card in plan9.ini.  Of course, best
would be to fix the driver, but that's work.


> > What do you think, would that work in your case?
> 
> If I plug in a usb device I expect it to become the default device. Maybe mixfs
> can do some clever stuff here?

Maybe, but I'm not sure how that would work, and it would be a bunch
of additional code, when in reality the simplest thing you could do is
to unmount #A and #u and remount them in the opposite order, or in
your case, just unmount #A.  After the discussions I've had, I'm
leaning towards having the user configure this themselves (usually
this would be a one time setup), leaving a note about it in nusb(4).
So far, the people who have participated in the discussion have all
had somewhat different opinions about this, so imho it's not really
clear what the expected behavior would be for most.

Cheers,
qwx

  reply	other threads:[~2023-12-20 23:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20 11:23 Arne Meyer
2023-12-20 16:44 ` qwx
2023-12-20 17:19   ` Kurt H Maier
2023-12-20 17:47     ` qwx
2023-12-20 17:51       ` Kurt H Maier
2023-12-20 18:11         ` qwx
2023-12-20 18:53   ` Arne Meyer
2023-12-20 23:10     ` qwx [this message]
2023-12-21  2:47     ` Sigrid Solveig Haflínudóttir
2023-12-21  7:53       ` hiro
2023-12-21 20:12         ` Arne Meyer
2023-12-21 20:48           ` hiro

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=C3E191AE5BF9934F377F8AE5C2A2AE67@wopr.sciops.net \
    --to=qwx@sciops.net \
    --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).