[nas] isolate input/output?

[Jon Trulson]

On Wed, 14 Mar 2007, Erik Auerswald wrote:

> Hi,
>
> On Tue, Mar 13, 2007 at 10:19:41AM -0600, Jon Trulson wrote:
>> On Tue, 13 Mar 2007, Paul Fox wrote:
>>
>>> logical sense.  as long as there's a config file mechanism to
>>> override, then i'd say "yes".  i'd both change the defaults in the
>>> code, and change the default config file to match.  and i'd put a
>>> note in the code somewhere noting that we're not sure why its
>>> necessary to be able to open readwrite -- just so the lucky
>>> volunteer who decides it's time to add direct alsa support
>>> doesn't feel they absolutely have to implement it.
>>
>>         To be honest, I cannot think of a reason why it would be
>>         'neccessary' to open read/write, unless the driver was just
>>         stupid.
>>
>>         I'm happy to make this change if there are no objections.
>
> With my hardware there is no difference if the output is opened rw or
> ro, nasd works full-duplex. I'd say go ahead and make the change.
>

         Excellent, change committed and patch attached FYI.


-- 
Jon Trulson
mailto:jon at radscan.com 
#include <std/disclaimer.h>
"No Kill I" -Horta
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nas-readwrite-default.patch
Type: text/x-diff
Size: 4964 bytes
Desc: 
URL: <http://radscan.com/pipermail/nas/attachments/20070313/47144ee2/attachment.patch>