From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <000001c6ba85$b023c9f0$0201010a@lorna>
From: "John Boutland" <boutland@exemail.com.au>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
References: <30f1d4833c6b9a1c6070bf7ccd56456d@mail.gmx.net>
Subject: Re: [9fans] Still trying to acd going
Date: Tue,  8 Aug 2006 06:58:15 +1000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 9922ad58-ead1-11e9-9d60-3106f5b1d025

  Thanks to various of you for the helpful mail. Am going to try out a few 
things from you later today.

Sasha, Yes, I'm new to Plan9. I just realised he extent of the private name 
space yesterday, when discovering that certain things done in the rio window 
had not affected the acme window.

Re your question, I found acd in  /acme/bin/386

----- Original Message ----- 
From: "Sascha Retzki" <sretzki@gmx.de>
To: <9fans@cse.psu.edu>
Sent: Tuesday, August 08, 2006 4:04 AM
Subject: Re: [9fans] Still trying to acd going


>> 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
>
>
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.10.7/409 - Release Date: 4/08/2006
>