13 Nov
2008
13 Nov
'08
8:25 p.m.
On Fri, 2008-11-14 at 01:08 +0100, Fons Adriaensen wrote:
Now if someone can point me to some existing docs
that
explain how I can e.g. set the sample clock source on a
RME MADI card in less than ten lines of C code (knowing
the parameter names, ranges, etc - no need to find them
out dynamically, I can read them asound.state) then I'll
eat my hat. It shouldn't be difficult. On some competing
systems all it takes is one ioctl().
i don't want to defend the lamentable state of the ALSA docs, but this
last shot was a bit cheap Fons. the idea behind the ALSA control API was
that equivalent controls on different cards would be controlled in the
same way. sure, OSS provides ioctl (fd,
OSS_THIS_ONE_DOES_MADI_CLOCK_SOURCE, &int) but move that code to any
other device and it breaks entirely. ALSA has its own major points of
API weakness, but this particular one was at least conceived with a
noble goal in mind.
btw, if i was the quality dept, this use of doxygen would not have
passed the "make me happy" test.