From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <30f1d4833c6b9a1c6070bf7ccd56456d@mail.gmx.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Still trying to acd going
From: "Sascha Retzki" <sretzki@gmx.de>
Date: Mon,  7 Aug 2006 20:04:37 +0200
In-Reply-To: <44D6D53A.8030706@exemail.com.au>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 98b44dd6-ead1-11e9-9d60-3106f5b1d025

> I mailed a couple of days ago on this subject but have not found an 
> answer yet. It would be vey nice to get this very neat
> bit of software going. 

I've got an interesting question for you, where can I find 'acd' :) ? I have no manpage, no source-code, no binary with that name, nor a grep acd /n/sources/contrib/*/INDEX found something.

>Following a reply from Gabi Diaz(?) who suggested 
> that the Ensoniq es1371 was not supported, I dug up an oldish SB16 card 
> but have still had no success. 

SB16 works, but AC97-cards (the ensoniq-chip is ac97) don't. Likely to change because I am an audiophile and will start to work on drivers some day. ;)

> From earlier postings, I've tried 
> audio0=type=sb16 port=0x220 (as well as audio1, type=ess1688 and various 
> other ports) in plan9.ini, and have run bind '#A' /dev. 

I have this one in my plan9.ini. I typed those values in from memory, I was 'passivly' using computers when ISA was in, so I never really got how to find these numbers out without trial-and-error methods:

audio0=type=sb16 port=0x220 irq=7 dma=5

(it is the only ISA-card on a two ISA-slot board, if that matters (probably doesn't)).


Note two things: 

1.) After this is in your plan9.ini, the kernel/driver will know what to do. You will still have to bind the file-system provided by the audio-driver into your namespace - that is bind -a '#A' /dev ...

2.) You are new to Plan9? Did you yet notice that there are private namespaces? That means if you open a window, and bind #A into your namespace, just that client (and childs) will see /dev/audio.. if you look in window2, you will not see /dev/audio in there until you bind it there, too (or, you put the bind 'up one layer', so bind #A before rio starts. Or, in acme, execute "Local bind -a '#A' /dev" (see Local in acme(1)).




But I am pretty sure gdiaz is right that 'acd', however where it is ;), as a cd-player (it apperently is), will just command the ATAPI-drive to start/stop playing. I do not know if you can change the volume from software, maybe check for that. 


Mfg, Sascha