9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] got a new feature: learning of resources and switching among them
Date: Mon, 27 Jan 2003 19:54:19 +0100	[thread overview]
Message-ID: <200301271854.h0RIsJS23954@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Fri, 24 Jan 2003 23:47:20 +0100." <3E31C278.6060207@plan9.escet.urjc.es>

> > (*) Via some crockery I send sound bytes from the cpu
> > server via drawterm to the audio device of the sun.)
> 
> The plan is actually to write some drivers in Linux and change u9fs
> to let Linux export resources for us an also make it think that some
> of our little trees are /dev things. But don't hold your breath :-)

Currently, I'm using drawterm under solaris.
In solaris I just have two named pipes /tmp/dev/^(audio volume)
that in drawterm are visible as /mnt/term/tmp/dev/^(audio volume) .
In drawterm I then just ``bind -a /mnt/term/tmp/dev /dev''.
Under solaris I run two programs, one to copy sound bytes from
/tmp/dev/audio to /dev/audio, and another to interpret lines read
from /tmp/dev/volume to update the master volume via /dev/audioctl
(currently, I also need/use sox to put in the solaris audio header,
 because I somehow cannot get the copying program to do that right).
Of course, this only works in one direction
(audio output from plan9 to solaris).

I think I would prefer to see such functionality somehow integrated
in (or connected to) drawterm, in the same way as drawterm makes
other devices available to plan 9, over something that uses u9fs --
but maybe I'm overlooking something.
I assume, a problem of audio will be that a ``host driver''
probably will be pretty machine (o.s.) dependent.
Just some thoughts.

Axel.


  reply	other threads:[~2003-01-27 18:54 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 19:04 Fco.J.Ballesteros
2003-01-24 21:23 ` Axel Belinfante
2003-01-24 22:47   ` FJ Ballesteros
2003-01-27 18:54     ` Axel Belinfante [this message]
2003-01-27 20:16       ` Russ Cox
2003-01-27 20:29         ` Axel Belinfante
2003-01-28  3:33         ` Skip Tavakkolian
2003-01-29  8:27       ` Fco.J.Ballesteros
2003-01-29 13:32         ` [9fans] " Jim Choate
2003-01-29 14:29           ` [9fans] When will we start listening to Jackass Jim? Sam
2003-01-24 21:31 ` [9fans] got a new feature: learning of resources and switching among them Skip Tavakkolian
2003-01-24 21:33   ` Jack Johnson
2003-01-24 22:39     ` FJ Ballesteros
2003-01-24 22:35   ` FJ Ballesteros
2003-01-27  1:31 okamoto
2003-01-27  8:13 ` Fco.J.Ballesteros
2003-01-27 11:47   ` Boyd Roberts
2003-01-27 12:05     ` Fco.J.Ballesteros
2003-01-27 16:26     ` Jack Johnson
2003-01-27 16:53       ` Boyd Roberts
2003-01-27  8:42 okamoto
2003-02-01 17:40 Keith Nash
2003-02-01 17:46 ` Russ Cox
2003-02-01 19:50 ` David Presotto
2003-02-03  8:43 ` Fco.J.Ballesteros
2003-02-03  8:51   ` Scott Schwartz
2003-02-03  8:58     ` Fco.J.Ballesteros
2003-02-01 17:52 Keith Nash
2003-02-01 17:56 ` rob pike, esq.
2003-02-01 18:25   ` Dan Cross
2003-02-01 18:29     ` Russ Cox
2003-02-01 23:34       ` Dan Cross
2003-02-01 18:11 Keith Nash
2003-02-02  6:23 Andrew Simmons
2003-02-02  6:32 Andrew Simmons

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=200301271854.h0RIsJS23954@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --cc=9fans@cse.psu.edu \
    /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).