Re: writeable /dev/pad0?

[Malcolm Herbert <mjch%mjch.net@localhost>]

On Thu, Apr 21, 2011 at 08:55:13PM +0200, Magnus Eriksson wrote:
|On Thu, 21 Apr 2011, Malcolm Herbert wrote:
|>as I was hoping to pump test audio data into /dev/pad0 and then use
|>esound on the associated /dev/audio0 to simulate what would happen on
|>the production host ... unfortunately in 5.1 it appears that /dev/pad0
|>is read-only ...
|
|It could be that I am misunderstanding what you plan to do here, but
|AFAIK pad backed audio devices are output only, so stuffing data into
|the /dev/pad side won't work.

yes, that's what I found although I hadn't realised that when I was
reading up on it ...

|(the "path" is application1 -> /dev/audioN -> pad -> /dev/padN ->
|application2; it's similar to tty/pty pairs)
|
|But I see that it apparently lists both "playback" and "capture" in my
|dmesg. Hmm. For compatibility reasons I guess?

on the face of it the ability to pump data into a pad device still      
appears that it would be useful ...                                     

As it happens, I ended up finding another sound card of almost the same
type as the original one I had, so for me this is less of an issue now
as I have one in both prod and dev hosts to play with.

Regards,
Malcolm

-- 
Malcolm Herbert                                This brain intentionally
mjch%mjch.net@localhost                                                left 
blank