[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hurd-bug
Subject:    Sound translator (was: Full-time developer available)
From:       Olaf Buddenhagen <olafbuddenhagen () gmx ! net>
Date:       2015-09-18 23:06:01
Message-ID: 20150918230558.GC6291 () alien ! local
[Download RAW message or body]

Hi,

On Thu, Sep 17, 2015 at 12:25:21PM -0300, Diego Nieto Cid wrote:

> Another alternative, I was considering while going back home from work, is
> to design this in layers. As in the following graph:
> 
> +--------------------------------+
> |         Applications           |
> +--------------------------------+
>                                     ----> read, write, ioctls...whatever is
> standard
> +------------+ +------------+
> | /dev/audio | | /dev/mixer | ...
> +------------+ +------------+
>                                     ----> might be some custom protocol if
> required
> +--------------------------------+
> |        driver translator       |
> |--------------------------------|
> |             rump               |
> +--------------------------------+
> +--------------------------------+
> |            hardware            |
> +--------------------------------+
> 
> In that way there are several sound related translators separating the
> concerns while the hardwarde is still accessed by a single translator
> avoiding the conflicts Robert mentioned.

This could work -- but I'm not sure it would be very useful? Is there
any actual logic that could be split out into the audio and mixer
translators? My suspicion is that they would rather just be
straightforward wrappers -- in which case it seems an unnecessary
complication...

-antrik-

[prev in list] [next in list] [prev in thread] [next in thread]